Strange loss of bandwidth

librano · 04-25-2006, 02:41 PM

Iam facing a strange problem...

I have a webserver which I am using as a gateway for my LAN... however another machine with the same type of network card running on windows achieves about twice (downloads at ~25kBs) the bandwidth if i plug it to the same internet connection as the server (running Mandriva and downloads at ~13kBs). The windows box, however, is not setup as a gateway... i cant think of any other difference that can cause this difference... of course, the 13kBs is when there is no internet activity from the LAN but still connected.

the ifconfig -a output is

Code:

eth0      Link encap:Ethernet  HWaddr 00:40:95:xx:xx:xx
         inet addr:86.104.xxx.xxx  Bcast:86.104.xxx.255  Mask:255.255.255.0
         inet6 addr: fe80::240:95ff:xxxx:xxxx/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:25562452 errors:0 dropped:0 overruns:0 frame:0
         TX packets:7117870 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:1320287313 (1.2 GiB)  TX bytes:1997891555 (1.8 GiB)
         Interrupt:21 Base address:0xef00

eth1      Link encap:Ethernet  HWaddr 00:01:02:xx:xx:xx
         inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
         inet6 addr: fe80::201:2ff:fed1:xxxx/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:2727447 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2514793 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:816169924 (778.3 MiB)  TX bytes:1297571245 (1.2 GiB)
         Interrupt:22 Base address:0x7480

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:31136 errors:0 dropped:0 overruns:0 frame:0
         TX packets:31136 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:8579552 (8.1 MiB)  TX bytes:8579552 (8.1 MiB)

sit0      Link encap:IPv6-in-IPv4
         NOARP  MTU:1480  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

thanks in advance.

lib.

satinet · 04-26-2006, 07:37 AM

it might be good to show the output of "netstat -rn" rather than if config.....

and your arp cache maybe.....

librano · 05-09-2006, 12:04 AM

hi all!

sorry for the delay in posting... i havent had access to the box in a while... hope intrest hasnt died...

Code:

> netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
86.104.xxx.0    0.0.0.0         255.255.255.0   U         0 0          0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 eth1
0.0.0.0         86.104.xxx.2    0.0.0.0         UG        0 0          0 eth0

Code:

> arp -e
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.0.2              ether   00:C0:xx:xx:xx:xx   C                     eth1
86.104.xxx.235           ether   00:08:xx:xx:xx:xx   C                     eth0
86.104.xxx.yyy           ether   00:0A:xx:xx:xx:xx   C                     eth0
86.104.xxx.2             ether   00:0E:xx:xx:xx:xx   C                     eth0
86.104.xxx.2             ether   00:0E:xx:xx:xx:xx   C                     eth0
> arp -i eth0
Address                  HWtype  HWaddress           Flags Mask            Iface
86.104.xxx.235           ether   00:08:xx:xx:xx:xx   C                     eth0
86.104.xxx.2             ether   00:0E:xx:xx:xx:xx   C                     eth0
86.104.xxx.2             ether   00:0E:xx:xx:xx:xx   C                     eth0

here 86.104.xxx.yyy is an address which i have no idea as to why it appears here...

cheers

ps: one more thing the metric setting of the ethernet cards is set to 1. shouldnt it be more?... 10 maybe...