Native IPv6 from German T-Online by pppoe but - what a bummer - dynamic….
recentently german isp t-online had upgraded their new connections to dualstack. Reason enough to try out pfsense 2.1 RC.
The pppoe Interface was set up like a charme, with the pfsense box alone (ssh'ing) ipv6 works nearly out of the box.
But now I wanted to get the /64 Subnet "routed" to some clients - what shouldn't be so difficult if the network would not change after
a reconnect… but it does!
So, how could I configure the DHCPv6 Daemon to cope with a dynamic IPv6 Prefix?
Any howto or tutorial I've seen its "fix" prefix.... not a dynamic one.
Any hints or suggestions are really appreciated!
Thanks a lot!
Great work so far! :-)
razzfazz last edited by
You'll probably want to look into "prefix delegation" (DHCP-PD).
But the Problem is, I have to assign a "Static" IPv6 Address to the local Network - but since the prefix is dynamic assigned and subneted by pfsense,
I don't know it in advance - or do I miss simething?
razzfazz last edited by
You'll want to set the LAN to "track interface" instead of a static IPv6 address.
if I do set the LAN interface to "track VDSLTRUNK" (thats my pppoe Interface) I cannot configure a DHCPv6 Server….:
The DHCPv6 Server can only be enabled on interfaces configured with static IP addresses. Only interfaces configured with a static IP will be shown.
If I try to configure a DHCPv6 Relay ( which might work….) I have the mentioned Problem....:
Destination server This is the IPv6 address of the server to which DHCPv6 requests are relayed. You can enter multiple server IPv6 addresses, separated by commas. Select "Proxy requests to DHCPv6 server on WAN subnet" to relay DHCPv6 packets to the server that was used on the WAN interface.
Which I don't have, because it's dynamic…
athurdent last edited by
It's been a while since I experimented with that, but IIRC you just need to configure the LAN interface to track the PPPoE interface. DHCPv6 / RADVD should start automatically, no need to configure them.
you're right… radvd stats up automatically.... I didn't notice that.
But there is now another Problem - a big one and a not so big one...
The big one: All IPv6 traffic is routeted absolutely unfiltered to the IPv6 clients rendering the firewall useless….
And the not so big one… everytime my IPv6 Address changes, the (linux) clients get an new (good) additional (bad) IP, so after the fourth change the Interface under debian linux looks like this....
inet6-Adresse: 200x:x0x1:3sce:64:exx0:fxfx:fe05:ef24/64 Gültigkeitsbereich:Global
inet6-Adresse: 200x:xxx5:as7e:64:ex40:f2xf:fe05:ef24/64 Gültigkeitsbereich:Global
inet6-Adresse: 200x:x0x1:3sce:0:eax0:f2xf:fe05:ef24/64 Gültigkeitsbereich:Global
inet6-Adresse: 200x:xbx5:ac82:64:ex40:xxxx:xe05:ef24/64 Gültigkeitsbereich:Global
- the locallink + loopback + ipv4 Addresses...:-)
But that might be a debian issue.....