Rogue DHCP Server - Colorado Springs, 80916 and Surrounding Area
Ehancing the network in the area is causing huge issue as many of us are getting a
24.128.XXX.XXX IP address. This is a Wallingford, Connecticut area IP address and is causing random disconnects. I was looking for a 75. or 70.162 or 70.163
Please look into this asap!
24.x.x.x addresses are not "rogue". They are valid Comcast IP addresses in some areas. You likely recently received a new / different WAN (public) IP address assignment to your connection from their DHCP server / IP address pool, and the rDNS / geolocation data that is associated with it is now incorrect for you as it previously belonged to someone else that lived in that area. Comcast shuffles blocks of IP addresses around the country all the time. ISP's don't correct this. A third party service does. Unfortunately, this is typically a *back-burner* thing to get corrected. The only thing that you can do is to report it. You can try this;
Wait for the geolocation provider to approve your request. If your request is approved, the amount of time it takes to see the correction varies by provider. The average is a month or more.
I was able to run a trace route to Google and the first hop on the internet is a 10.61.N.N. I know this where my issue is. The provisioning of the modem was messed up when "Comcast" enhnaced my internet to the new XFi, but in return messes up the provisioning on the modem.
IP addresses in the 10.61.x.x.x range are private (non-routable) addresses for a LAN.
The "provisioning" of a cable modem has nothing directly to do with the assignment of public / WAN IP addresses.
Random disconnects are typically related to RF signal / coax cable system impairments. What do the modem's signal stats look like ?
Start with the modem's signal stats. Perhaps they already are, or they are close to being out of spec and intermittently they go completely of spec. Try getting them here http://192.168.100.1 or here http://10.0.0.1
Please post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
What is the exact make and model number of the modem ?
Is this a WiFi connection ?
My service levels are good and I had a technician confirm all of that on Saturday. I am 1 of 3 people on the node. The node was enhanced and now this is what I get when I go out to the internet.
No my trace route to Google I get the following.
With my router
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 28 ms 10.61.XX.XX
3 7 ms 7 ms 7 ms 96.110.XX.XX
4 11 ms 12 ms 10 ms 162.151.XX.XX
5 11 ms 9 ms 9 ms be-36031-cs03.1601milehigh.co.ibone.comcast.net [96.110..XX.XX]
6 9 ms 8 ms 9 ms be-3302-pe02.910fifteenth.co.ibone.comcast.net [96.110..XX.XX]
7 10 ms 9 ms 9 ms as15133-3-c.nota.fl.ibone.comcast.net [23.30..XX.XX]
8 10 ms 10 ms 11 ms 209.85..XX.XX
9 8 ms 9 ms 9 ms 72.14..XX.XX
10 9 ms 9 ms 8 ms den16s03-in-f14.1e100.net [22.214.171.124]
Without my router
1 35 ms 36 ms 37 ms 10.61.XX.XX
2 7 ms 7 ms 7 ms 96.110.XX.XX
3 11 ms 12 ms 10 ms 162.151.XX.XX
4 11 ms 9 ms 9 ms be-36031-cs03.1601milehigh.co.ibone.comcast.net [96.110..XX.XX]
5 9 ms 8 ms 9 ms be-3302-pe02.910fifteenth.co.ibone.comcast.net [96.110..XX.XX]
6 10 ms 9 ms 9 ms as15133-3-c.nota.fl.ibone.comcast.net [23.30..XX.XX]
7 10 ms 10 ms 11 ms 209.85..XX.XX
8 8 ms 9 ms 9 ms 72.14..XX.XX
9 9 ms 9 ms 8 ms den16s03-in-f14.1e100.net [126.96.36.199]
The first hop should not be there at all.
1 35 ms 36 ms 37 ms 10.61.XX.XX <------ this is what is wrong and needs to addressed.
Are you behind some sort of an internet proxy ?
Click on that 10.61.x.x.x address here and see what info is returned;
Not at all.
I simply have the coax connected to the tap directly to my modem. Give of take 30~40 feet.
My modem pushes this when I am directly connected.
Simple laptop connecting directly to the modem. The tech meter could not determine a connection when conencted through the ethernet. Coax was pushing 1296 Mbps unfiltered down.
This is my modem signal as requested.
Warning : This is not a valid IP address on the Internet because it belongs to a private network. It does not identify a unique destination as it is only meant to be used inside local area networks
10.61.27.2 -- this is the first hop
The downstream stats are good. You didn't post the upstream power.
Right. That is a private intranet type of address. The Comcast DHCP server can not issue private / LAN IP addresses. It is something on your end. Look at the 10.61. addresses here on this google search and see if you can piece together some of the info;
Good luck !
Add that is what I am saying and it is servering a private IP and did so the day the enhancement happened. And this is happening to everyone that goes through this ehancement process.
This is absolutely 100% NOT on my end. Completely disagree with your assessment.
I have changed nothing and I mean nothing on my end for 5 years and now its my issue.
Upstream is fine. Then call in to customer service and ask them what it is ? I'm not an employee. Sorry I couldn't help you. Good luck again.
No prob. Maybe they've newly implemented a proxy ? They have always stated that they don't employ proxies. YMMV.
I doubt it. To what avail ? Why do that when their gateway devices are already doing NAT ? That is mainly employed by telecoms.
It does appear they may have introduced a Carrier grade NAT. The latency between the 10.61 to an IP4 translation keeps dropping. After a period of time I stop getting an IPV4 address and websites time out and my connection stalls while it tries to reconnect. It does this over and over through the day. Then it says my only connection is a IPV6 address becaue it cannot resolve an IPV4. That is unless I force my computer off IPV6. Then it resolves to a crazy IP address somewhere else in the country per the GEO Location that was last given by that IP.
Why would they need that? It was intended to address the potential shortage of IPv4 addresses. Now, with the implementation of an overabundance of IPv6 addresses, NAT is now basically obsolete.
Also, the middleboxes that would make it function would not need IP addresses (be IP addressable ) that would show up with ping / tracert probes. They would be invisible on the network just like the many many other middleboxes / devices that the general public doesn't know they even exist.
Something else is going on but I can't tell you what it may be, sorry.
I have truly gotten nowhere.
I have called over 65+ people in now 7 days.
I had 2 techs with another one coming again.
The tap is great pushing 1297 unfiltered packet size.
I am just as preplexed as you.
I think the TFTP could be wiped.
The area I did find out had a fiber cut as well. I am getting more and more pieces everytime I call in.