Apinger could not resolve address?



  • I'm running 2.25 release. My original nic seems to have died to I used the excuse to drop my hdd into another box, reconfigured it, and was off. Now, every couple hours or so, it blows up on me, and the net dies until I reboot.

    Last 50 system log entries
    May 8 21:05:33 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:34 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:35 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:36 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:37 apinger: alarm canceled: WAN_DHCP(173.49.250.1) *** down ***
    May 8 21:05:42 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:43 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:44 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:45 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:46 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:47 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:48 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:49 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:50 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:51 apinger: ALARM: WAN_DHCP(173.49.250.1) *** down ***
    May 8 21:05:51 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:52 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:53 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:54 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:55 apinger: alarm canceled: WAN_DHCP(173.49.250.1) *** down ***
    May 8 21:05:58 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:05:59 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:00 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:01 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:02 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:08 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:09 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:10 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:11 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:12 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:13 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:14 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:20 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:21 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:22 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:23 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:24 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:25 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:26 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:27 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:28 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:29 apinger: ALARM: WAN_DHCP(173.49.250.1) *** down ***
    May 8 21:06:29 apinger: alarm canceled: WAN_DHCP(173.49.250.1) *** down ***
    May 8 21:06:34 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:35 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:36 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:37 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:38 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:06:39 apinger: Could not bind socket on address(173.49.250.153) for monitoring address 173.49.250.1(WAN_DHCP) with error Can't assign requested address
    May 8 21:08:03 apinger: Starting Alarm Pinger, apinger(25275)



  • That is now a very old release of pfSense software. apinger was removed since then and replaced with "dpinger".
    Upgrade to the current release 2.3.4 for a start. Then you will be able to see if you have some other real underlying issue.



  • That's in the log. On the console I have this https://i.imgur.com/2C7G8ew.jpg followed by https://i.imgur.com/xWDI0Sn.jpg

    I'll try upgrading, makes me nervous though.



  • @nasomi:

    I'll try upgrading, makes me nervous though.

    It should, especially if you're a heavy user of packages on your current old version. The 2.3.x version tree made SIGNIFICANT changes to packages, including removing many that were out-of-date, not working properly anymore, or had been removed from FreeBSD ports.

    Make sure you read the upgrade notes before doing the upgrade!!!



  • Well, not so much.

    Last 50 Gateways Log Entries. (Maximum 50)
    Time Process PID Message
    May 8 22:45:41 dpinger WAN_DHCP 173.49.250.1: Alarm latency 0us stddev 0us loss 100%
    May 8 22:45:42 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:42 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:43 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:47 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 173.49.250.1 bind_addr 173.49.250.153 identifier "WAN_DHCP "
    May 8 22:45:48 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:48 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:49 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:49 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:50 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:50 dpinger WAN_DHCP 173.49.250.1: Alarm latency 0us stddev 0us loss 100%
    May 8 22:45:50 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:51 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:51 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:52 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:52 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:53 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:57 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 173.49.250.1 bind_addr 173.49.250.153 identifier "WAN_DHCP "
    May 8 22:45:57 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:58 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:58 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:59 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:45:59 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:00 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:00 dpinger WAN_DHCP 173.49.250.1: Alarm latency 0us stddev 0us loss 100%
    May 8 22:46:01 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:01 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:02 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:07 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:08 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:08 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:09 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:09 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:10 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:10 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:11 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:13 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 173.49.250.1 bind_addr 173.49.250.153 identifier "WAN_DHCP "
    May 8 22:46:16 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:16 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:17 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:17 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:18 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:18 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:18 dpinger WAN_DHCP 173.49.250.1: Alarm latency 1536us stddev 884us loss 33%
    May 8 22:46:19 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:19 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:20 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:20 dpinger WAN_DHCP 173.49.250.1: sendto error: 65
    May 8 22:46:21 dpinger WAN_DHCP 173.49.250.1: sendto error: 65



  • Any other suggestions aside from upgrading? Also I can't say I care for the new ui.



  • This is still happening. I can't figure out what's going on.



  • What type of nic is on that wan?

    Wiring faulty?



  • The NIC's are realtek, both onboard. The wiring should be fine, it started when verizon installed gigabit internet on monday. I don't think it's the ISP. I disabled dpinger and the issue persists, but there's nothing in the logs now that says it's broken. Basically the box lags and the web ui becomes unresponsive.

    On the console it says apresolve: can't allocate llinfo for xxx.xxx.xxx.xxx on re1.



  • The NIC's are realtek, both onboard.

    There is your issue. Freebsd isn't very kind for Realtek NICs.
    I suggest buying Intel


Log in to reply