pfSense

Jim Pingle wrote:

There isn't any evidence of an actionable bug in pfSense yet. Keep the discussion on the forum for now.

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .

See Reporting Issues with pfSense Software for more information

I don't understand what I'm being asked to do here to possibly provide an "actionable bug". I have 5+ installs on the same ISP the ones with a dynamic IP have suddenly stopped working while the Static installs continue without issues. I've exhausted all other possibilities and it must be a pfSense issue. So, does this mean that you only accept a bug if it comes from an internal NetGate folks? And in order to get that done I need a support contract?

Please let me know.

If they suddenly stopped working without changing anything on the firewall the cause is unlikely to be in pfSense software -- but instead in the environment (e.g. Hyper-V) or ISP.

You're being asked to provide enough information to show that there is something pfSense can do to solve the problem -- that hasn't been done. Keep troubleshooting on the forum thread. At the very least, try it outside of Hyper-V (e.g. bare metal) and try a 2.5.0 snapshot.

Jim Pingle wrote:

If they suddenly stopped working without changing anything on the firewall the cause is unlikely to be in pfSense software -- but instead in the environment (e.g. Hyper-V) or ISP.

You're being asked to provide enough information to show that there is something pfSense can do to solve the problem -- that hasn't been done. Keep troubleshooting on the forum thread. At the very least, try it outside of Hyper-V (e.g. bare metal) and try a 2.5.0 snapshot.

I had already run a stripped down bare metal install (detailed in the forum post). However, I hadn't tried that install with the nightly build of 2.5. I've just done this with the latest (pfSense-CE-2.5.0-DEVELOPMENT-amd64-20210120-2350.iso) and the same issue is occurring, i.e., WAN IP 0.0.0.0. I can perfectly ping all internal IP's but can't even ping the modem ip @192.168.100.1.

Look, if you're convinced that it's not a bug, then I'll sign up for a support contract. But, having many installs under my belt and using this for many years, I really don't think this is in any way a configuration or hardware issue. Certainly it can be an ISP related issue (if they've modded the modem firmware). But, they won't even consider any of this their fault since any other router and singular PC can get to the internet.

So, please let me know how to proceed. If I need a support contract I'll do that. Certainly, I'm willing to contribute to this software development as I think it's a fantastic product.
Thanks,
Gus

A support subscription isn't all that relevant here, unless it's a configuration problem in pfSense software itself which it doesn't appear to be. They could maybe help you diagnose it a bit more, but if it's a problem in your environment or ISP then it's out of scope there.

Again, if it was working before and suddenly stopped without you making changes on your firewalls, it's highly unlikely there is a bug in the software that we could do anything about.

Keep talking it through on the forum for now.