=?ISO-8859-1?Q?Internet is dying - d?= iagnostics

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
51 messages Options
123
Reply | Threaded
Open this post in threaded view
|

=?ISO-8859-1?Q?Internet is dying - d?= iagnostics

Volker Wysk
Hi

Now the connection is down again. I'm writing this with my laptop and
webmail... Here are the diagnostics:

1. ifconfig

desktop ~ $ ifconfig
enp2s0    Link encap:Ethernet  Hardware Adresse 60:a4:4c:4e:17:47
          inet Adresse:192.168.178.20  Bcast:192.168.178.255
Maske:255.255.255.0
          inet6-Adresse: fe80::967a:55d6:22b8:8659/64
Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:18590 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:21091 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:5836977 (5.8 MB)  TX-Bytes:3725082 (3.7 MB)

lo        Link encap:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX-Pakete:26912 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:26912 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1
          RX-Bytes:5745757 (5.7 MB)  TX-Bytes:5745757 (5.7 MB)

virbr0    Link encap:Ethernet  Hardware Adresse 00:00:00:00:00:00
          inet Adresse:192.168.122.1  Bcast:192.168.122.255
Maske:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:0 (0.0 B)  TX-Bytes:0 (0.0 B)



2. dhcp-discover

desktop ~/Internetproblem $ sudo ./dhcp-discover -i enp2s0 -e
60:a4:4c:4e:17:47
Ethernet hw addr to do discovery on : 60:a4:4c:4e:17:47

 - beginning of dump -
DHCP operation          : request
Hardware type           : ethernet
Hardware address length : 6 bytes
Hop count               : 0
Transaction ID          : 0xdeadbeef
Number of seconds       : 0
Flags                   : 0x8000
Client IP               : 0.0.0.0
Your IP                 : 0.0.0.0
Server IP               : 0.0.0.0
Gateway IP              : 0.0.0.0
Client hw addr          : 60:a4:4c:4e:17:47
Server hostname         :
Boot filename           :
Options
  Magic header          : 0x63825363 (OK)
  Message type          : discover
  Option 0x37           : len 7
 - end of dump -
desktop ~/Internetproblem $


3. ping IP-Address:

desktop ~/Internetproblem $ ping 193.99.144.80
PING 193.99.144.80 (193.99.144.80) 56(84) bytes of data.
From 192.168.178.20 icmp_seq=1 Destination Host Unreachable
From 192.168.178.20 icmp_seq=2 Destination Host Unreachable
From 192.168.178.20 icmp_seq=3 Destination Host Unreachable
^C
--- 193.99.144.80 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time
3016ms
pipe 3

desktop ~/Internetproblem $ ping heise.de
(no output)


Volker


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Colin Law
Are you on two local networks? You have two addresses, 192.168.178.20
and 192.168.122.1?
When it is working run
traceroute <some ip address>
You might have to install something to get traceroute, I think it will
tell you what.
Then do it again when it is broken. With luck that will tell you where
the link is broken

I presume others connected to the same router are not having problems.

Colin

On 21 October 2017 at 16:26,  <[hidden email]> wrote:

