2:21 p.m.
I have just noticed that most of my systems now have their Ethernet
interfaces running at 100 MBits/s half duplex rather than the expected
1GBits/s.
I think some update has caused this to happen, probably about 5 days ago
(noticed something was slow). These are KDE/Plasma GUI systems but I'm
not sure if this is due to a change in KDE/Plasma, NetworkManager or
something else.
The KDE/Plasma NeworkManager settings GUI interface now has an "Allow
auto-negotiation" checkbox which I don't think was there before and
there is now the entry ETHTOOL_OPTS="autoneg on" in the
/etc/sysconfig/network-scripts/ifcfg-* file if you set it. It appears
that the default setting is 100MBits/s half duplex rather than auto
negotiate...
3:05 p.m.
On 02/13/18 04:21, Terry Barnaby wrote:
I have just noticed that most of my systems now have their Ethernet
interfaces
running at 100 MBits/s half duplex rather than the expected 1GBits/s.
I think some update has caused this to happen, probably about 5 days ago (noticed
something was slow). These are KDE/Plasma GUI systems but I'm not sure if this is
due to a change in KDE/Plasma, NetworkManager or something else.
The KDE/Plasma NeworkManager settings GUI interface now has an "Allow
auto-negotiation" checkbox which I don't think was there before and there is
now
the entry ETHTOOL_OPTS="autoneg on" in the
/etc/sysconfig/network-scripts/ifcfg-*
file if you set it. It appears that the default setting is 100MBits/s half duplex
rather than auto negotiate...
All of my bare metal systems are KDE only. All of them are fully update. All of
them are running at....
Speed: 1000Mb/s
Duplex: Full
The "Allow auto-negotiation" box has been there for as long as I can recall.
As a
matter of fact, there was (maybe still is) a bug that prevents saving configuration
changes if that box is not checked.
What are the systems connected to? You may want to reset it?
--
A motto of mine is: When in doubt, try it out
3:43 p.m.
On 13/2/18 8:05 am, Ed Greshko wrote:
On 02/13/18 04:21, Terry Barnaby wrote:
> I have just noticed that most of my systems now have their Ethernet interfaces
> running at 100 MBits/s half duplex rather than the expected 1GBits/s.
>
> I think some update has caused this to happen, probably about 5 days ago (noticed
> something was slow). These are KDE/Plasma GUI systems but I'm not sure if this
is
> due to a change in KDE/Plasma, NetworkManager or something else.
>
> The KDE/Plasma NeworkManager settings GUI interface now has an "Allow
> auto-negotiation" checkbox which I don't think was there before and there is
now
> the entry ETHTOOL_OPTS="autoneg on" in the
/etc/sysconfig/network-scripts/ifcfg-*
> file if you set it. It appears that the default setting is 100MBits/s half duplex
> rather than auto negotiate...
All of my bare metal systems are KDE only. All of them are fully update. All of
them are running at....
Speed: 1000Mb/s
Duplex: Full
The "Allow auto-negotiation" box has been there for as long as I can recall.
As a
matter of fact, there was (maybe still is) a bug that prevents saving configuration
changes if that box is not checked.
What are the systems connected to? You may want to reset it?
I am using a home plug device to get ethernet access across the home
electrical wires. The home plug device is provide 500 Mb/s, so having
seen this thread I've checked my ethernet configuration and like Terry
is saying my settings have auto negotiate unchecked and the link speed
is set at 100 Mb/s and Half Duplex. I have not explicitly set that
configuration but what I don't know, because I haven't really taken any
notice of it as I only use this connection as a backup to wireless, is
whether or not those settings have always been there. I have done any
changes to the configuration since I set it up in F26.
regards,
Steve
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
3:46 p.m.
On 13/2/18 8:43 am, Stephen Morris wrote:
On 13/2/18 8:05 am, Ed Greshko wrote:
> On 02/13/18 04:21, Terry Barnaby wrote:
>> I have just noticed that most of my systems now have their Ethernet
>> interfaces
>> running at 100 MBits/s half duplex rather than the expected 1GBits/s.
>>
>> I think some update has caused this to happen, probably about 5 days
>> ago (noticed
>> something was slow). These are KDE/Plasma GUI systems but I'm not
>> sure if this is
>> due to a change in KDE/Plasma, NetworkManager or something else.
>>
>> The KDE/Plasma NeworkManager settings GUI interface now has an "Allow
>> auto-negotiation" checkbox which I don't think was there before and
>> there is now
>> the entry ETHTOOL_OPTS="autoneg on" in the
>> /etc/sysconfig/network-scripts/ifcfg-*
>> file if you set it. It appears that the default setting is
>> 100MBits/s half duplex
>> rather than auto negotiate...
>
> All of my bare metal systems are KDE only. All of them are fully
> update. All of
> them are running at....
>
> Speed: 1000Mb/s
> Duplex: Full
>
> The "Allow auto-negotiation" box has been there for as long as I can
> recall. As a
> matter of fact, there was (maybe still is) a bug that prevents saving
> configuration
> changes if that box is not checked.
>
> What are the systems connected to? You may want to reset it?
I am using a home plug device to get ethernet access across the home
electrical wires. The home plug device is provide 500 Mb/s, so having
seen this thread I've checked my ethernet configuration and like Terry
is saying my settings have auto negotiate unchecked and the link speed
is set at 100 Mb/s and Half Duplex. I have not explicitly set that
configuration but what I don't know, because I haven't really taken
any notice of it as I only use this connection as a backup to
wireless, is whether or not those settings have always been there. I
have done any changes to the configuration since I set it up in F26.
Just further to this, on my system when the auto negotiate box is
checked the link entry and the duplex entry are removed from the dialog.
regards,
Steve
>
>
> regards,
>
> Steve
>
>
>>
>>
>> _______________________________________________
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
4:42 p.m.
On 02/13/18 05:46, Stephen Morris wrote:
Just further to this, on my system when the auto negotiate box is
checked the link
entry and the duplex entry are removed from the dialog.
Which makes perfect sense, right?
If the negotiation is automatic then displaying the manual choices would be confusing
don't you think?
--
A motto of mine is: When in doubt, try it out
3:35 p.m.
On 13/2/18 9:42 am, Ed Greshko wrote:
On 02/13/18 05:46, Stephen Morris wrote:
> Just further to this, on my system when the auto negotiate box is checked the link
> entry and the duplex entry are removed from the dialog.
Which makes perfect sense, right?
If the negotiation is automatic then displaying the manual choices would be confusing
don't you think?
I was just surprised that it did that as I'm used to environments where,
when doing the same thing, the manual entries are ghosted rather than
removed. I was also confused by this when in your previous thread you
said you thought that you may still have to have auto negotiate checked
for configuration changes to be saved.
regards,
Steve
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
4:07 p.m.
On 02/14/18 05:35, Stephen Morris wrote:
On 13/2/18 9:42 am, Ed Greshko wrote:
> On 02/13/18 05:46, Stephen Morris wrote:
>> Just further to this, on my system when the auto negotiate box is checked the
link
>> entry and the duplex entry are removed from the dialog.
>
> Which makes perfect sense, right?
>
> If the negotiation is automatic then displaying the manual choices would be
confusing
> don't you think?
I was just surprised that it did that as I'm used to environments where, when doing
the same thing, the manual entries are ghosted rather than removed. I was also
confused by this when in your previous thread you said you thought that you may
still have to have auto negotiate checked for configuration changes to be saved.
Different GUI developers do things in different ways. Not a big deal to me.
The BZ about changes not taking was 1492378. Don't know if it is fixed. Feel free
to test it.
--
A motto of mine is: When in doubt, try it out
3:51 p.m.
On 02/13/18 05:43, Stephen Morris wrote:
I am using a home plug device to get ethernet access across the home
electrical
wires. The home plug device is provide 500 Mb/s, so having seen this thread I've
checked my ethernet configuration and like Terry is saying my settings have auto
negotiate unchecked and the link speed is set at 100 Mb/s and Half Duplex. I have
not explicitly set that configuration but what I don't know, because I haven't
really taken any notice of it as I only use this connection as a backup to
wireless, is whether or not those settings have always been there. I have done any
changes to the configuration since I set it up in F26.
One can always use
ethtool <devname> to determine what is available and what the current settings
are...
This is the view from the Fedora side....
This is what the Fedora side it telling the outside world what the HW supports
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
This is what the device that the Fedora system is connected to is saying what it
supports.
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
FWIW, I have never seen an advertised link speed of 500 Mb/s.
--
A motto of mine is: When in doubt, try it out
1:16 a.m.
On 12/02/18 21:51, Ed Greshko wrote:
On 02/13/18 05:43, Stephen Morris wrote:
> I am using a home plug device to get ethernet access across the home electrical
> wires. The home plug device is provide 500 Mb/s, so having seen this thread I've
> checked my ethernet configuration and like Terry is saying my settings have auto
> negotiate unchecked and the link speed is set at 100 Mb/s and Half Duplex. I have
> not explicitly set that configuration but what I don't know, because I
haven't
> really taken any notice of it as I only use this connection as a backup to
> wireless, is whether or not those settings have always been there. I have done any
> changes to the configuration since I set it up in F26.
One can always use
ethtool <devname> to determine what is available and what the current settings
are...
This is the view from the Fedora side....
This is what the Fedora side it telling the outside world what the HW supports
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
This is what the device that the Fedora system is connected to is saying what it
supports.
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
FWIW, I have never seen an advertised link speed of 500 Mb/s.
Yes, I used ethtool to find out what was happening after the performance
of NFS went down to 10 MBytes/s.
I think what has happened is:
1. I updated these systems (5 off) from F25. This was a clean/new
install but some configuration files were copied from the previous systems.
2. The /etc/sysconfig/network-scripts/ifcfg-Wired_connection_1 file (or
appropriate named one) was copied from the previous system.
3. These files did not have the new ETHTOOL_OPTS="autoneg on" entry.
4. All was working fine (Gigabit full duplex) for a month or so until
someone/something updated the ifcfg file. If you use the KDE-Plasma
NetworkManager settings tool and it sees no ETHTOOL_OPTS entry, it sets
the GUI settings to manual 100Mbits/s half duplex rather than auto. So
if you don't notice this and save the settings the Ethernet will be set
to this. I will try and enter a bug report for this somewhere.
In my case I don't believe I changed the Ethernet settings using the
KDE-Plasma NetworkManager settings tool, certainly not on all of the
systems. I think something else may have written the
ETHTOOL_OPTS="100mbps" entry somehow with an RPM update within the last
week.
8:53 a.m.
If auto neg is set on one end, and not on the other end, then the
standards says set things to 100mb/half (for gbit cards) since you
were unable to get information from the other end I believe this was
judged the most likely to work reasonably by the people who write the
standard. On 100mbit adapters the fail-safe was 10mb/half.
If the device on the other end is not doing auto-neg then I would
expect 100/half.
Either set the other end to auto-neg or figure out what the other end
does and set the computer end to match how it is explicitly set (if
not auto-neg).
If both ends are set to auto-neg and you are getting 100/half then
something is being detected to be wrong with the wiring and both ends
are using what they believe will run on the given wiring. This could
be broken wires, badly terminated wires, or not quite plugged in
right, or a number of other things.
On Tue, Feb 13, 2018 at 1:16 AM, Terry Barnaby <terry1(a)beam.ltd.uk> wrote:
> On 12/02/18 21:51, Ed Greshko wrote:
>>
>> On 02/13/18 05:43, Stephen Morris wrote:
>>>
>>> I am using a home plug device to get ethernet access across the home
>>> electrical
>>> wires. The home plug device is provide 500 Mb/s, so having seen this
>>> thread I've
>>> checked my ethernet configuration and like Terry is saying my settings
>>> have auto
>>> negotiate unchecked and the link speed is set at 100 Mb/s and Half
>>> Duplex. I have
>>> not explicitly set that configuration but what I don't know, because I
>>> haven't
>>> really taken any notice of it as I only use this connection as a backup
>>> to
>>> wireless, is whether or not those settings have always been there. I have
>>> done any
>>> changes to the configuration since I set it up in F26.
>>
>>
>> One can always use
>>
>> ethtool <devname> to determine what is available and what the current
>> settings are...
>>
>> This is the view from the Fedora side....
>>
>> This is what the Fedora side it telling the outside world what the HW
>> supports
>>
>> Advertised link modes: 10baseT/Half 10baseT/Full
>> 100baseT/Half 100baseT/Full
>> 1000baseT/Half 1000baseT/Full
>>
>> This is what the device that the Fedora system is connected to is saying
>> what it
>> supports.
>>
>>
>> Link partner advertised link modes: 10baseT/Half 10baseT/Full
>> 100baseT/Half 100baseT/Full
>> 1000baseT/Full
>>
>> FWIW, I have never seen an advertised link speed of 500 Mb/s.
>
>
> Yes, I used ethtool to find out what was happening after the performance of
> NFS went down to 10 MBytes/s.
>
> I think what has happened is:
>
> 1. I updated these systems (5 off) from F25. This was a clean/new install
> but some configuration files were copied from the previous systems.
>
> 2. The /etc/sysconfig/network-scripts/ifcfg-Wired_connection_1 file (or
> appropriate named one) was copied from the previous system.
>
> 3. These files did not have the new ETHTOOL_OPTS="autoneg on" entry.
>
> 4. All was working fine (Gigabit full duplex) for a month or so until
> someone/something updated the ifcfg file. If you use the KDE-Plasma
> NetworkManager settings tool and it sees no ETHTOOL_OPTS entry, it sets the
> GUI settings to manual 100Mbits/s half duplex rather than auto. So if you
> don't notice this and save the settings the Ethernet will be set to this. I
> will try and enter a bug report for this somewhere.
>
> In my case I don't believe I changed the Ethernet settings using the
> KDE-Plasma NetworkManager settings tool, certainly not on all of the
> systems. I think something else may have written the
ETHTOOL_OPTS="100mbps"
> entry somehow with an RPM update within the last week.
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
11:51 a.m.
On Tue, Feb 13, 2018 at 1:16 AM, Terry Barnaby
<terry1(a)beam.ltd.uk> wrote:
> On 12/02/18 21:51, Ed Greshko wrote:
>> On 02/13/18 05:43, Stephen Morris wrote:
>>> I am using a home plug device to get ethernet access across the home
>>> electrical
>>> wires. The home plug device is provide 500 Mb/s, so having seen this
>>> thread I've
>>> checked my ethernet configuration and like Terry is saying my settings
>>> have auto
>>> negotiate unchecked and the link speed is set at 100 Mb/s and Half
>>> Duplex. I have
>>> not explicitly set that configuration but what I don't know, because I
>>> haven't
>>> really taken any notice of it as I only use this connection as a backup
>>> to
>>> wireless, is whether or not those settings have always been there. I have
>>> done any
>>> changes to the configuration since I set it up in F26.
>>
>> One can always use
>>
>> ethtool <devname> to determine what is available and what the current
>> settings are...
>>
>> This is the view from the Fedora side....
>>
>> This is what the Fedora side it telling the outside world what the HW
>> supports
>>
>> Advertised link modes: 10baseT/Half 10baseT/Full
>> 100baseT/Half 100baseT/Full
>> 1000baseT/Half 1000baseT/Full
>>
>> This is what the device that the Fedora system is connected to is saying
>> what it
>> supports.
>>
>>
>> Link partner advertised link modes: 10baseT/Half 10baseT/Full
>> 100baseT/Half 100baseT/Full
>> 1000baseT/Full
>>
>> FWIW, I have never seen an advertised link speed of 500 Mb/s.
>
> Yes, I used ethtool to find out what was happening after the performance of
> NFS went down to 10 MBytes/s.
>
> I think what has happened is:
>
> 1. I updated these systems (5 off) from F25. This was a clean/new install
> but some configuration files were copied from the previous systems.
>
> 2. The /etc/sysconfig/network-scripts/ifcfg-Wired_connection_1 file (or
> appropriate named one) was copied from the previous system.
>
> 3. These files did not have the new ETHTOOL_OPTS="autoneg on" entry.
>
> 4. All was working fine (Gigabit full duplex) for a month or so until
> someone/something updated the ifcfg file. If you use the KDE-Plasma
> NetworkManager settings tool and it sees no ETHTOOL_OPTS entry, it sets the
> GUI settings to manual 100Mbits/s half duplex rather than auto. So if you
> don't notice this and save the settings the Ethernet will be set to this. I
> will try and enter a bug report for this somewhere.
>
> In my case I don't believe I changed the Ethernet settings using the
> KDE-Plasma NetworkManager settings tool, certainly not on all of the
> systems. I think something else may have written the
ETHTOOL_OPTS="100mbps"
> entry somehow with an RPM update within the last week.
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
On 13/02/18
14:53, Roger Heflin wrote:
If auto neg is set on one end, and not on the other end, then the
standards says set things to 100mb/half (for gbit cards) since you
were unable to get information from the other end I believe this was
judged the most likely to work reasonably by the people who write the
standard. On 100mbit adapters the fail-safe was 10mb/half.
If the device on the other end is not doing auto-neg then I would
expect 100/half.
Either set the other end to auto-neg or figure out what the other end
does and set the computer end to match how it is explicitly set (if
not auto-neg).
If both ends are set to auto-neg and you are getting 100/half then
something is being detected to be wrong with the wiring and both ends
are using what they believe will run on the given wiring. This could
be broken wires, badly terminated wires, or not quite plugged in
right, or a number of other things.
In my case it is the KDE-PLASMA/NetworkManager
configuration that was
forcing 100 MBits/s half duplex at the Linux end. There are
configuration parameters for this now in the KDE-PLASMA applet. Its just
that these default to 100 MBits/s half duplex when there is no setting
in the ifcfg-* file rather than a more useful "auto negotiate" setting.
So if you are using older ifcfg-* files from previous Linux system
versions, you might have the same issue as i did.
3:57 p.m.
On 13/2/18 8:51 am, Ed Greshko wrote:
On 02/13/18 05:43, Stephen Morris wrote:
> I am using a home plug device to get ethernet access across the home electrical
> wires. The home plug device is provide 500 Mb/s, so having seen this thread I've
> checked my ethernet configuration and like Terry is saying my settings have auto
> negotiate unchecked and the link speed is set at 100 Mb/s and Half Duplex. I have
> not explicitly set that configuration but what I don't know, because I
haven't
> really taken any notice of it as I only use this connection as a backup to
> wireless, is whether or not those settings have always been there. I have done any
> changes to the configuration since I set it up in F26.
One can always use
ethtool <devname> to determine what is available and what the current settings
are...
This is the view from the Fedora side....
This is what the Fedora side it telling the outside world what the HW supports
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
This is what the device that the Fedora system is connected to is saying what it
supports.
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
FWIW, I have never seen an advertised link speed of 500 Mb/s.
I ran the ethtool command and received the following output:
ethtool enp7s0
Settings for enp7s0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
This surprises me, as this is saying the home plug device is only
running at 100 Mbps, but it is packaged as 500 Mbps and the device
itself has 500 Mbps physically stamped on the front of it. I did set the
manual configuration to 500 Mbps and full duplex, and when I turned on
auto negotiate and then switched it off, the link speed was reset to 100
Mbps.
regards,
Steve
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
8:05 p.m.
On 02/13/2018 01:57 PM, Stephen Morris wrote:
On 13/2/18 8:51 am, Ed Greshko wrote:
> On 02/13/18 05:43, Stephen Morris wrote:
>> I am using a home plug device to get ethernet access across the home
>> electrical
>> wires. The home plug device is provide 500 Mb/s, so having seen this
>> thread I've
>> checked my ethernet configuration and like Terry is saying my
>> settings have auto
>> negotiate unchecked and the link speed is set at 100 Mb/s and Half
>> Duplex. I have
>> not explicitly set that configuration but what I don't know, because
>> I haven't
>> really taken any notice of it as I only use this connection as a
>> backup to
>> wireless, is whether or not those settings have always been there. I
>> have done any
>> changes to the configuration since I set it up in F26.
>
> One can always use
>
> ethtool <devname> to determine what is available and what the
> current settings are...
>
> This is the view from the Fedora side....
>
> This is what the Fedora side it telling the outside world what the HW
> supports
>
> Advertised link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Half 1000baseT/Full
>
> This is what the device that the Fedora system is connected to is
> saying what it
> supports.
>
>
> Link partner advertised link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
>
> FWIW, I have never seen an advertised link speed of 500 Mb/s.
I ran the ethtool command and received the following output:
ethtool enp7s0
Settings for enp7s0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
This surprises me, as this is saying the home plug device is only
running at 100 Mbps, but it is packaged as 500 Mbps and the device
itself has 500 Mbps physically stamped on the front of it. I did set the
manual configuration to 500 Mbps and full duplex, and when I turned on
auto negotiate and then switched it off, the link speed was reset to 100
Mbps.
The fact that the link partner advertises 10 and 100baseT, either full
or half duplex indicates that 100baseT/Full is the max it can do (at
least on that port). Typically, a switch won't advertise a higher speed
than it can do. It can, however, connect at a lower speed than it
advertises. In other words, 10Mbps and 100Mbps aren't the _only_ speeds
it can do, but it can't go above 100Mbps on that port.
As an example, I have some HP gear that has a segmentable 10Gbps switch
where I've divvied up its 10Gbps bandwidth into three VLANs, two at
4.5Gbps and one at 1Gbps. Looking at the interfaces of one of the
machines connected to one of the 4.5Gbps VLANs, you find this:
[root@seg3-r0 ~]# ethtool eth2
Settings for eth2:
Supported ports: [ TP ]
Supported link modes: 1000baseT/Full
10000baseT/Full
Supports auto-negotiation: No
Advertised link modes: 1000baseT/Full
10000baseT/Full
Advertised auto-negotiation: No
Speed: 4500Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Link detected: yes
Note that the host can do 1000baseT/Full and 10000baseT/Full. I'm not
sure if the switch advertises (I'm sure it does but the host I'm looking
at is an ancient CentOS 5 machine so its ethtool output may be different
than current versions). That being said, the actual speed of the link
is 4500Mbps (4.5Gbps), which is what I expect over that link. Before you
ask, it's not really twisted pair, it's a backplane...this is all in a
big blade-based system.
On your host, you can try to force a faster speed by doing
ethtool -s enp7s0 speed 500
as root to see if you can get it to go 500Mbps (or "...speed 250" to try
250Mbps). I doubt it'll work, but it's quick and easy to try.
Just because the device is advertised at 500Mbps doesn't mean it can
actually do it and it may be that it's 500Mbps _aggregate_ (i.e. if it
has five ports, each can be set to 100Mbps without contention). If
that's the case, yes the device can do 500Mbps total and they didn't
fib about it, but any _single_ port is limited to 100Mbps.
Now, if the device supports 802.3ad, you could use two NICs on your
host to two ports on the device, set up bonding using mode 4 and get
200Mbps (ok, now I'm just getting crazy!)
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Never test for an error condition you don't know how to handle. -
----------------------------------------------------------------------
8:49 p.m.
On 02/13/2018 01:57 PM, Stephen Morris wrote:
This surprises me, as this is saying the home plug device is only
running at 100 Mbps, but it is packaged as 500 Mbps and the device
itself has 500 Mbps physically stamped on the front of it. I did set the
manual configuration to 500 Mbps and full duplex, and when I turned on
auto negotiate and then switched it off, the link speed was reset to 100
Mbps.
Welcome to the world of marketing. I assume the protocol can do that
speed, but the ethernet port on the device can only handle up to 100.
The ethernet card in your computer can only do 10, 100, 1000 Mbps.
There are no other options. You can't do 500Mbps and the other side has
already said it doesn't support 1000.
2282
days inactive
2284
days old
13 comments
7 participants
participants (7)
-
Ed Greshko -
Ed Greshko -
Rick Stevens -
Roger Heflin -
Samuel Sieb -
Stephen Morris -
Terry Barnaby