@“x”#297727Yes, I had that problem too at first. Fortunately, I still have my IB in storage and after a bit of back and forth with Swisscom support, I was able to activate ipv6 (there are probably limitations in connection with the Internet Booster, which was sent to me without asking).
With the IB on Anschluss, ipv6 is active and works as expected. But unfortunately not with the pfsense 😕
@hed no, the booster was never used by me. I normally never have the IB in use and without it it doesn’t do anything. But I had to have Swisscom Support remove it completely from my connection config. Before that, it didn’t even work with the IB.
What happened next in this matter?
Today I also tried to activate IPv6 on my PFsense with Zyxel Bridge. But unfortunately without success.
I also found an old IB standard, updated the firmware and successfully activated IPv6 there and saw the DualStack config as active.
On the Pfsense I tried the WAN interface on DHCPv6 client with various other options. However without success.
Request only an IPv6 prefix = enabled
DHCPv6 Prefix Delegation size = 58
Send IPv6 prefix hint = disable
Do not wait for a RA = enabled
| Apr 5 21:33:13 | dhcp6c | 72448 | script “/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh” terminated |
| Apr 5 21:33:13 | dhcp6c | 73166 | dhcp6c renew, no change - bypassing update on igb0 |
| Apr 5 21:33:13 | dhcp6c | 72448 | executes /var/etc/dhcp6c_wan_dhcp6withoutra_script.sh |
| Apr 5 21:33:13 | dhcp6c | 72448 | status code for PD-0: success |
| Apr 5 21:33:13 | dhcp6c | 72448 | update a prefix 2a02:1210:2a8a:3600::/56 pltime=7200, vltime=21600 |
| Apr 5 21:33:13 | dhcp6c | 72448 | update an IA: PD-0 |
| Apr 5 21:33:13 | dhcp6c | 72448 | dhcp6c Received INFO |
| Apr 5 21:33:13 | dhcp6c | 72448 | status code: success |
| Apr 5 21:33:13 | dhcp6c | 72448 | get DHCP option status code, len 9 |
| Apr 5 21:33:13 | dhcp6c | 72448 | IA_PD prefix: 2a02:1210:2a8a:3600::/56 pltime=7200 vltime=21600 |
| Apr 5 21:33:13 | dhcp6c | 72448 | get DHCP option IA_PD prefix, len 25 |
| Apr 5 21:33:13 | dhcp6c | 72448 | IA_PD: ID=0, T1=3600, T2=5760 |
| Apr 5 21:33:13 | dhcp6c | 72448 | get DHCP option IA_PD, len 54 |
| Apr 5 21:33:13 | dhcp6c | 72448 | DUID: fe:80:00:00:00:00:00:00:02:00:5e:ff:fe:00:01:2c |
| Apr 5 21:33:13 | dhcp6c | 72448 | get DHCP option server ID, len 16 |
| Apr 5 21:33:13 | dhcp6c | 72448 | DUID: 00:01:00:01:2b:c0:58:9b:00:0d:b9:42:69:a8 |
| Apr 5 21:33:13 | dhcp6c | 72448 | get DHCP option client ID, len 14 |
| Apr 5 21:33:13 | dhcp6c | 72448 | receive reply from fe80::200:5eff:fe00:12c%igb0 on igb0 |
| Apr 5 21:33:13 | dhcp6c | 72448 | send renew to ff02::1:2%igb0 |
Ich hab es hinbekommen…
WAN Interface:
IPv6 Configuration Type = DHCP6
Request only an IPv6 prefix = yes
DHCPv6 Prefix Delegation size = 62
Send IPv6 prefix hint = no
Do not wait for a RA = yes
DHCPv6 Server & RA
DHCPv6 Server
DHCPv6 Server = Enable DHCPv6 server on interface LAN
Subnet = Delegated Prefix: WAN/0 (2a02:1210:2a8b:f300::/62)
Range =::ffff:ffff:ffff:0000 -::ffff:ffff:ffff:ffff
Router Advertisements
Router Mode = Assisted
Firewall Rules
LAN Interface: IPv6 Any Proto, Source LAN Net, Destination any, allow
Hello @macaholic
Have you been able to check tohil’s feedback and could it help you find a solution? If this is the case, we would be happy if you mark the comment as a solution or share further details.
I have now struggled a bit to ensure that Android devices also receive IPv6 delegation via SLAAC.
RA (and therefore SLAAC) not working after updating to 2.5.0 | Netgate Forum
It has to be like this:
WAN interface
IPv6 Configuration Type = DHCP6
Request only an IPv6 prefix = checked
DHCPv6 Prefix Delegation size = 56
LAN interface
IPv6 Configuration Type = Track Interface
DHCPv6 Server & RA
DHCPv6 server
Range:::0000:0000:0000:0000 -::ffff:ffff:ffff:ffff
Prefix Delegation Size= 64
Provide DNS servers to DHCPv6 clients =yes
Router advertisements
Router mode = assisted
Provide DNS configuration via radvd = checked
The following pfsense system patch is also important (for 2.6.0 and 23.01)
https://redmine.pfsense.org/issues/13851
otherwise access to the DNS resolver for IPv6 will not work.
Hello tohil
I’ve put the topic on hold for some time now (enjoy the summer). Does the configuration work stably for you? I’ve set everything up as you described, but I don’t have a connection via IPv6. Get a prefix and can also assign addresses to clients but it seems like no routes are created for IPv6. Ping always results in 100% loss, whether from my network to the outside or from outside to me. (Corresponding firewall rules have been created)
I mean, I tested it before the summer and it worked so far, but now nothing at all.
hi macaholic
It’s good that you enjoyed the summer and didn’t waste your time with IPv6 🙂
Yes, the setup works very well and stable for me. All IPv6-capable devices (Windows Devices, Android, iOS, etc.) receive IPv6 addresses and also use them for transport. pfBlockerNG also works for IPv6.
What kind of device are you testing with?
First and foremost, it is important that you see the IPv6 address on your interfaces:
The internal interfaces should then be able to issue IPv6 leases via DHCPv6 and RA. Please note that Android, for example, does not support DHCPv6, only RA/SLAAC.
Greetings Tohil
