Return to Answer

If you are intending to configure an AAAA record, then configure that address as a static IP address on the host that requires a static IP address. DHCP can be used to serve static IP addresses, but it is a poor second choice solution.

OpenWRT has used dnsmasq for DHCP (v4 and v6) and DNS. dnsmasq can be configured to supply a static IPv6 address if the client using DHCPv6. The latest version of OpenWRT appears to use odhcpd for some if not all DHCP services.

Use the firewall to open ports from the Internet to the server. (The address you assigned will be its address from the Internet as well as your LAN.) You should be able to connect locally to the server without opening any ports on the firewall.

odhcpd does support static IP address by adding a host section to its configuration. I haven't my router to the lastest OpenWRT version, so I am using dnsmasq which can also provide RA and DHCPv6 services. You should be able to specify the static IP address at the bottom of the DHCP and DNS configuration page.

IPv6 should not require NAT, although they may be the destination behind a Proxy or VIP (Virtual IP). Build a /64 from the /56 delegated to you, and assign an address from that /64 to your web server. This is the address you should use. Your web server will need a Dynamic IP client that can update your DNS whenever it's address change.

Address in the network block with fc00:/8 should not be used for communications with the internet. These are intended for use as unique local addresses, similar to the IPv4 private addresses.

If you are intending to configure an AAAA record, then configure that address as a static IP address on the host that requires a static IP address. DHCP can be used to serve static IP addresses, but it is a poor second choice solution.

OpenWRT has used dnsmasq for DHCP (v4 and v6) and DNS. dnsmasq can be configured to supply a static IPv6 address if the client using DHCPv6. It might be appropriate use these as a destination for a proxy or VIP (Virtual IP. The latest version of OpenWRT appears to use odhcpd for some if not all DHCP services.

Use the firewall to open ports from the Internet to the server. (The address you assigned will be its address from the Internet as well as your LAN.) You should be able to connect locally to the server without opening any ports on the firewall.

odhcpd does support static IP address by adding a host section to its configuration. I haven't my router to the lastest OpenWRT version, so I am using dnsmasq which can also provide RA and DHCPv6 services. You should be able to specify the static IP address at the bottom of the DHCP and DNS configuration page.

IPv6 should not require NAT, although they may be the destination behind a Proxy or VIP (Virtual IP). Build a /64 from the /56 delegated to you, and assign an address from that /64 to your web server. This is the address you should use. Your web server will need a Dynamic IP client that can update your DNS whenever it's address change. Until you get DHCP static IP addresses working, the MAC based address will be your stable address.

Address in the network block with fc00:/8 should not be used for communications with the internet. These are intended for use as unique local addresses, similar to the IPv4 private addresses.

You may need to develop your own dynamic IP address scripts. On the router you will need to update the firewall when the /56 changes, and may need to make some other changes. On the web server, you will need to update DNS, and possibly assign a new static IP address. (I think assignment on IP address prefix change may be simpler than DHCP static IPv6 address assignment.)

If you are intending to configure an AAAA record, then configure that address as a static IP address on the host that requires a static IP address. DHCP can be used to serve static IP addresses, but it is a poor second choice solution.

OpenWRT has used dnsmasq for DHCP (v4 and v6) and DNS. dnsmasq can be configured to supply a static IPv6 address if the client using DHCPv6. The latest version of OpenWRT appears to use odhcpd for some if not all DHCP services.

Use the firewall to open ports from the Internet to the server. (The address you assigned will be its address from the Internet as well as your LAN.) You should be able to connect locally to the server without opening any ports on the firewall.

odhcpd does support static IP address by adding a host section to its configuration. I haven't my router to the lastest OpenWRT version, so I am using dnsmasq which can also provide RA and DHCPv6 services. You should be able to specify the static IP address at the bottom of the DHCP and DNS configuration page.

If you are intending to configure an AAAA record, then configure that address as a static IP address on the host that requires a static IP address. DHCP can be used to serve static IP addresses, but it is a poor second choice solution.

OpenWRT has used dnsmasq for DHCP (v4 and v6) and DNS. dnsmasq can be configured to supply a static IPv6 address if the client using DHCPv6. The latest version of OpenWRT appears to use odhcpd for some if not all DHCP services.

Use the firewall to open ports from the Internet to the server. (The address you assigned will be its address from the Internet as well as your LAN.) You should be able to connect locally to the server without opening any ports on the firewall.

odhcpd does support static IP address by adding a host section to its configuration. I haven't my router to the lastest OpenWRT version, so I am using dnsmasq which can also provide RA and DHCPv6 services. You should be able to specify the static IP address at the bottom of the DHCP and DNS configuration page.

IPv6 should not require NAT, although they may be the destination behind a Proxy or VIP (Virtual IP). Build a /64 from the /56 delegated to you, and assign an address from that /64 to your web server. This is the address you should use. Your web server will need a Dynamic IP client that can update your DNS whenever it's address change.

Address in the network block with fc00:/8 should not be used for communications with the internet. These are intended for use as unique local addresses, similar to the IPv4 private addresses.

If you are intending to configure an AAAA record, then configure that address as a static IP address. It is best to do that on the server. OpenWRT uses dnsmasq for DHCP and DNS. dnsmasq can be configured to supply a static IPv6 address if the client using DHCPv6.

Use the firewall to open ports from the Internet to the server. (The address you assigned will be its address from the Internet as well as your LAN.) You should be able to connect locally to the server without opening any ports on the firewall.

odhcpd does support static IP address by adding a host section to its configuration. I haven't my router to the lastest OpenWRT version, so I am using dnsmasq which can also provide RA and DHCPv6 services. You should be able to specify the static IP address at the bottom of the DHCP and DNS configuration page.

If you are intending to configure an AAAA record, then configure that address as a static IP address on the host that requires a static IP address. DHCP can be used to serve static IP addresses, but it is a poor second choice solution.

OpenWRT has used dnsmasq for DHCP (v4 and v6) and DNS. dnsmasq can be configured to supply a static IPv6 address if the client using DHCPv6. The latest version of OpenWRT appears to use odhcpd for some if not all DHCP services.

Use the firewall to open ports from the Internet to the server. (The address you assigned will be its address from the Internet as well as your LAN.) You should be able to connect locally to the server without opening any ports on the firewall.

odhcpd does support static IP address by adding a host section to its configuration. I haven't my router to the lastest OpenWRT version, so I am using dnsmasq which can also provide RA and DHCPv6 services. You should be able to specify the static IP address at the bottom of the DHCP and DNS configuration page.