WAN interface going down



  • Hi.

    I have really strange problem and I have no idea how to deal with it. So here is the thing..

    Our pfSense has 3 interfaces (WAN, LAN and DMZ). WAN and DMZ interfaces are bridged. To bridged interfaces there are connected some servers with public IPs assigned. One server is for videoconferencing demo environment.

    During test, after few minutes our video call gets disconnected. At the same time we are pinging 3 IP addresses:

    • IP of that server
    • IP of pfSense
    • IP of router, which is a gateway for our public IP network.

    So when that disconnect happens - both pfSense and server IP are unreachable. Router can be pinged all the time. So it points to problem with pfSense. And it's pfSense for sure, because when we plugged in that server directly to router - we didn't have any problem.

    What is more - during disconnect we were monitoring pfSense system status on display connected to pfSense machine and also from the LAN side. So pfSense didn't restart, it was working all the time and also from the LAN side it could be pinged all the time.

    So for me it looks like some kind of problem with either WAN interface or maybe with bridge?

    I've disabled aPinger on gateway, but it also didn't help….

    In System Logs > System > Gateway, it was showing this (before disabling aPinger):
    Nov 12 09:43:37 apinger: alarm canceled: WANGW(10.10.10.10) *** down ***
    Nov 12 09:43:01 apinger: ALARM: WANGW(10.10.10.10) *** down ***
    Nov 12 09:42:46 apinger: alarm canceled: WANGW(10.10.10.10) *** down ***
    Nov 12 09:40:50 apinger: ALARM: WANGW(10.10.10.10) *** down ***
    Nov 12 08:35:33 apinger: alarm canceled: WANGW(10.10.10.10) *** down ***
    Nov 12 08:34:58 apinger: ALARM: WANGW(10.10.10.10) *** down ***
    Nov 12 08:34:42 apinger: alarm canceled: WANGW(10.10.10.10) *** down ***
    Nov 12 08:32:47 apinger: ALARM: WANGW(10.10.10.10) *** down ***
    Nov 12 08:14:19 apinger: alarm canceled: WANGW(10.10.10.10) *** down ***
    Nov 12 08:14:03 apinger: ALARM: WANGW(10.10.10.10) *** down ***
    Nov 12 08:13:53 apinger: alarm canceled: WANGW(10.10.10.10) *** down ***
    Nov 12 08:12:59 apinger: ALARM: WANGW(10.10.10.10) *** down ***

    In System logs > System > General it's only something like this:

    Nov 12 09:43:56 php: rc.start_packages: Restarting/Starting all packages.
    Nov 12 08:43:54 check_reload_status: Starting packages
    Nov 12 09:43:54 php: rc.newwanip: pfSense package system has detected an ip change -> 172.30.201.1 … Restarting packages.
    Nov 12 09:43:54 php: rc.newwanip: rc.newwanip: on (IP address: 172.30.201.1) (interface: []) (real interface: ovpns1).
    Nov 12 09:43:54 php: rc.newwanip: rc.newwanip: Informational is starting ovpns1.
    Nov 12 08:43:51 check_reload_status: rc.newwanip starting ovpns1
    Nov 12 09:43:51 kernel: ovpns1: link state changed to UP
    Nov 12 08:43:51 check_reload_status: Reloading filter
    Nov 12 09:43:51 kernel: ovpns1: link state changed to DOWN
    Nov 12 09:43:50 php: rc.openvpn: OpenVPN: Resync server1 OpenVPN
    Nov 12 09:43:50 php: rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WANGW.
    Nov 12 08:43:47 check_reload_status: Reloading filter
    Nov 12 08:43:47 check_reload_status: Restarting OpenVPN tunnels/interfaces
    Nov 12 08:43:47 check_reload_status: Restarting ipsec tunnels
    Nov 12 08:43:47 check_reload_status: updating dyndns WANGW
    Nov 12 09:43:18 php: rc.start_packages: Restarting/Starting all packages.
    Nov 12 08:43:16 check_reload_status: Starting packages
    Nov 12 09:43:16 php: rc.newwanip: pfSense package system has detected an ip change -> 172.30.201.1 ... Restarting packages.
    Nov 12 09:43:16 php: rc.newwanip: rc.newwanip: on (IP address: 172.30.201.1) (interface: []) (real interface: ovpns1).
    Nov 12 09:43:16 php: rc.newwanip: rc.newwanip: Informational is starting ovpns1.
    Nov 12 08:43:14 check_reload_status: rc.newwanip starting ovpns1
    Nov 12 09:43:14 kernel: ovpns1: link state changed to UP
    Nov 12 09:43:14 kernel: ovpns1: link state changed to DOWN
    Nov 12 09:43:13 php: rc.openvpn: OpenVPN: Resync server1 OpenVPN
    Nov 12 09:43:13 php: rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WANGW.
    Nov 12 08:43:11 check_reload_status: Restarting OpenVPN tunnels/interfaces
    Nov 12 08:43:11 check_reload_status: Restarting ipsec tunnels
    Nov 12 08:43:11 check_reload_status: updating dyndns WANGW

    How can I debug what is happening? Can you guys help me with this?


Log in to reply