IPV6 - pfsense behind BT Hub

stephenw10

Indeed, BT don't usually give you a WAN IP just a Prefix. That's exactly what I see on my BT connection.

But unlike the OP I am using pfSense to get that prefix, he is using the BT Hub router. I am setting up a PD in that edge pfSense device to pass a /60 to my inner pfSense device. He is just configuring it statically on pfSense with no way to tell the BT Hub about that route.

Steve

Jid

@JKnott
Will try the Capture and see what i find
Regards

stephenw10

Is there any ability to add routes and gateways in the BT Business hub?

Jid

@stephenw10

Yes exactly ,but i was expecting the BT hub to give Pfsence an ip in the 2a0X:xxxx:xxxx:xx00:: /64 but it wasnt but gave it a fe80:: ?? will try to keep this as fe80:: and then use the /64 from the BT wan range in the LAN ,BUT that will still pose the issue of the BT box knowing how to get to this /64.

Jid

@stephenw10
Will look into this by weekend,so set a static route(BT hUB) for the /64 to the pfsense WAN (fe80::)??

stephenw10

Yes I would expect that to work. Odd that it doesn't assign the pfSense WAN a routable v6 IP though, it's set to DHCPv6? I assume other devices connected to the hub do get a v6 IP in that /64?

JKnott

@stephenw10 said in IPV6 - pfsense behind BT Hub:

he is using the BT Hub router

I didn't see that. In that case prefix delegation won't work. He wants to put the modem in bridge mode. With it in gateway mode, only devices connected directly to it will get an address.

JKnott

@Jid said in IPV6 - pfsense behind BT Hub:

@stephenw10

Yes exactly ,but i was expecting the BT hub to give Pfsence an ip in the 2a0X:xxxx:xxxx:xx00:: /64 but it wasnt but gave it a fe80:: ?? will try to keep this as fe80:: and then use the /64 from the BT wan range in the LAN ,BUT that will still pose the issue of the BT box knowing how to get to this /64.

If that modem is in gateway mode, you can't put pfSense behind it and expect it to work properly. The pfSense WAN interface should get an address, but no prefix for the LAN. Every IPv6 capable device will have a link local fe80 address, no matter what it's connected to. That does not come from the ISP. It's often derived from the MAC address.

Jid

@JKnott
"With it in gateway mode, only devices connected directly to it will get an address". That is the case here .
The Probem is HOW do I get Devices on LAN side of Pfsense(connected directly to BT hub) to be able to route out in ipv6.

Jid

@stephenw10

Yes they do in the 2a0X:xxxx:xxxx:xx00:: range, however in the pfsense WAN(directly connected to LAN of BT Hub) its showing in the fe80:: range.

stephenw10

Some sort of route on the BT Hub, static or added via a PD.

Or put the hub in modem mode and just use pfSense directly.

I know the Business hub used to do something funky with static IPv4 subnets though that caused problems with that.

stephenw10

What is the pfSense WAN set to for IPv6? Or what was it set to before you set it statically?

If dhcpv6 doesn't work try SLAAC.

Steve

Jid

@stephenw10
DHCPV6 it gets fe80:: range , Static applied 2a0X:xxxx:xxxx:xx00:: /64 to match the 2a0X:xxxx:xxxx:xx00:: on the BT hub.

Jid

@stephenw10
Just tried SLAAC and getting this fdaa:bbcc:ddee:0:215: is that good.
But i cant access any Node to test now .

stephenw10

If other clients connected to the Hub do get an IPv6 IP as expected, what are they set to?

That address with SLACC is not any better really.

Jid

@stephenw10

Thanks ,Stv unfortunateley no device is currently connected to LANof BT hub ,apart from Pfsense.

Jid

@Jid
Tried DHCPv6 now getting this fdaa:bbcc:ddee: ?
For the LAN side what should it ? Statics? with DHCPv6 active?

stephenw10

I expect dhcpv6 to pull an routable v6 IP from a /64 withing the /56 BT are delegating to you.

I think you probably need to confirm a laptop connected to the Hub is getting that before going further here.

Steve

Jid

@stephenw10

BT Hub IPv6 status:
Enabled

IPv6 network status:
Enabled

IPv6 WAN details
Global unicast address:
2a00:xxxx:xxxx:x801:86a1:d1ff:fea1:f0dd

Global unicast prefix/length:
2a00:xxxx:xxxx:x801::/64

Link local address:
fe80::86a1:d1ff:fea1:f0dd

Remote link local address:
fe80::1e6a:7aff:fe68:f00

DNS:
Not available

IPv6 LAN details
Global unicast address:
2a00:xxxx:xxxx:x800:86a1:d1ff:fea1:f0df

ULA prefix / length:
fdaa:bbcc:ddee::/64

Link local address:
fe80::86a1:d1ff:fea1:f0df

Pfsense Status:
WAN : fdaa:bbcc:ddee:0:215:5dff:feb8:ea10 9 (DhcpV6)
LAN: 2a00:xxxx:xxxx:x802:87a1:d1ff:fea1:1000 /64 (Static)
Dhcpv6 server (enabled)
Range: 2a00:xxxx:xxxx:x802::100 to 2a00:xxxx:xxxx:x802::250 (PC are getting this range)
RA: RouterMOde Assisted.
Priority Normal
DNS Config. : 2001:4860:4860::8888

Is any thing unusual here?

Jid

@stephenw10

Thanks will try this later as its remote site .