Classic Setup Flow (Static IP)
This documentation is still being edited and may differ from the actual version.
The key idea: buying a static IP does not mean your existing MAP-E / DS-Lite path must stop being used.
You can keep ordinary LAN clients on Flet'H IPoE, while handing the static public IPv4 address only to a DMZ-side device such as a firewall, business router, or server. Flet’H static IP passthrough is designed for this.
Recommended layout: normal exit + static IP DMZ
Section titled “Recommended layout: normal exit + static IP DMZ”Internet / NTT NGN | v ONU | vOpenWrt WAN -> wan6 | +-- Flet'H IPoE | | | +-- ordinary LAN / Wi-Fi | PCs, phones, TVs, IoT | continue using MAP-E / DS-Lite | +-- Flet'H Static IP (Passthrough) | +-- dedicated DMZ port or VLAN firewall / business router / server uses the static public IPv4This keeps normal home devices away from the public static IPv4, while giving the fixed address to the equipment that actually needs it.
What passthrough solves
Section titled “What passthrough solves”Many static IP services still use an IPv6 / IPIP6 tunnel underneath. The usual approach is to make OpenWrt own the public IPv4 address and handle all port forwarding and firewalling there.
Sometimes that is not what you want. You may want the public IPv4 to be used directly by a DMZ-side firewall, business router, server, or virtualization host.
Flet'H Static IP (Passthrough) solves this by letting OpenWrt terminate the IPv6 tunnel while a DMZ-side device uses the static public IPv4 address.
When to use normal static IP
Section titled “When to use normal static IP”Choose Flet'H Static IP when OpenWrt itself should own the public IPv4 address.
OpenWrt WAN -> Flet'H Static IP tunnelOpenWrt owns the static public IPv4OpenWrt LAN -> ordinary LAN clientsPrepare:
BR AddressPublic IPv4 AddressIPv6 Interface ID, if required by the ISPTunnel Link, usuallywan6ファイアウォール設定: leave it unspecified; do not assign any firewall zone
IPIP6H firewall warning:
Flet'H Static IPusesIPIP6H. Do not assign its new IPIP6H interface to any firewall zone, especially thewanzone. Doing so creates conflicting firewall rules, so the interface may appear connected while IPv4 communication fails completely. This warning applies to theFlet'H Static IPinterface; the upstreamwan6interface should remain in thewanzone.
If a zone is already assigned, open Network -> Interfaces -> Flet'H Static IP -> Edit -> Firewall Settings, remove the interface from every zone, and leave it unspecified. Save and apply, then restart the static IP interface.
When to use static IP passthrough
Section titled “When to use static IP passthrough”Choose Flet'H Static IP (Passthrough) when a DMZ-side device should use the public IPv4 address.
OpenWrt WAN -> Flet'H Static IP (Passthrough)OpenWrt DMZ -> firewall / business router / serverDMZ-side device uses the static public IPv4Use a dedicated port or VLAN for the DMZ when possible.
Setup order
Section titled “Setup order”1. Make normal Flet’H IPoE work first
Section titled “1. Make normal Flet’H IPoE work first”Follow the classic setup flow until wan6 has IPv6 and ordinary Flet'H IPoE works.
2. Prepare a DMZ port or VLAN
Section titled “2. Prepare a DMZ port or VLAN”Use a port or VLAN that only connects to the DMZ-side device that should use the static public IPv4 address.
3. Create the static IP passthrough interface
Section titled “3. Create the static IP passthrough interface”In Network -> Interfaces, create a new interface and choose Flet'H Static IP (Passthrough).
Main fields:
BR AddressClient IPv4 AddressClient IPv4 CIDR prefix lengthClient Gateway IPv4 AddressIPv6 Interface ID, if required by the ISPTunnel Link: usuallywan6- Passthrough device: the DMZ port or VLAN
4. Configure the DMZ-side device with static IPv4
Section titled “4. Configure the DMZ-side device with static IPv4”IP address: Client IPv4 AddressPrefix length: Client IPv4 CIDR prefix lengthGateway: Client Gateway IPv4 AddressDNS: ISP DNS, public DNS, or internal DNSOrdinary LAN / Wi-Fi should continue using Flet'H IPoE. Do not point the whole home LAN at the DMZ device unless you intentionally want all traffic to pass through that DMZ-side firewall.