Livebox Orange: Wireshark Internet Capture
molo2003
Posted messages
50
Status
Membre
-
molo2003 -
molo2003 -
Hello,
My PC running Windows 10 Home is connected to my box (RJ45).
The internet display is slow on my PC and even slower on my laptop over Wi-Fi.
So I'm blaming my Box.
A Wireshark capture shows me a lot of bad frames (on a black background) and many "Keep Alive" or "Dump Ack" frames. I am a retired IT professional but not used to reading internet frames in Wireshark.
Thank you in advance for enlightening me based on the capture image I am sending you below.
Thank you very much in advance
Configuration: Windows / Firefox 72.0
My PC running Windows 10 Home is connected to my box (RJ45).
The internet display is slow on my PC and even slower on my laptop over Wi-Fi.
So I'm blaming my Box.
A Wireshark capture shows me a lot of bad frames (on a black background) and many "Keep Alive" or "Dump Ack" frames. I am a retired IT professional but not used to reading internet frames in Wireshark.
Thank you in advance for enlightening me based on the capture image I am sending you below.
Thank you very much in advance
Configuration: Windows / Firefox 72.0
7 réponses
Hello,
First of all, you should start by doing a speed test https://www.speedtest.net/fr
--
bazfile
Moderator/Contributor security.
click here
First of all, you should start by doing a speed test https://www.speedtest.net/fr
--
bazfile
Moderator/Contributor security.
click here
Hi,
in your capture,
the black frames are not in error; they are emitted by your PC, at least the first ones during the data transfer at the beginning. If they are in error and the PC still emits them, it might have a schizophrenia problem maybe :-)
After that,
the keepalive at the end are on several different connections to different addresses. Nothing indicates a blockage; quite the opposite, as these TCP keepalives seem to be working, each being acknowledged.
in your capture,
the black frames are not in error; they are emitted by your PC, at least the first ones during the data transfer at the beginning. If they are in error and the PC still emits them, it might have a schizophrenia problem maybe :-)
After that,
the keepalive at the end are on several different connections to different addresses. Nothing indicates a blockage; quite the opposite, as these TCP keepalives seem to be working, each being acknowledged.
Thank you very much to Bazfile and Brupala for your responses and hello to all of you.
Response to Bazfile: Speedtest result: 5 Mbps downstream and 0.55 Mbps upstream.
I had much more 6 months ago... I am observing a degradation of internet service.
Response to Brupala: consulting the Wireshark documentation confirms that frames with a black background are "bad" (bad in transmission). The capture taken is too small to see the problem: many other frames are "Retransmissions" and many others are "Dump ACK"; all these frames clearly indicate transmission problems. A few months ago, when I monitored my network on Wireshark, I am not aware of having one in three frames with a black background, like today. The frames "Keep Alive" or "Retransmission" or "Dump ACK" should be exceptional on a functional TCP/IP network. In my professional life, I have done protocol analysis but other than TCP/IP. Moreover, from my laptop via Wi-Fi, sometimes the internet is not connected... the message on the background screen "Establishing a TLS connection with Google..." stays displayed for 30 seconds, then "Connection failed."
I continue to search. Thank you and have a good day.
Response to Bazfile: Speedtest result: 5 Mbps downstream and 0.55 Mbps upstream.
I had much more 6 months ago... I am observing a degradation of internet service.
Response to Brupala: consulting the Wireshark documentation confirms that frames with a black background are "bad" (bad in transmission). The capture taken is too small to see the problem: many other frames are "Retransmissions" and many others are "Dump ACK"; all these frames clearly indicate transmission problems. A few months ago, when I monitored my network on Wireshark, I am not aware of having one in three frames with a black background, like today. The frames "Keep Alive" or "Retransmission" or "Dump ACK" should be exceptional on a functional TCP/IP network. In my professional life, I have done protocol analysis but other than TCP/IP. Moreover, from my laptop via Wi-Fi, sometimes the internet is not connected... the message on the background screen "Establishing a TLS connection with Google..." stays displayed for 30 seconds, then "Connection failed."
I continue to search. Thank you and have a good day.
The speed is actually quite low; if you have TV through ADSL + 2 connected PCs, with such a speed it's normal for it to be slow.
Restart your Livebox, and if that doesn't solve the problem, contact Orange and tell them that your speed has noticeably decreased. There may be an issue with your line or at the NRA.
Restart your Livebox, and if that doesn't solve the problem, contact Orange and tell them that your speed has noticeably decreased. There may be an issue with your line or at the NRA.
Thank you again to Bazfile and Brupala;
To Bazfile: yes, I will call Orange to report this low speed and ask if there is a fault with my line. I am eager for fiber, but my neighborhood is not yet wired... I'm impatient on that front.
To Brupala: Doesn't Keep Alive mean that the acknowledgment of a frame takes a long time to arrive? So a "delay" in transmission???
Depending on the moment, a lot of "Retransmissions" of frames and "Dup ACK". In short, by default, the capture of frames on a black background is indicated by Wireshark's documentation as "Bad frame"... and overall 1 frame out of 3 is on a black background... which seems problematic to me.
On my laptop over Wifi... I can't do much online, but I have a Wifi repeater... I will set this device up as a "Wifi access point" to see if there is any improvement.
Thank you very much again.
A confession: I can't respond right away because a very close family member is in the hospital (medical emergency). Also, the internet is not my first concern.
Have a good day everyone.
To Bazfile: yes, I will call Orange to report this low speed and ask if there is a fault with my line. I am eager for fiber, but my neighborhood is not yet wired... I'm impatient on that front.
To Brupala: Doesn't Keep Alive mean that the acknowledgment of a frame takes a long time to arrive? So a "delay" in transmission???
Depending on the moment, a lot of "Retransmissions" of frames and "Dup ACK". In short, by default, the capture of frames on a black background is indicated by Wireshark's documentation as "Bad frame"... and overall 1 frame out of 3 is on a black background... which seems problematic to me.
On my laptop over Wifi... I can't do much online, but I have a Wifi repeater... I will set this device up as a "Wifi access point" to see if there is any improvement.
Thank you very much again.
A confession: I can't respond right away because a very close family member is in the hospital (medical emergency). Also, the internet is not my first concern.
Have a good day everyone.
Thank you;
I reiterate my question: how can I capture IP packets at the output of my LiveBox using Wireshark??? This way, I would have a real trace of my outgoing traffic, downstream of my box.
Perhaps a network specialist has a solution???
Moreover, I am willing to connect to fiber... but I am being told "the fiber is in your city but not in your neighborhood..."
Thank you and have a nice day.
I reiterate my question: how can I capture IP packets at the output of my LiveBox using Wireshark??? This way, I would have a real trace of my outgoing traffic, downstream of my box.
Perhaps a network specialist has a solution???
Moreover, I am willing to connect to fiber... but I am being told "the fiber is in your city but not in your neighborhood..."
Thank you and have a nice day.
Gafor
Let's see what Google's connection is to my Internet traffic problem.
You are being irresponsibly intrusive.
molo2003
Let's see what Google's connection is to my Internet traffic problem.
You are being irresponsibly intrusive.
molo2003