[Snap] Setting up IPv6 on Mikrotik with PPPoE - no reply from IPv6 DHCP server

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] Setting up IPv6 on Mikrotik with PPPoE - no reply from IPv6 DHCP server

zenourn

271 posts

Ultimate Geek

Trusted

#172061 10-May-2015 15:13

Hi,

I have a Mikrotik RB2011 establishing a connection using PPPoE (via a Draytek Vigor 130 in full bridge mode, ADSL2+ link). Now that Snap offer static IPv6 addresses I thought I would give it a go and have been assigned my static block. However, I can't seem to get past the first step of receiving a reply from the IPv6 DHCP server and am curious if anyone has Snap and IPv6 working with a Mikrotik router and could share their relevant config? Config and details below. Thanks.

Mikrotik config (ROS 6.28, Snap PPP profile with IPv6 enabled, IPv6 DHCP client on PPPoE interface):

/ppp profile
add name=snap use-ipv6=yes

/ipv6 dhcp-client
add add-default-route=yes interface=pppoe-snap pool-name=snap-ipv6

Output (DHCP client gives is a status of error, debug logs show it is sending multiple solicits but never gets a reply):

/ipv6 dhcp-client> print detail
Flags: D - dynamic, X - disabled, I - invalid
0    interface=pppoe-snap pool-name="snap-ipv6" pool-prefix-length=64
      prefix-hint=::/0 status=error duid="000300014c5e0c32c7ed"
      add-default-route=yes use-peer-dns=yes

May/10/2015 02:46:29 dhcp,debug dhcp: discovering...
May/10/2015 02:46:29 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:29 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:29 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:29 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:29 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:29 dhcp,debug,packet dhcp: -> elapsed_time: 0
May/10/2015 02:46:29 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:29 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:29 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:29 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:31 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:31 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:31 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:31 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:31 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:31 dhcp,debug,packet dhcp: -> elapsed_time: 2
May/10/2015 02:46:31 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:31 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:31 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:31 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:31 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:31 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:31 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:31 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:31 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:31 dhcp,debug,packet dhcp: -> elapsed_time: 3
May/10/2015 02:46:31 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:31 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:31 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:31 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:33 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:33 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:33 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:33 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:33 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:33 dhcp,debug,packet dhcp: -> elapsed_time: 4
May/10/2015 02:46:33 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:33 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:33 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:33 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:33 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:33 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:33 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:33 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:33 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:33 dhcp,debug,packet dhcp: -> elapsed_time: 4
May/10/2015 02:46:33 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:33 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:33 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:33 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:34 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:34 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:34 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:34 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:34 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:34 dhcp,debug,packet dhcp: -> elapsed_time: 5
May/10/2015 02:46:34 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:34 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:34 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:34 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:35 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:35 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:35 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:35 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:35 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:35 dhcp,debug,packet dhcp: -> elapsed_time: 6
May/10/2015 02:46:35 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:35 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:35 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:35 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:36 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:36 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:36 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:36 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:36 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:36 dhcp,debug,packet dhcp: -> elapsed_time: 7
May/10/2015 02:46:36 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:36 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:36 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:36 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:36 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:36 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:36 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:36 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:36 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:36 dhcp,debug,packet dhcp: -> elapsed_time: 7
May/10/2015 02:46:36 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:36 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:36 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:36 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:37 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:37 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:37 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:37 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:37 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:37 dhcp,debug,packet dhcp: -> elapsed_time: 9
May/10/2015 02:46:37 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:37 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:37 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:37 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:38 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:38 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:38 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:38 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:38 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:38 dhcp,debug,packet dhcp: -> elapsed_time: 9
May/10/2015 02:46:38 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:38 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:38 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:38 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:39 dhcp,debug,packet dhcp: send pppoe-snap -> ff02::1:2%22
May/10/2015 02:46:39 dhcp,debug,packet dhcp: type: solicit
May/10/2015 02:46:39 dhcp,debug,packet dhcp: transaction-id: 1a8bcd
May/10/2015 02:46:39 dhcp,debug,packet dhcp: -> clientid: 00030001 4c5e0c32 c7ed
May/10/2015 02:46:39 dhcp,debug,packet dhcp: -> oro: 23
May/10/2015 02:46:39 dhcp,debug,packet dhcp: -> elapsed_time: 10
May/10/2015 02:46:39 dhcp,debug,packet dhcp: -> ia_pd:
May/10/2015 02:46:39 dhcp,debug,packet dhcp:    t1: 1800
May/10/2015 02:46:39 dhcp,debug,packet dhcp:    t2: 2880
May/10/2015 02:46:39 dhcp,debug,packet dhcp:    id: 0x10
May/10/2015 02:46:39 dhcp,debug dhcp: initial send failed

