From root@mail.clinet.fi  Sat Aug 16 11:33:36 1997
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04298
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 16 Aug 1997 11:33:34 -0700 (PDT)
Received: from innopoli10-gw.espoo.clinet.fi (root@innopoli10-gw.espoo.clinet.fi [194.100.0.197])
	by hauki.clinet.fi (8.8.6/8.8.6) with ESMTP id VAA28751
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 16 Aug 1997 21:33:31 +0300 (EET DST)
Received: (root@localhost) by innopoli10-gw.espoo.clinet.fi (8.8.5/8.6.4) id SAA17932; Sat, 16 Aug 1997 18:33:30 GMT
Message-Id: <199708161833.SAA17932@innopoli10-gw.espoo.clinet.fi>
Date: Sat, 16 Aug 1997 18:33:30 GMT
From: Charlie Root <root@mail.clinet.fi>
Reply-To: root@mail.clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: arplookup 194.100.0.193 failed: gateway route is not ours
X-Send-Pr-Version: 3.2

>Number:         4312
>Category:       kern
>Synopsis:       arp table gets messed up, syslog "gateway route is not ours"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Aug 16 11:40:01 PDT 1997
>Closed-Date:    Mon Mar 26 15:51:57 PST 2001
>Last-Modified:  Mon Mar 26 15:54:51 PST 2001
>Originator:     hsu@clinet.fi
>Release:        FreeBSD 2.2-STABLE i386
>Organization:
Clinet Ltd
>Environment:

FreeBSD 2.2-STABLE used as a router.  Runs gated, OSPF, BGP4.

>Description:

Without any obvious reason one of the neighbour routers disappears and 
gateway route is not ours is printed by kernel. 

Aug 16 18:20:19 innopoli10-gw /kernel: arpresolve: can't allocate llinfo for 194
.100.0.193
Aug 16 18:20:24 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours
Aug 16 18:20:24 innopoli10-gw /kernel: arpresolve: can't allocate llinfo for 194
.100.0.193
Aug 16 18:20:29 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours
Aug 16 18:20:29 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours
Aug 16 18:20:29 innopoli10-gw /kernel: arpresolve: can't allocate llinfo for 194
.100.0.193
Aug 16 18:20:30 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours

arp -a shows 194.100.0.193 "incomplete"

I looked back the logs and found this, this seems to be the first time
the problem appeared, but I am not yet sure whether reachability
was lost right here.  Restarting gated solved the problem.

Aug 16 17:33:54 innopoli10-gw gated[28762]: KRT SENT dest 194.100.0.193 gateway 
194.100.0.193
Aug 16 17:33:54 innopoli10-gw gated[28762]: KRT SEND CHANGE 194.100.0.193   mask
 255.255.255.255 router 194.100.0.193   flags <GW>2: Can't assign requested addr
ess
Aug 16 17:33:54 innopoli10-gw gated[28762]: KRT SENT type DELETE(2)flags UP GW H
OST(7) error 3: No such process
Aug 16 17:33:54 innopoli10-gw gated[28762]: KRT SENT dest 194.100.0.193
Aug 16 17:33:54 innopoli10-gw gated[28762]: KRT SEND DELETE 194.100.0.193   mask
 255.255.255.255 router 194.100.0.206   flags <GW>2: No such process
Aug 16 17:33:54 innopoli10-gw gated[28762]: KRT SENT type ADD(1)flags UP GW HOST
(7) error 49: Can't assign requested address
Aug 16 17:33:54 innopoli10-gw gated[28762]: KRT SENT dest 194.100.0.193 gateway 
194.100.0.193
Aug 16 17:33:54 innopoli10-gw gated[28762]: KRT SEND ADD    194.100.0.193   mask
 255.255.255.255 router 194.100.0.193   flags <GW>2: Can't assign requested addr
ess
Aug 16 17:35:15 innopoli10-gw /kernel: arp_rtrequest: bad gateway value
Aug 16 17:35:19 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours
Aug 16 17:35:19 innopoli10-gw /kernel: arpresolve: can't allocate llinfo for 194
.100.0.193
Aug 16 17:35:24 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours
Aug 16 17:35:24 innopoli10-gw /kernel: arpresolve: can't allocate llinfo for 194
.100.0.193
Aug 16 17:35:24 innopoli10-gw /kernel: arp_rtrequest: bad gateway value
Aug 16 17:35:29 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours
Aug 16 17:35:29 innopoli10-gw /kernel: arpresolve: can't allocate llinfo for 194
.100.0.193
Aug 16 17:35:31 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours
Aug 16 17:35:34 innopoli10-gw last message repeated 4 times
Aug 16 17:35:34 innopoli10-gw /kernel: arpresolve: can't allocate llinfo for 194
.100.0.193
Aug 16 17:35:39 innopoli10-gw /kernel: arplookup 194.100.0.193 failed: gateway r
oute is not ours
Aug 16 17:35:39 innopoli10-gw /kernel: arpresolve: can't allocate llinfo for 194
.100.0.193

>How-To-Repeat:

I do not know yet, this has been seen only once this far.

>Fix:
	

>Release-Note:
>Audit-Trail:

From: Bill Fenner <fenner@parc.xerox.com>
To: FreeBSD-gnats-submit@freebsd.org, root@mail.clinet.fi
Cc:  Subject: Re:  kern/4312: arplookup 194.100.0.193 failed: gateway route is not ours
Date: Sat, 16 Aug 1997 14:00:57 PDT

 If this is repeatable, can you follow up with what "route get 194.100.0.193"
 says when the problem occurs?
 
 Thanks,
   Bill
State-Changed-From-To: open->closed 
State-Changed-By: iedowse 
State-Changed-When: Mon Mar 26 15:51:57 PST 2001 
State-Changed-Why:  
Feedback timeout (fenner asked for feedback in Aug 1997, 
and there is no record in the archives of any reply). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=4312 
>Unformatted:
