-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It would appear that on Jun 4, T. 'Nifty New Hat' Mitchell did say:
> Netgear hardware seems to have some issues when you are moving
> large piles of bits.
>
> You did not say what physical layer connection you are making to your
> netgear box.
>
> What does mii-tool return?
>
> I have found that my OLD netgear box likes half duplex
> with my network adapter. I do not know if my little bug is
> in the netgear box, mother board or driver.
>
> For me my little bug is easy to work around by
> turning off full duplex.
>
> # mii-tool
> eth0: negotiated 100baseTx-HD, link OK
>
> You can change it...
>
> # mii-tool -A 100baseTx-HD
> or
> # mii-tool -A 100baseTx-FD
>
> This bug was obvious when I was doing an rsync between two
> boxes behind the NAT box.
>
> You may wish to go as far as forcing 10BaseT on the connection
> as a test or connect to the net directly.
>
> Check with netgear for a firmware update.
> Same for the cable modem vendor.
Thanks for the clue.
# mii-tool -v -v
eth0: negotiated 100baseTx-FD flow-control, link ok
registers for MII PHY 1:
1000 782d 02a8 0154 05e1 45e1 0001 0000
0000 0000 0000 0000 0000 0000 0000 0000
0203 0000 0001 ffff 0000 000d ffff 000b
000a 0000 0000 0000 00b0 0000 0000 0000
product info: Intel 82555 rev 4
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
OK I'm definately out of my depth here... It may be that a
# mii-tool -A 100baseTx-HD
would solve the problem like it did for you.
However when I look at "man mii-tool" the text seems to assume a deeper
understanding than I have of the process...
I gather that this
# mii-tool -A 100baseTx-HD
can be done while the internet connection is running? (should I ifdown
first and ifup afterwards?) And is it something that needs to be redone
every time I reboot the PC or more likely every time the router's power
is interupted?
Also, I notice that the man page said of the -A option
"Multiple technologies should be separated by commas. Valid media
are 100baseT4, 100baseTx-FD, 100baseTx-HD, 10baseT-FD, and 10baseT-HD."
So I figured that the only thing I wanted to subtract from the default "advertiseing" was the "100baseTx-FD" so using the above -v -v output as a guide I tried:
# mii-tool -A 100baseTx-HD, 10baseT-FD, 10baseT-HD, flow-control
SIOCGMIIPHY on '10baseT-FD,' failed: No such device
SIOCGMIIPHY on '10baseT-HD,' failed: No such device
SIOCGMIIPHY on 'flow-control' failed: No such device
If the default setting can advertise those media, why can't I include
them in my list of advertised media??
In any case since my router is connected to comcast via a motorola
surfboard, I'm guessing this is all I need to advertize...
# mii-tool -A 100baseTx-HD
restarting autonegotiation...
# mii-tool -v -v
eth0: negotiated 100baseTx-HD, link ok
registers for MII PHY 1:
1000 782d 02a8 0154 0081 45e1 0003 0000
0000 0000 0000 0000 0000 0000 0000 0000
0202 0000 0001 1246 0000 0000 106d 0000
0000 0000 0000 0000 0010 0000 0000 0000
product info: Intel 82555 rev 4
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-HD
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
- --
| ~^~ ~^~
| <?> <?> Joe (theWordy) Philbrook
| ^ J(tWdy)P
| \___/ <<jtwdyp@xxxxxxxx>>
But if I actually knew everything, then I'd know I was an idiot...
##############################################################
# You can find my public gpg key at http://pgpkeys.mit.edu/ #
##############################################################
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAwWJpRZ/61mwhY94RAnpTAKCcB/EFhbyIKLOJZqJwNNtTw66pxgCdHWXt
u+oON8Yq8ez06hsxLC390EY=
=hN2W
-----END PGP SIGNATURE-----
