Quote:
Originally Posted by computersavvy
Realistically, to avoid network issues, you should not connect both ethernet and wifi at the same time. Unless you are connecting to different networks it usually causes conflicts and communication errors.
If you want to use ethernet then I suggest that you use the settings panel and turn off wifi then connect the ethernet. It should just work, and if not then you can manually connect it, also using the settings panel.
If instead you wish to use wifi then I suggest you not connect the ethernet since wifi is already configured.
As to your question about the led on the ethernet port.
If I am reading the question properly it seems the light for the port on the router is staying on. My first reaction to that would be 1) power cycle the router. If the light fails to turn off with no cable connected then 2) consider replacing the router. The led on with no cable connected shows the port senses a connection even with nothing connected.
|
Thank you! @computersavvy
on the notebook; In reality, the amber LED is off (it does not turn on) and only the green LED remains on, whether or not a network cable is connected.
Some time ago, after a system update, I had received a Tigon3 "firmware missing" message.
I didn't give it much importance at the time because everything was working fine; and I said that I would see it later, since then a lot of time has passed and now I just wanted to clear up the doubts if it is just a misconfiguration or the port is physically damaged.
Code:
lspci | egrep -i --color 'network|ethernet'
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5764M Gigabit Ethernet PCIe (rev 10)
Quote:
Originally Posted by michaelk
I assume your system as to networking has not been changed from the default installation.
Typically network manager when a cable is plugged in and a link established will automatically switch from wireless to wired and when the cable is disconnected will switch back to wireless.
If the the link light remains illuminated when the cable is disconnected then there is a good possibility ethernet is bad.
Was the output of the ethtool command ran when the cable was connected or disconnected?
|
@michaelk I have executed the ethtool command with the cable connected, and then without the cable connected. Compare the outputs and they were the same, so attach an answer.
Quote:
Originally Posted by Soadyheid
What have you done to see if the ethernet works?
Have you tried pinging anywhere?
Code:
$ping google.com
PING google.com (216.58.212.206) 56(84) bytes of data.
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=1 ttl=115 time=24.2 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=2 ttl=115 time=23.4 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=3 ttl=115 time=20.2 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=4 ttl=115 time=19.7 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=5 ttl=115 time=20.4 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=6 ttl=115 time=26.8 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=7 ttl=115 time=20.1 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=8 ttl=115 time=19.6 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=9 ttl=115 time=19.8 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=10 ttl=115 time=19.9 ms
64 bytes from ams16s21-in-f206.1e100.net (216.58.212.206): icmp_seq=11 ttl=115 time=19.7 ms
If you get a response as above, it works, i.e. it's running.
(I never check the lights as my desktop lives under the bench in my "Man Cave". Can't see them!)
My 
Play Bonny!
 |
@Soadyheid there is no ping; Destination host is unreachable. I have already verified the "/etc/network/interfaces", when in doubt of a bad assignment. I tried "inet static" and "inet dhcp". And there is nothing.
Quote:
Originally Posted by uteck
I had an odd issue with my laptop were Network Manager was not managing the ethernet port, just the wireless. So it did nothing when I plugged in a cable.
What does this command report?
If Network Manager is not controlling an interface, its STATE will be listed as unmanaged. |
@uteck result of:
is:
Code:
DEVICE TYPE STATE CONNECTION
enp2s0 ethernet not available --
__
personal comment; I imagine that the easiest thing would be to disassemble the entire motherboard and make some measurements, so we would be ruling out possible physical damage to the port.
But I have my doubts, as I mentioned above, that after the system update. I wonder;
Perhaps the firmware that corresponds to the Ethernet port has been removed or removed from the Debian repositories ? But, must there be a method to determine by software that the port is physically damaged?
Actually, I don't know what I would do without all the support and recommendations. From now on, I am grateful to each of you.
¿ Ethernet running or not running ?
