Reply
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

[ Edited ]

Hi,

 

I'am trying to replace a AVM FritzBox with USG 3P and get an IPv6 over PPPoE (DHCPv6 - Prefix Delegation size: 56)

I can obtain an IPv4 with my credentials and everything works fine except that impossible to get an IPv6.

 

Untitled 2.jpg

 

It works with the FritzBox, and I called the provider support (POST Luxembourg) which told me that there is no restriction on the brand to get IPv6 but they don't offer support for other brands than AVM FritzBox Man Happy

 

Could you help?

 

--- show interfaces

 

Interface    IP Address                        S/L  Description                 
---------    ----------                        ---  -----------                 
eth0         -                                 u/u  WAN                         
eth0.35      -                                 u/u  WAN                         
eth1         172.16.8.1/24                     u/u  LAN                         
eth1.107     192.168.107.1/28                  u/u                              
eth1.666     192.168.66.1/29                   u/u                              
eth2         -                                 A/D                              
lo           127.0.0.1/8                       u/u                              
             ::1/128                          
pppoe2       xxx.xxx.xxx.xxx                   u/u             

 

 

--- show ipv6 route

 

Codes: K - kernel route, C - connected, S - static, R - RIPng, O - OSPFv3,
       I - ISIS, B - BGP, * - FIB route.

K>* ::/0 via fe80::2a0:a50f:fc90:3fcc, pppoe2
S   ::/0 [1/0] is directly connected, pppoe2
C>* ::1/128 is directly connected, lo
K * fe80::/10 is directly connected, pppoe2
C>* fe80::/10 is directly connected, pppoe2
C * fe80::/64 is directly connected, eth1.666
C * fe80::/64 is directly connected, eth0.35
C * fe80::/64 is directly connected, eth1.107
C * fe80::/64 is directly connected, eth0
C>* fe80::/64 is directly connected, eth1

 

 

 

--- ppp_pppoe2.log

 

Connected to 84:18:88:28:a7:c0 via interface eth0.35
using channel 3
Using interface ppp0
Connect: ppp0 <--> eth0.35
sent [LCP ConfReq id=0x4 <mru 1492> <magic 0x47c0866c>]
rcvd [LCP ConfReq id=0x9 <mru 1492> <auth chap MD5> <magic 0x13faf379>]
lcp_reqci: returning CONFACK.
sent [LCP ConfAck id=0x9 <mru 1492> <auth chap MD5> <magic 0x13faf379>]
rcvd [LCP ConfAck id=0x4 <mru 1492> <magic 0x47c0866c>]
IPCP: Up event in state 2!
IPV6CP: Up event in state 2!
rcvd [CHAP Challenge id=0xae <93d68565084c74dada0f5ca62f2552cc2bb689042bcad39c>, name = "XXXXX"]
sent [CHAP Response id=0xae <dbaff29fd808ed703d2911d027d2d49b>, name = "XXXXX"]
rcvd [CHAP Success id=0xae ""]
CHAP authentication succeeded
CHAP authentication succeeded
peer from calling number 84:18:88:28:A7:C0 authorized
sent [IPCP ConfReq id=0x3 <addr 0.0.0.0>]
sent [IPV6CP ConfReq id=0x2 <addr fe80::89eb:d582:0dc5:8136>]
rcvd [IPCP ConfNak id=0x3 <addr 88.207.150.163>]
sent [IPCP ConfReq id=0x4 <addr 88.207.150.163>]
rcvd [IPV6CP ConfAck id=0x2 <addr fe80::89eb:d582:0dc5:8136>]
rcvd [IPCP ConfAck id=0x4 <addr 88.207.150.163>]
rcvd [IPCP ConfReq id=0xe7 <addr 88.207.158.1>]
ipcp: returning Configure-ACK
sent [IPCP ConfAck id=0xe7 <addr 88.207.158.1>]
ipcp: up
Script /etc/ppp/ip-pre-up started (pid 2229)
Script /etc/ppp/ip-pre-up finished (pid 2229), status = 0x0
local  IP address 88.207.150.163
remote IP address 88.207.158.1
Script /etc/ppp/ip-up started (pid 2292)
rcvd [IPV6CP ConfReq id=0xdd <addr fe80::02a0:a50f:fc90:3fcc>]
ipv6cp: received interface identifier
(fe80::02a0:a50f:fc90:3fcc)
 (ACK)
