How to remove a damaged Wired Connection
Colin Law
clanlaw at gmail.com
Sun Sep 4 07:29:07 UTC 2016
On 4 September 2016 at 06:31, Chas IRONS <ironscf at telkomsa.net> wrote:
> ...
> As you suggested above I started the PC & ran ifconfig:
> chas at Charles-PC:~$ sudo ifconfig -a
> [sudo] password for chas:
> eth0 Link encap:Ethernet HWaddr 10:c3:7b:6a:c5:ea
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:1700 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1700 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1
> RX bytes:125976 (125.9 KB) TX bytes:125976 (125.9 KB)
> ******************
> Then started the router & ran ifconfig:
> chas at Charles-PC:~$ sudo ifconfig -a
> eth0 Link encap:Ethernet HWaddr 10:c3:7b:6a:c5:ea
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> eth1 Link encap:Ethernet HWaddr 3c:1e:04:96:54:05
> inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::3e1e:4ff:fe96:5405/64 Scope:Link
> inet6 addr: fc00::3e1e:4ff:fe96:5405/64 Scope:Global
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:285 errors:2 dropped:0 overruns:0 frame:0
> TX packets:351 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:22491 (22.4 KB) TX bytes:56209 (56.2 KB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:2199 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2199 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1
> RX bytes:157589 (157.5 KB) TX bytes:157589 (157.5 KB)
>
> chas at Charles-PC:~$
> ******************
> Before I could paste the results above, a message showed "Disconnected" and
> soon "Connected" again.
>
> Restarted the PC & ran ifconfig:
> chas at Charles-PC:~$ sudo ifconfig -a
> [sudo] password for chas:
> eth0 Link encap:Ethernet HWaddr 10:c3:7b:6a:c5:ea
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> eth1 Link encap:Ethernet HWaddr 3c:1e:04:96:54:05
> inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::3e1e:4ff:fe96:5405/64 Scope:Link
> inet6 addr: fc00::3e1e:4ff:fe96:5405/64 Scope:Global
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:95 errors:0 dropped:0 overruns:0 frame:0
> TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:42811 (42.8 KB) TX bytes:37283 (37.2 KB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:253 errors:0 dropped:0 overruns:0 frame:0
> TX packets:253 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1
> RX bytes:21110 (21.1 KB) TX bytes:21110 (21.1 KB)
>
> chas at Charles-PC:~$
> Hooray. Opera works on my ISP websites so the router is "Connected"
> So what do you suggest now?
> Sorry for the long email with all the ifconfig results.
> I wonder if I could disable the network card (eth0) in bios before Ubuntu
> boots up?
I don't know why you think that would help. I do not see that the
problem is anything to do with eth0. Is this a correct summary of the
situation:
1. If you restart the router, so it is in a known good working state,
and then start the PC everything works correctly.
2. If you wait till the router is in a strange state (not responding
to the power down switch) and start the PC then the PC does not
connect to the router until you power cycle the router.
If the above is correct then it seems to me, as I previously
suggested, that there is a problem with the router and nothing wrong
with the PC at all.
I suggest (if you have not already done it) that you check to see if
there is a firmware upgrade for the router and apply that if so. If
not then either get a replacement router or resign yourself to
resetting when required.
Colin
More information about the ubuntu-users
mailing list