| View previous topic :: View next topic |
| Author |
Message |
Selkie
n00b
Joined: 15 Jul 2002
Posts: 27
|
 Posted: Mon Oct 04, 2004 12:07 am Post subject: Gentoo Router: many collisions on the eth1 (->DSL) |
 |
|
Hi, my gentoo-router seems to have a problem with the connection to the DSL Modem.
While downloading works great and the ping is perfect games still lag. I hope somebody here can help me with this one.
Setup is as follows:
eth0 -> Switch -> LAN
eth1 -> DSL Modem
ifconfig says:
| Code: | eth0 Link encap:Ethernet HWaddr 00:01:02:50:C8:45
inet addr:172.20.xxx.xxx Bcast:172.20.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:91344658 errors:0 dropped:0 overruns:65 frame:0
TX packets:83832276 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2622415903 (2500.9 Mb) TX bytes:4140310822 (3948.5 Mb)
Interrupt:9 Base address:0xd000
eth1 Link encap:Ethernet HWaddr 00:E0:29:5B:D4:EB
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13557964 errors:0 dropped:0 overruns:0 frame:0
TX packets:14068332 errors:0 dropped:0 overruns:0 carrier:0
collisions:579939 txqueuelen:1000
RX bytes:3514890918 (3352.0 Mb) TX bytes:1253819672 (1195.7 Mb)
Interrupt:12 Base address:0xd400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:56 (56.0 b) TX bytes:56 (56.0 b)
ppp0 Link encap:Point-to-Point Protocol
inet addr:212.xxx.xxx.xxx P-t-P:213.xxx.xxx.xxx Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:13531474 errors:0 dropped:0 overruns:0 frame:0
TX packets:14041841 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:3215574883 (3066.6 Mb) TX bytes:943242745 (899.5 Mb)
|
notice the HUGE amount of collisions? maybe thats the problem?
mii-tool output:
| Code: | eth0: negotiated 100baseTx-FD flow-control, link ok
product info: vendor 00:10:5a, model 0 rev 0
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
eth1: autonegotiation failed, link ok
product info: vendor 00:00:00, model 0 rev 0
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
|
autonegation failed ... that sounds bad, could that be it?
thanks in advance for any hints
Last edited by Selkie on Mon Oct 04, 2004 1:44 am; edited 2 times in total |
|
| Back to top |
|
 |
