Route messages

Tue Jul 1 06:32:10 UTC 2008

At 02:26 AM 7/1/2008, Paul wrote:
>Turning on / off fastforwarding has no effect for me. I still get 
>the messages.
>I also get major ticks of  'destinations found unreachable' in  netstat -rs

if you use
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/netinet/ip_input.c?rev=1.332.2.1;content-type=text%2Fplain

does it fix it for you ? I just cvsup'd to a RELENG_7 as of today, 
but used the older version of ip_input.c and I no longer get the 
blast of RTM_MISS messages

         ---Mike

>Mike Tancsa wrote:
>>At 10:34 PM 6/27/2008, mike at sentex.net wrote:
>>>On Sun, 15 Jun 2008 11:16:17 +0100, in sentex.lists.freebsd.net you
>>>wrote:
>>>
>>> >Paul wrote:
>>> >> Get these with GRE tunnel on
>>> >> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Sun May 11 19:00:57 EDT
>>> >> 2008     :/usr/obj/usr/src/sys/ROUTER  amd64
>>> >> But do not get them with 7.0-RELEASE
>>> >>
>>> >> Any ideas what changed? :)  Wish there was some sort of changelog..
>>> >> # of messages per second seems consistent with packets per second on
>>> >> GRE interface..
>>> >> No impact in routing, but definitely impact in cpu usage for all
>>> >> processes monitoring the route messages.
>>> >
>>> >RTM_MISS is actually fairly common when you don't have a default route.
>>> >
>>>
>>>Hi,
>>>         I am seeing this issue as well on a pair of  recently deployed
>>>boxes, one  running MPD and one acting as an area router in front of
>>>it. The MPD box has a default route and only has 400 routes or so.
>>>
>>>A steady stream of those messages, upwards of 500 per second.
>>>
>>>got message of size 96 on Fri Jun 27 22:25:42 2008
>>>RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, errno
>>>0, flags:<DONE>
>>>locks:  inits:
>>>sockaddrs: <DST>
>>>  default
>>>
>>>got message of size 96 on Fri Jun 27 22:25:42 2008
>>>RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, errno
>>>0, flags:<DONE>
>>>locks:  inits:
>>>sockaddrs: <DST>
>>>  default
>>>
>>>Is there a way to try and track down what is generating those messages
>>>? Its eating up a fair bit of cpu with quagga (the zebra process
>>>specifically)
>>
>>I narrowed down where the change to RELENG_7 happened.  It looks 
>>like a commit around April 22nd caused the behaviour to change.
>>
>>When a box acting as a router has a packet transit it, an RTM_MISS 
>>is generated for *each packet*...
>>
>>
>>Given a setup of
>>
>>H1 ---- R1 ----- H2
>>
>>where
>>H1 is 10.10.1.2/24
>>H2 is 10.20.1.2/24
>>and
>>R1 has 2 interfaces, 10.10.1.1/24 and 10.20.1.1/24
>>
>>Pinging H2 from H1 makes R1 generate a RTM_MISS for each 
>>packet!  For routing daemons such as zebra, this eats up a *lot* of 
>>CPU.  Turning on ip_fast_forwarding stops this behaviour on 
>>R1.  However, if the interface routing the packet is an netgraph 
>>interface (e.g. mpd) fast_forwarding doesnt seem to have an effect 
>>and the RTM_MISS messages are generated again for each packet.
>>
>>
>>The ping packet below is a valid icmp echo request and reply.
>>
>>e.g
>>0[releng7]# ping -c 2 -S 10.20.1.2 10.10.1.2
>>PING 10.10.1.2 (10.10.1.2) from 10.20.1.2: 56 data bytes
>>64 bytes from 10.10.1.2: icmp_seq=0 ttl=63 time=0.302 ms
>>64 bytes from 10.10.1.2: icmp_seq=1 ttl=63 time=0.337 ms
>>
>>--- 10.10.1.2 ping statistics ---
>>2 packets transmitted, 2 packets received, 0.0% packet loss
>>round-trip min/avg/max/stddev = 0.302/0.320/0.337/0.018 ms
>>0[releng7]#
>>
>>generates 4 messages on the router
>>
>>[r7-router]# route -n monitor
>>
>>got message of size 96 on Tue Jul  1 00:42:35 2008
>>RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, 
>>errno 0, flags:<DONE>
>>locks:  inits:
>>sockaddrs: <DST>
>>  default
>>
>>got message of size 96 on Tue Jul  1 00:42:35 2008
>>RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, 
>>errno 0, flags:<DONE>
>>locks:  inits:
>>sockaddrs: <DST>
>>  default
>>
>>got message of size 96 on Tue Jul  1 00:42:36 2008
>>RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, 
>>errno 0, flags:<DONE>
>>locks:  inits:
>>sockaddrs: <DST>
>>  default
>>
>>got message of size 96 on Tue Jul  1 00:42:36 2008
>>RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, 
>>errno 0, flags:<DONE>
>>locks:  inits:
>>sockaddrs: <DST>
>>  default
>>
>>
>>
>>I am thinking
>>
>>http://lists.freebsd.org/pipermail/cvs-src/2008-April/090303.html
>>is the commit ? If I revert to the prev version, the issue goes away.
>>
>>
>>kernel is just
>>
>>0[r7-router]% diff router GENERIC
>>24,27c24
>>< ident         router
>><
>>< makeoptions     MODULES_OVERRIDE="ipfw acpi"
>><
>>---
>> > ident         GENERIC
>>37,38c34,35
>>< #options      INET6                   # IPv6 communications protocols
>>< #options      SCTP                    # Stream Control 
>>Transmission Protocol
>>---
>> > options       INET6                   # IPv6 communications protocols
>> > options       SCTP                    # Stream Control 
>> Transmission Protocol
>>47c44
>>< #options      NFSLOCKD                # Network Lock Manager
>>---
>> > options       NFSLOCKD                # Network Lock Manager
>>61c58
>>< #options      STACK                   # stack(9) support
>>---
>> > options       STACK                   # stack(9) support
>>303c300
>>< #device               uslcom          # SI Labs CP2101/CP2102 
>>serial adapters
>>---
>> > device                uslcom          # SI Labs CP2101/CP2102 
>> serial adapters
>>
>>
>>         ---Mike
>>_______________________________________________
>>freebsd-net at freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-net
>>To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>
>_______________________________________________
>freebsd-net at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-net
>To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"