pfSense 2.5.1 not recognizing my default ipv4 route

brianj2k

@gertjan said in pfSense 2.5.1 not recognizing my default ipv4 route:

@brianj2k said in pfSense 2.5.1 not recognizing my default ipv4 route:
@gertjan I know this is a delayed response
To what question ?

To your response to the original poster... I thought that was obvious...

@brianj2k said in pfSense 2.5.1 not recognizing my default ipv4 route:

but making pfSense unusable to "solve" the problem is actually more of a pfSense issue.

A developer should have that ISP connection at hand so the situation can get analyzed.

I find this to be an odd response. I do lots of development without the assistance, or knowledge, of my ISP. I think you may be a bit naive to think that every developer has access at that level to their ISP.

Gertjan

@brianj2k said in pfSense 2.5.1 not recognizing my default ipv4 route:

I think you may be a bit naive to think that every developer has access at that level to their ISP.

I didn't say that. It's the other way around ;)
A pfSense developer would 'code around' the situation when it happens to his connection => issue solved - no need to contact the ISP.

Still, in this special case , I maintain my position : if an ISP really assigns a https://en.wikipedia.org/wiki/Link-local_address I would contact its client service just ones : to say 'good bye', as it's plain broken.
And that's a language every ISP will understand.

jimp

You are aware the issue linked upthread has a committed fix already which addresses the problem? We didn't have any problem solving it, there just hasn't been a release including the fix yet.

https://redmine.pfsense.org/issues/11806

You can apply the commit there with the system patches package if you need to use IPv4 link local gateways.