Monitor IP blank after disabled and enabled back interface

Started by niex, July 28, 2016, 05:15:48 PM

Previous topic - Next topic
Hi all,

I set up WAN gateway using external IP as the monitor IP. I did a test by disabling and enabling back the WAN interface. However, the status of the gateway is not turn back to online instead is stated as pending. Also I did noticed the monitor IP becomes blanks. Did anyone else facing the same issue? Is it a bug on this version?

Hi there,

What version are you running? :)

This is caused by JavaScript disabling the elements, which was eventually removed. There's 16.1.20 and 16.7 available, these should work?

Lastly, "pending" means the gateway monitor wasn't ready to reload, can you restart it from Services: Diagnostics and see if it comes back? Ticket is here:

https://github.com/opnsense/core/issues/1016


Cheers,
Franco

Hi,

I am currently using version 16.7 R2.

Yes, restart the apinger service make the gateway to come back online again. But should it come back automatically after enabled back the interface without the need to restart apinger?

Apinger is restarted, but the interface isn't ready for apinger to reconfigure it. It's a bit complicated, but the gist is that apinger cannot reconfigure again after startup so it misses the pending interface until it is next restarted. We're going to fix this for 17.1, though it's been an issue for many years and not easy to fix.

Can you let me know how to reproduce blanking the monitor IP? I'm doing something wrong here, unable to reproduce.


Thanks,
Franco

Hi,

Let say I have one interface with static IP 192.168.1.100 and the gateway IP is 192.168.1.1. I set the gateway to have monitor IP 8.8.8.8. I did the testing by disabled the interface and enabled back again, checked the status from Status:Gateways. From this menu, I can see that the monitor IP will become blank and the status will become pending.