If one side is full duplex and the other half duplex, you'll see most
frames in one direction work and most frames in the other direction error.

If both sides are half duplex you'll see lots of collisions.

Make sure both sides are full duplex (they should autoneg to fdx) and
change the cable. Then change the NIC in the server. Then buy another WRAP.

adam.

> It might be a bad cable or connector - maybe hairline crack in board..
>
> Set up a 'viewer' to look at errors on line (maybe Wireshark in 
> realtime mode) and then wiggle cables and connectors - look for 
> changes in the error rate.
>
> A software problem usually gives 0 errors or 100% errors. Hardware 
> problem is most probable.
>
> Good luck
>
> Bob G
>
> lutz dot niederer at gmx dot net wrote:
>> Hello,
>>
>> I do have a problem with the network connection between my wrap and 
>> my server.  As you can see from the attached data below, I get lots 
>> of errors and I have no idea where they are coming from.  I changed 
>> cables, I changed the duplex/full-duplex.  Nothing helped.  The 
>> connection between the Wrap and the cable modem is without errors, 
>> the connection between my server and other networking devices is 
>> without any errors.  On the server there is a linux 2.4.32 kernel and 
>> a 4-port tulip-based card (adaptec).  On the Wrap there is m0n0 
>> version 1.231.
>> These errors raise enormously in very short time if I transfer lots 
>> of data.  I am pretty sure that this is the problem why I only get 
>> about 10mbit from my provider where I should get more than 20mbit.
>>
>> If anybody has an idea what I can do, please tell me.
>>
>> Thanks a lot!
>> -lutzn
>>
>>
>>
>> M0N0 LAN interface                       
>> MAC address    00:0d:b9:01:90:ec                    
>> IP address    10.252.229.254                      
>> Subnet mask    255.255.255.0                        
>> Media    100baseTX                        
>> In/out packets    20054856/26404594 (1.39 GB/3.40 GB)            
>> In/out errors    0/1577620                        
>> Collisions    1586502                        
>>
>> M0N0 DMZ interface                       
>> Status    up                        
>> MAC address    00:0d:b9:01:90:ed                    
>> IP address    10.252.228.254                      
>> Subnet mask    255.255.255.0                        
>> Media    100baseTX                        
>> In/out packets    157816/139828 (62.64 MB/24.41 MB)            
>> In/out errors    0/201                        
>> Collisions    300                        
>>
>>
>> SERVER DMZ interface 
>> eth3      Link encap:Ethernet  HWaddr 00:C0:95:E0:98:DA
>>           inet addr:10.252.228.1  Bcast:10.252.228.255  
>> Mask:255.255.255.0
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:201426 errors:211 dropped:0 overruns:0 frame:320
>>           TX packets:220316 errors:3 dropped:0 overruns:0 carrier:6
>>           collisions:0 txqueuelen:1000
>>           RX bytes:47272559 (45.0 Mb)  TX bytes:96989387 (92.4 Mb)
>>           Interrupt:21 Base address:0x6000
>>
>> SERVER LAN interface
>> eth4      Link encap:Ethernet  HWaddr 00:C0:95:E0:98:DB
>>           inet addr:10.252.229.1  Bcast:10.252.229.255  
>> Mask:255.255.255.0
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:43793462 errors:1601114 dropped:0 overruns:0 
>> frame:2396528
>>           TX packets:34521256 errors:3 dropped:0 overruns:0 carrier:6
>>           collisions:0 txqueuelen:1000
>>           RX bytes:2331563867 (2223.5 Mb)  TX bytes:2690282837 
>> (2565.6 Mb)
>>           Interrupt:22 Base address:0x8000
>>
>>  
>>
>>
>>   
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>