fe31nz

1233 posts

Uber Geek

#1301577 10-May-2015 19:36

Snap gives you a /56 prefix when you have a static address. I am not familiar with Mikrotiks, but "pool-prefix-length=64" seems wrong - try changing it to "pool-prefix-length=56".

zenourn

271 posts

Ultimate Geek

Trusted

#1301613 10-May-2015 20:49

fe31nz: Snap gives you a /56 prefix when you have a static address. I am not familiar with Mikrotiks, but "pool-prefix-length=64" seems wrong - try changing it to "pool-prefix-length=56".

Thanks, but from my understanding the "pool-name" defines the IPv6 pool that is created on the router and "pool-prefix-length" defines the size of the prefixes that are given out from this pool. From the manual:

http://wiki.mikrotik.com/wiki/Manual:IPv6/DHCP_Client

"Prefix length parameter that will be set for IPv6 pool in which received IPv6 prefix is added. Prefix length must be greater than the length of received prefix, otherwise prefix-length will be set to received prefix length + 8 bits."

I just tried on a Snap UFB (Enable) and Snap VDSL connections both with Mikrotik routers and it worked perfectly:

Flags: D - dynamic, X - disabled, I - invalid
0    interface=pppoe-snap pool-name="snap-ipv6" pool-prefix-length=64 prefix-hint=::/0 status=bound
      prefix=2406:e007:xxxx::/48 expires-after=23h52m46s duid="00030001000c42be0acf"
      add-default-route=yes use-peer-dns=yes

So Mikrotik & Snap IPv6 definitely can work but for some reason not working over my Draytek PPPoE bridge. I'll need to determine if due to the Draytek Vigor 130, the ADSL2+ connection (I am rural and on a RBI-upgraded exchange), or something wrong with my Snap account configuration.

fe31nz

1233 posts

Uber Geek

#1301643 10-May-2015 22:54

Have you checked that IPv6 packets are being received at all with the bridge? You should see the router advertisements at the very least - nothing will work if you do not see them.

MattR

224 posts

Master Geek

#1302070 11-May-2015 16:21

Are you blocking UDP port 546? that will break DHCPv6.

    ;;; ipv6 DHCP PD
      chain=input action=accept protocol=udp in-interface=snap-pppoe
      dst-port=546 log=no log-prefix=""

zenourn

271 posts

Ultimate Geek

Trusted

#1302104 11-May-2015 17:10

MattR: Are you blocking UDP port 546? that will break DHCPv6.

    ;;; ipv6 DHCP PD
      chain=input action=accept protocol=udp in-interface=snap-pppoe
      dst-port=546 log=no log-prefix=""

Not blocking UDP port 546 (and config works on two other Snap connections, one UFB other VDSL).

Today I ran a packet sniffer and filtering for MAC protocol 86dd (IPv6) over the pppoe-snap interface I don't see any incoming IPv6 (both when a Draytek Vigor 130 and Draytek Vigor 120 are used for the PPPoA to PPPoE bridge; IPv6 should be passed over the bridge without issue). I also setup the Vigor 130 as a router with a DHCPv6 client and not a single IPv6 packet received. I'm getting suspicious IPv6 is being dropped somewhere and will try a Frtitzbox - I expect that won't work with IPv6 either.

MattR

224 posts

Master Geek

#1302127 11-May-2015 17:46

Yeah sounds like your modem is the problem. I'm running mine on VDSL with a ZyXel P-870H-51A V2, and also on UFB.

zenourn

271 posts

Ultimate Geek

Trusted

#1303182 12-May-2015 22:50

I hooked up a Fritzbox 7340 and no IPv6 either. Fritzbox log shows "Could not establish IPv6 Internet connection: No response from DHCPv6 server (SOL)."

So no IPv6 on my ADSL2+ connection. I will see if Snap can sort it out.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

Zeon

3918 posts

Uber Geek

Trusted

#1323245 12-Jun-2015 10:32

