From owner-freebsd-hackers Fri Sep 26 02:46:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA25229 for hackers-outgoing; Fri, 26 Sep 1997 02:46:44 -0700 (PDT) Received: from docenti.ing.unipi.it (docenti.ing.unipi.it [131.114.28.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA25213 for ; Fri, 26 Sep 1997 02:46:23 -0700 (PDT) Received: (from gabriele@localhost) by docenti.ing.unipi.it (8.8.5/8.8.5) id LAA24047; Fri, 26 Sep 1997 11:43:56 +0200 (MET DST) Date: Fri, 26 Sep 1997 11:43:56 +0200 (MET DST) From: Gabriele Cecchetti To: Ruslan Ermilov cc: tarkhil@mgt.msk.ru, hackers@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <199709260753.KAA01057@relay.ucb.crimea.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Sep 1997, Ruslan Ermilov wrote: > Once Alexander B. Povolotsky wrote: > > Hello! > > > > I'm running FreeBSD-2.2.2-stable on P-133, with EtherExpress card (fxp0 interface). Sometimes (about 3-4 times per week) I'm getting troubles with IP. 127.0.0.1 pings ok, and my fxp0's address as well, but no other computer can see me, and I can't see any others. > > > > Putting fxp0 in promiscous mode heals the trouble in several seconds, but shutdown (without reboot) doesn't help. Routing tables remains unchanged. It happened at both day and night, the only program that could receive something thry TCP/IP was sendmail. > > > > make world and kernel recompilatin didn't help. > > > > Any other suggestions? > > > > Alex. > > > > The same problems. > I'm using 3 EtherExpress cards: > > fxp0 rev 2 int a irq 10 on pci0:10 > fxp0: Ethernet address 00:a0:c9:55:13:22 > fxp1 rev 1 int a irq 9 on pci0:12 > fxp1: Ethernet address 00:a0:c9:10:68:a0, 10Mbps > fxp2 rev 1 int a irq 9 on pci0:14 > fxp2: Ethernet address 00:a0:c9:5a:51:f9, 10Mbps > > Sometimes, ~ 1/2 per week, my fxp0, which is revision 2 card, silently freezes. > When I `ifconfig down delete fxp0' and then ifconfig it up, the situation > resolves. > > ;-( I use a simple 'trick' to avoid this problem (works with rev 1 too): add to your crontab entry: * * * * * root /sbin/ping -i 5 -c 12 router_ip > /dev/null or if you wish */5 * * * * root /sbin/ping -i 5 -c 60 router_ip > /dev/null where router_ip could be any machine or your router. Using this the fxp0 is 'almost always' active: the interface dont'freeze if you use it to send packet. I use it for 2 month and the problem is disappeared. The very little overhead can be acceptable. Gabriele ============================================================================ Ing. Gabriele Cecchetti Millennium Information Engineering email: gabriele@ing.unipi.it Via Lenin 127 http://www.ing.unipi.it/~gabriele 56010 Pappiana, PISA (Italy) Tel: +39-50-862316 =============================================================================