[solved, bad peering from Deutsche Telekom] after suricata 5.0.4_1 Update, suricata is no longer active
-
I was able to verify this 100%, that this is a peering problem of Deutsche Telekom, other ISP using the same Line, like 1&1, don't have this problem. The Download starts and then gets terrible slow, but there is no disconnect or reject , which make things even worse I think. But also there is a time frame where it does work, I think to the beginning of every day, there seems to be some kind of counting going on and then peering will become miserable again. So you could think that maybe pfBlocker was the reason, but in reality, it is the time of day.
Just to let you know.
-
@bob-dig said in [solved, bad peering from Deutsche Telekom] after suricata 5.0.4_1 Update, suricata is no longer active:
Just to let you know.
So, as I see it, it’s not just your problem and it’s not today’s thing.
f.e.: https://www.reddit.com/r/de_EDV/comments/agor82/grausames_peering_bei_der_telekom_update/
https://www.teltarif.de/forum/s80229/peering-ist-ein-erhebliches-groesseres-problem/1.htmlI think you need to choose a good VPN provider, Nord or Express VPN I have a lot of experience with them and .... - a little privacy it won't hurt anyone.
if you're worried about the speed, I'll tell you....
for example, ExpVPN - in PT
ISP 1000/500 FTTH
pfSense, Supermicro EPYC 3151 with LOM 4 pcs. Intel I350
the established VPN speed: D 670 - 720 / U 370-400 it is enough for everything.PS:
bufferbloat A++ -
To make things worse, or better : a "peering" issue can be cut in half, or doubles : Wha(s been seen before : our ISP all trying to propose their 'IPv6' - none of them actually read the reaRFC : they made something up that looks like an IPv6 RFC.
So, if you have IPv6 : stop it, reboot everything, check that's it is gone, and try again.Guess what happens when an ISP uses IPv6 - and implements it badly (many do so) : you think you can't access resources any more because their IPv6 peering is plain bad.
Our their iPV6 implementation is plain bad.
Or both.Start to check with what one might "presume working Ok" : IPv4 only.
If an ISP has bad peering - or blocks networks like "amazonaws.com" then I really would like to know : that info wasn't knows before ? You really want to use an ISP that blocks hostnames like that ? I understand, one can find tonnes of pure BS on "amazonaws.com" - it's just up to us not to go there .... If your ISP start to "pfBlockerNG' over your head, I would advise to leave them.
And before choosing another ISP : But document yourself about a new choice first. Remember : "money" is not an issue - but "not much' won't bring you much. .
And never read their own advertisement.Btw : a bad IPv6 implementation or peering can be redone on your side : join he.net.
Or VPN out.
By default : leave your ISP. -
Discussion continues here.