ipv6cp: returning Configure-ACK
sent [IPV6CP ConfAck id=0xdd <addr fe80::02a0:a50f:fc90:3fcc>]
ipv6cp: up
local  LL address fe80::89eb:d582:0dc5:8136
remote LL address fe80::02a0:a50f:fc90:3fcc
Script /etc/ppp/ipv6-up started (pid 2293)
Script /etc/ppp/ipv6-up finished (pid 2293), status = 0x0
Script /etc/ppp/ip-up finished (pid 2292), status = 0x0

 

--- dhcpv6c.log

 

May/02/2018 15:58:26: dhcp6_ctl_init: bind(control sock): Address already in use
May/02/2018 15:58:26: client6_init: failed to initialize control channel

 

--- Messages

 

May  2 15:55:22 gw2-hell dhcp6c: dhcp6_remove_event: removing an event on eth0.35, state=SOLICIT
May  2 15:55:22 gw2-hell dhcp6c: get_duid: extracted an existing DUID from /var/lib/dhcpv6/dhcp6c_duid: 00:01:00:01:22:29:79:71:f0:9f:c2:17:c8:64
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>comment [# This file was auto-generated by /opt/vyatta/sbin/dhcpv6-pd-client.pl] (70)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>comment [# configuration sub-system.  Do not edit it.] (44)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[interface] (9)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <5>[eth0.35] (7)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>begin of closure [{] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[send] (4)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[ia-na] (5)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[0] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[request] (7)
May  2 15:55:22 gw2-hell sudo: pam_unix(sudo:session): session closed for user root
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[domain-name-servers] (19)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[,] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[domain-name] (11)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[send] (4)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[rapid-commit] (12)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[send] (4)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[ia-pd] (5)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[0] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[script] (6)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>["/opt/vyatta/sbin/ubnt-dhcp6c-script"] (37)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of closure [}] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[id-assoc] (8)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <15>[na] (2)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <15>[0] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <15>begin of closure [{] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of closure [}] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[id-assoc] (8)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <15>[pd] (2)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <15>[0] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <15>begin of closure [{] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[prefix] (6)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[::] (2)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[/] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[55] (2)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>[infinity] (8)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of closure [}] (1)
May  2 15:55:22 gw2-hell dhcp6c: cfdebug_print: <3>end of sentence [;] (1)

