If you just want to act as a bridge, I don't believe you want to run radvd
. Just build a bridge configuration between the two interfaces. I believe your requirements don't fit with bridging. If the bridge is correctly configured, traffic will flow cleanly between the sides. If you want an IP address on the host doing the bridging, it appears that it needs to be configured on the bridge not one of the interfaces.
The providers I have worked, provide one connection on a dedicated /64 network and at least a /64 for the internal network. You may want to clarify what is being provided. If they do provide a an address range for the internal network, pick a /64 and configure radvd
on the internal network accordingly. This configuration will not require a bridge.
IPv6 does not provide the protection afforded by private IP addresses ranges and Network Address Translation. Consider your firewall requirements.
EDIT: I broke the bridge on my OpenWRT (Linxu) router deliberately, but by default the LAN and WiFi were bridged. My current configuration has the wireless and LAN bridged, and I run my IPv6 router using a tunnel from a system on the LAN. Wireless clients pick up addresses and route appropriately.
From the comments it appears you have gotten a block of /64 networks for your own use. Configure radvd
to announce one on the WiFi network. This is the way IPv6 is indended to be be configured. If you have configured your network to allow IPv6 forwarding, this should work.
I split my network and had different /64 blocks for WiFi and LAN. I documented my experience providing IPv6 DNS resolver data with radvd. There is an example radvd
config in my article on implementing IPv6 6to4 on OpenWRT.
/50
if I want. But for this case I want to extend the connection without changing anything in upstream routers./64
to, for example,/60
in router advertisments, stations stop auto-configuring their IPv6 address...