> Hi
>
> Now the connection is down again. I'm writing this with my laptop and
> webmail... Here are the diagnostics:
>
> 1. ifconfig
>
> desktop ~ $ ifconfig
> enp2s0    Link encap:Ethernet  Hardware Adresse 60:a4:4c:4e:17:47
>           inet Adresse:192.168.178.20  Bcast:192.168.178.255
> Maske:255.255.255.0
>           inet6-Adresse: fe80::967a:55d6:22b8:8659/64
> Gültigkeitsbereich:Verbindung
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
>           RX-Pakete:18590 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
>           TX-Pakete:21091 Fehler:0 Verloren:0 Überläufe:0 Träger:0
>           Kollisionen:0 Sendewarteschlangenlänge:1000
>           RX-Bytes:5836977 (5.8 MB)  TX-Bytes:3725082 (3.7 MB)
>
> lo        Link encap:Lokale Schleife
>           inet Adresse:127.0.0.1  Maske:255.0.0.0
>           inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
>           UP LOOPBACK RUNNING  MTU:65536  Metrik:1
>           RX-Pakete:26912 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
>           TX-Pakete:26912 Fehler:0 Verloren:0 Überläufe:0 Träger:0
>           Kollisionen:0 Sendewarteschlangenlänge:1
>           RX-Bytes:5745757 (5.7 MB)  TX-Bytes:5745757 (5.7 MB)
>
> virbr0    Link encap:Ethernet  Hardware Adresse 00:00:00:00:00:00
>           inet Adresse:192.168.122.1  Bcast:192.168.122.255
> Maske:255.255.255.0
>           UP BROADCAST MULTICAST  MTU:1500  Metrik:1
>           RX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
>           TX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Träger:0
>           Kollisionen:0 Sendewarteschlangenlänge:1000
>           RX-Bytes:0 (0.0 B)  TX-Bytes:0 (0.0 B)
>
>
>
> 2. dhcp-discover
>
> desktop ~/Internetproblem $ sudo ./dhcp-discover -i enp2s0 -e
> 60:a4:4c:4e:17:47
> Ethernet hw addr to do discovery on : 60:a4:4c:4e:17:47
>
>  - beginning of dump -
> DHCP operation          : request
> Hardware type           : ethernet
> Hardware address length : 6 bytes
> Hop count               : 0
> Transaction ID          : 0xdeadbeef
> Number of seconds       : 0
> Flags                   : 0x8000
> Client IP               : 0.0.0.0
> Your IP                 : 0.0.0.0
> Server IP               : 0.0.0.0
> Gateway IP              : 0.0.0.0
> Client hw addr          : 60:a4:4c:4e:17:47
> Server hostname         :
> Boot filename           :
> Options
>   Magic header          : 0x63825363 (OK)
>   Message type          : discover
>   Option 0x37           : len 7
>  - end of dump -
> desktop ~/Internetproblem $
>
>
> 3. ping IP-Address:
>
> desktop ~/Internetproblem $ ping 193.99.144.80
> PING 193.99.144.80 (193.99.144.80) 56(84) bytes of data.
> From 192.168.178.20 icmp_seq=1 Destination Host Unreachable
> From 192.168.178.20 icmp_seq=2 Destination Host Unreachable
> From 192.168.178.20 icmp_seq=3 Destination Host Unreachable
> ^C
> --- 193.99.144.80 ping statistics ---
> 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time
> 3016ms
> pipe 3
>
> desktop ~/Internetproblem $ ping heise.de
> (no output)
>
>
> Volker
>
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Thufir Hawat
In reply to this post by Volker Wysk
On Sat, 21 Oct 2017 17:26:07 +0200, post wrote:


> Now the connection is down again.



did you change the DNS?


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Colin Law
On 21 October 2017 at 16:44, thufir <[hidden email]> wrote:
> On Sat, 21 Oct 2017 17:26:07 +0200, post wrote:
>
>> Now the connection is down again.
>
> did you change the DNS?

It is not the DNS as it fails with an ip address. If it were a DNS
issue it would work with an address but fail with a name.

Colin

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Xen
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Xen
In reply to this post by Volker Wysk
[hidden email] schreef op 21-10-2017 15:26:

> desktop ~/Internetproblem $ sudo ./dhcp-discover -i enp2s0 -e
> 60:a4:4c:4e:17:47
> Ethernet hw addr to do discovery on : 60:a4:4c:4e:17:47
>
>  - beginning of dump -
> DHCP operation          : request
> Hardware type           : ethernet
> Hardware address length : 6 bytes
> Hop count               : 0
> Transaction ID          : 0xdeadbeef
> Number of seconds       : 0
> Flags                   : 0x8000
> Client IP               : 0.0.0.0
> Your IP                 : 0.0.0.0
> Server IP               : 0.0.0.0
> Gateway IP              : 0.0.0.0
> Client hw addr          : 60:a4:4c:4e:17:47
> Server hostname         :
> Boot filename           :
> Options
>   Magic header          : 0x63825363 (OK)
>   Message type          : discover
>   Option 0x37           : len 7
>  - end of dump -