Hey guys,
I've just got the Mikrotik hAP LITE plugged into a Draytek Vigor 2710 in full bridge (PPP pass thru) mode. Was really painless to get working for IPv4 and PPPoE but now I'm looking to setup IPv6. Could I ask for a brief set of steps to get this working? I had IPv6 at another location on Unleash VDSL2 and I think I enabled one setting through the Mikrotik UI and it just worked so never looked into it further.

Thanks

Speedtest 2019-10-14

Zeon

3918 posts

Uber Geek

Trusted

#1324411 14-Jun-2015 13:02

Ah I got it to work. Instructions

Install/enable the IPv6 package
Go to IPv6->DHCP client and add a pool, defualt settings are fine give it a name like IPv6 and set the size - SNAP is 56

Then it just worked giving my computers address via SLAAC! You may need to go to DHCPv6 server as per this video
https://www.youtube.com/watch?v=NG0AvAkwHp0

Speedtest 2019-10-14

zenourn

271 posts

Ultimate Geek

Trusted

#1373449 24-Aug-2015 23:53

Just an update for the archives - there was a fault with certain Chorus DSLAMs which broke IPv6 with PPPoA. A patch is being rolled out now:

http://list.waikato.ac.nz/pipermail/nznog/2015-August/021832.html

Just tested and this has been fixed on the exchange I'm connected to. I worked around the bug by using VPI/VCI 0/110 VLAN 10 and 1483 Bridged IP LLC. This is a better config anyway as then supports PPPoE directly and no need for the PPPoE to PPPoA bridge.

bonkas

314 posts

Ultimate Geek

#1415628 28-Oct-2015 17:24

I wonder if this affected PFsense config's also.. I had nothing but issue after issue with IPv6 - When it was "working" many websites would time out and refuse to load at all.

fe31nz

1233 posts

Uber Geek

#1415820 28-Oct-2015 22:17

bonkas: I wonder if this affected PFsense config's also.. I had nothing but issue after issue with IPv6 - When it was "working" many websites would time out and refuse to load at all.

Your symptoms are exactly those of an MTU problem. IPv6 does not automatically fragment packets, but relies on Path MTU discovery to set the MTU for each connection. Packets that are too long are dropped. For Path MTU Discovery to work, all the routers involved must allow certain ICMPv6 packets, so that notice of packets dropped for being too long gets back to the source of those packets.

When the connection is via PPPoE, this can cause MTU problems that are not detectable by Path MTU Discovery. This is due to the overhead bytes used for the PPPoE connection reducing the maximum MTU available, but the router doing that not sending the appropriate ICMPv6 packets when it sees oversize packets being sent over PPPoE. It is a common problem.

Initially, on my fibre connection, I had to have my router (Ubiquiti EdgeRouter Lite) set to send a smaller MTU value in its RA (Router Advertisment) packets, so my IPv6 connections worked properly despite the PPPoE problems. Later, Snap seems to have changed the router I was connected to for a Juniper one that does PPPoE better and it allowed me to use the overcommitted bandwidth that Chorus provides. I was able to configure the PPPoE connetion for the full 1500 bytes of a normal Ethernet connection and that fixed all the MTU problems.

Not all routers will allow you to use larger packets with PPPoE, but I think the FritzBoxes do it automatically if the router they are connected to allows it. Hopefully, your router will allow 1500 byte packets over PPPoE if you configure it right and that should solve your IPv6 problems. If not, try forcing the use of a reduced MTU in the RA packets.

Ragnor

8223 posts

Uber Geek

Trusted

#1417075 30-Oct-2015 15:12

zenourn: I worked around the bug by using VPI/VCI 0/110 VLAN 10 and 1483 Bridged IP LLC. This is a better config anyway as then supports PPPoE directly and no need for the PPPoE to PPPoA bridge.

Wait can we use IPoE / 1483 Bridged IP LLC now if on Chorus equipment on any ISP or only on ISP's supporting it?

zenourn

271 posts

Ultimate Geek

Trusted

#1417289 30-Oct-2015 19:28

Wait can we use IPoE / 1483 Bridged IP LLC now if on Chorus equipment on any ISP or only on ISP's supporting it?

I'm no expert on this, but I think EUBA is the primary requirement, which is the case for most connections these days (although BUBA is still around due to Conklin's, etc).