Web Squad ISP

Status
Not open for further replies.
Sounds like possibly a firewall issue, i saw in one of your other posts you are running an MT router.
Do you have a rule at the top of your "Filter rules" to allow established and related connections?

Sorry, a bit of a noob with MT routers as it is on loan from Web Squad, do you mean under Routing/Filters? I went there and there are no rules at all, only has add new
 
Sorry, a bit of a noob with MT routers as it is on load from Web Squad, do you mean under Routing/Filters? I went there and there are no rules at all, only has add new

oh ok i see, wont be firewall then if that's empty, sounds like a pretty strange issue :(

Edit: IP > Firewall > Filter Rules.
 
oh ok i see, wont be firewall then if that's empty, sounds like a pretty strange issue :(

Edit: IP > Firewall > Filter Rules.

Seeing the following under IP > Firewall > Filter Rules, anything I should change?
 
Last edited:
Seeing the following under IP > Firewall > Filter Rules, anything I should change?

Looks fine to me, so not sure :(

Last thing i can think of is to try connect your PC directly to the CPE then try load the pages, will help you figure out if its a router config issue or not.
 
Looks fine to me, so not sure :(

Last thing i can think of is to try connect your PC directly to the CPE then try load the pages, will help you figure out if its a router config issue or not.

Thanks for the help, also running out of ideas.
 
Code:
This site can’t be reached
www.rt.com took too long to respond.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_TIMED_OUT

Cant open it in browser, but curl works

Code:
$ curl -IXGET https://www.rt.com
HTTP/2 200
server: nginx
date: Fri, 18 Sep 2020 20:43:11 GMT
content-type: text/html; charset=UTF-8
cache-control: no-cache,no-store,max-age=0
x-4vcta: H2171N
strict-transport-security: max-age=31536000; includeSubDomains; preload
 
on further inspection, browser is redirecting to https://rt.com while curl stays on https://www.rt.com

Code:
$ ping www.rt.com
PING wpc.en.rt.com (37.48.108.112): 56 data bytes
64 bytes from 37.48.108.112: icmp_seq=0 ttl=49 time=182.694 ms

$ ping rt.com
PING rt.com (207.244.80.166): 56 data bytes
64 bytes from 207.244.80.166: icmp_seq=0 ttl=46 time=256.815 ms
 
on further inspection, browser is redirecting to https://rt.com while curl stays on https://www.rt.com

Code:
$ ping www.rt.com
PING wpc.en.rt.com (37.48.108.112): 56 data bytes
64 bytes from 37.48.108.112: icmp_seq=0 ttl=49 time=182.694 ms

$ ping rt.com
PING rt.com (207.244.80.166): 56 data bytes
64 bytes from 207.244.80.166: icmp_seq=0 ttl=46 time=256.815 ms

Looked into this a little further and seems like the rt.com CDN is failing to load resources some resources, even if the page loads. Testing from the office now, no issues loading rt.com (besides some failed resources all from a CDN in the background)
 
So uhh, this is fun to wake up to on a 1gbps line?



@websquadza do I need to open a ticket?

As always, if it's that bad on the local loop, it's most probably Octotel. I'll update your open ticket. It doesn't help that they only get to a ticket after while and the issue has cleared. Seeing packet loss to you, as usual.
 
As always, if it's that bad on the local loop, it's most probably Octotel. I'll update your open ticket. It doesn't help that they only get to a ticket after while and the issue has cleared. Seeing packet loss to you, as usual.

Oddly I'm not seeing packet loss, it's almost as if the line has been set to a 20/2mbps profile:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   24 |   24 |    0 |    0 |    0 |    0 |
|                         160.119.238.105 -    0 |   24 |   24 |    0 |    0 |    3 |    0 |
|             core.cr-01.cp1.za.ws.net.za -    0 |   24 |   24 |    0 |    0 |    1 |    0 |
|           165-69-148-197.as37497.za.net -    0 |   24 |   24 |    0 |    0 |    2 |    0 |
|           162-68-148-197.as37497.za.net -    0 |   24 |   24 |  141 |  141 |  143 |  141 |
|            54-71-148-197.as37497.za.net -    0 |   24 |   24 |  141 |  160 |  202 |  199 |
|            41-66-148-197.as37497.za.net -    0 |   24 |   24 |  141 |  141 |  143 |  141 |
|ge-0-1-0-68.peering1.the.lon1.coreix.net -    0 |   24 |   24 |  141 |  141 |  143 |  141 |
|        xe-5-1.edge4.enf.lon5.coreix.net -    0 |   24 |   24 |  142 |  144 |  164 |  142 |
|        85.13.221.178.reverse.coreix.net -    0 |   24 |   24 |  141 |  142 |  144 |  141 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
That's interesting, so it's not just me, hmmm.
on further inspection, browser is redirecting to https://rt.com while curl stays on https://www.rt.com

Code:
$ ping www.rt.com
PING wpc.en.rt.com (37.48.108.112): 56 data bytes
64 bytes from 37.48.108.112: icmp_seq=0 ttl=49 time=182.694 ms

$ ping rt.com
PING rt.com (207.244.80.166): 56 data bytes
64 bytes from 207.244.80.166: icmp_seq=0 ttl=46 time=256.815 ms

You're both currently using IPv6 :unsure:? I see rt.com resolves in v6 too - wonder if the issue isn't related. Trying to reproduce and see.
 
You're both currently using IPv6 :unsure:? I see rt.com resolves in v6 too - wonder if the issue isn't related. Trying to reproduce and see.

I also have a feeling this is IPv6 related because I couldn't run an IPv6 MTU test yesterday at all
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X