How to remove a damaged Wired Connection

[Ralf Mardorf]

On Sun, 2016-08-28 at 19:17 +0200, Ralf Mardorf wrote:
> On Sun, 28 Aug 2016 10:16:59 -0600, compdoc wrote:
> > You [snipped] off some of the important parts.
> The OP did not snipped off anything¹, you confused it with my post.
> 
> ¹Begin forwarded message
> < https://lists.ubuntu.com/archives/ubuntu-users/2016-August/287135.html >:
> 
> Date: Sun, 28 Aug 2016 17:42:06 +0200
> From: Chas IRONS
> To: ubuntu-users at lists.ubuntu.com
> Subject: Re: How to remove a damaged Wired Connection
> 
> [snip]
> 
> chas at Charles-PC:~$ lsb_release -rc; ifconfig -a
> Release:	16.04
> Codename:	xenial
> 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:35687 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:32279 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:22535304 (22.5 MB)  TX bytes:4018013 (4.0 MB)
> 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:11764 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11764 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1 
>           RX bytes:1320544 (1.3 MB)  TX bytes:1320544 (1.3 MB)
> chas at Charles-PC:~$
> 
> [snip]

PS: JFTR due to the device names, this seems to be not a default xenial
install. By default xinial unlikely uses kernel names.