Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Native IPv6 on PPPoE

    IPv6
    1
    2
    2.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      fab1330
      last edited by

      Hello,

      My ISP propose an IPv4 and IPv6 (/56) dual-stack. The connexion is established by pfSense in PPPoE (on my WAN interface) to my ISP.

      I receive my IPv6 configuration via my FAI in DHCP6.

      I would like to link the computers which are connected to my LAN to IPv6 websites.
      I configured my LAN interface in "Track Interface IPv6" to the WAN interface.

      Here is my problem : from pfSense I can ping some IPv6 websites but it isn't possible from my LAN. The global IPv6 adress is attributed to the lo0 loopback interface and not to my LAN interface.

      However sometimes the LAN interface receive this global IPv6 adress and it works! Unfortunately it's unfrequent. If it works, I reboot pfSense and then the global adress can't reach the LAN interface anymore.

      In the log, I have some abnormal items :

      Dec 28 15:12:26	php: rc.resolv_conf_generate: The command '/sbin/route change -host -inet6 2a00:xxxx:xxxx:c05::66 fe80::230:88ff:fe04:67e7' returned exit code '1', the output was 'route: writing to routing socket: No such process route: writing to routing socket: Network is unreachable change host 2a00:xxxx:xxxx:c05::66: gateway fe80::230:88ff:fe04:67e7: Network is unreachable'

Dec 28 15:12:30	UNKNOWN[56897]: no auto-selected prefix on interface vr0 (LAN), disabling advertisements

      Complet log :

      Dec 28 15:11:52	syslogd: kernel boot file is /boot/kernel/kernel
Dec 28 15:12:10	check_reload_status: Syncing firewall
Dec 28 15:12:18	check_reload_status: Rewriting resolv.conf
Dec 28 15:12:19	check_reload_status: Rewriting resolv.conf
Dec 28 15:12:23	UNKNOWN[56897]: attempting to reread config file
Dec 28 15:12:23	UNKNOWN[56897]: resuming normal operation
Dec 28 15:12:23	kernel: IPv6 address: "fe80:d::230:88ff:fe04:67e7" is not on the network
Dec 28 15:12:24	php: /interfaces.php: Starting 3gstats.php on device '' for interface 'wan'
Dec 28 15:12:25	php: /interfaces.php: ROUTING: setting default route to 91.xxxx.48.1
Dec 28 15:12:26	php: rc.resolv_conf_generate: The command '/sbin/route change -host -inet6 2a00:xxxx:xxxx:c05::66 fe80::230:88ff:fe04:67e7' returned exit code '1', the output was 'route: writing to routing socket: No such process route: writing to routing socket: Network is unreachable change host 2a00:xxxx:xxxx:c05::66: gateway fe80::230:88ff:fe04:67e7: Network is unreachable'
Dec 28 15:12:27	dhcpleases: Could not deliver signal HUP to process because its pidfile does not exist, No such process.
Dec 28 15:12:30	php: rc.resolv_conf_generate: The command '/sbin/route change -host -inet6 2a00:xxxx:xxxx:c05::66 fe80::230:88ff:fe04:67e7' returned exit code '1', the output was 'route: writing to routing socket: No such process route: writing to routing socket: Network is unreachable change host 2a00:xxxx:xxxx:c05::66: gateway fe80::230:88ff:fe04:67e7: Network is unreachable'
Dec 28 15:12:30	UNKNOWN[56897]: attempting to reread config file
Dec 28 15:12:30	UNKNOWN[56897]: no auto-selected prefix on interface vr0 (LAN), disabling advertisements
Dec 28 15:12:30	UNKNOWN[56897]: resuming normal operation
Dec 28 15:12:30	check_reload_status: updating dyndns wan
Dec 28 15:12:32	php: /interfaces.php: Creating rrd update script
Dec 28 15:12:33	check_reload_status: Reloading filter
Dec 28 15:12:35	php: rc.newwanip: The command '/sbin/route change -host -inet6 2a00:xxxx:xxxx:c05::66 fe80::230:88ff:fe04:67e7' returned exit code '1', the output was 'route: writing to routing socket: No such process route: writing to routing socket: Network is unreachable change host 2a00:xxxx:xxxx:c05::66: gateway fe80::230:88ff:fe04:67e7: Network is unreachable'
Dec 28 15:12:37	php: rc.newwanip: ROUTING: setting default route to 91.xxx.48.1
Dec 28 15:12:40	UNKNOWN[56897]: attempting to reread config file
Dec 28 15:12:40	UNKNOWN[56897]: no auto-selected prefix on interface vr0, disabling advertisements
Dec 28 15:12:40	UNKNOWN[56897]: resuming normal operation
Dec 28 15:12:41	php: rc.newwanipv6: The command '/sbin/route change -host -inet6 2a00:xxxx:xxxx:c05::66 fe80::230:88ff:fe04:67e7' returned exit code '1', the output was 'route: writing to routing socket: No such process route: writing to routing socket: Network is unreachable change host 2a00:xxxx:xxxx:c05::66: gateway fe80::230:88ff:fe04:67e7: Network is unreachable'
Dec 28 15:12:41	php: rc.newwanipv6: ROUTING: setting default route to 91.xxx.48.1
Dec 28 15:12:41	check_reload_status: Reloading filter
Dec 28 15:12:47	php: rc.newwanip: Forcefully reloading IPsec racoon daemon
Dec 28 15:12:48	php: rc.newwanipv6: Forcefully reloading IPsec racoon daemon
Dec 28 15:12:48	php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Dec 28 15:12:54	php: rc.newwanipv6: Creating rrd update script
Dec 28 15:12:54	php: rc.newwanip: Creating rrd update script
Dec 28 15:12:55	php: rc.newwanipv6: pfSense package system has detected an ip change -> fe80::20d:b9ff:fe32:a321%vr1 ... Restarting packages.
Dec 28 15:12:55	check_reload_status: Starting packages
Dec 28 15:12:58	php: rc.newwanip: pfSense package system has detected an ip change 81.xxx.232.243 -> 91.xxx.54.241 ... Restarting packages.
Dec 28 15:12:58	check_reload_status: Starting packages

      My configuration :

      My problem seems similar to this one https://forum.pfsense.org/index.php?topic=70791.15

      The few times and it worked on my LAN, the routable table looked like this:

      But it happens once in ten … :-(

      Could you help me?

      Thanks a lot :--)

      Fabien

      1 Reply Last reply Reply Quote 0
      • F
        fab1330
        last edited by

        Since this morning the LAN interface had no public IPv6 address, and now I returning on pfSense and the LAN interface has received its IPv6 address ..
        Why must wait several hours before the interface obtains its IPv6 address?

        Now :

        But if I reboot pfSense now I know I should not have IPv6 address on my LAN interface for some hours…

        1 Reply Last reply Reply Quote 0
        • First post
          Last post