ay  2 15:55:22 gw2-hell dhcp6c: configure_pool: called
May  2 15:55:22 gw2-hell dhcp6c: clear_poolconf: called
May  2 15:55:22 gw2-hell dhcp6c: dhcp6_reset_timer: reset a timer on eth0.35, state=INIT, timeo=0, retrans=532
May  2 15:55:22 gw2-hell sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/opt/vyatta/sbin/dhcpv6-pd-client.pl --ifname=pppoe2 --update
May  2 15:55:22 gw2-hell sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
May  2 15:55:23 gw2-hell dhcp6c: client6_send: a new XID (c67a99) is generated
May  2 15:55:23 gw2-hell dhcp6c: copy_option: set client ID (len 14)
May  2 15:55:23 gw2-hell dhcp6c: copyout_option: set identity association
May  2 15:55:23 gw2-hell dhcp6c: copy_option: set rapid commit (len 0)
May  2 15:55:23 gw2-hell dhcp6c: copy_option: set elapsed time (len 2)
May  2 15:55:23 gw2-hell dhcp6c: copy_option: set option request (len 4)
May  2 15:55:23 gw2-hell dhcp6c: copyout_option: set IA_PD prefix
May  2 15:55:23 gw2-hell dhcp6c: copyout_option: set IA_PD
May  2 15:55:23 gw2-hell dhcp6c: client6_send: send solicit to ff02::1:2%eth0.35
May  2 15:55:23 gw2-hell dhcp6c: dhcp6_reset_timer: reset a timer on eth0.35, state=SOLICIT, timeo=0, retrans=1028
May  2 15:55:24 gw2-hell dhcp6c: copy_option: set client ID (len 14)
May  2 15:55:24 gw2-hell dhcp6c: copyout_option: set identity association
May  2 15:55:24 gw2-hell dhcp6c: copy_option: set rapid commit (len 0)
May  2 15:55:24 gw2-hell dhcp6c: copy_option: set elapsed time (len 2)
May  2 15:55:24 gw2-hell dhcp6c: copy_option: set option request (len 4)
May  2 15:55:24 gw2-hell dhcp6c: copyout_option: set IA_PD prefix
May  2 15:55:24 gw2-hell dhcp6c: copyout_option: set IA_PD
May  2 15:55:24 gw2-hell dhcp6c: client6_send: send solicit to ff02::1:2%eth0.35
May  2 15:55:24 gw2-hell dhcp6c: dhcp6_reset_timer: reset a timer on eth0.35, state=SOLICIT, timeo=1, retrans=1981
May  2 15:55:24 gw2-hell dhcp6c: get_duid: extracted an existing DUID from /var/lib/dhcpv6/dhcp6c_duid: 00:01:00:01:22:29:79:71:f0:9f:c2:17:c8:64
May  2 15:55:24 gw2-hell sudo: pam_unix(sudo:session): session closed for user root
May  2 15:55:26 gw2-hell dhcp6c: copy_option: set client ID (len 14)
May  2 15:55:26 gw2-hell dhcp6c: copyout_option: set identity association
May  2 15:55:26 gw2-hell dhcp6c: copy_option: set rapid commit (len 0)
May  2 15:55:26 gw2-hell dhcp6c: copy_option: set elapsed time (len 2)
May  2 15:55:26 gw2-hell dhcp6c: copy_option: set option request (len 4)
May  2 15:55:26 gw2-hell dhcp6c: copyout_option: set IA_PD prefix
May  2 15:55:26 gw2-hell dhcp6c: copyout_option: set IA_PD
May  2 15:55:26 gw2-hell dhcp6c: client6_send: send solicit to ff02::1:2%eth0.35
May  2 15:55:26 gw2-hell dhcp6c: dhcp6_reset_timer: reset a timer on eth0.35, state=SOLICIT, timeo=2, retrans=4149
May  2 15:55:30 gw2-hell mca-monitor: mca-monitor.do_monitor(): mcad.setparam in progress, elapsed=62 (max=960)
May  2 15:55:30 gw2-hell dhcp6c: copy_option: set client ID (len 14)
May  2 15:55:30 gw2-hell dhcp6c: copyout_option: set identity association
May  2 15:55:30 gw2-hell dhcp6c: copy_option: set rapid commit (len 0)
May  2 15:55:30 gw2-hell dhcp6c: copy_option: set elapsed time (len 2)
May  2 15:55:30 gw2-hell dhcp6c: copy_option: set option request (len 4)
May  2 15:55:30 gw2-hell dhcp6c: copyout_option: set IA_PD prefix
May  2 15:55:30 gw2-hell dhcp6c: copyout_option: set IA_PD
May  2 15:55:30 gw2-hell dhcp6c: client6_send: send solicit to ff02::1:2%eth0.35
May  2 15:55:30 gw2-hell dhcp6c: dhcp6_reset_timer: reset a timer on eth0.35, state=SOLICIT, timeo=3, retrans=8663
May  2 15:55:32 gw2-hell mcad: ace_reporter.reporter_handle_response(): [setparam] applying system.cfg done
May  2 15:55:33 gw2-hell mcad: dpi.ubnt_init(): mcast_ip is 239.254.127.63

May  2 15:55:35 gw2-hell mcad: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
May  2 15:55:39 gw2-hell dhcp6c: copy_option: set client ID (len 14)
May  2 15:55:39 gw2-hell dhcp6c: copyout_option: set identity association
May  2 15:55:39 gw2-hell dhcp6c: copy_option: set rapid commit (len 0)
May  2 15:55:39 gw2-hell dhcp6c: copy_option: set elapsed time (len 2)
May  2 15:55:39 gw2-hell dhcp6c: copy_option: set option request (len 4)
May  2 15:55:39 gw2-hell dhcp6c: copyout_option: set IA_PD prefix
May  2 15:55:39 gw2-hell dhcp6c: copyout_option: set IA_PD
May  2 15:55:39 gw2-hell dhcp6c: client6_send: send solicit to ff02::1:2%eth0.35
May  2 15:55:39 gw2-hell dhcp6c: dhcp6_reset_timer: reset a timer on eth0.35, state=SOLICIT, timeo=4, retrans=17962

USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
New Member
Posts: 15
Registered: ‎03-13-2017
Kudos: 68

Re: USG (4.5.3) can't get an IPv6 from POST Luxembourg via PPPoE

Having the same issue - did you find a solution in the meanwhile?

USG-4P / USW-24-250W / USW-16-150W / USW-8 / 3x UAP-AC-IW / 3x UAP-AC-Pro / 2x UVC-G3-Dome / 2x UVC-G3-Micro / 2x UVC-G3 / CloudKey G2-plus
Member
Posts: 151
Registered: ‎07-14-2018
Kudos: 34
Solutions: 18

