Kernel: arpresolve: can't allocate llinfo for 192.168.100.1 (cable modem)



  • Hi all,

    I ran into issue where my VOIP box (elastix) would not work when issuing:

    linux*CLI> sip show registry
    Host                                    dnsmgr Username      Refresh State                Reg.Time               
    sip.anveo.com:5010                      N      3233207817        120 Request Sent                                 
    callcentric.com:5060                    N      17772527263        46 Registered          Sat, 15 Jun 2013 18:44:46
    sipgate.com:5060                        N      7006583e0          120 Request Sent                                 
    sip.voipcheap.com:5060                  N      marinko.esca      120 Request Sent                                 
    sipgate.de:5060                        N      5028298            120 Request Sent                                 
    sip.future-nine.com:5060                N      27514245          1185 Registered          Sat, 15 Jun 2013 18:44:02
    atlanta.voip.ms:5060                    N      101539            120 Request Sent                                 
    7 SIP registrations.

    So lots of request sent. Looking in the pfSense logs I saw lots pages of this (192.168.100.1 is my cable modem):

    Jun 15 18:45:57	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:01	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:01	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:01	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:02	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:02	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:02	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:03	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:03	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    Jun 15 18:46:05	kernel: arpresolve: can't allocate llinfo for 192.168.100.1
    

    I've rebooted Elastix multiple times and nothing helped until I rebooted both cable modem (Comcast) and pfSense.

    Is this known issue and will be fixed when 2.1 gets released?
    I almost want to install 2.1-RC (i386) just to see if this will happen again.



  • Not enough info there to tell you where the problem even might be. The "can't allocate llinfo" might be harmless or completely unrelated. Can you still get out in general and just your VoIP is broken?



  • Are you using multi-WAN ?



  • @cmb:

    Not enough info there to tell you where the problem even might be. The "can't allocate llinfo" might be harmless or completely unrelated. Can you still get out in general and just your VoIP is broken?

    Yes, I could get out and my VOIP was broken.
    Next time it happens what other info do you need?



  • @dhatz:

    Are you using multi-WAN ?

    No.



  • Not sure if relates to my first issue?

    Jun 16 13:09:16	dnsmasq[37465]: failed to send packet: Host is down
    Jun 16 13:09:16	dnsmasq[37465]: failed to send packet: Host is down
    Jun 16 13:09:21	dnsmasq[37465]: failed to send packet: Host is down
    Jun 16 13:09:21	dnsmasq[37465]: failed to send packet: Host is down
    Jun 16 13:09:26	dnsmasq[37465]: failed to send packet: Host is down
    Jun 16 13:09:26	dnsmasq[37465]: failed to send packet: Host is down
    Jun 16 13:09:31	dnsmasq[37465]: failed to send packet: Host is down
    Jun 16 13:09:31	dnsmasq[37465]: failed to send packet: Host is down
    

  • Rebel Alliance Developer Netgate

    There are many posts here on the forum about that. Search for 192.168.100.1 or the llinfo error and you'll turn up several useful discussions.

    http://forum.pfsense.org/index.php?topic=54171.0
    http://forum.pfsense.org/index.php?topic=56330.0
    http://forum.pfsense.org/index.php?topic=62964.0
    http://redmine.pfsense.org/issues/2704



  • Depending on the brand of cable modem provided.. ie if it's Motorola I wouldn't be using 192.168.100.x/24 on your internal network as it's also used by the modem and can cause issues.



  • @jimp:

    There are many posts here on the forum about that. Search for 192.168.100.1 or the llinfo error and you'll turn up several useful discussions.

    http://forum.pfsense.org/index.php?topic=54171.0
    http://forum.pfsense.org/index.php?topic=56330.0
    http://forum.pfsense.org/index.php?topic=62964.0
    http://redmine.pfsense.org/issues/2704

    Since you mentioned in this post http://forum.pfsense.org/index.php/topic,62964.0.html that with v2.1 might be better I will wait for the final version.
    At least I know what its causing my issue so I know how to fix it.


Log in to reply