Normally this dump would contain responses from DHCP servers.

The only thing dhcp-discover requires is for the link to be up:

sudo ip link set enp2s0 up

But if you set it "down" it disappears from ifconfig, so that is not it.

So basically your entire hardware device stops working.

I don't know at this point how to test ethernet using ethtool.

This runs a self-test:

sudo ethtool -t enp2s0

sudo ethtool -S enp2s0 will also give error statistics.


Unless you:

- have another computer on the network with the same IP

It seems to me that you have a hardware failure.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Xen
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Xen
In reply to this post by Colin Law
Colin Law schreef op 21-10-2017 15:44:
> Are you on two local networks? You have two addresses, 192.168.178.20
> and 192.168.122.1?

Karl is right.

The other IP is on a virtual bridge, not a real network interface.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
Am Samstag, 21. Oktober 2017, 21:08:16 CEST schrieb Xen:
> Colin Law schreef op 21-10-2017 15:44:
> > Are you on two local networks? You have two addresses, 192.168.178.20
> > and 192.168.122.1?
>
> Karl is right.
>
> The other IP is on a virtual bridge, not a real network interface.

It seems to belong to my virtual machine manager.

Volker


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

compdoc
On 10/21/2017 07:50 PM, Volker Wysk wrote:

> It seems to belong to my virtual machine manager.
>
> Volker

Unless you changed something manually, theres a good chance you should
not worry about 192.168.122.1.

What sort of router is it? If its consumer brand like d-link and many
others, they tend to die after a few years of 24/ use.

I've owned many over the years, before switching to a distro based
router running on PC hardware. No failures in years.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
In reply to this post by Xen
Am Samstag, 21. Oktober 2017, 21:05:45 CEST schrieb Xen:

> [hidden email] schreef op 21-10-2017 15:26:
> > desktop ~/Internetproblem $ sudo ./dhcp-discover -i enp2s0 -e
> > 60:a4:4c:4e:17:47
> > Ethernet hw addr to do discovery on : 60:a4:4c:4e:17:47
> >
> >  - beginning of dump -
> >
> > DHCP operation          : request
> > Hardware type           : ethernet
> > Hardware address length : 6 bytes
> > Hop count               : 0
> > Transaction ID          : 0xdeadbeef
> > Number of seconds       : 0
> > Flags                   : 0x8000
> > Client IP               : 0.0.0.0
> > Your IP                 : 0.0.0.0
> > Server IP               : 0.0.0.0
> > Gateway IP              : 0.0.0.0
> > Client hw addr          : 60:a4:4c:4e:17:47
> > Server hostname         :
> > Boot filename           :
> > Options
> >
> >   Magic header          : 0x63825363 (OK)
> >   Message type          : discover
> >   Option 0x37           : len 7
> >  
> >  - end of dump -
>
> Normally this dump would contain responses from DHCP servers.

It's the same output at the moment, now that the connection is up.


> The only thing dhcp-discover requires is for the link to be up:
>
> sudo ip link set enp2s0 up
>
> But if you set it "down" it disappears from ifconfig, so that is not it.
>
> So basically your entire hardware device stops working.

So the network card is broken?

 
> I don't know at this point how to test ethernet using ethtool.
>
> This runs a self-test:
>
> sudo ethtool -t enp2s0

This doesn't work, although it is in the man page. Does that mean that my
network card (device) doesn't support it?

desktop ~/Internetproblem $ sudo ethtool -t enp2s0 online
Cannot test: Operation not supported
desktop ~/Internetproblem $ sudo ethtool -t enp2s0 offline
Cannot test: Operation not supported
desktop ~/Internetproblem $ sudo ethtool -t enp2s0 external_lb
Cannot test: Operation not supported
desktop ~/Internetproblem $ sudo ethtool -t enp2s0
Cannot test: Operation not supported