Re: USG (4.5.3) can't get an IPv6 from POST Luxembourg via PPPoE

It's same problem here with german Telekom.
I descripted a workaround here:
http://translate.google.com/translate?js=n&sl=auto&tl=en&u=https://spflug.de/?p=175
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.5.3) can't get an IPv6 from POST Luxembourg via PPPoE


@dlaplexurenet wrote:

Having the same issue - did you find a solution in the meanwhile?


Unfortunately, no ...

even with an IP Fix solution from POST it doesn’t work. I got rid of the FritzBox and as IPv6 is not a critical need I’ll wait for a fix from Ubiquiti ...

USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.5.3) can't get an IPv6 from POST Luxembourg via PPPoE


@stefanpf wrote:
It's same problem here with german Telekom.
I descripted a workaround here:
http://translate.google.com/translate?js=n&sl=auto&tl=en&u=https://spflug.de/?p=175

The problem here in Luxembourg is that PPPoE2 doesn’t aven get an IPv6 ... 

USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
New Member
Posts: 14
Registered: ‎12-18-2016
Solutions: 1

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

Same problem with USG firmware 4.4.29.5124210 on controller version 5.9.29. The DHCPv6 daemon is listening on eth0 instead of pppeo0. This functionality used to work fine earlier firmware/controller versions, but I'm not sure exactly which version broke this.

New Member
Posts: 27
Registered: ‎07-01-2014
Kudos: 5
Solutions: 1

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

Is this still the case with POST Luxembourg? Since yesterday I've got my fiber connected and only had time to quickly test ipv6 which failed, but in my case most probably because of a wrong prefix setting (/48 instead of /56).

In any case I will do another test this weekend with the correct prefix setting.

Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE


@rthill wrote:

Is this still the case with POST Luxembourg? Since yesterday I've got my fiber connected and only had time to quickly test ipv6 which failed, but in my case most probably because of a wrong prefix setting (/48 instead of /56).

In any case I will do another test this weekend with the correct prefix setting.


Yes it still the case ...

USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

@rthill Oh, if it works for you, your feedback will be appreciated Man Happy

USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
New Member
Posts: 15
Registered: ‎03-13-2017
Kudos: 68

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

I found an interesting article about UBNT and POST: https://marc.storck.lu/blog/2017/12/post-iptv-unifi-security-gateway-pro-4/ (mainly for the IGMP proxy for POST TV), but @pwal did also ask the same question there (down in the comments), and Marc said he could make it work by setting the DHCP-PD to 0:

  • There seems to be an issue with the DHCP-PD request sent by the USG, I’m having similar issues with an EdgeRouter X. I’m in contact with Ubiquiti support but it could take several months to see a change… BTW when manually setting the requested prefix size to /0, the PD works fine, but the CLI/GUI doesn’t allow /0 as the prefix size.

Unfortunately I couldn't set the value to 0. CLI/GUI is not working and setting it in the config file doesn't work neither.

I don't know what makes the setup from POST so exceptional. I'll address the question to POST internal people to get eventually an answer.

 

USG-4P / USW-24-250W / USW-16-150W / USW-8 / 3x UAP-AC-IW / 3x UAP-AC-Pro / 2x UVC-G3-Dome / 2x UVC-G3-Micro / 2x UVC-G3 / CloudKey G2-plus
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

@dlaplexurenet I Know about Marc Storck blog, I'am p.wal ...

 

I already contacted POST support who, unfortunatly, is not keen to help on some "exotic" hardawre.... Man Happy

But if you get luckier than me on this, let me know ... 

USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
New Member
Posts: 15
Registered: ‎03-13-2017
Kudos: 68

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

I got a pretty fast answer from POST's Access Services team (translated):

 

The DUID of the solicit request has to be done using the MAC-address of the PPPoE session. e.g. the MAC of the PPPoE session is 02:03:04:05:06:07, the DUID should be 00030001020304050607 (DUID-LL, Ethernet). The DHCPv6 request have to be done inside of the PPPoE tunnel, not ouside.

 

 

Most important was the fact that the DHCPv6 request has to be done inside of the PPPoE tunnel, thus on eth2.35. So basically what I did now (after having configured IPv6 in the GUI with a prefix of ::/56), confirm that it's not working:

