editor
471
edits
OpenWRT routers: Difference between revisions
Mention NAT64
(Configuring the local network - devices, interfaces, zones) |
(Mention NAT64) |
||
| (3 intermediate revisions by the same user not shown) | |||
|
option ip6ifaceid 'eui64'
option ip6assign '64'
The ''list ip6class wan_6'' line causes the lan to use the delegated prefix from wan_6. ''option ip6ifaceid eui64'' makes the local IPv6 address on the lan use the 64 bits derived from the MAC address as the suffix (you might choose to use ''::1'' instead). ''option ip6assign 64'' defines the netmask associated with the prefix delegation.
== Multiple routed IPv6 /64 blocks ==
OpenWrt fully supports IPv6, as well as IPv4 and dual stacks to enable the mix of both protocols.
The easiest approach is to use prefix delegation from the WAN to provide the network address. This is achieved by configuration of the ''wan'' interface to obtain the IPv6 address automatically, and to delegate IPv6 addresses downstream.
Then on the ''lan'' interface configure the IPv6 prefix filter to ''wan_6'' and set the IPv6 assignment length to 64. There is a choice of the suffix to append to the prefix - popular choices would be ''::1'' (to use that fixed value), or ''eui64'' (to use an address based on the MAC address).
There is the possibility of running a NAT64 server on OpenWrt, so the local network can use only IPv6 but hosts on it can still reach IPv4 hosts on the Internet.
= Advanced configuration of the local network =
You can do some quite advanced configurations of the local network. But first you have to understand OpenWrt's naming convention.
If you want guests to have access to the LAN zone, then just add the new ''lan2'' interface to the list of interfaces covered by the ''LAN'' zone, job done.
If you want guests to have no access to the LAN zone, then you need to create a new zone (let's go wild and call it ''GUEST''), make it cover just the ''lan2'' interface and define its relationships to the other existing zones. We want to have the same access to the WAN zone, so we configure that relationship like the ''LAN'' zone. But we want the ''LAN'' and ''GUEST'' zones to be separate, so we don't define any relationship between them.
| |||