* Port-forwarding + collisions
@ 2005-02-25 3:48 Rudi Starcevic
2005-02-24 13:16 ` Jason Opperisano
0 siblings, 1 reply; 2+ messages in thread
From: Rudi Starcevic @ 2005-02-25 3:48 UTC (permalink / raw)
To: netfilter
Hi,
I'm still working on why I have poor performance and have found some
data I need to check as I'm not that familiar.
Below I have the output from ifconfig.
eth0 is my Internet NIC with eth1 my internal 192.168.0.x network.
On my eth0 NIC we can see there is 0 collisions
On eth1 we can see collisions:6810362
This must mean a problem on the 192 end.
These are colo servers which are configured by techs over there so I
don't have physical access to these machines ...
What could cause such a problem I wonder ?
It seems highly likely that this may be the cause of my bandwidth problems.
It is quite surprising that there is problems as there is only two machines.
--------------------------------------
Windnows 192.x.x.x = Gigabit card
|
Gigabit Switch
|
Linux 192.x.x.x = 10/100 MB card
Linux 64.x.x.x = 10/100 MB card
--------------------------------------
Is there anything special I need to do on the Linux end ?
I am told it is all supposed to auto detect ..
eth0 Link encap:Ethernet HWaddr xx:xx:xx
inet addr:66.xxx.xx.79 Bcast:64.255.255.255 Mask:255.255.255.192
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:93820046 errors:0 dropped:0 overruns:0 frame:0
TX packets:112683401 errors:0 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:1000
RX bytes:375314364 (357.9 MiB) TX bytes:2449306437 (2.2 GiB)
Interrupt:10 Base address:0x1000 Memory:40000000-40000038
eth0:0 Link encap:Ethernet HWaddr xx:xx:xx
inet addr:66.xxx.xx.100 Bcast:64.255.255.255
Mask:255.255.255.192
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0x1000 Memory:40000000-40000038
eth1 Link encap:Ethernet HWaddr xx:xx:xx
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110547112 errors:0 dropped:0 overruns:0 frame:0
TX packets:85362007 errors:85 dropped:0 overruns:0 carrier:85
collisions:6810362 txqueuelen:1000
Thanks
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Port-forwarding + collisions
2005-02-25 3:48 Port-forwarding + collisions Rudi Starcevic
@ 2005-02-24 13:16 ` Jason Opperisano
0 siblings, 0 replies; 2+ messages in thread
From: Jason Opperisano @ 2005-02-24 13:16 UTC (permalink / raw)
To: netfilter
On Thu, 2005-02-24 at 22:48, Rudi Starcevic wrote:
> Hi,
>
> I'm still working on why I have poor performance and have found some
> data I need to check as I'm not that familiar.
>
> Below I have the output from ifconfig.
> eth0 is my Internet NIC with eth1 my internal 192.168.0.x network.
>
> On my eth0 NIC we can see there is 0 collisions
>
> On eth1 we can see collisions:6810362
i would go out on a limb and say that's your problem. how's about
tcpdumping eth1 on the linux machine and see what's really going on on
the wire?
i would also point back to the possibility that the internal switch is
horribly misconfigured.
-j
--
"I bet Einstein turned himself all sorts of colors before he invented
the light bulb."
--The Simpsons
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-02-25 3:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-25 3:48 Port-forwarding + collisions Rudi Starcevic
2005-02-24 13:16 ` Jason Opperisano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox