- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have different routes for wired and wireless traffic from the same router. It's not intermittent, it's permanent.
Traceroute via WiFi:
Tracing route to google.com [72.14.204.104]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 5 ms 5 ms L100.PHLAPA-VFTTP-52.verizon-gni.net [96.227.231.1]
3 7 ms 6 ms 6 ms 9-3-552.PHLAPA-LCR-05.verizon-gni.net [130.81.97.50]
4 15 ms 25 ms 21 ms so-5-2-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.28.158]
5 15 ms 14 ms 13 ms so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.17.3]
6 14 ms * 13 ms 0.xe-8-1-0.BR2.IAD8.ALTER.NET [152.63.37.149]
7 13 ms 14 ms 14 ms xe-5-1-0.edge1.washinton4.level3.net [4.68.62.97]
8 14 ms 14 ms 15 ms ae-1-69.edge1.Washington1.Level3.net [4.68.17.16]
9 16 ms 15 ms 14 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.231.6]
10 16 ms 15 ms 15 ms 209.85.240.136
11 17 ms 16 ms 22 ms 66.249.94.46
12 17 ms 18 ms 17 ms iad04s01-in-f104.1e100.net [72.14.204.104]
Traceroute via Witred Ethernet:
Tracing route to google.com [64.233.169.105]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.PHLAPA-VFTTP-52.verizon-gni.net [96.227.231.1]
3 7 ms 6 ms 6 ms 9-3-652.PHLAPA-LCR-06.verizon-gni.net [130.81.104.128]
4 7 ms 6 ms 6 ms so-5-2-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.28.156]
5 12 ms 13 ms 12 ms so-13-2-0-0.RES-BB-RTR2.verizon-gni.net [130.81.19.118]
6 12 ms 12 ms 13 ms 0.xe-11-0-0.BR2.IAD8.ALTER.NET [152.63.34.13]
7 13 ms 13 ms 13 ms te-11-0-0.edge1.Washington4.level3.net [4.68.111.253]
8 14 ms 13 ms 14 ms ae-3-89.edge1.Washington1.Level3.net [4.68.17.144]
9 15 ms 15 ms 14 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.228.38]
10 14 ms 15 ms 15 ms 209.85.241.50
11 15 ms 16 ms 15 ms 72.14.236.200
12 18 ms 17 ms 18 ms 72.14.232.21
13 15 ms 15 ms 15 ms yo-in-f105.1e100.net [64.233.169.105]
Trace complete.
The reason I bring it up is because this router,9-3-552.PHLAPA-LCR-05.verizon-gni.net [130.81.97.50], stinks and has horrible latency/routing issues. It's the one my wireless traffic goes to. If I connect with the wire, boom, I'm golden. No latency, fast FiOS.
Can we get some confirmations out there? Why does Verizon have to overcomplicate these things?
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are going to two different IP addresses for Google:
Wireless: 72.14.204.104
Wired: 64.233.169.105
My guess is that you have a different DNS setting being used by the two different adapters. If you have a specific DNS set in one for example, and not in the other and let it default to whatever is in the router, you can get different results (I think). I suggest you take a look at the DNS definitions for both the wired and wireless adapters and see if there is a difference.
Another possibility I suppose could be that you have multipe Bookmarks saved and you are using different ones for the two connections (how, why, would it make a difference, I don't know).
Anyway, I really think it is somewhere in your setup, router and PC adapters, that is causing what you are seeing.
__________________________________
Justin
Verizon FiOS TV, Internet, and phone
QIP6416-P1, IMG 1.7C, Build 09.83
Keller, TX 76248
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There may be more to this... I'd just noticed how vastly different my google.com DNS results were to trace the route. Could it be that the wireless equipment is getting diffferent DNS information than wired instead of different routes?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
it's not the route that is your problem, you can see the latency there between the two are virtually identical.
6ms and 7 ms will see little to no discernable difference in how fast you get to a website.
My guess, your problem is probably just related to your wifi in general, change the channel of it, and you should be golden.
just to let you know, verizon doesn't do any static routing, meaning they don't tell their routers to always hit this hop and then that hop. all verizon cares about is getting from your router, to that first hop and then after that its noraml net traffic meaning that it takes the fastest path/shortest path to its destination.
but again your latency is identical on the 05 vs the 06.
try the wifi channel thing, you might get better results, but it may be just the wifi in general.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@TheTechMan wrote:There may be more to this... I'd just noticed how vastly different my google.com DNS results were to trace the route. Could it be that the wireless equipment is getting diffferent DNS information than wired instead of different routes?
the internet side/wan side of the vz router gets one set of dns info, so it distributes that out to the pc's unless you change that.
try changing it to open dns's
or googles dns's
or genuity's dns's
4.2.2.1
4.2.2.2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are going to two different IP addresses for Google:
Wireless: 72.14.204.104
Wired: 64.233.169.105
My guess is that you have a different DNS setting being used by the two different adapters. If you have a specific DNS set in one for example, and not in the other and let it default to whatever is in the router, you can get different results (I think). I suggest you take a look at the DNS definitions for both the wired and wireless adapters and see if there is a difference.
Another possibility I suppose could be that you have multipe Bookmarks saved and you are using different ones for the two connections (how, why, would it make a difference, I don't know).
Anyway, I really think it is somewhere in your setup, router and PC adapters, that is causing what you are seeing.
__________________________________
Justin
Verizon FiOS TV, Internet, and phone
QIP6416-P1, IMG 1.7C, Build 09.83
Keller, TX 76248
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I spoke too soon... DNS is autoconfigured via DHCP. I'll try to dig more details.