Internode Native IPv6, No Address?

ingmthompson

Did you manage to get Internode IPv6 working with pfSense? I'm struggling to get "Track Interface" working on the LAN interface. Ping from the default interface to Google DNS works, but it appears that the /56 is being assigned to the WAN interface rather than LAN.

Toje

Huh. I set it to DHCPV6 with the request of a prefix only. I request it over v4.

I then have LAN set to a static address in my /56 range, e.g ::50 and its worked with other systems on IPV6 static on my servers.

RA is my problem that's left.

ingmthompson

I've tried statically assigning an address to the LAN interface, but it's still not working. For some reason the LAN link-local address is stuck on fe80::1:1, which I'm pretty sure shouldn't be the case. I can get an IPv6 ping out from the WAN interface (which actually appears to be the dynamic /64 upon closer inspection), that's about all that I can make work properly.

RA is also giving me headaches, but I'd say I'm better off crossing that bridge when I come to it.

Toje

Well I get a dynamic /64 on my WAN interface as well, once the dynamic address is assigned it seems to use that to route my /56 that's static on the LAN interface.

ingmthompson

My settings are as follows for DHCP6 on the WAN interface, can you confirm that yours are the same?

Use IPv4 connectivity as parent interface: Yes
Request only a IPv6 prefix: Yes
DHCPv6 Prefix Delegation size: None
Send IPv6 prefix hint: No

Toje

I have DHCPv6 Prefix Delegation size set to 56

Toje

I also notice I have a WAN V6 address of fe80::20c:29ff:fe65:5f35%em1

ingmthompson

My WAN v6 address is fe80::225:90ff:fe91:d2e6%em0, which seems more or less correct. This "track interface" thing on the LAN interface should Just Work, but instead it's driving me mental. It gives me an option for inputting a hexadecimal prefix ID between 0 and ff, but I have no idea what it should be set to. Maybe I need to go down the static configuration route after all.

Toje

Sigh, I just tested it for shit n giggles, its not working anymore either grown

ingmthompson

What address are you getting for your IPv6 gateway? I'm seeing fe80::224:14ff:fe9a:9700, which seems a bit suspect.

Toje

What I got in my last post. fe80::225:90ff:fe91:d2e6%em0

Toje

dhcp6c[52181]: client6_recvadvert: XID mismatch

Now this on restart.

Honestly I am lost now, it was working.

Rezin

Same boat. Had it working yesterday, but no go today. Maybe it's on Node's end? Although I can't see any advisories which would suggest that. I might give support a call tomorrow.

doktornotor

@ingenieurmt:

My WAN v6 address is fe80::225:90ff:fe91:d2e6%em0, which seems more or less correct.

These are link-local addresses -> definitely NOT correct.

Toje

Looking over my logs, I have a feeling something's gone wrong on the nodes end.

It was not link local in the past.

Rezin

I haven't called support yet, but in the meantime I thought I'd try disabling IPv6 in the Node CP, and will enable it again later tonight… might kick something on their end into working differently.

Toje

As silly as it sounds, try changing your MAC,

Rezin

Tried setting it all up again today… still doesn't work 100%. I can use Diagnostics > Ping to google.com using IPv6, and get replies... but nothing on the LAN side can access remote IPv6 addresses.

Toje, are you seeing entries like these in your System Log?

php: rc.filter_configure_sync: The command '/sbin/route change -inet6 default fe80::224:14ff:fe9a:9810' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::224:14ff:fe9a:9810: Network is unreachable'

php: rc.newwanip: The command '/sbin/route change -inet6 default fe80::224:14ff:fe9a:9810' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::224:14ff:fe9a:9810: Network is unreachable'

IPv6
Destination	Gateway					Flags	Refs	Use	Mtu	Netif	Expire
default		fe80::224:14ff:fe9a:9810%pppoe0		UGS	0	2146	1492	pppoe0

Similar to another thread here.

Edit: Seems to be working now, for some reason. ??? ;D

The settings I'm using:

WAN:

IPv6 Configuration Type: DHCP6
Use IPv4 connectivity as parent interface: Ticked
Request only a IPv6 prefix: Ticked
DHCPv6 Prefix Delegation size: 64
Send IPv6 prefix hint: Ticked

LAN:

IPv6 Configuration Type: Static IPv6
IPv6 address: 2001:44b8:xxx:yyyy:: (/64)

DHCP:

Enable DHCPv6 server on LAN interface: Un-ticked
Router Advertisements: Assisted (though I think it should be Unmanaged.. but I'll just leave it as is for the minute ;))

… and a few WAN and LAN firewall rules.

Edit 2: ugh, borked again, without any changes made.

razzfazz

@ingenieurmt:

Request only a IPv6 prefix: Yes
DHCPv6 Prefix Delegation size: None

That seems a bit odd; the first option says you only want a delegated prefix, but the second option says you don't want a prefix. Why do you think you want the first one, anyway?

razzfazz

@Rezin:

The settings I'm using:

WAN:

IPv6 Configuration Type: DHCP6

Request only a IPv6 prefix: Ticked

DHCPv6 Prefix Delegation size: 64

Send IPv6 prefix hint: Ticked

LAN:

IPv6 Configuration Type: Static IPv6

That, too, seems odd: You're requesting prefix delegation, but then you're not actually using the prefix information obtained via DHCP-PD but instead configure your prefix statically. Also, I thought the delegated prefix was supposed to be a /56, not a /64?!