IPv6 default GW

vitafit

Hi,

simple question - simple issue as i thought. My Root-Server provider is offering a /64 subnet, which looks like this:
Subnet: 2001:4bf0:ffa0:00d3::0 /64
Gateway: 2001:4bf0:ffa0:1:beef::1

My pfSense is running on an ESXi - IPv4 is working perfectly. So i also enabled IPv6 and restart the ESXi. On my pfSense WAN interface i configured 2001:4bf0:ffa0:00d3::1 as the address. But i can't use the GW:
The following input errors were detected:

The gateway address 2001:4bf0:ffa0:1:beef::1 does not lie within one of the chosen interface's subnets.

I was trying to solve this via SSH:
route add -inet6 -net 2001:4bf0:ffa0:1:beef::0 -iface le0
route add -inet6 default 2001:4bf0:ffa0:1:beef::1

Also does not work:

[2.1.5-RELEASE][root@pfs01.xxx.com]/root(6): route add -inet6 default 2001:4bf0:ffa0:1:beef::1
route: writing to routing socket: Network is unreachable
add net default: gateway 2001:4bf0:ffa0:1:beef::1: Network is unreachable

I had the same problem on my IPv4-Network which i solved my making the GW-subnet known in the pfSense. Any idea on this one?

//Edit: Also tried using route add -inet6 -net 2001:4bf0:ffa0:1:beef:: -iface le0 as i was not sure about the zero in the end - same result…

JasonTracy

@vitafit:

Hi,

simple question - simple issue as i thought. My Root-Server provider is offering a /64 subnet, which looks like this:
Subnet: 2001:4bf0:ffa0:00d3::0 /64
Gateway: 2001:4bf0:ffa0:1:beef::1

If your subnet is 2001:4bf0:ffa0:00d3::0/64, then your Gateway is wrong. On a /64, the first 4 groups need to match. I expanded the addresses so you can see:

2001:4bf0:ffa0:00d3:0000:0000:0000:0000
2001:4bf0:ffa0:0001:beef:0000:0000:0000

See the issue?

vitafit

Hi Jason,

thanks for your response -yes that's something i am aware off so i talked to my ISP which told me no this is not an issue - the default GW is realy on that different subnet which of course totally sucks. I had the exact same issues with IPv4 - as there my default GW is on a different subnet than the IP-address i was trying to use. So i had to make the network known by the interface in order to use the gateway :(

So it seems that we have the same issue here…

JasonTracy

Can you share your IPv4 example info? Maybe we can figure out the solution based of what you already fixed.

vitafit

Sure, that's what i added to my config.xml in order to solve the same problem in IPv4:
<shellcmd>route add -net 85.14.2XX.0 -iface le0</shellcmd>
<shellcmd>route add default 85.14.2XX.129</shellcmd>

So my Interface has no GW set as i am doing this via the script because as i told before my public IPv4 is on a different subnet.

Thanks.

JasonTracy

Based off that, would this work?

<shellcmd>route add -6 -net 2001:4bf0:ffa0:1:: -iface le0</shellcmd>
<shellcmd>route add -6 default 2001:4bf0:ffa0:1:beef::1</shellcmd>

kroberts

While I wouldn't claim to be any sort of expert on ipv6, the clearest part of ipv6 to me is the routing.

The default route must be on the same subnet as the address. Any other configuration leads to a network without a router, which means local traffic only.

The way I see it, doing what you have been doing is essentially adding another network configuration on top of the same physical device, which means your existing ipv6 address will only be used for local traffic.