Alternate gateway monitoring and IPv6
-
@GeorgePatches my ISP issues a
/64address to my gateway. AT&T typically issues/60but that's only if you use their gateway. In order to make it work on mine I have to set the DHCP client as/64and set Router Advertisement toManaged. But that limits you to one subnet getting a v6 block. -
@BigTulsa Oh, yes I see how that would work. I get a /56 delegation and I'm using more than one. I don't really have to have more than one, but I like it.
@JKnott said in Alternate gateway monitoring and IPv6:
What happens when you try a public address? I don't know what subnet is used when the WAN has only a link local address. Perhaps the LAN subnet? Give it a try and see what happens.
So with IPv6, point to point links don't need a public address. If you look at your laprop/desktop ip config you'll see that it lists your gateway as a fe80 address of some kind...usually.
However, monitoring a global address with a link-local is...not possible. So when I set the v6 gateway interface to monitor a public address it just doesn't go anywhere.
-
@GeorgePatches said in Alternate gateway monitoring and IPv6:
So when I set the v6 gateway interface to monitor a public address it just doesn't go anywhere.
Have you tried? You can ping from any interface and it works fine. Perhaps pfSense uses another interface when the WAN doesn't have a public address. I can't try here because I have a public address on WAN. Any public address on the pfSense box is routeable through the link local WAN address.
-
@JKnott I have tried and it doesn't work. :(
-
@GeorgePatches said in Alternate gateway monitoring and IPv6:
@JKnott I have tried and it doesn't work. :(
Then just turn off monitoring. It doesn't do much anyway.
-
@JKnott this is what I did initially until I found out about changing the monitoring address.
-
@GeorgePatches said in Alternate gateway monitoring and IPv6:
@BigTulsa OOOOO, you have an IPv6 address on your WAN, don't you? Mine only has a link-local and the IPv6 address goes on the LAN interface. How did you get an address on the WAN? I thought it only did prefix delegation.
If you're only getting a link local on WAN then it's likely your ISP is either not configured for IPv6, or, you don't have the DHCP6 server configured on the WAN interface properly. It can be very specific for different ISPs.
My interface details on the dashboard look like this:
-
@BigTulsa said in Alternate gateway monitoring and IPv6:
If you're only getting a link local on WAN then it's likely your ISP is either not configured for IPv6,
Some ISPs provide IPv6 with only a link local address on the WAN interface. On IPv6, routing is normally done via link local addresses.
-
@JKnott said in Alternate gateway monitoring and IPv6:
@BigTulsa said in Alternate gateway monitoring and IPv6:
If you're only getting a link local on WAN then it's likely your ISP is either not configured for IPv6,
Some ISPs provide IPv6 with only a link local address on the WAN interface. On IPv6, routing is normally done via link local addresses.
I'll take your word for that as my knowledge of IPv6 and how it works is limited for now.
-
@BigTulsa said in Alternate gateway monitoring and IPv6:
I'll take your word for that as my knowledge of IPv6 and how it works is limited for now.
Just a suggestion, look up like the beginning of a current Cisco CCNA course. They cover IPv6 stuff in great detail before they start to get into the specific Cisco stuff. Really good way to get spun up on all the settings.
