Personal computing discussed
Moderators: renee, Steel, notfred
Nitrodist wrote:It sounds like you're operating in half-duplex mode. The WRT54G series, if I'm not mistaken as I've seen 10+ of them, all have 100mbit Ethernet ports, so if it was operating in half-duplex mode, then that could very well be what is stopping you.
At 100mbit speeds, the Ethernet wire uses 2 pairs out of the 4 to operate. If one of those pair is damaged, then it could just be using 1 of the pairs to operate at half speed (50 mbit).
The other option is that either port is set to half-duplex operation (on your PC or on the router). AFAIK, the router doesn't have an option for this (at least not with the default firmware).
Might I suggest that you upgrade to a different firmware, as well? There are several flavours out there that are quite robust in comparison to the vanilla firmware that the WRT54GL offers. You even bought the 'L' version, which means that you're able to do that with your router instead of the other flavours which have a small RAM footprint.
arsenhazzard wrote:The router can't handle it. MOST consumer routers can't. It just hasn't mattered (and in most places, still doesn't) since net speeds have been lower than the throughput the routers can handle.
Nitrodist wrote:It sounds like you're operating in half-duplex mode. The WRT54G series, if I'm not mistaken as I've seen 10+ of them, all have 100mbit Ethernet ports, so if it was operating in half-duplex mode, then that could very well be what is stopping you.
At 100mbit speeds, the Ethernet wire uses 2 pairs out of the 4 to operate. If one of those pair is damaged, then it could just be using 1 of the pairs to operate at half speed (50 mbit).
The other option is that either port is set to half-duplex operation (on your PC or on the router). AFAIK, the router doesn't have an option for this (at least not with the default firmware).
Might I suggest that you upgrade to a different firmware, as well? There are several flavours out there that are quite robust in comparison to the vanilla firmware that the WRT54GL offers. You even bought the 'L' version, which means that you're able to do that with your router instead of the other flavours which have a small RAM footprint.
Nitrodist wrote:It sounds like you're operating in half-duplex mode. The WRT54G series, if I'm not mistaken as I've seen 10+ of them, all have 100mbit Ethernet ports, so if it was operating in half-duplex mode, then that could very well be what is stopping you.
At 100mbit speeds, the Ethernet wire uses 2 pairs out of the 4 to operate. If one of those pair is damaged, then it could just be using 1 of the pairs to operate at half speed (50 mbit).
Pizzapotamus wrote:Nitrodist wrote:It sounds like you're operating in half-duplex mode. The WRT54G series, if I'm not mistaken as I've seen 10+ of them, all have 100mbit Ethernet ports, so if it was operating in half-duplex mode, then that could very well be what is stopping you.
At 100mbit speeds, the Ethernet wire uses 2 pairs out of the 4 to operate. If one of those pair is damaged, then it could just be using 1 of the pairs to operate at half speed (50 mbit).
That's not what full and half-duplex mean. Duplexing in regards to ethernet connections is the ability to send and receive simultaneously. Half-duplex means it can only do one at a time, not that it runs at half of 100Mbit/s. If we state the bandwidth as tx and rx added together then the nominal data rate for full-duplex Fast Ethernet would be 200Mbit/s but that requires a rather unrealistic symmetrical traffic pattern and thankfully was apparently too misleading even for most marketers
[nitro ~]$ iperf -c 192.168.1.125
------------------------------------------------------------
Client connecting to 192.168.1.125, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.148 port 44272 connected with 192.168.1.125 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 114 MBytes 95.0 Mbits/sec
Contingency wrote:You tested the switching chip. Try running it across the router (LAN<>WAN) where the CPU has an impact.
Nitrodist wrote:Contingency wrote:You tested the switching chip. Try running it across the router (LAN<>WAN) where the CPU has an impact.
Will do! This is shaping up to be the most fun I've had this weekend.
But, I have to sleep now, so probably in about 16 hours or so I'll get to it.
Nitrodist wrote:Pizzapotamus wrote:Nitrodist wrote:It sounds like you're operating in half-duplex mode. The WRT54G series, if I'm not mistaken as I've seen 10+ of them, all have 100mbit Ethernet ports, so if it was operating in half-duplex mode, then that could very well be what is stopping you.
At 100mbit speeds, the Ethernet wire uses 2 pairs out of the 4 to operate. If one of those pair is damaged, then it could just be using 1 of the pairs to operate at half speed (50 mbit).
That's not what full and half-duplex mean. Duplexing in regards to ethernet connections is the ability to send and receive simultaneously. Half-duplex means it can only do one at a time, not that it runs at half of 100Mbit/s. If we state the bandwidth as tx and rx added together then the nominal data rate for full-duplex Fast Ethernet would be 200Mbit/s but that requires a rather unrealistic symmetrical traffic pattern and thankfully was apparently too misleading even for most marketers
They are separate paragraphs for a reason (they are separate ideas)
The first paragraph I'm saying that the device is set to half-duplex mode. The second paragraph is where one of the pairs is damaged and the actual throughput of the operations is limited through Ethernet frame loss or otherwise.