hds
Advocate
Joined: 21 Aug 2004
Posts: 2629
Location: Sprockhoevel [GER]
|
| Posted: Mon Oct 04, 2004 12:29 am Post subject: |
|
|
hmm, my guess is - your DSL provider/modem is using 10mbit HD. at least this is the case over here in germany using t-online. heres my output:
| Code: |
router:~ # mii-tool -v
eth0: negotiated 100baseTx-FD, link ok
product info: vendor 00:00:00, model 0 rev 0
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
eth1: 10 Mbit, half duplex, link ok
product info: vendor 00:00:34, model 0 rev 8
basic mode: 10 Mbit, half duplex
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising:
link partner: 10baseT-HD
router:~ #
|
could you somehow force your eth1 to use 10mbit HD?
//edit: ah, i just see you are at QSL. is that SDSL?
Last edited by hds on Mon Oct 04, 2004 12:34 am; edited 1 time in total |
|
| Back to top |
|
|
kashani
Advocate
Joined: 02 Sep 2002
Posts: 2032
Location: San Francisco
|
| Posted: Mon Oct 04, 2004 12:33 am Post subject: |
|
|
That's most likely it. When the connections fail to autonegotiate they usually choose half duplex connections. Collisions are pretty much a fact of life when the connection is half duplex.
Try manually set full duplex and see if it gets better. If the SMC card, your eth1, is older it may have problems with newer switches... and vice versa.
kashani
_________________
Will personally fix your server in exchange for motorcycle related shop tools in good shape. |
|
| Back to top |
|
|
Selkie
n00b
Joined: 15 Jul 2002
Posts: 27
|
| Posted: Mon Oct 04, 2004 1:08 am Post subject: |
|
|
@hds: yes, QDSL uses SDSL technology
@hds&kashani:
i tried forcing 100mbit full/halfduplex -> the link is lost
then i forced 10mbit halfduplex -> many collisions
after that i forced 10mbit fullduplex -> no collisions 
but now there is a constant increase of "errors" on eth1
what are errors? could errors be weird packets from the internet? |
|
| Back to top |
|
|
hds
Advocate
Joined: 21 Aug 2004
Posts: 2629
Location: Sprockhoevel [GER]
|
| Posted: Mon Oct 04, 2004 1:19 am Post subject: |
|
|
hmm.. you had no errors in your first screenshot. do you have dropped packets now as well, that you are using 10mbit FD?
heres my eth1:
| Code: |
eth1 Link encap:Ethernet HWaddr 00:A0:FF:FF:28:05
inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22693170 errors:29 dropped:0 overruns:0 frame:8
TX packets:19931162 errors:74 dropped:0 overruns:0 carrier:33
collisions:61578 txqueuelen:100
RX bytes:2458129898 (2344.2 Mb) TX bytes:965470880 (920.7 Mb)
Interrupt:12 Base address:0xec00
|
| Code: |
ppp0 Link encap:Point-to-Point Protocol
inet addr:217.xxx.xx.xxx P-t-P:217.x.xx.xx Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:58591 errors:0 dropped:0 overruns:0 frame:0
TX packets:38866 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:40540447 (38.6 Mb) TX bytes:4619264 (4.4 Mb)
|
the errors on ETH1 are normal, the uptime is 3 month or so  . my IP changes every 24h - so thats why the errors i guess. as you can see there is nothing wrong with ppp0 (the same card)
well, infact you are using SDSL, i wonder if you havent to set something special in roaring penguin (or whatever you use)? AFAIk SDSL is synchronus negotiation, unlike to ADSL? |
|
| Back to top |
|
|
Selkie
n00b
Joined: 15 Jul 2002
Posts: 27
|
| Posted: Mon Oct 04, 2004 1:25 am Post subject: |
|
|
| Code: |
eth1 Link encap:Ethernet HWaddr 00:E0:29:5B:D4:EB
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9831 errors:10 dropped:0 overruns:0 frame:0
TX packets:11024 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:986521 (963.3 Kb) TX bytes:6081015 (5.7 Mb)
Interrupt:12 Base address:0xd400
ppp0 Link encap:Point-to-Point Protocol
inet addr:212.xxx.xxx.xxx P-t-P:213.xxx.xxx.xxx Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:9772 errors:0 dropped:0 overruns:0 frame:0
TX packets:10966 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:767834 (749.8 Kb) TX bytes:5835835 (5.5 Mb)
|
This is after a fresh reboot of the router and a few minutes of emule, no drops, but obviuosly more errorsthan you
concerning the differnce ADSL/SDSL: i thought that was handled withing the modem, the PC just uses PPPoE and doesn't know/care about the underlying technology
Last edited by Selkie on Mon Oct 04, 2004 1:43 am; edited 1 time in total |
|
| Back to top |
|
|
hds
Advocate
Joined: 21 Aug 2004
Posts: 2629
Location: Sprockhoevel [GER]
|
| Posted: Mon Oct 04, 2004 1:43 am Post subject: |
|
|
but you have no errors on ppp0 either. well, i really dunno, maybe this is just "normal" then? i must admit, everything works well here (no corrupted files or whatever), so i never looked at this deeply yet.
though, if downloading works great and you have a nice pingrate, wonder why your game(s) should lag then. dou you have your emule running while playing?
also i noticed (yeah, sorry<g>) that you have your port80 open. perhaps you get a lot of attacks from windows clients looking to execute whatever virus? check your apache.log |
|
| Back to top |
|
|
|
Networking & Security
