IPv6 Connection Problem for VDSL (but not ADSL, same ISP)
-
Hi!
I have an ADSL and a VDSL connection configured for German Telekom according to
https://moerbst.wordpress.com/2016/07/31/ipv6mit-pfsense-an-dsl-der-telekom/
It's basically a PPPoE/DHCP6 setup for the WAN side and a Static IPv4/Track Interface/RA Unmanaged for the LAN side. The boxes run on pfSense 2.3.4 p1.
While the ADSL connection works smoothly, I have trouble with the VDSL connection. IPv6 is enabled for the Modem "ALLNET ALL-BM100VDSL2 / VDSL2 Bridge Modem mit Vectoring"
It seems as if everything is working (i.e. at least an IPv6 address is received), except that unbound fails with messages like
Oct 31 11:01:47 php-fpm 63307 /rc.newwanipv6: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1509444107] unbound[70712:0] error: bind: address already in use [1509444107] unbound[70712:0] fatal error: could not open ports'
Additionally dpinger writes messages like
Oct 31 11:01:57 dpinger send_interval 1000ms loss_interval 2000ms time_period 100000ms report_interval 0ms data_len 0 alert_interval 2000ms latency_alarm 500ms loss_alarm 20% dest_addr 23.215.122.69 bind_addr 87.140.145.55 identifier "DTAG " Oct 31 11:01:52 dpinger send_interval 1000ms loss_interval 2000ms time_period 100000ms report_interval 0ms data_len 0 alert_interval 2000ms latency_alarm 500ms loss_alarm 20% dest_addr 23.215.122.69 bind_addr 87.140.145.55 identifier "DTAG " Oct 31 11:01:48 dpinger send_interval 1000ms loss_interval 2000ms time_period 100000ms report_interval 0ms data_len 0 alert_interval 2000ms latency_alarm 500ms loss_alarm 20% dest_addr 23.215.122.69 bind_addr 87.140.145.55 identifier "DTAG " Oct 31 11:01:18 dpinger send_interval 1000ms loss_interval 2000ms time_period 100000ms report_interval 0ms data_len 0 alert_interval 2000ms latency_alarm 500ms loss_alarm 20% dest_addr 23.215.122.69 bind_addr 87.140.145.55 identifier "DTAG " Oct 31 11:01:13 dpinger send_interval 1000ms loss_interval 2000ms time_period 100000ms report_interval 0ms data_len 0 alert_interval 2000ms latency_alarm 500ms loss_alarm 20% dest_addr 23.215.122.69 bind_addr 87.140.145.55 identifier "DTAG " Oct 31 10:00:14 dpinger send_interval 1000ms loss_interval 2000ms time_period 100000ms report_interval 0ms data_len 0 alert_interval 2000ms latency_alarm 500ms loss_alarm 20% dest_addr 23.215.122.69 bind_addr 87.140.145.55 identifier "DTAG ```" every 5 seconds, which is usually only the case when the WAN-connection changes or gets interrupted. The WAN connection itself works only intermittently. If I remove the IPv6 connection on the WAN side, everything works as expected, except that there is not IPv6. Does someone know what could cause this behavior?
-
https://forum.pfsense.org/index.php?topic=138417.msg757461#msg757461
-
Was soll davon von Bedeutung sein? Die moerbst-Seite kenne ich und die Anleitung funktioniert teilweise, aber VDSL verhält sich irgendwie anders.
-
It seems that rc.newwanipv6 gets called every 5 seconds. I don't know why the IP gets renewed.
Oct 31 15:38:31 php-fpm 38641 /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:a:127f:8e03:82ee:73ff:fec5:5e47) (interface: wan) (real interface: pppoe1). Oct 31 15:38:31 php-fpm 38641 /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe1. Oct 31 15:38:30 check_reload_status Reloading filter Oct 31 15:38:30 php-fpm 7258 /rc.newwanipv6: Removing static route for monitor 23.215.128.67 and adding a new route through 62.156.242.5 Oct 31 15:38:30 php-fpm 7258 /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a500:8c:15f6%pppoe1 Oct 31 15:38:30 php-fpm 7258 /rc.newwanipv6: ROUTING: setting default route to 62.156.242.5 Oct 31 15:38:27 php-fpm 7258 /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:a:127f:8e03:82ee:73ff:fec5:5e47) (interface: wan) (real interface: pppoe1). Oct 31 15:38:27 php-fpm 7258 /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe1. Oct 31 15:38:25 check_reload_status Reloading filter Oct 31 15:38:25 php-fpm 5847 /rc.newwanipv6: Removing static route for monitor 23.215.128.67 and adding a new route through 62.156.242.5 Oct 31 15:38:25 php-fpm 5847 /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a500:8c:15f6%pppoe1 Oct 31 15:38:25 php-fpm 5847 /rc.newwanipv6: ROUTING: setting default route to 62.156.242.5 Oct 31 15:38:21 php-fpm 5847 /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:a:127f:8e03:82ee:73ff:fec5:5e47) (interface: wan) (real interface: pppoe1). Oct 31 15:38:21 php-fpm 5847 /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe1. Oct 31 15:38:20 check_reload_status Reloading filter
-
Prior to 2.4.* there were issues with newwanipv6 getting called repeatedly, this has been resolved in 2.4.*.
As the fixes for this also required modifications to the dhcp6c client the changes have not been back-ported to earlier versions of pfSense.
The only solution is to update to 2.4.1. If you are prepared to go with the dev version, then 2.4.2 is working very well for me.
-
Thank you.