Eir issue : TraceRT on phone

LeinsterDub

Hi Guys would really appericate some help here . I've contact Eir so many time and there only suggestions are constantly to send me yet a other modem.

The issue that my phone on wireless is extremely slow the issue seems to be the my phone is following a different route than my PC on the same wireless network.

PC TraceRT
Tracing route to www.google.ie [159.134.171.234]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms 192.168.1.254
2 16 ms 7 ms 7 ms 95.45.52.1
3 5 ms 6 ms 6 ms lag-5.pe1.fng.bdt-fng.eircom.net [86.43.255.25]
4 * 7 ms 6 ms lag-30.core2.srl.core.eircom.net [86.43.9.252]
5 6 ms 7 ms 6 ms lag-100.coreb.srl.core.eircom.net [86.43.9.66]
6 5 ms 6 ms 6 ms 159.134.171.234

Trace complete.

TraceRT from phone in the images. Can someone even put a name of this so I know what to tell Eir is the issue?

LeinsterDub

Screens from phone

PAKNET

Google on your PC (www.google.ie) and google on your phone (m.google.ie) will be served by different web servers which may be in totally different datacentres, hence the different routes. Perhaps google is able to distinguish a ping from your phone versus a ping from a PC.

What is "slow" exactly?
If you go to the same site/app via 3G/4G is it any faster?
Make/model of phone?

LeinsterDub

PAKNET wrote: »

Google on your PC (www.google.ie) and google on your phone (m.google.ie) will be served by different web servers which may be in totally different datacentres, hence the different routes. Perhaps google is able to distinguish a ping from your phone versus a ping from a PC.

What is "slow" exactly?
If you go to the same site/app via 3G/4G is it any faster?
Make/model of phone?

Tracert on my phone surely goes to www not m. I'll try a tracert to a site without a m. if you think it will make a difference. If I load rte.ie on my phone it takes about 5-10 seconds to 'resolve' the route while on my pc it loads nearly instantly

ED E

A trace wont show the issue you're seeing. DNS.

Are you using any kinda of app to watch georestricted content?

LeinsterDub

ED E wrote: »

A trace wont show the issue you're seeing. DNS.

Are you using any kinda of app to watch georestricted content?

Why would DNS change the route? I don't think it's DNS as I've switched to using Googles DNS before and it made no odds

Nope I'm not using any apps

LeinsterDub

Any ideas?

ED E

LeinsterDub wrote: »

'resolve' the route

The route isnt resolved. The BRs already know where things should go in their tables. No computing required, its just matched.


So either its saying its "resolving" which means its resolving the host slowly, which is a DNS issue or its not.

And see how one device gets 159.134.171.234 and the other gets 209.85.202.94? Guess where that came from? DNS.

LeinsterDub

ED E wrote: »

The route isnt resolved. The BRs already know where things should go in their tables. No computing required, its just matched.


So either its saying its "resolving" which means its resolving the host slowly, which is a DNS issue or its not.

And see how one device gets 159.134.171.234 and the other gets 209.85.202.94? Guess where that came from? DNS.

Ok thanks and how would I resolve this issue? I've tried pointing the Dns at Google's and it didn't seem to make any odds

ED E

If that app is Pingtools like it looks like then go to Info and click on the network configuration card. Thatll give you the IPs of the DNS servers its using.

LeinsterDub

ED E wrote: »

If that app is Pingtools like it looks like then go to Info and click on the network configuration card. Thatll give you the IPs of the DNS servers its using.

But changing the DNS before didn't resolve the issue?