On Tue, 2007-09-25 at 08:27 -0500, Aaron Konstam wrote: > On Mon, 2007-09-24 at 17:09 -0700, Rick Stevens wrote: > > On Mon, 2007-09-24 at 16:58 -0500, Aaron Konstam wrote: > > > On Mon, 2007-09-24 at 19:43 +0200, Gilboa Davara wrote: > > > > On Mon, 2007-09-24 at 13:34 -0400, Jon Shorie wrote: > > > > > Does anyone know how I can find out the speed of my network connection on a > > > > > fedora machine? > > > > > > > > > > On my ubunto boxen, I do a > > > > > > > > > > dmesg | grep eth0 > > > > > > > > > > and it usually tells me > > > > > > > > > > something like: > > > > > > > > > > [ 24.527986] eth0: no IPv6 routers present > > > > > [ 2466.508627] e1000: eth0: e1000_watchdog: NIC Link is Down > > > > > [ 2472.385648] e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full > > > > > Duplex > > > > > > > > > > but on fedora, I get: > > > > > > > > > > eth0: RTL8168b/8111b at 0xf883e000, 00:16:e6:6c:42:a1, IRQ 17 > > > > > r8169: eth0: link up > > > > > r8169: eth0: link up > > > > > eth0: no IPv6 routers present > > > > > r8169: eth0: link down > > > > > r8169: eth0: link up > > > > > > > > > > a uname -r gives me: > > > > > 2.6.20-1.2944.fc6 > > > > > > > > > > any suggestions? I want to know if I am getting a 100 or 1000 mb/s > > > > > connection. > > > > > > > > > > > Thank you > > > > > > > > > > Jon Shorie > > > > > Systems Administrator > > > > > Medina County Sanitary Engineers > > > > > > > > > > > > > $ ethtool ethX > > > ethtool does not do this for me. > > > I get: > > > ethtool eth1 > > > Settings for eth1: > > > Link detected: yes > > > > That's hard to believe for a wired card. > > > > Settings for eth0: > > Supported ports: [ TP ] > > Supported link modes: 10baseT/Half 10baseT/Full > > 100baseT/Half 100baseT/Full > > 1000baseT/Full > > Supports auto-negotiation: Yes > > Advertised link modes: 10baseT/Half 10baseT/Full > > 100baseT/Half 100baseT/Full > > Advertised auto-negotiation: Yes > > ------> Speed: 100Mb/s > > Duplex: Full > > Port: Twisted Pair > > PHYAD: 0 > > Transceiver: internal > > Auto-negotiation: on > > Supports Wake-on: pumbg > > Wake-on: g > > Current message level: 0x00000033 (51) > > Link detected: yes > > > > Is this a wireless card? If so, you need to use iwconfig and look > > for the "Bit Rate" value: > > > > [root@golem3 ~]# iwconfig wlan0 > > wlan0 IEEE 802.11g ESSID:"mynetwork" > > Mode:Managed Frequency:2.452 GHz Access Point: > > xx:xx:xx:xx:xx:xx > > -------> Bit Rate=54 Mb/s > > Retry min limit:7 RTS thr:off Fragment thr=2346 B > > Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx > > Link Quality=100/100 Signal level=-39 dBm Noise level=-95 > > dBm > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > Exactly where in your posting did you say that ethtool only works on > wired cards? I never did, but many wireless drivers don't support ethtool. That's a fact, not conjecture. For example, the iwl4965 driver (with mac80211, etc.) for my Intel card doesn't support ethtool or mii-tool: [root@golem3 ~]# ethtool wlan0 Settings for wlan0: No data available [root@golem3 ~]# mii-tool wlan0 SIOCGMIIPHY on 'wlan0' failed: Operation not supported ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@xxxxxxxxxxxx - - CDN Systems, Internap, Inc. http://www.internap.com - - - - I was married by a judge. I should have asked for a jury. - - -- Groucho Marx - ----------------------------------------------------------------------
