Re: [leaf-user] Cable Modem speeds with Bering-uClibc
Exactly Bob, and this was why Andrew, I suggested using the DOS utility to force half-duplex, full duplex with testing performed each time. And as far as the networking terms go, errors = bad. Pretty simple. As you can see with your test, every one of those errors are overruns. 3: eth0: BROADCAST,MULTICAST,NOTRAILERS,UP mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:20:af:17:57:b2 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 741077003 1773743 18161 0 18161 0 TX: bytes packets errors dropped carrier collsns 438580149 852431 0 0 219 2150 4: eth1: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:20:af:3f:53:d4 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 440479032 855735 42710 42710 TX: bytes packets errors dropped carrier collsns 680103683 783492 0 0 0 4193 Andrew, you've spent this much time with this, what's another 20 minutes with the DOS utility (which was designed for that card) to change the settings? Tony Bob Coffman Jr - Info From Data wrote: One thing to check is that your NICs are negotiating duplex properly. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Cable Modem speeds with Bering-uClibc
I half understand duplex (don't bother explaining it - I'll look it up for myself) but I don't understand how duplex could be negotiated improperly? I speak from experience! I had EXACTLY the same problem, Internet was slow through the Leaf box, directly connected PC bypassing the router, it was fast. But in testing (ie Leaf not connected to cable modem) it was fast. It was an older box, like yours, with older cards, like yours, and it turned out that duplex was negotiated incorrectly. Once I solved that, it was fine. - Bob - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
[leaf-user] Ok, the Cable Modem discussion has me concerned...
After reading the thread, I checked my Bering uClib 3.0.1 (latest and greatest ISO) and discovered the following using ip -s link: 3: eth0: BROADCAST,MULTICAST,NOTRAILERS,UP mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0c:41:ec:40:78 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 2724718608 42870003 0 0 0 0 TX: bytes packets errors dropped carrier collsns 441074316 4000179 2 0 2 0 4: eth1: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0c:41:e9:34:dd brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1152457833 11965659 79 0 0 0 TX: bytes packets errors dropped carrier collsns 0 011399780 0 11399778 0 5: eth2: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0c:41:e9:36:79 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 6273713538700 0 0 0 TX: bytes packets errors dropped carrier collsns 97303534 772500 0 0 0 I am connected to my ISP via a Motorola Surfboard SB4100 then to my LEAF box which has three LinkSys LNE100TX ver 5.1 cards. eth0: is the FW, as usual eth1: is the private LAN -- connected to a NETGEAR dual speead DS108 10/100 hub eth2: is the DMZ Concerning me is the number of errors on eth1 - I'm wondering if I have similar duplex problems as Bob had. ethtool shows me nothing about my cards, for some reason. I have had intermittent bizarre behavior on the network (that I've been blaming on Comcast). Do I have a problem here? Performance improvements would be a big hit with my users. Ken - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Cable Modem speeds with Bering-uClibc
Andrew Haninger wrote: I half understand duplex (don't bother explaining it - I'll look it up for myself) but I don't understand how duplex could be negotiated improperly? Any number of things could cause that. My concern is, sometimes Motorolas don't handle forced duplex settings well, and sometimes half-duplex will make things problematic to begin with. Example: I have an SB5120. I was testing my father's rather old Wireless B Linksys router because he was getting constant network drops on his DSL. I hooked it up, and it ran okay, but I saw some of the same drops. Upgraded the firmware to the latest and greatest, and suddenly there's a dropdown to configure it for 10 or 100, full or half, but no autodetect. So, since my downstream is 30Mbit/sec, I set it to 100 Full... and it started running like a slug. 100 Half didn't help any either. So I hooked up my PC to the modem direct, and discovered that the SB5120 doesn't like forced duplex modes. 100 Full and Half ran like a slug, but autodetect would configure for 100 full and it ran like a champ. So, it's possible that you've got a similar problem. The difficulty in determining that is that it could just be the firmware on my modem that caused that, and every cable provider does their own firmware releases. You can always try connecting the laptop and forcing 10 full and 10 half to see if the performance is similar to what you're getting out of the LEAF box. If you are, then the problem is that the modem doesn't like the forced settings. If not, then it's probably something on either the cards or the motherboard. Out of curiosity, have you tried switching which card is connected where? In other words, Eth0 internal and Eth1 external? For what it's worth, I've acquired a replacement box that has PCI slots in it and I'll set up my LEAF box with 3c905's (10/100) which should (hopefully) solve the problem. Probably will. I myself had switched over to 3c905Cs when I finally got rid of the 486 system. George - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Ok, the Cable Modem discussion has me concerned...
Ken Gentle wrote: snip! 4: eth1: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0c:41:e9:34:dd brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1152457833 11965659 79 0 0 0 TX: bytes packets errors dropped carrier collsns 0 011399780 0 11399778 0 snip! Concerning me is the number of errors on eth1 - I'm wondering if I have similar duplex problems as Bob had. Nope, that's not a duplex issue. If it were, you'd be getting overruns and collisions. What we've got here is, probably, a bad NIC, bad wire, or bad port on the hub, or a bad hub in general. Notice that you've got zero transmit packets, but nearly as many transmit errors as you do receive packets. I'd try changing the cat 5 and the card, if you've got a spare; probably not the hub, or if it is then it's probably just the port itself, so try a different port too. George Metz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Ok, the Cable Modem discussion has me concerned...
Just what a Software geek loves to hear - its a hardware problem. ;-) Oh, wait a minute, its *my* hardware problem! *PANIC* =-O Luckily, I do have some diagnostic equipment for the CAT 5... and plug pray for the hub ports. Thanks, George. BTW, is there a RTFM of the ip -s link output somewhere? The google for man ip wasn't particularly helpful... At 15:45 2007-02-26, George Metz wrote: Ken Gentle wrote: snip! 4: eth1: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0c:41:e9:34:dd brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1152457833 11965659 79 0 0 0 TX: bytes packets errors dropped carrier collsns 0 011399780 0 11399778 0 snip! Concerning me is the number of errors on eth1 - I'm wondering if I have similar duplex problems as Bob had. Nope, that's not a duplex issue. If it were, you'd be getting overruns and collisions. What we've got here is, probably, a bad NIC, bad wire, or bad port on the hub, or a bad hub in general. Notice that you've got zero transmit packets, but nearly as many transmit errors as you do receive packets. I'd try changing the cat 5 and the card, if you've got a spare; probably not the hub, or if it is then it's probably just the port itself, so try a different port too. George Metz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Ok, the Cable Modem discussion has me concerned...
Hi, Just what a Software geek loves to hear - its a hardware problem. ;-) Oh, wait a minute, its *my* hardware problem! *PANIC* =-O Luckily, I do have some diagnostic equipment for the CAT 5... and plug pray for the hub ports. Thanks, George. BTW, is there a RTFM of the ip -s link output somewhere? The google for man ip wasn't particularly helpful... Yes there is, the suite is called iproute2: http://www.policyrouting.org/iproute2.doc.html Eric At 15:45 2007-02-26, George Metz wrote: Ken Gentle wrote: snip! 4: eth1: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0c:41:e9:34:dd brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 1152457833 11965659 79 0 0 0 TX: bytes packets errors dropped carrier collsns 0 011399780 0 11399778 0 snip! Concerning me is the number of errors on eth1 - I'm wondering if I have similar duplex problems as Bob had. Nope, that's not a duplex issue. If it were, you'd be getting overruns and collisions. What we've got here is, probably, a bad NIC, bad wire, or bad port on the hub, or a bad hub in general. Notice that you've got zero transmit packets, but nearly as many transmit errors as you do receive packets. I'd try changing the cat 5 and the card, if you've got a spare; probably not the hub, or if it is then it's probably just the port itself, so try a different port too. George Metz --- -- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDE V leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
