User comments on ISPs
  >> Zen Internet


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | (show all)   Print Thread
Standard User jelv
(knowledge is power) Wed 03-May-23 09:06:05
Print Post

Dripping blood


[link to this post]
 
Yesterdays BQM to my router doesn't look good.

My Broadband Ping

What's puzzling me is that I also have a BQM running to my NAS box using IPv6 and that looked OK:

My Broadband Ping

Overnight, between 2 and 3 AM, it returned to normal with nothing happening at this end.

Looking back through previous days there was a very small amount at odd times on Monday, then all OK back to Mon 24th when there was a similar amount to yesterday, again stopping in the early hours of the following morning. Looking further back there are more odd days with varying amounts of blood.

jelv

FTTC & Line rental: ZeN from March 2021

Previously: AAISP (November 2016 to March 2021) & Pulse8 line rental
Plusnet November 2001 to October 2016
Standard User bloodycat
(member) Wed 03-May-23 09:46:27
Print Post

Re: Dripping blood


[re: jelv] [link to this post]
 
Since the latest Firmware update on the FRitzbox a few months ago I have noticed this qyite a lot - IPv6 to my server is fine but IPv4 to the router often has latency spikes and up to 20% packet loss showing.. I don't believe it is a genuine problem (though there could be difference between the paths of the 2 protocols I suspect it is more down to the fritzbox not repsonding than any real connectivity issues.

Interestingly for the last week it was looking all good again - until the connection dropped on Monday night and has since been showing llots of packet loss and latency spikes again on IPv4.
Standard User AndrewNi
(member) Wed 03-May-23 11:38:22
Print Post

Re: Dripping blood


[re: jelv] [link to this post]
 
I've always assumed it's something to do with the Fritz!Box de-prioritising pings. I get a similar effect on my BQMs, like yesterday:

My Broadband Ping

My connection's fine. Several years ago I had major packet loss with lots of "blood" on the BQM, and the impact on the connection speed was very noticeable.


Register (or login) on our website and you will not see this ad.

Standard User jimbof
(member) Tue 09-May-23 14:32:11
Print Post

Re: Dripping blood


[re: jelv] [link to this post]
 
I think it's totally down to chance whether you get away with doing BQM monitoring with the Fritzbox. If you download and decrypt the config you can see that pings have a 1 per second rate limit. If you have some amount of jitter then sometimes you'll have 1 ping per second, sometimes 0, and sometimes 2...
Standard User prlzx
(experienced) Wed 10-May-23 09:23:24
Print Post

Re: Dripping blood


[re: jimbof] [link to this post]
 
yes as jimbof says its a given with the Fritzbox config that for monitoring pings unless they are less frequent, we need to ping an IPv6 address on the LAN behind the router - something that is always-on and preferably wired.

The OP's NAS is already performing that role so should be regarded as the real stats.

For others trying to set this up, the Fritzbox Permit Access section allows for both v4 destination NAT (port forwarding) and v6 firewall-allow rules, so there is a dedicated tick box for allowing PING6 (to an IPv6 interface ID).
This means you can allow PING with or without other TCP/UDP ports and without needing to expose the device completely to the Internet.



prlzx on Zen: FTTC (VDSL) at ~40Mbps / 10Mbps
with IP4/6 (no v6? - not true Internet)
Standard User kam67
(member) Fri 12-May-23 22:42:16
Print Post

Re: Dripping blood


[re: bloodycat] [link to this post]
 
Exactly the same has been occurring for me and I too know this is not a real world issue (e.g. when pinging google from my Fritzbox no packets dropped whatsoever) as it does not affect my connection in anyway except when trying to ping the router (which leads to what appears to be considerable packet loss and latency).

Edited by kam67 (Fri 12-May-23 22:43:01)

Standard User jelv
(knowledge is power) Sat 13-May-23 09:32:29
Print Post

Re: Dripping blood


[re: kam67] [link to this post]
 
What puzzles me is that it can go several days without any dripping blood at all (there's been none since around 5am on Wednesday) when nothing internally has changed. There is something external that is causing this.

jelv

FTTC & Line rental: ZeN from March 2021

Previously: AAISP (November 2016 to March 2021) & Pulse8 line rental
Plusnet November 2001 to October 2016
Standard User gnt
(newbie) Wed 31-May-23 08:16:54
Print Post

Re: Dripping blood


[re: jelv] [link to this post]
 
Been with zen 3 years and only noticed this packet loss in the last few months, it happens random day and night.
Still happening now, and im a light user on 80/20 fttp.

check my graph https://ibb.co/9Nnt4Z3

Why are zen not doing anything about this ?
Standard User gnt
(newbie) Wed 31-May-23 08:37:02
Print Post

Re: Dripping blood


[re: jelv] [link to this post]
 
hmm i just made a post and its no longer here how odd, and had no message to say who removed it and why...

I was replying to these posts to say that for the last few months i have had packet loss day and night with my zen 80/20 fttp connection, even had it over night into this morning.
i did post a link to my graph showing all the packet loss but maybe i broke rules in doing so, so i wont add it again just incase.

What id like to know is ... Do zen know about this and are they working on a fix!

Edited by gnt (Wed 31-May-23 08:38:58)

Standard User bloodycat
(member) Wed 31-May-23 10:38:46
Print Post

Re: Dripping blood


[re: gnt] [link to this post]
 
I suspect your post just didn't get properly submitted rather than being deleted. I have experienced that a few times on here - never quite sure if it is the site or an error on my part not pressing the right button.

As fo the apparrent packet loss - the general concensus is that most of the time it is not actually a genuine issue and is probably down to how the fritzbox handles the requests.
The fact it seems to come and go is a slight mystery - could be down to subtle changes in the network or maybe an interaction with some routine network monitoring/checking that Zen perform.
Pages in this thread: 1 | 2 | (show all)   Print Thread

Jump to