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

IPv6 WAN interface not getting prefix, only single IPv6 address

Scheduled Pinned Locked Moved IPv6
12 Posts 4 Posters 2.5k Views
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.
  • E
    earlish
    last edited by Jun 20, 2017, 2:10 PM

    Hi All,

    I recently purchased an SG-2440 for my new internet service which was supposed to be 100/100M (best effort)

    | System | Netgate SG-2440 |
    | BIOS Vendor: | coreboot |
    | Version: | ADI_RCCVE-01.00.00.12-nodebug |
    | Release Date: | 02/07/2017 |
    | Version | 2.3.4-RELEASE (amd64) built on Wed May 03 16:53:25 CDT 2017 FreeBSD 10.3-RELEASE-p19 |
    | | |

    The IPv4 is working fine until 6pm-2am where it gets completely congested and I only get 500kpbs down although I still get 60-80Mbps up

    I called the ISP and they activated IPv6 on my account. My ISP is So-net with infrastructure by Docomo/Flets-East Hikari. IPv4 is with a PPPoE tunnel and IPv6 is IPoE apparently.

    I would appreciate if someone could check over my setup and let me know if I am doing something wrong, or I should get rid of my ISP after just 3 days and suck up the early termination penalty.

    With a PC connected directly (bypassing pfSense) I can pull an IPv6 address with a 64 subnet and IPv6 traffic is around 90/90M;

    $ ifconfig en10
    en10: flags=8863 <up,broadcast,smart,running,simplex,multicast>mtu 1500
    	options=10b <rxcsum,txcsum,vlan_hwtagging,av>ether 10:dd:b1:e3:e7:2d 
    	inet6 fe80::180e:8cbb:d5c8:2865%en10 prefixlen 64 secured scopeid 0xb 
    	inet6 2409:10:a860:3000:4ff:4101:c878:648b prefixlen 64 autoconf secured 
    	inet6 2409:10:a860:3000:88ab:4169:1bb5:dcf6 prefixlen 64 autoconf temporary 
    	nd6 options=201 <performnud,dad>media: autoselect (1000baseT <full-duplex,flow-control,energy-efficient-ethernet>)
    	status: active</full-duplex,flow-control,energy-efficient-ethernet></performnud,dad></rxcsum,txcsum,vlan_hwtagging,av></up,broadcast,smart,running,simplex,multicast>
    

    The (lacking) IPv6 information on the ISPs website says that a /56 of address space is available per customer. While other pages are indicating that a /60 is allocated if you have a VoIP service and a /64 if you don't have VoIP. At this stage I would be happy just to have a /64 and use that for just 1 LAN interface.

    Now the problem appears to be that the WAN interface on the pfSense is only being allocated 1 IPv6 address instead of a /56 prefix and it is unable to then delegate /64's to my LAN interfaces.
    I am quiet new to the IPv6 world, so please correct me if I am not understanding things correctly, but this looks like the prefix delegation is not working at all?

    I have configured the IPv4 as PPPoE, IPv6 as DHCP6 with the LAN interface IPv4 Static, IPv6 as Tracking.

    If I configure the WAN interface as a 6to4 tunnel, I can get the proper prefix on the WAN, and the LAN interfaces work as expected with Tracking. But I guess this completely defeats the purpose of having IPv6 and all my traffic will still be on the congested IPv4.

    I have also tried factory resetting and configuring just the WAN interface with the same results.
    My setup is as follows, and I have tried pretty much every combination without any success.

    http://imgur.com/a/Axcc0

    ifconfig from shell;

    /root: ifconfig
    igb0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4c
            inet6 fe80::208:a2ff:fe0b:d44c%igb0 prefixlen 64 scopeid 0x1
            inet6 2409:10:a860:3000:208:a2ff:fe0b:d44c prefixlen 64 autoconf
            nd6 options=23 <performnud,accept_rtadv,auto_linklocal>media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    igb1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4d
            inet 10.0.10.1 netmask 0xffffff00 broadcast 10.0.10.255
            inet6 fe80::1:1%igb1 prefixlen 64 scopeid 0x2
            nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (1000baseT <full-duplex>)
            status: active
    igb2: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4e
            inet6 fe80::208:a2ff:fe0b:d44e%igb2 prefixlen 64 scopeid 0x3
            nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
            status: no carrier
    igb3: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
            options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4f
            nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
            status: no carrier
    pflog0: flags=100 <promisc>metric 0 mtu 33160
    pfsync0: flags=0<> metric 0 mtu 1500
            syncpeer: 224.0.0.240 maxupd: 128 defer: on
            syncok: 1
    enc0: flags=41 <up,running>metric 0 mtu 1536
            nd6 options=21 <performnud,auto_linklocal>lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
            options=600003 <rxcsum,txcsum,rxcsum_ipv6,txcsum_ipv6>inet 127.0.0.1 netmask 0xff000000
            inet6 ::1 prefixlen 128
            inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
            nd6 options=21 <performnud,auto_linklocal>pppoe1: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1454
            inet 223.132.83.150 --> 59.146.161.162 netmask 0xffffffff
            inet6 fe80::208:a2ff:fe0b:d44c%pppoe1 prefixlen 64 scopeid 0x9
            nd6 options=21<performnud,auto_linklocal></performnud,auto_linklocal></up,pointopoint,running,noarp,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,rxcsum_ipv6,txcsum_ipv6></up,loopback,running,multicast></performnud,auto_linklocal></up,running></promisc></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast>
    

    dhcp6c system logs;

    Jun 20 20:03:56 	dhcp6c 	40338 	removing an event on igb0, state=SOLICIT
    Jun 20 20:03:56 	dhcp6c 	40338 	executes /var/etc/dhcp6c_wan_script.sh
    Jun 20 20:03:56 	dhcp6c 	40338 	script "/var/etc/dhcp6c_wan_script.sh" terminated
    Jun 20 20:03:56 	dhcp6c 	40338 	exiting
    Jun 20 20:03:57 	dhcp6c 	46001 	extracted an existing DUID from /var/db/dhcp6c_duid: 00:01:00:01:20:db:7a:a5:00:08:a2:0b:d4:4c
    Jun 20 20:03:57 	dhcp6c 	46001 	failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
    Jun 20 20:03:57 	dhcp6c 	46001 	failed initialize control message authentication
    Jun 20 20:03:57 	dhcp6c 	46001 	skip opening control port
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[interface] (9)
    Jun 20 20:03:57 	dhcp6c 	46001 	<5>[igb0] (4)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>begin of closure [{] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[send] (4)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[ia-pd] (5)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[0] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>comment [# request prefix delegation] (27)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[request] (7)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[domain-name-servers] (19)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[request] (7)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[domain-name] (11)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[script] (6)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>["/var/etc/dhcp6c_wan_script.sh"] (31)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>comment [# we'd like some nameservers please] (35)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of closure [}] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[id-assoc] (8)
    Jun 20 20:03:57 	dhcp6c 	46001 	<13>[pd] (2)
    Jun 20 20:03:57 	dhcp6c 	46001 	<13>[0] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<13>begin of closure [{] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[prefix] (6)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[::] (2)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[/] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[56] (2)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[infinity] (8)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[prefix-interface] (16)
    Jun 20 20:03:57 	dhcp6c 	46001 	<5>[igb1] (4)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>begin of closure [{] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[sla-id] (6)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[0] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[sla-len] (7)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>[8] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of closure [}] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of closure [}] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	<3>end of sentence [;] (1)
    Jun 20 20:03:57 	dhcp6c 	46001 	called
    Jun 20 20:03:57 	dhcp6c 	46001 	called
    Jun 20 20:03:57 	dhcp6c 	46283 	reset a timer on igb0, state=INIT, timeo=0, retrans=383
    Jun 20 20:03:57 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:03:57 	dhcp6c 	46283 	a new XID (71f27c) is generated
    Jun 20 20:03:57 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:03:57 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:03:57 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:03:57 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:03:57 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:03:57 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:03:57 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=0, retrans=1088
    Jun 20 20:03:58 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:03:58 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:03:58 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:03:58 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:03:58 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:03:58 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:03:58 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:03:58 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=1, retrans=2151
    Jun 20 20:04:00 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:04:00 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:04:00 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:04:00 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:04:00 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:04:00 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:04:00 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:04:00 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=2, retrans=4283
    Jun 20 20:04:05 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:04:05 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:04:05 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:04:05 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:04:05 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:04:05 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:04:05 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:04:05 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=3, retrans=8905
    Jun 20 20:04:14 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:04:14 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:04:14 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:04:14 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:04:14 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:04:14 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:04:14 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:04:14 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=4, retrans=17217
    Jun 20 20:04:31 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:04:31 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:04:31 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:04:31 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:04:31 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:04:31 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:04:31 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:04:31 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=5, retrans=35098
    Jun 20 20:05:06 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:05:06 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:05:06 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:05:06 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:05:06 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:05:06 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:05:06 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:05:06 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=6, retrans=68413
    Jun 20 20:06:14 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:06:14 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:06:14 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:06:14 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:06:14 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:06:14 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:06:14 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:06:14 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=7, retrans=115788
    Jun 20 20:08:10 	dhcp6c 	46283 	Sending Solicit
    Jun 20 20:08:10 	dhcp6c 	46283 	set client ID (len 14)
    Jun 20 20:08:10 	dhcp6c 	46283 	set elapsed time (len 2)
    Jun 20 20:08:10 	dhcp6c 	46283 	set option request (len 4)
    Jun 20 20:08:10 	dhcp6c 	46283 	set IA_PD prefix
    Jun 20 20:08:10 	dhcp6c 	46283 	set IA_PD
    Jun 20 20:08:10 	dhcp6c 	46283 	send solicit to ff02::1:2%igb0
    Jun 20 20:08:10 	dhcp6c 	46283 	reset a timer on igb0, state=SOLICIT, timeo=8, retrans=125052 
    
    1 Reply Last reply Reply Quote 0
    • ?
      Guest
      last edited by Jun 20, 2017, 8:41 PM

      If your V4 is PPPoE, set the WAN v6 to DHCP and tick the box 'Use IPv4 Connectivity as parent interface.

      The dhcp6c client needs to talk over the PPPoE connection.

      Set LAN IPv6 to track the WAN interface and you should get it working.

      1 Reply Last reply Reply Quote 0
      • E
        earlish
        last edited by Jun 20, 2017, 11:42 PM

        When I set the 'Use IPv4 Connectivity as parent interface' I just get a local link address on the WAN interface;

        /root: ifconfig
        igb0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4c
        	inet6 fe80::208:a2ff:fe0b:d44c%igb0 prefixlen 64 scopeid 0x1 
        	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (100baseTX <full-duplex>)
        	status: active
        igb1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4d
        	inet 10.0.10.1 netmask 0xffffff00 broadcast 10.0.10.255 
        	inet6 fe80::1:1%igb1 prefixlen 64 scopeid 0x2 
        	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (1000baseT <full-duplex>)
        	status: active</full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast>
        

        System>Routing log shows;

        Jun 21 08:35:28 	radvd 	32913 	version 1.9.1 started
        Jun 21 08:35:28 	radvd 	32913 	no auto-selected prefix on interface igb1, disabling advertisements 
        

        dhcp6c;

        Jun 21 08:30:42 	dhcp6c 	16741 	Sending Solicit
        Jun 21 08:30:42 	dhcp6c 	16741 	set client ID (len 14)
        Jun 21 08:30:42 	dhcp6c 	16741 	set elapsed time (len 2)
        Jun 21 08:30:42 	dhcp6c 	16741 	set option request (len 4)
        Jun 21 08:30:42 	dhcp6c 	16741 	set IA_PD prefix
        Jun 21 08:30:42 	dhcp6c 	16741 	set IA_PD
        Jun 21 08:30:42 	dhcp6c 	16741 	send solicit to ff02::1:2%igb0
        Jun 21 08:30:42 	dhcp6c 	16741 	reset a timer on igb0, state=SOLICIT, timeo=228, retrans=129432
        Jun 21 08:32:51 	dhcp6c 	16741 	Sending Solicit
        Jun 21 08:32:51 	dhcp6c 	16741 	set client ID (len 14)
        Jun 21 08:32:51 	dhcp6c 	16741 	set elapsed time (len 2)
        Jun 21 08:32:51 	dhcp6c 	16741 	set option request (len 4)
        Jun 21 08:32:51 	dhcp6c 	16741 	set IA_PD prefix
        Jun 21 08:32:51 	dhcp6c 	16741 	set IA_PD
        Jun 21 08:32:51 	dhcp6c 	16741 	send solicit to ff02::1:2%igb0
        Jun 21 08:32:51 	dhcp6c 	16741 	reset a timer on igb0, state=SOLICIT, timeo=229, retrans=128028 
        
        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by Jun 21, 2017, 5:56 AM

          Something is definitely wrong, if you have selected use parent interface then the line in your logs that says this:

          Jun 21 08:32:51 dhcp6c 16741 send solicit to ff02::1:2%igb0

          Should be showing something like this:

          Jun 21 06:43:01 dhcp6c 43299 send solicit to ff02::1:2%pppoe0

          Note the pppoe0

          In either case, dhcp6c is sending solicits but is getting no response from the ISP.

          The settings should be like those I have shown in the attached image.

          Capture.JPG
          Capture.JPG_thumb

          1 Reply Last reply Reply Quote 0
          • E
            earlish
            last edited by Jun 21, 2017, 10:25 AM

            I factory defaulted the pfSense and I put the same config as yours, but still no IPv6.

            ifconfig;

            root: ifconfig
            igb0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4c
            	inet6 fe80::208:a2ff:fe0b:d44c%igb0 prefixlen 64 scopeid 0x1 
            	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (100baseTX <full-duplex>)
            	status: active
            igb1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4d
            	inet 10.0.10.1 netmask 0xffffff00 broadcast 10.0.10.255 
            	inet6 fe80::1:1%igb1 prefixlen 64 scopeid 0x2 
            	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (1000baseT <full-duplex>)
            	status: active
            igb2: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
            	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4e
            	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
            	status: no carrier
            igb3: flags=8c02 <broadcast,oactive,simplex,multicast>metric 0 mtu 1500
            	options=400bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso>ether 00:08:a2:0b:d4:4f
            	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
            	status: no carrier
            pflog0: flags=100 <promisc>metric 0 mtu 33160
            pfsync0: flags=0<> metric 0 mtu 1500
            	syncpeer: 224.0.0.240 maxupd: 128 defer: on
            	syncok: 1
            enc0: flags=0<> metric 0 mtu 1536
            	nd6 options=21 <performnud,auto_linklocal>lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
            	options=600003 <rxcsum,txcsum,rxcsum_ipv6,txcsum_ipv6>inet 127.0.0.1 netmask 0xff000000 
            	inet6 ::1 prefixlen 128 
            	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 
            	nd6 options=21 <performnud,auto_linklocal>pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1454
            	inet 115.163.163.254 --> 59.146.160.74 netmask 0xffffffff 
            	inet6 fe80::208:a2ff:fe0b:d44c%pppoe0 prefixlen 64 scopeid 0x9 
            	nd6 options=21<performnud,auto_linklocal></performnud,auto_linklocal></up,pointopoint,running,noarp,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,rxcsum_ipv6,txcsum_ipv6></up,loopback,running,multicast></performnud,auto_linklocal></promisc></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></broadcast,oactive,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast>
            

            dhcp6c logs;

            Jun 21 18:52:27 	dhcp6c 	72748 	failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
            Jun 21 18:52:27 	dhcp6c 	72748 	failed initialize control message authentication
            Jun 21 18:52:27 	dhcp6c 	72748 	skip opening control port
            Jun 21 18:52:28 	dhcp6c 	72900 	Sending Solicit
            Jun 21 18:52:28 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
            Jun 21 18:52:29 	dhcp6c 	72900 	Sending Solicit
            Jun 21 18:52:29 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
            Jun 21 18:52:31 	dhcp6c 	72900 	Sending Solicit
            Jun 21 18:52:31 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
            Jun 21 18:52:35 	dhcp6c 	72900 	Sending Solicit
            Jun 21 18:52:35 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
            Jun 21 18:52:44 	dhcp6c 	72900 	Sending Solicit
            Jun 21 18:52:44 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
            Jun 21 18:53:01 	dhcp6c 	72900 	Sending Solicit
            Jun 21 18:53:01 	dhcp6c 	72900 	advertise contains NoPrefixAvail status
            Jun 21 18:53:37 	dhcp6c 	72900 	Sending Solicit
            Jun 21 18:53:37 	dhcp6c 	72900 	advertise contains NoPrefixAvail status 
            

            Does this mean dhcp6c is getting a response, but there is no prefix?

            1 Reply Last reply Reply Quote 0
            • ?
              Guest
              last edited by Jun 21, 2017, 12:33 PM

              Indeed it does, they are not offering a prefix.

              1 Reply Last reply Reply Quote 0
              • E
                earlish
                last edited by Jun 22, 2017, 3:37 PM

                Thanks for that,

                So I'm wondering what does my ISP expect I can do with 1 IPv6 address (/128 ?) is that some kind of joke?

                How can the crap consumer grade routers work in this case? Some kind of IPv6 pass-through/bridge?

                Sorry I'm not so familiar with IPv6, but I thought it was supposed to get rid of all this NAT nonsense.

                1 Reply Last reply Reply Quote 0
                • awebsterA
                  awebster
                  last edited by Jun 22, 2017, 3:42 PM

                  The sad truth is that many ISPs don't have a clue either and are hopelessly stuck in IPv4 mentality. 
                  Exercise your opinion with your wallet.

                  –A.

                  1 Reply Last reply Reply Quote 0
                  • ?
                    Guest
                    last edited by Jun 22, 2017, 3:44 PM

                    Best thing to do in the first instance is to email your ISP 2nd tier support and ask them what exactly they supply IPv6 wise.

                    1 Reply Last reply Reply Quote 0
                    • E
                      earlish
                      last edited by Jun 22, 2017, 4:00 PM

                      Well it looks like I will be exercising my wallet, after I cancel this ISP after just one week and I have to pay the cancellation penalty. Their IPv4 is absolutely completely useless and going to IPv6 probably won't solve the problem as a lot of stuff is still in the IPv4 domain.

                      I just wanted to confirm that there is nothing silly I am doing with pfsense that would prevent me from getting IPv6 to work properly before I complained again to the ISP.

                      Cheers.

                      1 Reply Last reply Reply Quote 0
                      • E
                        earlish
                        last edited by Jun 25, 2017, 3:51 PM

                        So it turns out if I use a v6 username (i.e. user@v6-isp.jp instead of user@isp.jp) for the PPPoE I can get a /56 prefix assigned. But by doing this I do not get an IPv4 address.

                        I did manage to get both IPv4 and IPv6 to work by adding another PPPoE tunnel on another interface. (OPT1 in my case)

                        So now my question is; do I need to use 2 interfaces (WAN and OPT1) to use 2 PPPoE tunnels, or can I use 2 PPPoE tunnels on 1 interface?
                        I couldn't find any information about this but I'm sure there is a better way than what I'm doing. Or is using 2 PPPoE tunnels just not the usual thing to do, as I did come across this thread https://arstechnica.com/civis/viewtopic.php?f=10&t=1378151

                        1 Reply Last reply Reply Quote 0
                        • G
                          gaijinboy
                          last edited by Feb 12, 2019, 4:51 AM

                          @earlish Hi,

                          Do you still use pfsense?
                          I'm facing the same problem as you using AsashiNET provider.
                          Only the WAN gets the prefix, LAN It is not getting anything.
                          Please let me know if you found a solution because my provider doesn't support PPPoE for IPv6.

                          Thanks in advance.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                            This community forum collects and processes your personal information.
                            consent.not_received