2.1.2 & 2.1.3 apinger and gateway monitoring broken!



  • Hello

    I have a gateway towards my ISP IPv4 DHCP no problem.
    I also have a OpenVPN GW configured towards my VPN supplier, i run all my incoming / outgoing traffic over this one.
    Since upgrading to 2.1.2 and 2.1.3 the apinger gw monitoring has not worked at all! There is no definition in the apinger.conf for my OpenVPN gateway.

    Have tried the solution proposed in BUG#3607 but that doesn't help.

    Any ideas please, doesn't feel good to have to run an old outdated version because of this not working!



  • I have had this issue since 2.1. The only solution i have found is to set the gateway manually in the routing settings.

    I get these errors in the systemlog:

    May 11 11:25:48 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt1).
    May 11 11:25:48 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt1).
    May 11 11:25:48 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt1).
    May 11 11:25:48 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt1).
    May 11 11:25:48 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt1).

    Somehow the system can't figure out the proper gateway, but the openvpn connection is up and running and
    the gateway is passed correctly in the initialization.



  • I have no problem with this in 2.1-RELEASE (amd64)
    And everything works fine "functionality wise" in 2.1.2 & 2.1.3 but apinger GW monitoring doesn't work at all.



  • Hi All,

    I would like to agree with the above.

    I am unable to utilise policy based routing only for my OpenVPN client gateway. I can use it for all other gateways.

    From what I can see, the interface for the OpenVPN client gets an IP address (ifconfig shows the expected IP and gateway), and if I do not use "route-nopull" in the advanced config, I can happily send data via the default routing table. However, if I set the Firewall rule to use my OpenVPN gateway, the firewall blocks traffic handled by that rule – NOTE: I have the System > Advanced > Miscellaneous > Gateway Monitoring > "Skip rules when gateway is down" checked, so this is expected behaviour, provided that the gateway really is down...

    My systemlog also shows:

    Jun 24 23:08:58   php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt4).

    I am running 2.1.3-RELEASE (i386).

    Has anybody else come across this?

    -dan



  • Hello

    This is sadly still true for 2.1.4.

    2.1.4-RELEASE (amd64)
    built on Fri Jun 20 12:59:50 EDT 2014
    FreeBSD 8.3-RELEASE-p16


Log in to reply