> sudo ethtool -S enp2s0 will also give error statistics.

desktop ~/Internetproblem $ sudo ethtool -S enp2s0
NIC statistics:
     tx_packets: 43833
     rx_packets: 45593
     tx_errors: 0
     rx_errors: 0
     rx_missed: 0
     align_errors: 0
     tx_single_collisions: 0
     tx_multi_collisions: 0
     unicast: 45287
     broadcast: 92
     multicast: 216
     tx_aborted: 0
     tx_underrun: 0


> Unless you:
>
> - have another computer on the network with the same IP

I don't, I've checked.

 
> It seems to me that you have a hardware failure.

So, build a new network card? The current one should be on the main board, not
changable.


Volker


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
In reply to this post by compdoc
Am Samstag, 21. Oktober 2017, 19:57:45 CEST schrieb compdoc:
> What sort of router is it? If its consumer brand like d-link and many
> others, they tend to die after a few years of 24/ use.

Really?? Now I'm shocked.

It's a Fritz!Box 7490 or Fritz!Box 6490 Cable.

> I've owned many over the years, before switching to a distro based
> router running on PC hardware. No failures in years.


Bye


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Colin Law
Have you posted the result of traceroute to an external IP address when it is not working? Perhaps I missed it. That may show you where it stops

Colin

On 22 Oct 2017 3:33 a.m., "Volker Wysk" <[hidden email]> wrote:
Am Samstag, 21. Oktober 2017, 19:57:45 CEST schrieb compdoc:
> What sort of router is it? If its consumer brand like d-link and many
> others, they tend to die after a few years of 24/ use.

Really?? Now I'm shocked.

It's a Fritz!Box 7490 or Fritz!Box 6490 Cable.

> I've owned many over the years, before switching to a distro based
> router running on PC hardware. No failures in years.


Bye


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
Am Sonntag, 22. Oktober 2017, 07:35:31 CEST schrieb Colin Law:
> Have you posted the result of traceroute to an external IP address when it
> is not working? Perhaps I missed it. That may show you where it stops

Um, no, not jet. When you want it to break, it doesn't. It's crazy. I'm
waiting again, for half an hour now, for the connection to go down, but it
doesn't.

Still waiting...

Volker


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
In reply to this post by Colin Law
Am Sonntag, 22. Oktober 2017, 07:35:31 CEST schrieb Colin Law:
> Have you posted the result of traceroute to an external IP address when it
> is not working? Perhaps I missed it. That may show you where it stops

Here it is:

desktop ~ $ traceroute 193.99.144.80
traceroute to 193.99.144.80 (193.99.144.80), 30 hops max, 60 byte packets
 1  192.168.178.20 (192.168.178.20)  2747.404 ms !H  2747.386 ms !H  2747.376
ms !H

The IP belongs to heise.de. So it should be all right. The traceroute command
takes some 10 seconds. No more output.

Does this hint at a broken router?

Bye
Volker


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
In reply to this post by Volker Wysk
Hello

It may be the router. I've reset it (power off and on), and the connection
came back. It's not clear, though. I'll try again.

Volker


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Colin Law
In reply to this post by Volker Wysk
On 22 October 2017 at 09:29, Volker Wysk <[hidden email]> wrote:

>
> desktop ~ $ traceroute 193.99.144.80
> traceroute to 193.99.144.80 (193.99.144.80), 30 hops max, 60 byte packets
>  1  192.168.178.20 (192.168.178.20)  2747.404 ms !H  2747.386 ms !H  2747.376
> ms !H
>
> The IP belongs to heise.de. So it should be all right. The traceroute command
> takes some 10 seconds. No more output.
>
> Does this hint at a broken router?

Well 192.168.178.20 is your own address, so it doesn't get any further
than that. So that suggests either your network card, the
cable/connectors or the router.  Are there other devices plugged into
the router? if so then switch the connections for yourself and the
other device (keep a note of where you started or you will get
confused, or at least I would) and if you have a spare cable then
switch cables (or swap the cable with another device). If it is still
your PC that fails then that suggests the card in the PC. If you can
open the PC up and disconnect the card from the mother board and
reconnect it, and do the same with the other end of the cable if you
can, then if it is a poor connection that might well fix it.

