From owner-freebsd-stable@FreeBSD.ORG Sun Aug 10 19:50:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85B251065680 for ; Sun, 10 Aug 2008 19:50:46 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from webmail25.yandex.ru (webmail25.yandex.ru [213.180.223.152]) by mx1.freebsd.org (Postfix) with ESMTP id 16ABC8FC1E for ; Sun, 10 Aug 2008 19:50:45 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from YAMAIL (webmail25) by mail.yandex.ru id S3686448AbYHJTuh for ; Sun, 10 Aug 2008 23:50:37 +0400 X-Yandex-Spam: 1 Received: from [92.113.12.164] ([92.113.12.164]) by mail.yandex.ru with HTTP; Sun, 10 Aug 2008 23:50:37 +0400 From: KES To: pi@opsec.eu In-Reply-To: <20080809143019.GB3984@home.opsec.eu> References: <358831218288212@webmail24.yandex.ru> <20080809143019.GB3984@home.opsec.eu> MIME-Version: 1.0 Message-Id: <375251218397837@webmail25.yandex.ru> Date: Sun, 10 Aug 2008 23:50:37 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-stable@freebsd.org Subject: Re: IMPORTANT! Network is unreachable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2008 19:50:46 -0000 09.08.08, 18:30, "Kurt Jaeger" : > Hi! > > So I do not think that problem is with the network mask. Because of even ping 10.11.16.14 > > returns network is unreachable! > > Now when I upgraded to v7 I see trouble described earlier. > > So this is must be counted as BUG of v7 > It might be some issue with ARP timeouts ? 10.11.16.14 is local address tcpdump on the interface with this address shows nothing >The system learns > the other IPs using some indirect way and forgets it as soon > as the arp address times out ? I do not think so. Because of when I ping local address 10.11.16.14 for an our without breaking this ping. So mac address can not die because of timeout. It dissappears from kernel routing table by some other cause. I do not know which cause > > 5min period is seen without routed. > > With routed I get next picture: > > start routed: network is unreachable > > stop routed: network still unreacheable > > start routed: network is reachable > > stop routed: network is reacheable > > start routed: network is unreachable again > > > > The thing which is very interesting is: > > Why period is 5 min? > Why do you run routed ? I want to use RIP > Why don't you just statically assign the routes ? Because of I have two links to same place router1 --- LAN1 --- router2 | / LAN2 LAN3 | / router3 ---------/ router1: 10.0.16.1/24, 10.10.16.8/24 router2: 10.11.16.1/24, 10.0.16.3/24 router3: 10.11.16.14/24, 10.10.16.3/24 LAN1: 10.0.16.0 LAN2: 10.10.16.0 LAN3: 10.11.16.0 router3: rl0: flags=8843 metric 0 mtu 1500 options=8 ether 00:0e:2e:db:4f:d4 inet 10.11.16.14 netmask 0xffffff00 broadcast 10.11.16.255 inet 10.11.16.9 netmask 0xffffff00 broadcast 10.11.16.255 inet 10.10.16.3 netmask 0xfffffff0 broadcast 10.10.16.15 media: Ethernet autoselect (100baseTX ) status: active I add 10.10.16.3 address to rl0 by mistake. It must be on rl1 interface. But when I added it I lose connection to my LAN. I think this behavior is bug so I describe problem in letters earlier