search for: 10baset

...bonding/bond0` I get 100Mbps for the member interfaces, and when I ` mii-tool bond0` I get 10Mbps for the bond? ----------------------------------------------------------------------------------------- ethtool em1 Settings for em1: 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...

in dom0, how does one get and set the link information for a NIC? In a non-xen kernel, we could get this info by simply running: # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s...

...d, but trying to continue You probably have a hardware problem with your RAM chips TLAN: eth0: Adaptor Error = 0x180002 TLAN: eth0: Starting autonegotiation. TLAN: eth0: Autonegotiation complete. TLAN: eth0: Link active with AutoNegotiation enabled, at 100Mbps Full-Duplex TLAN: Partner capability: 10BaseT-HD 10BaseT-FD 100baseTx-HD 100baseTx-FD TLAN: eth0: Adaptor Error = 0x180002 TLAN: eth0: Starting autonegotiation. TLAN: eth0: Autonegotiation complete. TLAN: eth0: Link active with AutoNegotiation enabled, at 100Mbps Full-Duplex TLAN: Partner capability: 10BaseT-HD 10BaseT-FD 100baseTx-HD 100base...

...Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) It is detected, but why the speed is always 100Mbps, already change cable but still no luck. I use ethtool and from the output it seems that system know that this NIC support gigabit speed : ??????? 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 ?????????????????...

...status: active inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::202:55ff:fe30:5428%fxp0 prefixlen 64 scopeid 0x1 xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:01:02:78:11:e8 media: Ethernet autoselect (10baseT) status: active inet 203.219.167.126 netmask 0xfffffffc broadcast 203.219.167.127 inet6 fe80::201:2ff:fe78:11e8%xl0 prefixlen 64 scopeid 0x2 For fxp0, the internal interface although the nic can do full-duplex it seems to me that it is only running simplex!! Same for x...

Hi there, I'm having an odd problem where this NIC (cheap-o, yes I know) doesn't seem to work on FreeBSD correctly. I have the same cards (even revision models) in two win boxen and they work fine. 10baseT works but not 100baseT. With a normal NIC config, without explicitly setting the media to 10baseT, it will autosense as 100BaseT @ full-duplex, showing active. However I can't ping any IP. My switch indicates that the port is not active either. If a 10baseT config, the switch will recognise...

My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on

...T too. > > anyone else run into anything like this before? oh. # mii-tool -v eth0 eth0: negotiated, link ok product info: vendor 00:50:43, model 11 rev 1 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 # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full...

...want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full                             1000baseT/Half 1000baseT/Full     Supports auto-negotiation: Yes     Advertised link modes:  10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full                  ...

...want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full                             1000baseT/Half 1000baseT/Full     Supports auto-negotiation: Yes     Advertised link modes:  10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full                  ...

...that doesn''t support the extra network function calls, or if I am dealing with a mismatch between the ethtool and the xen kernel. Any ideas? It should look like this: [root@fermigrid4 var]# ethtool eth0 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...

...e0: EEPROM read timed out bge0: failed to read EEPROM device_attach: bge0 attach returned 6 bge1: <Broadcom BCM5703 B0, ASIC rev. 0x1100> mem 0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3 miibus0: <MII bus> on bge1 brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:21:5e:4d:05:c8 any hints? P.S. I see EEPROM timeout fixes were already merged to RELENG_6 (I have post-fix version certainly). May that issue be somehow related? -- wbr, pluknet

We have an HP DL360 server with dual on-board Tigon3 ethernet cards. We are using eth0, eth1 is unused at the moment. Sometimes when the network interface is under heavy load, for example moving large file transfers over rsync or NFS, the network interface stops working and we lose all connection to the server. The only solution at this point is to jump on the console and restart the network

Hi List, I am running a x86_64 Centos server, after a reboot the network has decided to not work.. this particular machine has 8 eth ports eth0-7. eth0 and eth3 were bonded (mode 1 ) after reboot the bond did not work. It came up OK but no data was passing through it. all other interfaces on the machine were working. I decided to remove the bond, so after removing the bond i was left with eth0

...t = @root [web] comment = Web Root path = /var/www/html read only = no ##public = yes writable = yes group = samba create mask = 0664 directory mask = 0775 ##guest ok = yes ethtool info: 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...

anyone know how to force network cards talk at gig speeds when all it wants to do is establish a connection at 100mbits root at host1 [/backup/cpbackup/daily]# mii-tool eth0: negotiated 100baseTx-FD, link ok eth1: negotiated 100baseTx-FD flow-control, link ok 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11) Subsystem: Broadcom

...this that mabye I can bounce a few questions off you? Heres some output to look at: >> ifconfig -a pn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 ether 87:ff:87:ff:87:ff media: autoselect (10baseT/UTP <half-duplex>) supported media: autoselect 100baseT4 100baseTX <full-duplex> 100baseTX <half-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex> 10baseT/UTP lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 tun0: flags=801...

I'm experiencing similar problems with a 3C996-T under 4.8-REL. In particular, connecting a 4.8-REL machine to a 5.1-REL machine leads to some interesting situations: I can do simple pings across the link, but ssh fails, and heavy pings crash the 4.8 machine. Similarly changing the interface configuration with ifconfig tends to crash the 4.8 machine (mtu, link0, up/down, etc). The

I've got a pair of identical CentOS 6.7 servers, with SuperMicro X8DTE-F motherboards, these have 2 each Intel 82574L ethernet ports. The eth0 ports are plugged in with 10' runs of brand new cat 5e cable to a Cisco Nexxus 9000 switch (provided by the data center). These servers keep coming up at 100baseT rather than gigE. I've swapped ports and cables with a different server,

...ogic GD5430 SVGA controller> at 6.0 tl0: <Compaq Netelligent 10/100 Proliant> port 0x6480-0x648f mem 0x40001500-0x4000150f irq 5 at device 7.0 on pci1 tl0: Ethernet address: 00:08:c7:78:08:57 miibus0: <MII bus> on tl0 nsphy0: <DP83840 10/100 media interface> on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto tlphy0: <ThunderLAN 10baseT media interface> on miibus0 tlphy0: 10base2/BNC, 10base5/AUI sym0: <875> port 0x6000-0x60ff mem 0x40000000-0x40000fff,0x40001400-0x400014ff irq 11 at device 9.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity ch...