superadm@UniFiGateway:~$ show dhcpv6-pd log
Jan/07/2019 07:19:59: dhcp6_ctl_init: bind(control sock): Address already in use
Jan/07/2019 07:19:59: client6_init: failed to initialize control channel

Finally, followed by:

configure
delete interfaces ethernet eth2 vif 35 dhcpv6-pd
commit
exit

release dhcpv6-pd interface pppoe2
delete dhcpv6-pd duid
renew dhcpv6-pd interface pppoe2

If now you recheck the log:

superadm@UniFiGateway:~$ show dhcpv6-pd log
Jan/07/2019 16:55:35: client6_recvadvert: unexpected advertise

Check your assigned IPv6 using

superadm@UniFiGateway:~$ show interfaces

So finally, all interfaces I configured got now an IPv6 address. This blog post had exactly the same issue and it also contains a script in order to make this change permanent (not tested yet):https://www.noodles.net.nz/2018/09/20/ipv6-workaround-for-unifi-usg-on-2-degrees-ufb/

 

Let me know if it did also work for you.

 

// Kudos to Pedro and Jero from POST Technologies!

 

USG-4P / USW-24-250W / USW-16-150W / USW-8 / 3x UAP-AC-IW / 3x UAP-AC-Pro / 2x UVC-G3-Dome / 2x UVC-G3-Micro / 2x UVC-G3 / CloudKey G2-plus
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

@dlaplexurenet Still not working for me Man Sad

which "IPv6 Prefix ID" did you set on your local network ?

 

Screenshot 2019-01-07 at 17.52.38.png

USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
New Member
Posts: 15
Registered: ‎03-13-2017
Kudos: 68

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

Hi @pwal. I have the same settings as you have on my corporate networks. No Prefix ID set, but with the exception that I have set the RA prio to High.

Screenshot 2019-01-07 at 22.47.41.pngRegarding the IPv6 assignment, I have configured the WAN interface like this:

Screenshot 2019-01-07 at 22.46.54.png
So basically, the only change I had to do using the CLI is was:

configure
delete interfaces ethernet eth2 dhcpv6-pd
delete interfaces ethernet eth2 vif 35 dhcpv6-pd
set interfaces ethernet eth2 vif 35 pppoe 2 dhcpv6-pd pd 0 prefix-length 56
commit
save
exit
disconnect interface pppoe2
connect interface pppoe2
release dhcpv6-pd interface pppoe2
delete dhcpv6-pd duid
renew dhcpv6-pd interface pppoe2
show interfaces

 

Surprisingly I had almost all the same commands in a previous script and it didn't work out. Now it does. In terms of the firmware, I am running 4.4.36.5146617.

 

USG-4P / USW-24-250W / USW-16-150W / USW-8 / 3x UAP-AC-IW / 3x UAP-AC-Pro / 2x UVC-G3-Dome / 2x UVC-G3-Micro / 2x UVC-G3 / CloudKey G2-plus
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

I'll try this tonight...
Ps: You were luckier than me with POST, I had no support at all...
USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

@dlaplexurenet 

 

Didn't work for me...

I don't get it because as soon I put the Fritzbox in place I got IPv6... (so the connexion is ok)

 

I'am using FW 4.37dev

USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
New Member
Posts: 15
Registered: ‎03-13-2017
Kudos: 68

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

So basically you have your WAN on eth0 right?

 

Can you put your eth0 config output from CLI here, including vif 35 and pppoe2 (removing sensible data like PPPoE user/pass)?

USG-4P / USW-24-250W / USW-16-150W / USW-8 / 3x UAP-AC-IW / 3x UAP-AC-Pro / 2x UVC-G3-Dome / 2x UVC-G3-Micro / 2x UVC-G3 / CloudKey G2-plus
Emerging Member
Posts: 61
Registered: ‎04-19-2017
Kudos: 14

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

@dlaplexurenet

 

