From owner-freebsd-current@FreeBSD.ORG Thu Mar 22 16:51:59 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9AE216A417 for ; Thu, 22 Mar 2007 16:51:59 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 8264513C448 for ; Thu, 22 Mar 2007 16:51:59 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (unknown [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 9B37720C19D; Thu, 22 Mar 2007 12:51:56 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 22 Mar 2007 12:51:59 -0400 X-Sasl-enc: RerlZ2W5I1oPGNgEt5y+Kx2Bw5NO8wZGF7oMgc2W++0L 1174582319 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 371801855A; Thu, 22 Mar 2007 12:51:59 -0400 (EDT) Message-ID: <4602B42D.5060102@FreeBSD.org> Date: Thu, 22 Mar 2007 16:51:57 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Scot Hetzel References: <46025922.4090809@vlink.ru> <790a9fff0703220825g69405b89j123f7be87fadcb10@mail.gmail.com> In-Reply-To: <790a9fff0703220825g69405b89j123f7be87fadcb10@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Denis Shaposhnikov , current@freebsd.org Subject: Re: no network access on today's CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2007 16:51:59 -0000 Scot Hetzel wrote: > I had a similar problem with rl(4), but thought it was due to the > wireless radio (wireless ISP) that was the cause of the problem due to > storms last night. I did notice, while running tcpdump, that FreeBSD > was trying to obtain the mac address of the wireless radio, but the > radio wasn't responding. I then used 'arp -s > ' > > This morning it still wasn't working, so I powercycled the radio, and > the ethernet switch. I then noticed that the radio was now trying to > obtain the mac address of the FreeBSD system, but it wasn't > responding. Tried ifconfig rl0 down/up of the interface and it still > wasn't sending out arp replies. Rebooted the system, and now I can > access the internet thru this system. Are you able to tcpdump at both ends when this happens? Please see my reply to Denis for more diagnostics which would be required. Regards, BMS