cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

1.6Gbit connection new smart hub (white, small box) sporadic issues? DNS MITM?

allamavortex
Established Contributor
Established Contributor

Hello all,

So I recently changed my service from 900mbit to 1.6Gbit and that involved a change of router and obviously the OR ONT on the wall.

Ever since having it installed there seems to be an issue with (most likely DNS issues). Whatever is loaded/playing/game continue to work, but I have spells where NO further DNS requests seem to make it through.

I totally forgot to nslookup during one of these issues, but I will the next time it happens (it's pretty frequent and annoying). I can ping 8.8.8.8 (google) whilst being unable to load any webpages on any device/browser. Thus removing the possibility of it being localised to a single machine/device as some were using the router, some were set to DNS over HTTPS and some were using Google's 8.8.8.8 etc. 

It is very much like the router is playing the MITM and intercepting the requests and then slowly, or failing to process these requests at all for a period of time which ranges up to about 45 seconds.

As I said, cached requests, or those already in process are fine, but even something as trivial as trying to watch a YT video is met with 45 seconds of nothing, totally unable to look up ANY address, but established connections and new connections not requiring DNS all work fine.

I'm not really one for conspiracies but I really feel like this new router is intercepting (MITM), attempting to do something with, and failing the DNS requests. This behaviour is only been present since getting the new Smart Hub (the tall, thing white one).

I did a quick google and it seems I'm not alone with this - is anyone else noticing this type of behavior?

Mixture of wired and wireless devices, same behaviour.

338 REPLIES 338

@bobpullen as you asked - I have tried every combination of turning on/off things like WIFI enhancer, parental controls, gaming mode, working mode (or whatever it's called), and everything else 'optional' I can find.  None of it makes any difference to this issue. 

@ryajohnst that’s superb. I reckon there’s definitely merit in running for an extended period of time. Doesn’t seem to be a consistent period of time between failures but maybe an extended run would show something? I’m reading that we’ve DNS failures whether forwarded via hub or direct to resolver (making me think custom DNS wouldn’t help), plus elevated pings to the hub when DNS is failing.

Pointing to the hub getting itself into a tangle periodically. What’s your current setup? Default or using something else for DHCP/DNS?

If the script’s in a state to share then I’d be curious to try it in my own environment.

ryajohnst
Established Contributor
Established Contributor

@bobpullen, I'm starting to think the root cause isn't in DNS at all but in establishing any new connections that occur during the period it's in a tangle. But it doesn't seem to affect ICMP at all (apart from increasing the response time from the router).

I'm currently using a completely standard setup and would prefer not having to set up local DHCP/DNS servers at home unless I have to. (Especially with the cost of this package, I'd like to think EE will have this fixed with some urgency). However, I'm not adverse to setting something up for testing purposes if it's going to be of any help.

I'm currently out for evening now, but I'll tidy the script up (so it outputs something that's shareable) tomorrow and share it. Along with leaving it running for 24 hours or so .

If EE are actively monitoring this thread, it would be great if they could post with their thoughts and let us know what to expect.

EE CS doesn't if that's who you're thinking of.

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Home Broadband & Home Phone or Option 2 for Mobile Phone & Mobile Broadband

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP
ryajohnst
Established Contributor
Established Contributor

Here's a copy of the script as promised:

https://pastecode.io/s/o5565wp7

I've started it running now and will leave it going for the rest of the weekend.

ryajohnst
Established Contributor
Established Contributor

Further update,

I've confirmed it is unrelated to DNS in particular.

The router refuses any new TCP or UDP connections during it's tangle but continues to allow ICMP. I established this by attempting to open an SSH connection to an IP address during such a period and it times out.

tnj
Skilled Contributor
Skilled Contributor

I am currently running an independent DHCP and DNS service having turned the DHCP off on my Smart Hub Pro and this has not improved the issues under discussion. On my mobile devices when  I change from WiFi to mobile 5G, all the issues go away. There is some fundamental problem with the busiest home bundle service.

I have the same issue, started happening week commencing the 4th of August.

Britboy4321
Investigator
Investigator

@Sync0r   As someone that has spend hours and hours and days and days trying to fix it, my advice is:

 

1)  If sorting it out is a kinda' fun, technical challenge you are interested in - keep going!

2)  If it's not - just trust me, give up now, plug in a different router, and wait for this all to blow over ..

Yeah, I'll just go back to my Asus GT-AX6000. Like you say, hopefully they release a firmware update to resolve it, many people on this 1.6gbit product must notice the problem and hopefully report it. I'll give them a call tomorrow.