To All:
I am using a pair of 3C905B-TX NICS. I pulled the logs. Here is what
I have:
WAN interface
Status up
MAC address
IP address 208.17.66.204
Subnet mask 255.255.255.224
Gateway 208.17.66.193
Media 100baseTX <full-duplex>
In/out packets 471805/453678 (248.37 MB/105.20 MB)
In/out errors 0/0
Collisions 0
LAN interface
Status up
MAC address
IP address 192.168.14.10
Subnet mask 255.255.255.0
Media 100baseTX <full-duplex>
In/out packets 1114677/1051494 (189.18 MB/333.25 MB)
In/out errors 0/0
Collisions 0
2 days, 00:15 I have reboot once a month to clear the modem. I have been
tweaking my configuration to the limit. I have it running perfectly.
I am using a c3 giga pro motherboard with 256 mb of ram. I have a total of
4 interfaces. The 2 3com adapters, the on-board adapter, athern wireless
adapter. I am bridging the wireless to the LAN side. I would look at the
link speed of the port that the 3 Com adapter is connected in. I recently
ran into a issue where one of the 3Com adapters was negotiating 100 half but
reporting 100 full. I found the issue with Ethereal. I saw error in the
trace. I set the post speed of the WAN to 100 full and my DSL modem has to
be set to 10 half. This was step up with a managed switch with 3 vlans.
VLAN1 - modem connection
VLAN2 - LAN Connection
VLAN3 - OPT1
OPT2 - bridged to the LAN via the M0n0Wall
Once done it was great. It was no issues. I have simplified my network
with a Netgear router. Just for a 4 port switch. I am only using 1 port
and everything else is wireless. I be glad to give anyone on the forum
anything that I can.
RC
----- Original Message -----
From: "Göran Samuelsson" <goran at samuelsson dot pp dot se>
To: <m0n0wall at lists dot m0n0 dot ch>
Sent: Tuesday, January 02, 2007 5:21 PM
Subject: Re: [m0n0wall] Problems w NIC in the 1.3b2 release
> Exactly what I have on just the WAN, my log is identical on that NIC.
> /Göran
>
> 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
>>
>>
>>
>> Göran Samuelsson skrev:
>>> 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
>>> Göran Samuelsson
>>>
>>>
>>
>>
>
| 