Intel Pro 1000 MT only runs at 100Mbps

[Inglewood Jack]

I will be running in an Untrusted/DMZ/Trusted zone configuration. I will be backing up servers from my Trusted zone to a server in my DMZ. To facilitate this I need plenty of throughput between the Trusted zone and the DMZ and utilized Intel Pro 1000 MT cards to facilitate it. I can install Untangle just fine and it finds and configures the NIC cards but identifies and runs them as 100Mbps interfaces. Is there any way I can get them to run at 1000Mbps? This will be a deal breaker if I can't get it to work at 1GB hardware speeds; I'd have to go with a different, inferior, and far less robust solution.

Rich Banta
Lifeline Data Centers, LLC

[mdh]

Jack/Rich/<your name here>,

Welcome! There have been many users who have reported throughput at higher speeds than 100mbps. In SUPPORT -> NETWORK INTERFACES, set the mode of each NIC to AUTO-NEGOTIATE, SAVE and see if you can measure what your results really are. Just because we don't list 1gbps doesn't necessarily mean that it won't. Let us know.

[gwijsman]

In the hardware list at:

http://wiki.untangle.com/index.php/Hardware_Compatibility_List

there is:

Pro/1000 Gt Desktop Adapter
v 5.0.3 Works with no modifications

so running on v 5.1.0 I expect my 1 G throughput

I have to discover that it is running on:
100 full duplex
I tryed of cource you auto save trick but it does not work for me.

Any idea what i do wrong (or untangle ;-) )

Gert

[gwijsman]

Is it possible that the speed is 1 G but that the interface is showing 100M?
The other site of the networkkabel looks to indicate 1 G...:confused:

[Mathiau]

i added that nic, i didnt even think to test speeds, since it is on my external side, which only has a 1.5MB fiber line on it, once in the office i will check the details on it.

[mdh]

Just so you guys know.....

When I find posts by the same people on the same subject in multiple places, I am sometimes prone to start cleaning house. I really don't think it gives the posts any more visibility by being in multiple places, and some people tend to ignore them all. I'm letting you know now because I know your goal is to get your questions answered, and many of us would like to help you reach your goal.

[gwijsman]

Hoi mdh,

sorry for messing up your nice forum. I will take more care next time.

But still I have no idea why my nice intel network card shows no 1 Gb connecion to the dmz and the internal network. :-(

Keep up the information sharing!
Regards,
Gert

[md3v]

Run ethtool from the shell and you'll see the current negotiated network speed and duplex:


~ # ethtool eth0 [root @ utm1]
Settings for eth0:
Supported ports: [ MII ]
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
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes


Note the 'Speed' and 'Duplex' shown above.

You could also run mii-tool but its depreciated and essentially out of date.

To validate your network card type and operational mode run dmesg | grep "eth0", for example:


~ # dmesg | grep eth0
[ 84.056452] eth0: Tigon3 [partno(BCM95721) rev 4201 PHY(5750)] (PCI Express) 10/100/1000Base-T Ethernet 00:19:b9:fa:3c:67
[ 84.056457] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] WireSpeed[1] TSOcap[1]
[ 84.056459] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
[ 105.044822] device eth0 entered promiscuous mode
[ 105.044826] audit(1205986542.337:3): dev=eth0 prom=256 old_prom=0 auid=4294967295
[ 106.697905] tg3: eth0: Link is up at 1000 Mbps, full duplex.
[ 106.697908] tg3: eth0: Flow control is off for TX and off for RX.


Note the card info and the 'eth0: Link is up at 1000 Mbps, full duplex' lines above. In our case we're running Untangle 5.1 on a Dell PowerEdge R200.

We have noticed that the speed listed in the Untangle interface does not necessarily match the speed negotiated by the network card/operating system.

m.

[gwijsman]

Thanks md3v

This is my output:

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
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes

Settings for eth1:
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
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes

I had an overnight update of the server (aint it great!)
And now it is correct in 5.2
so the two correspond now to each other!

Thanks for pointing me to the ethtool

Regards,
Gert