17.1.6 - default gw missing / apinger won't start

[netranger]

Good morning guys!

I have a strange behavior after upgrading to 17.1.6:

It seems that my DHCP lease no more contains a default gateway I get my internal IP address as usual but default gateway is just empty. When I set a static IP and static default gateway on my client the connection works again. So in order to fix this I went to Services > DHCP > Server and in the "Gateway" field, which was empty, I did set the firewall IP (for example 192.168.1.1). And now after ipconfig /renew on the client, everything works again. I am not sure about the config of this field before my upgrade though... if this got deleted or the mechanics changed?

Another thing I noticed after the upgrade (not sure if this has something to do with this): The apinger Gateway Monitoring Daemon fails to start, it just stays red. Is there a log for this somewhere so I could get some information?

I updated from 17.1.3 with the bootstrap command because I wanted (needed) a clean installation because I originally came from the 17.1 beta version.

Best,
Net

[Taomyn]

Another thing I noticed after the upgrade (not sure if this has something to do with this): The apinger Gateway Monitoring Daemon fails to start, it just stays red. Is there a log for this somewhere so I could get some information?

Can't help on the rest of your post, but for this all I can say is that it's been like that for me since I started with v16 (now on v17.1.6), and I always have to start it manually after a reboot. I think it simply dies as it runs too soon after boot or errors (maybe as I use a VLAN's PPPoE, which seems to break no end of things) and never tries again which is probably kind of daft for a monitoring service.

[netranger]

how can you start it? when I click the play button to start the service manually, nothing happens.

[franco]

Hi netranger,

17.1-BETA should upgrade cleanly, or at least in the same way that opnsense-bootstrap would to 17.1.6

The apinger log is under System: Gateways: Log File.

I'm not aware of a change in DHCP, but apinger failing and a missing gateway suggest there is an issue with your config. What kind of IP config do you have for your WAN(s)?


Cheers,
Franco

[netranger]

Thanks for your feedback! I used the bootstrap command because I also had this issue:
https://forum.opnsense.org/index.php?topic=4916.msg20552

So now I checked the log and found something:

May 8 13:20:08   apinger: No usable targets found, exiting
May 8 13:20:08   apinger: Starting Alarm Pinger, apinger(27708)

Then I looked at the Gateway configuration. There is one entry with my router IP as "Gateway" and the same IP as "Monitor IP" which is correct... (192.168.1.1). But when I click to edit this gateway, the monitor IP field is empty, not sure if this is normal? So I typed 192.168.1.1 in the "Monitor IP" field and save and guess what - apinger starting again no idea why 

Cheers,

[Droppie391]

i may be mistaking but my setup is to monitor a remote server/gateway ip address as that would generate an alarm when the link goes down. using a local ip address would not which may be the reason why you cannot start the apinger service.

[netranger]

hmm no 192.168.1.1 in my case is not the "local" firewall IP. It is the IP of my default gateway, the remote IP if you will. So it makes sense that this is monitored.

No idea what it was however.

[jan]

I do see the same symptoms after upgrading to 17.1.7 (I skipped 17.1.6):

 - The default gateway is no longer sent to the DHCP clients
 - the apinger service does not start

The respective field for the gw is empty, but it was so before the upgrade, so the indeed the mechanics changed. Setting it explicitly remedied the problem. I would expect that this should happen to quite a lot of users.

(Regarding the apinger, I did not yet check any details, it does not seem to impact me at  the moment.)

[franco]

Do you guys have a default gateway set in System: Gateway: Status?

[geofflowemn]

I'm having the exact same issue on a 16.7.x firewall I upgraded to 17.1.8 today.

Same log messages and apinger is red and won't start.

[JohnDoe17]

I'll add my voice to the chorus - I'm having the same issue.

The entry called "WANGW" is marked as "(default)" in System:Gateways:All.

But there is no such indication in System:Gateway:Status.

Is that what you mean, Franco?

Btw, I also have other Gateways defined too.

[JohnDoe17]

Any ideas, Franco?

[jan]

Do you guys have a default gateway set in System: Gateway: Status?

I do have an Entry in System: Gateways: Status called "WANGW" with a status of "pending"

And on this page in the upper left, there is the red "stopped" sign for the apinger Service

[jan]

Regarding the apinger, there is a workaround as per this post:
  https://forum.opnsense.org/index.php?topic=5196.msg21689#msg21689
which is to edit the WAN Gateway settings (System: Gateways: All) without changing anything.
It works for me on 17.1.8

Whether or not this remedies the DHCP Gateway problem, I cannot say, as I did not test it.
Maybe someone with more insight into OPNSense can see the connection between the two symptoms?

[remd]

Also the default gateway monitoring has to be enabled (uncheck disable gateway monitoring) for Apinger to work - solved it for me.