No WAN is on eth2 ...

                        "eth2": {
                                "description": "WAN",
                                "vif": {
                                        "35": {
                                                "description": "WAN",
                                                "dhcpv6-pd": {
                                                        "pd": {
                                                                "0": {
                                                                        "prefix-length": "56"
                                                                }
                                                        },
                                                        "rapid-commit": "enable"
                                                },
                                                "firewall": {
                                                        "in": {
                                                                "ipv6-name": "WANv6_IN",
                                                                "name": "WAN_IN"
                                                        },
                                                        "local": {
                                                                "ipv6-name": "WANv6_LOCAL",
                                                                "name": "WAN_LOCAL"
                                                        },
                                                        "out": {
                                                                "ipv6-name": "WANv6_OUT",
                                                                "name": "WAN_OUT"
                                                        }
                                                },
                                                "pppoe": {
                                                        "2": {
                                                                "default-route": "none",
                                                                "dhcpv6-pd": {
                                                                        "pd": {
                                                                                "0": {
                                                                                        "prefix-length": "56"
                                                                                }
                                                                        },
                                                                        "rapid-commit": "enable"
                                                                },
                                                                "firewall": {
                                                                        "in": {
                                                                                "ipv6-name": "WANv6_IN",
                                                                                "name": "WAN_IN"
                                                                        },
                                                                        "local": {
                                                                                "ipv6-name": "WANv6_LOCAL",
                                                                                "name": "WAN_LOCAL"
                                                                        },
                                                                        "out": {
                                                                                "ipv6-name": "WANv6_OUT",
                                                                                "name": "WAN_OUT"
                                                                        }
                                                                },
                                                                "ipv6": {
                                                                        "address": "autoconf",
                                                                        "enable": "''"
                                                                },
                                                                "name-server": "none",
                                                                "password": "xxxxxxx",
                                                                "user-id": "yyyyyy"
                                                        }
                                                }
                                        }
                                }
                        },
USG-4-Pro / USW-16-150W / 2 x USW-8 / 2 x UAP-AC-Pro / CloudKey Gen2
https://pakal.org/
New Member
Posts: 15
Registered: ‎03-13-2017
Kudos: 68

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

Do you have a USG4-PRO? I have the same but my config format looks a bit different. Is this a change between our firmwares?

 

Nonetheless, here is the config I have and the deltas I see:

  • You have dhcpv6-pd configured on eth2.35 (internet VLAN), this might be already the root cause, remove it with

 

configure
delete interfaces ethernet eth2 vif 35 dhcpv6-pd
commit
save
exit

 

  • I have interfaces within pppoe2 > dhcpv6-pd 0. Sorry for the stupid question, but did you apply the IPv6 settings within GUI > Settings > Networks > Networks of choice? I didn't add these configs manually so I guess they have been added due to the config I did in the GUI. But this should not avoid the fact that you don't get any IPv6 on PPPoE, it might be a source when you do not get IPv6 addresses on your (virtual) interfaces.

I believe that if you remove the dhcpv6-pd on eth2.vif35, it might work by executing the following commands later on:

release dhcpv6-pd interface pppoe2
delete dhcpv6-pd duid
renew dhcpv6-pd interface pppoe2

 

 

My full config of eth2

 

ethernet eth2 {
   description WAN
   vif 35 {
       description WAN
       firewall {
           in {
               ipv6-name WANv6_IN
               name WAN_IN
           }
           local {
               ipv6-name WANv6_LOCAL
               name WAN_LOCAL
           }
           out {
               ipv6-name WANv6_OUT
               name WAN_OUT
           }
       }
       pppoe 2 {
           default-route none
           dhcpv6-pd {
               pd 0 {
                   interface eth0 {
                   }
                   interface eth0.101 {
                   }
                   interface eth0.103 {
                   }
                   interface eth0.104 {
                   }
                   interface eth1.201 {
                   }
                   interface eth1.202 {
                   }
                   interface eth1.203 {
                   }
                   interface eth1.204 {
                   }
                   prefix-length 56
               }
               rapid-commit enable
           }
           firewall {
               in {
                   ipv6-name WANv6_IN
                   name WAN_IN
               }
               local {
                   ipv6-name WANv6_LOCAL
                   name WAN_LOCAL
               }
               out {
                   ipv6-name WANv6_OUT
                   name WAN_OUT
               }
           }
           ipv6 {
               address {
                   autoconf
               }
               enable {
               }
           }
           password xxxxxx
           user-id xxxxxx
       }
   }
}

 

 

USG-4P / USW-24-250W / USW-16-150W / USW-8 / 3x UAP-AC-IW / 3x UAP-AC-Pro / 2x UVC-G3-Dome / 2x UVC-G3-Micro / 2x UVC-G3 / CloudKey G2-plus
New Member
Posts: 27
Registered: ‎07-01-2014
Kudos: 5
Solutions: 1

Re: USG (4.4.xx) can't get any IPv6 from POST Luxembourg via PPPoE

Thanks David, that works for me, at least I do receive now an IPv6 address on my clients in the definded LAN. Next I have to figure out why I can't create IPv6 firewall rules in the controller.

Reply