Professional Web Applications Themes

arplookup failed - FreeBSD

I've got a system running 5.3-p6, and am getting this error every 20 minutes or so: kernel: arplookup 69.61.54.33 failed: host is not on local network I get that the host isn't on the network, but I don't have any idea where the message is coming from. It's in /var/log/messages, shows up about every 20 minutes. Any ideas?...

  1. #1

    Default arplookup failed

    I've got a system running 5.3-p6, and am getting this error every 20
    minutes or so:
    kernel: arplookup 69.61.54.33 failed: host is not on local network

    I get that the host isn't on the network, but I don't have any idea
    where the message is coming from. It's in /var/log/messages, shows up
    about every 20 minutes. Any ideas?
    Pat Guest

  2. #2

    Default Re: arplookup failed

    Pat Maddox wrote: 


    Maybe a direct route to that host is specified
    in your routing table. Provide the output of
    `netstat -rn` please.

    Best wishes,
    Andrew P.
    Andrew Guest

  3. #3

    Default Re: arplookup failed

    Routing tables

    Internet:
    Destination Gateway Flags Refs Use Netif Expire
    default 69.61.54.161 UGS 0 838 rl0
    69.61.54.160/29 link#1 UC 0 0 rl0
    69.61.54.161 00:02:85:0d:7c:80 UHLW 1 0 rl0 156
    127.0.0.1 127.0.0.1 UH 0 0 lo0

    Internet6:
    Destination Gateway Flags
    Netif Expire
    ::1 ::1 UH lo0
    fe80::%rl0/64 link#1 UC rl0
    fe80::20c:6eff:fe44:4391%rl0 00:0c:6e:44:43:91 UHL lo0
    fe80::%lo0/64 fe80::1%lo0 U lo0
    fe80::1%lo0 link#2 UHL lo0
    ff01::/32 ::1 U lo0
    ff02::%rl0/32 link#1 UC rl0
    ff02::%lo0/32 ::1 UC lo0




    On Apr 4, 2005 5:48 AM, Andrew P. <ru> wrote: 
    >
    > Maybe a direct route to that host is specified
    > in your routing table. Provide the output of
    > `netstat -rn` please.
    >
    > Best wishes,
    > Andrew P.
    >[/ref]
    Pat Guest

  4. #4

    Default Re: arplookup failed

    Pat Maddox wrote: 
    >>
    >>Maybe a direct route to that host is specified
    >>in your routing table. Provide the output of
    >>`netstat -rn` please.[/ref]
    >
    > Destination Gateway Flags Refs Use Netif
    > default 69.61.54.161 UGS 0 838 rl0
    > 69.61.54.160/29 link#1 UC 0 0 rl0
    > 69.61.54.161 00:02:85:0d:7c:80 UHLW 1 0 rl0
    > 127.0.0.1 127.0.0.1 UH 0 0 lo0[/ref]


    Hmm, according to this table every packet with
    69.61.54.33 destination would be sent to
    69.61.54.161 gateway, arplookup would not be
    performed for the 33 address. What comes to my
    mind is that some broken router might be messing
    your routing table via ICMP (or do you use
    a routing protocol like RIP or OSPF?) You might
    need to run 'route monitor > route_changes.log &'
    for a few hours and post the log, for us to see
    what's happening.

    Best wishes,
    Andrew P.
    Andrew Guest

Similar Threads

  1. Replies: 5
    Last Post: March 2nd, 02:30 PM
  2. Replies: 0
    Last Post: May 13th, 04:40 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139