Colin

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
Am Sonntag, 22. Oktober 2017, 09:47:28 CEST schrieb Colin Law:

> On 22 October 2017 at 09:29, Volker Wysk <[hidden email]> wrote:
> > desktop ~ $ traceroute 193.99.144.80
> > traceroute to 193.99.144.80 (193.99.144.80), 30 hops max, 60 byte packets
> >
> >  1  192.168.178.20 (192.168.178.20)  2747.404 ms !H  2747.386 ms !H
> >  2747.376>
> > ms !H
> >
> > The IP belongs to heise.de. So it should be all right. The traceroute
> > command takes some 10 seconds. No more output.
> >
> > Does this hint at a broken router?
>
> Well 192.168.178.20 is your own address, so it doesn't get any further
> than that. So that suggests either your network card, the
> cable/connectors or the router.  

I think, it's the router. The connection was broken, just now, and I turned
the router off/on. When the router's lights finished blinking, the connection
was back.


> Are there other devices plugged into
> the router?

My laptop and my smartphone, are "plugged in" over WLAN.

> if so then switch the connections for yourself and the
> other device

You mean, interchange the two network cables? (I've got only one, but I also
don't really understand.)

> (keep a note of where you started or you will get
> confused, or at least I would) and if you have a spare cable then
> switch cables (or swap the cable with another device). If it is still
> your PC that fails then that suggests the card in the PC. If you can
> open the PC up and disconnect the card from the mother board

Networks cards are integrated in the motherboard, nowadays, aren't they? Can't
be disconnected.

> and
> reconnect it, and do the same with the other end of the cable if you
> can, then if it is a poor connection that might well fix it.

Bye
V.W.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Colin Law
On 22 October 2017 at 10:05, Volker Wysk <[hidden email]> wrote:

> Am Sonntag, 22. Oktober 2017, 09:47:28 CEST schrieb Colin Law:
>> On 22 October 2017 at 09:29, Volker Wysk <[hidden email]> wrote:
>> > desktop ~ $ traceroute 193.99.144.80
>> > traceroute to 193.99.144.80 (193.99.144.80), 30 hops max, 60 byte packets
>> >
>> >  1  192.168.178.20 (192.168.178.20)  2747.404 ms !H  2747.386 ms !H
>> >  2747.376>
>> > ms !H
>> >
>> > The IP belongs to heise.de. So it should be all right. The traceroute
>> > command takes some 10 seconds. No more output.
>> >
>> > Does this hint at a broken router?
>>
>> Well 192.168.178.20 is your own address, so it doesn't get any further
>> than that. So that suggests either your network card, the
>> cable/connectors or the router.
>
> I think, it's the router. The connection was broken, just now, and I turned
> the router off/on. When the router's lights finished blinking, the connection
> was back.

Not necessarily the network card might be confused and recovers by
being, effectively, disconnected and reconnected. You might find the
same thing if you unplug the cable wait for 10 seconds and plug it
back in.

>
>
>> Are there other devices plugged into
>> the router?
>
> My laptop and my smartphone, are "plugged in" over WLAN.
>
>> if so then switch the connections for yourself and the
>> other device

I meant unplug the two cables and plug them back in but the other way
round, so if it is just one connection in the router then the PC
should now work and the other device might be intermittent.

>
> You mean, interchange the two network cables? (I've got only one, but I also
> don't really understand.)

How can you only have one cable if the PC and the smartphone are both
plugged in? Perhaps you mean that the phone is on wifi and only the PC
is plugged in. In which case try the cable in another socket on the
router and if that doesn't help then get hold of another cable, with
luck it is that.  If not then it may be difficult to determine whether
it is the router or the PC if you haven't got something else to plug
in to test it.

>
> Networks cards are integrated in the motherboard, nowadays, aren't they? Can't
> be disconnected.

Yes, very likely.

Colin

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
Am Sonntag, 22. Oktober 2017, 10:37:53 CEST schrieb Colin Law:
> On 22 October 2017 at 10:05, Volker Wysk <[hidden email]> wrote:
> > Am Sonntag, 22. Oktober 2017, 09:47:28 CEST schrieb Colin Law:

> >> Well 192.168.178.20 is your own address, so it doesn't get any further
> >> than that. So that suggests either your network card, the
> >> cable/connectors or the router.
> >
> > I think, it's the router. The connection was broken, just now, and I
> > turned
> > the router off/on. When the router's lights finished blinking, the
> > connection was back.
>
> Not necessarily the network card might be confused and recovers by
> being, effectively, disconnected and reconnected. You might find the
> same thing if you unplug the cable wait for 10 seconds and plug it
> back in.
>
> >> Are there other devices plugged into
> >> the router?
> >
> > My laptop and my smartphone, are "plugged in" over WLAN.
> >
> >> if so then switch the connections for yourself and the
> >> other device
>
> I meant unplug the two cables and plug them back in but the other way
> round, so if it is just one connection in the router then the PC
> should now work and the other device might be intermittent.
>
> > You mean, interchange the two network cables? (I've got only one, but I
> > also don't really understand.)
>
> How can you only have one cable if the PC and the smartphone are both
> plugged in?

Therefore, I've enclosed the phrase "plugged in" in quotes, above.

> Perhaps you mean that the phone is on wifi and only the PC
> is plugged in.

Yes.

> In which case try the cable in another socket on the
> router and if that doesn't help then get hold of another cable, with
> luck it is that.  If not then it may be difficult to determine whether
> it is the router or the PC if you haven't got something else to plug
> in to test it.

Okay, I'll try it. Now I have to wait for the error to occur again.

I could buy another cable, and try plugging my laptop in...

Bye
V.W.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Xen
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Xen
In reply to this post by Volker Wysk
Volker Wysk schreef op 22-10-2017 2:25:

>> Normally this dump would contain responses from DHCP servers.
>
> It's the same output at the moment, now that the connection is up.

Really? This is the sort of output I get:

  - beginning of dump -
DHCP operation          : reply
Hardware type           : ethernet
Hardware address length : 6 bytes
Hop count               : 0
Transaction ID          : 0xdeadbeef
Number of seconds       : 0
Flags                   : 0x8000
Client IP               : 0.0.0.0
Your IP                 : 192.168.0.5
Server IP               : 192.168.0.1
Gateway IP              : 0.0.0.0
Client hw addr          : 00:1f:c6:25:10:e8
Server hostname         :
Boot filename           :
Options
   Magic header          : 0x63825363 (OK)
   Message type          : offer
   SERVIDENT             : 192.168.0.1
   LEASETIME             : 40000 seconds
   RENEWTIME             : 20000 seconds
   REBINDTIME            : 36000 seconds
   SUBNETMASK            : 255.255.255.0
   BROADCASTADDR         : 192.168.0.255
   DNS                   : 192.168.0.1
   DOMAINNAME            : local
   ROUTER                : 192.168.0.1
  - end of dump -


> So the network card is broken?

In general like others say it is more likely that it is the switch.

> This doesn't work, although it is in the man page. Does that mean that
> my
> network card (device) doesn't support it?

I guess.

>> It seems to me that you have a hardware failure.
>
> So, build a new network card? The current one should be on the main
> board, not
> changable.

You can always try with an different OS or different router cq. switch.

If you can take your router out of the loop, then you can test directly
with something else.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Internet is dying - diagnostics

Volker Wysk
In reply to this post by Volker Wysk
Hi

Someone asked for the output of "traceroute".  Here it is:

desktop ~ $ traceroute 193.99.144.80
traceroute to 193.99.144.80 (193.99.144.80), 30 hops max, 60 byte packets

(No more output)

Volker


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
123