[SOLVED] The package manager is not responding

[tre4bax]

agh1701 (should that not be ncc?) 

Try this and see if you get the same as me.  On you workstation ping 130.225.254.116.  Then try the same through the opnsense diagnostic tool.  Go into ping and ping 130.225.254.116.

If yours is the same as mine you can ping that server from a machine connected to the network but you cannot ping it from the firewall/router itself.

[agh1701]

Franco how a bout an other address with an up address in it will that work?

[agh1701]

http://207.244.94.80/opnsense
Worked!

[agh1701]

There is still something wrong.  My dashboard says 18.7.7 however, my firmware page says the latest firmware is 18.7.6.  I also noticed that when I did the upgrade there was no upgrade splash telling me what is new only packages.

[tre4bax]

Not for me.  My Shell or anywhere else on the opnsense device itself cannot pin 207.244.94.80, or pretty much any other address.

I can happily ping 1.0.0.1 because this appears in my routing table courtesy of having a gateway defined with the DNS entry.

On this basis then if I go ahead and add a static route to the update cache I should be able to make it work.

[tre4bax]

And now I have it working by having put in a static route to 212.32.245.0/24.  Obtained by doing an opnsense-update -M then pinging the route of the address returned.

I have no understanding of why I should have to do this and the default route just does not work locally on the device.  It makes no sense.

For now at least it works

[crazie]

If this is an issue related to DNS, please explain why you are able to upgrade from console WITHOUT any issues at all. This is clearly a webgui update system issue, not related to DNS or anything else.