ne1 device timeouts

ne1 device timeouts

Post by John C. Holleman » Thu, 22 Nov 2001 05:00:03



_____
Hi all,

Have 2.6 OBSD system running as firewall for two years now, using two
vanilla ISA bus NE2000 NICs.  Last few weeks i occasionally lose the
connection from clients on LAN to Internet, while firewall connectivity
to Internet is fine.  When connection is lost to firewall i cannot ping
or ssh from clients on LAN to firewall, yet when i ping from firewall to
clients, the NIC clears and connection is reestablished.

The /var/log/messages log shows "/bsd: ne1: device timeout".  Has anyone
seen this before and if so, does it look like the NIC hardware is
starting to fail ??

/ John

--
Message prepared:                                      10:55, 20/11/2001

 
 
 

ne1 device timeouts

Post by acw.. » Thu, 22 Nov 2001 14:20:50



Quote:>Have 2.6 OBSD system running as firewall for two years now, using two
>vanilla ISA bus NE2000 NICs.  Last few weeks i occasionally lose the
>connection from clients on LAN to Internet, while firewall connectivity
>to Internet is fine.  When connection is lost to firewall i cannot ping
>or ssh from clients on LAN to firewall, yet when i ping from firewall to
>clients, the NIC clears and connection is reestablished.
>The /var/log/messages log shows "/bsd: ne1: device timeout".  Has anyone
>seen this before and if so, does it look like the NIC hardware is
>starting to fail ??

I've been getting the same behaviour with 2.7. This has only happened since
Rogers switched to their new dhcp system, so I am running the most recent
dhclient instead of the default one. The solution I have found is to run a
cron job every ten minutes that deletes the routes that have been added to
each individual local machine. The default route for the interface is okay.
after I set up this cron job, there have been no problems.
Originally I set up the cron job to maintain continuous pings to each local
machine, but the connectivity still dropped. The route thing works. I have
no idea WHY it works, though.

--
Craig West         Ph: (416) 213-0300   |  It's not a bug,


 
 
 

ne1 device timeouts

Post by John C. Holleman » Thu, 22 Nov 2001 16:00:02



> >Have 2.6 OBSD system running as firewall for two years now, using two
> >vanilla ISA bus NE2000 NICs.  Last few weeks i occasionally lose the
> >connection from clients on LAN to Internet, while firewall connectivity
> >to Internet is fine.  When connection is lost to firewall i cannot ping
> >or ssh from clients on LAN to firewall, yet when i ping from firewall to
> >clients, the NIC clears and connection is reestablished.

> >The /var/log/messages log shows "/bsd: ne1: device timeout".  Has anyone
> >seen this before and if so, does it look like the NIC hardware is
> >starting to fail ??

> I've been getting the same behaviour with 2.7. This has only happened since
> Rogers switched to their new dhcp system, so I am running the most recent
> dhclient instead of the default one. The solution I have found is to run a
> cron job every ten minutes that deletes the routes that have been added to
> each individual local machine. The default route for the interface is okay.
> after I set up this cron job, there have been no problems.
> Originally I set up the cron job to maintain continuous pings to each local
> machine, but the connectivity still dropped. The route thing works. I have
> no idea WHY it works, though.

_____
Interesting !  I will give your suggestion a try.  Thanks.

/ John

--
Message prepared:                                      22:57, 20/11/2001

 
 
 

1. ne1 : device timeout.

I have a NE2000 ISA Network Card. When I tried to boot it tells me NE1 : IRQ
10 already in use.

So I got in the bios.. at the ISA IRQ10 place I change secondary for primary
and then at boot I got my ne1 initliazed...

Now, my internet work properly on my ne3 interface, all the settings is done
properly for my hostname.ne1 but I got the message

NE1 : Device timeout..

so when I go to my Windows box. I can ping 192.68.0.2 ! But that's it!!

Please help me! My ISA Card isn't PNP ! Or if it is, it's not righted in
every files of the driver disk.

Thank you very much for your help

Mathieu Landry

2. wheel mouse

3. ne1: device timeout

4. Redhat 6.0 Network Setup

5. Triton P90 1542CF No devices - Bus Timeout Problems (help)

6. Disabling FTP log

7. xe0 device timeout on toshiba satellite 4010 CDS

8. NEAT WAY TO PREVENT USERS FROM ESCAPING TO THE SHELL

9. Multi-Homed FreeBSD 2.28 ed0: device timeout

10. What is ed1: device timeout?

11. Problem->device timeout

12. PPC / WaveLAN Configuration device timeout

13. Device timeout (2.1.5 + Intel ether16)