[ previous ] [ next ] [ threads ]
 
 From:  =?ISO-8859-1?Q?G=F6ran_Samuelsson?= <goran at samuelsson dot pp dot se>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Problems w NIC in the 1.3b2 release
 Date:  Tue, 02 Jan 2007 23:21:59 +0100
Exactly what I have on just the WAN, my log is identical on that NIC.


Arne Varholm skrev:
> I have the same two NIC's and also see a lot of watchdog timeout, in 
> the log I have just entries from one of them,
> but I have I/O errors on both
>
> Uptime: 1 day, 07:30
> In/out errors     3/52
> In/out errors     337/0
>
> Arne
>
> kernel: xl1: link state changed to UP
> Jan 2 19:50:12     kernel: xl1: link state changed to DOWN
> Jan 2 19:50:12     kernel: xl1: watchdog timeout
> Jan 2 19:12:01     kernel: xl1: link state changed to UP
> Jan 2 19:11:59     kernel: xl1: link state changed to DOWN
> Jan 2 19:11:59     kernel: xl1: watchdog timeout
> Jan 2 19:07:23     kernel: xl1: link state changed to UP
> Jan 2 19:07:21     kernel: xl1: link state changed to DOWN
> Jan 2 19:07:21     kernel: xl1: watchdog timeout
> Jan 2 18:05:58     kernel: xl1: link state changed to UP
> Jan 2 18:05:56     kernel: xl1: link state changed to DOWN
> Jan 2 18:05:56     kernel: xl1: watchdog timeout
> Jan 2 17:49:50     kernel: xl1: link state changed to UP
> Jan 2 17:49:48     kernel: xl1: link state changed to DOWN
>
>
>

>> Hi,
>>
>> just tried to upgrade to 1.3b2 from the 1.23b1 release an cannot get 
>> it to work properly.
>>
>> The problem seams to be with the NIC at the WAN-side. I have a 
>> generic PC, an Compaq DPENS with two 3com 3C905B-TX NICS. (see 
>> http://m0n0.ch/wall/gallery/43.jpg)
>>
>> When upgrading to 1.3b2 the communication almost stops, if i type 
>> "www.google.com" in a browser at the LAN it takes several minutes to 
>> go through. I've also notised that I cannot release the lease of the 
>> WAN interface and that I get a "xl1 watchdog timeout" on the console. 
>> (xl1 => WAN i/f)
>>
>> Been trying to change irq's on the NIC but nothing helps, when 
>> downgrading to 1.23b1 all works fine again...
>>
>> best

>>
>>
>
>