New Member
•
3 Messages
Issues Routing to GoDaddy Hosted Site Only At Home - Fails at ars.mgmt.phx3.gdg
Good Evening -
I have Xfinity / Comcast Internet (Business-class) at my house and ran into an issue this weekend. When working on one of my own websites - guidesforit.com - I couldn't access it all of a sudden. I tried the following to resolve:
- Different computers
- Flushing DNS
- Restarting gateway & routers
- Testing at different locations
Every other location / connection I tried worked. It seems to be resolving correctly, but the routing is not working right. I called GoDaddy (website host) and they looked at my trace routes and said it wasn't on their end, but on the host side.
Below is a trace router from my home to the site followed by a trace route from a different location / connection to the site which works:
Trace Route From Home (Does Not Work)
1 2 ms 13 ms <1 ms OpenWrt.lan [192.168.0.1]
2 5 ms 1 ms <1 ms 10.1.10.1
3 30 ms 31 ms 29 ms c-69-138-x-x.hsd1.tn.comcast.net [69.138.x.x] (Edited for security)
4 14 ms 20 ms 18 ms xe-11-2-0-32767-sur02.williamson.tn.nash.comcast.net [68.86.151.149]
5 58 ms 23 ms 25 ms xe-5-0-6-0-ar01.goodslettvll.tn.nash.comcast.net [162.151.9.85]
6 26 ms 43 ms 61 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189]
7 35 ms 39 ms 34 ms he-2-15-0-0-cr01.chicago.il.ibone.comcast.net [68.86.86.245]
8 39 ms 34 ms 38 ms he-1-5-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.88.38]
9 33 ms 31 ms 48 ms he-0-10-0-0-pe04.350ecermak.il.ibone.comcast.net [68.86.83.50]
10 50 ms 40 ms 46 ms as26496-1-c.350ecermak.il.ibone.comcast.net [23.30.207.222]
11 98 ms 101 ms 109 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
12 99 ms 94 ms 101 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
Trace Route from Different Location (Does Work)
Tracing route to guidesforit.com [184.168.237.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 10.1.10.1
3 51 ms 11 ms 10 ms 98.211.0.1
4 9 ms 14 ms 19 ms 68.85.51.173
5 17 ms 17 ms 17 ms xe-7-1-0-0-sur02.murfreesboro.tn.nash.comcast.net [68.86.176.254]
6 11 ms 27 ms 14 ms xe-0-0-10-0-ar01.goodslettvll.tn.nash.comcast.net [162.151.9.61]
7 22 ms 19 ms 19 ms he-5-6-0-0-cr01.56marietta.ga.ibone.comcast.net[68.86.90.89]
8 40 ms 43 ms 30 ms he-2-9-0-0-cr01.chicago.il.ibone.comcast.net [68.86.85.169]
9 33 ms 31 ms 31 ms he-1-2-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.88.26]
10 31 ms 38 ms 30 ms he-0-10-0-1-pe04.350ecermak.il.ibone.comcast.net[68.86.83.54]
11 37 ms 29 ms 30 ms as26496-1-c.350ecermak.il.ibone.comcast.net [23.30.207.222]
12 92 ms 92 ms 93 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
13 91 ms 95 ms 93 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
14 92 ms 101 ms 93 ms ip-97-74-255-129.ip.secureserver.net [97.74.255.129]
15 93 ms 92 ms 91 ms p3nlhg138c1138.shr.prod.phx3.secureserver.net [184.168.237.1]
Trace complete.
What's wrong with my routing / connection which is causing this issue and more importantly, what may I do to fix this? I need to edit this site ASAP!
Please let me know what I may do or provide direct contact information. Thank You - Ben
Accepted Solution
BenK
New Member
•
3 Messages
11 years ago
Thanks to those that replied - but - after 6 days, it automatically started working again. No emails, notification, or any other communication. I can access the site and trace routes properly resolve.
Thanks!
0
0
Accepted Solution
VBSSP-RICH
Advocate
•
1.4K Messages
11 years ago
Hello again BenK,
Glad to hear that all is working again for you in that technologically mysterious manner. lol
Just wanted to clarify some aspects of your network interconnect for you:
"
Comcast Business Gateway
WAN = Ext IP
LAN = 10.1.10.0/24 This DHCP server SHOULD be 10.1.10.1.....fyi
DHCP On (Don't think I can turn off) You can disable the DHCP Server by logging into the Gateway.LAN.then click on the enable DHCP Server check mark to disable it.....fyi
Port Forwarding - 1 Rule
Rule #1 - All ports (1 - 65000) Both (TCP & UDP) --> 10.1.10.10 well you like to live risque I see. You can also do this by putting your 10.1.10.10 into the DMZ....fyi
OpenWRT Router
WAN = 10.1.10.10 (Statically set) Yup, this says you are definitely getting your dynamic IP address from the gateway, which is fine.
LAN = 192.168.0.0/24 sometimes having two DHCP servers concatenating can cause conflicts. I have found it is router specific whether it does or not and by conflicts I am referring to traceroute packet loss.
"
0
0
VBSSP-RICH
Advocate
•
1.4K Messages
11 years ago
Hello BenK and welcome,
It looks to me that you may be having DHCP conflicts between you firewall/router DCHP server and your Comcast modem DHCP server due to the following observatiion:
1 2 ms 13 ms <1 ms OpenWrt.lan [192.168.0.1] - this looks like a firewall/router DHCP Server or Gateway address
2 5 ms 1 ms <1 ms 10.1.10.1 ------------------------- this is the Comcast modem internal DHCP server address
So the above indicates that you have you firewall/router directly plugged into one of the LanPorts 1-4 and using the Comcast Modem internal DHCP server. These kind of conflicts can cause intermittent packet routing/loss issues. I am not saying this is the actual root cause of your issue, just and observation but more data below seems to provide additional justification.
No does not work:
10 50 ms 40 ms 46 ms as26496-1-c.350ecermak.il.ibone.comcast.net [23.30.207.222]
11 98 ms 101 ms 109 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
12 99 ms 94 ms 101 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
13 * * * Request timed out. -- this shows that two loses of all 3 packets have occurred on your 184.168.0.73 device. This could be due to the DHCP conflicts could be causing intermittent and inadvertent packet loss.
14 * * * Request timed out.
15 * * * Request timed out.
Yes does work:
10 31 ms 38 ms 30 ms he-0-10-0-1-pe04.350ecermak.il.ibone.comcast.net[68.86.83.54]
11 37 ms 29 ms 30 ms as26496-1-c.350ecermak.il.ibone.comcast.net [23.30.207.222]
12 92 ms 92 ms 93 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
13 91 ms 95 ms 93 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
14 92 ms 101 ms 93 ms ip-97-74-255-129.ip.secureserver.net [97.74.255.129]
15 93 ms 92 ms 91 ms p3nlhg138c1138.shr.prod.phx3.secureserver.net [184.168.237.1]
Trace complete.
I would recommend you try setting up a NAT public address to access resources outside your intra-network, like the Internet for your devices behind your firewall/router. These computers have to have a public address in order for responses to their requests to consistently return to them and avoid your above packet loss.
Hope this helps you out.
0
0
BenK
New Member
•
3 Messages
11 years ago
Thank you for your suggestions...
The odd thing is that it's worked for over a year without issue using the same setup - plus - when th issue occured, no new devices were added to the network which would prompt a potential DHCP issue.
Either way, below is how I currently have it configured. Unfortunately, the gateway's configuration options are limited. Are you suggesting using the gateway, itself, to create the NAT?
Comcast Business Gateway
WAN = Ext IP
LAN = 10.1.10.0/24
DHCP On (Don't think I can turn off)
Port Forwarding - 1 Rule
Rule #1 - All ports (1 - 65000) Both (TCP & UDP) --> 10.1.10.10
OpenWRT Router
WAN = 10.1.10.10 (Statically set)
LAN = 192.168.0.0/24
Thanks -
0
0