[Snap] VDSL + IPv6

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] VDSL + IPv6 - Possible?

breakaway

112 posts

Master Geek

#171955 6-May-2015 20:16

As in title. I'm trying to get this working with a pfSense + Snap VDSL. Modem is a Draytek Vigor DV130.

Looking back through these forums show a few people have gotten it working over UFB but can't find any reports of whether or not it works over VDSL.

Benoire

2798 posts

Uber Geek

#1299433 6-May-2015 20:43

My VDSL connection has IPv6 enabled, infact I have a /56 static IPv6 from SNAP right now. However, if this is related to getting IPv6 running through the modem you have then I have no idea, sorry!

eXDee

4032 posts

Uber Geek

Trusted

#1299451 6-May-2015 21:02

Put the Vigor 130 into full bridge mode with a VLAN 10 tag on it. If it can't tag in bridge mode, tag the pfsense interface. Establish the PPP session on pfsense, with v6 negotiation enabled (if thats an option like in openwrt). To get an IP range, you'll need to run DHCPv6 client. You'll then need to get IPs to clients, eg via a routing advertisement daemon.

JamesL

956 posts

Ultimate Geek
Inactive user

#1299498 6-May-2015 21:58

I don't think its possible to get ipv6 working with pfsense and Snap due to them doing things slightly different/weird. I spent ages trying to get it working to no avail, I've only had ipv6 working using victek's tomato usb build because he specifically added a flag for Snap ipv6 when Lorenco worked with him.

You can probably get it working by asking for a static ipv6 as it definitely wont work with dhcpv6

breakaway

112 posts

Master Geek

#1300448 8-May-2015 09:37

I already have my DV130 on full bridge mode with VLAN tagging handled by the modem. I just enter PPPoE creds into my pfSense and it comes up with the WAN IPv4 address. I've spent some time playing around with it and can't quite get it receive an IPv6 address.

What should the "IPV6 type" be set at? Any advanced options I need to set?

fe31nz

1232 posts

Uber Geek

#1300706 8-May-2015 14:22

I am not familiar with pfSense, but having the option "Request an IPv6 prefix/information through the IPv4 connectivity link" selected looks wrong to me. Snap IPv6 is fully native using the IPv6 protocol only. It is fully dual-stack, with the IPv4 and IPv6 traffic running in parallel with each other and not interacting.

I think you may need to select the option "Only request an IPv6 prefix, do not request an IPv6 address" as I do not get an IPv6 address from Snap automatically on my Cisco 877 on the external interface - I had to configure it manually.

Pinkfish

49 posts

Geek

#1301540 10-May-2015 18:16

I've got Snap IPv6 working correctly on my PFSense box.

Hope this helps

breakaway

112 posts

Master Geek

#1301619 10-May-2015 21:06

Pinkfish: I've got Snap IPv6 working correctly on my PFSense box.

Pinkfish, is that VDSL or UFB? If its VDSL, can you say which modem you're using? I tried setting those exact settings on my pfSense and only got a link local address.

fe31nz: as I do not get an IPv6 address from Snap automatically on my Cisco 877 on the external interface - I had to configure it manually.

I called them up and got them to assign a static IPv6 -- I suppose I could try statically configuring IPv6, what is the IPv6 gateway address?

<<edit>> I tried to unticking the "Request a IPv6 prefix/information through the IPv4 connectivity link" but still ended up with a link local address.

Sharesies

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

fe31nz

1232 posts

Uber Geek

#1301640 10-May-2015 22:50

Try setting the prefix size to /56. That is what Snap allocates for static IPv6.

breakaway

112 posts

Master Geek

#1301642 10-May-2015 22:53

Tried it -- doesn't work -- my config is identical to the screenshot posted by Pinkfish. Care to throw me the IPv6 default GW?

fe31nz

1232 posts

Uber Geek

#1301662 11-May-2015 03:14

I just checked my Cisco 877, and it does not tell me what the default IPv6 gateway is - the "show ipv6 ro" command just lists ::0/0 as "via Dialer0, direct connected". So I ran "traceroute ipv6 google.com" and got this:

Tracing the route to google.com (2404:6800:4003:808::1004)

1 2406:E000:2801:2::1 92 msec 84 msec 52 msec
2 2406:E000:2800:4::1 116 msec 60 msec 72 msec
3 * * *
4 2406:E000:400::2 132 msec 124 msec 124 msec
5 2406:E000:400::3 96 msec 164 msec 104 msec
6 2001:4860::1:0:8604 124 msec
    2001:4860::1:0:8613 116 msec 148 msec
7 2001:4860::8:0:79A0 220 msec
    2001:4860::8:0:81AC 180 msec
    2001:4860::8:0:79A0 212 msec
8 2001:4860::8:0:8877 300 msec 284 msec
    2001:4860::8:0:96E9 308 msec
9 2001:4860::1:0:337F 300 msec 288 msec 260 msec
10 2001:4860:0:1::26F 316 msec 296 msec 288 msec
11 2404:6800:4003:808::10 244 msec 260 msec 284 msec

So the gateway is likely 2406:E000:2801:2::1, but as I am in Palmerston North and on ADSL, your gateway might be different. And routers often use the link-local IPv6 address for the next hop, rather than the global unicast address. A router may not even have a global unicast address - with IPv6, it is not necessary for it to be able to route packets. So I also ran a "show ipv6 neighbors dialer 0" command, and that showed one neighbour at FE80::200:F:FC00:0, which is going to be the gateway.

What you may need to do is set up so that you can capture the ICMPv6 traffic on you VDSL connection, then see what is in the Router Advertisement ICMPv6 packets. That will give you the definitive answer to what you need to set up for static configuration.

Bare in mind though, that Snap can later change how the IPv6 routers work to use a different gateway router by just adding a new one that is multicasting a RA packets with the same or higher "preference" value. Then the old router can stop multicasting RAs and when the lifetime it was putting in its RAs has elapsed, it can be shut down. This is one of the advantages of IPv6 networks - you can reconfigure them without the users needing to know, unlike with IPv4 routers.

breakaway

112 posts

Master Geek

#1302241 11-May-2015 20:07

Ok it's working. I set the WAN side as described in pinkfish's post, and then the LAN side to IPv6: Follow Interface an set the interface to follow to be my WAN interface.

Now I've got IPv6 connectivity -- thanks team.

JamesL

956 posts

Ultimate Geek
Inactive user

#1302250 11-May-2015 20:26

They must've fixed it recently as I had mine configured the same and could never get an ipv6 address

Good to know!

JamesL

956 posts

Ultimate Geek
Inactive user

#1302781 12-May-2015 13:49

On the LAN interface what'd you set the prefix ID to under Track IPv6 Interface?

Edit: NVM, had to restart the WAN interface for it to work. Left the prefix ID as 0 on the LAN interface.