/60 on WAN, /63 on LAN

Derelict

You are probably actually getting a /59 from Comcast which is pretty much nonsensical.

This seems familiar to me. I think they have another modem that doesn't exhibit that issue.

Turn on the debug logging options in the WAN DHCP configuration and search the DHCP system logs for command dhcp6c and see what is actually happening.

deet

Thank you — that helped me find this:

https://forum.netgate.com/topic/101581/comcast-business-56-fails-60-works-but-delegates-63s

This is exactly my scenario. I have a Cisco modem instead of a Netgear, and I have one static IPv4 address, so I can't go to bridge mode.

In the DHCP logs, it says "create a prefix" and then show a /59.

Not optimistic for a resolution at the moment.

johnpoz

While a /59 is borked for the prefix, why wouldn't the tracked prefix on your lan be /64? Why would it be a /63 that doesn't make any sense...

It should be the /64 out of that /59 via the prefix id you used 0, 1, 2 etc..

is there something odd that causing a failure of the math when the prefix is not normal /60, 56 /48 etc.

Derelict

There is room for improvement where the delegation setting does not match the delegation received.

But that comcast situation is simply broken.

johnpoz

ah.. So your asking for /60 and they give you /59 and the screws up the math to figure out the tracked..

Derelict

Yeah something gets off by a bit.

johnpoz

So can he not just pick /59 in the dropdown for what he is asking for - or does it then give him /58 or some oddness like that.

Derelict

I can't remember. I think if a /59 is requested there is no delegation received or something. Totally hosed.

johnpoz

Yeah that would be borked - just setup a HE tunnel and be done with all this ISP lack of understanding would be my suggestion..

JKnott

@derelict said in /60 on WAN, /63 on LAN:

You are probably actually getting a /59 from Comcast which is pretty much nonsensical.

It may be unusual, but there's nothing wrong with it, as it will provide 32 /64s. With my ISP, I can select anything between a /64 and /56.

johnpoz

I think the problem is asking for /60 and getting /59..

If you ask for /59 do you get a /58?

deet

@johnpoz said in /60 on WAN, /63 on LAN:

Yeah that would be borked - just setup a HE tunnel and be done with all this ISP lack of understanding would be my suggestion..

Does Netflix still block He.net?

deet

@johnpoz said in /60 on WAN, /63 on LAN:

I think the problem is asking for /60 and getting /59..

If you ask for /59 do you get a /58?

I don’t have /59 as an option in the drop-down. I suppose I could try configuring it manually.

johnpoz

sure its there..

Where are you not seeing that as an option?

deet

@johnpoz perhaps that’s not available on this 32-bit system running 2.3.4.

johnpoz

dude... If your running old, you need to state that.. Why would you not be running current?

JKnott

@johnpoz said in /60 on WAN, /63 on LAN:

dude... If your running old, you need to state that.. Why would you not be running current?

There's also a setting in newer versions that prevent pfSense from releasing the prefix for something as trivial as disconnecting/reconnecting the WAN Ethernet connection. Until that setting appeared, I had to occasionally update my DNS AAAA records with the new addresses.

deet

@johnpoz 2.3 is current for 32-bit systems. It’s not a factor, except in the UI, which is a factor only because of the need for a workaround, which is just as feasible in a manual configuration. Forget I mentioned it.

johnpoz

No 2.3.5p2 is current for 32 bit.. not 2.3.4

Which not only all the pfsense changes that have happened in the 4 different releases your behind

.4p1
.5
.5p1
.5p2

Your also behind be the base changes to freebsd, 2.3.4 is 10.3p17 while current on 2.3.5p2 is p26

I just do not get why anyone be behind on updates to their freaking firewall.. If your hardware can only run 32bit - guess what its time for an upgrade!!!

deet

@johnpoz for what it's worth, when i was asking the firewall to check for updates, it was telling me it was on the current version. If it puts your mind at ease, I have downloaded and installed the latest version separately. The issue persists.

The firewall otherwise meets the performance requirements and is stable. Unless this issue is addressed on a 64-bit system, I see no reason to replace the equipment.

In fact, none of this seems relevant to the thread.

Asking for a /59 delegation through the GUI has not helped. I've cleared the DUID. The messages in the logs are effectively the same. The consensus seems to be that this is errant behavior by the Cisco CPE from Comcast, and there seems to be no stable resolution, except to ask for different CPE from Comcast, which I can do next week.

Thanks to everyone for having a look.