Jump to content
Posted 25 August 2012 - 11:33 PM
Posted 26 August 2012 - 01:24 AM
Posted 26 August 2012 - 10:53 AM
Posted 26 August 2012 - 12:43 PM
Posted 30 August 2012 - 02:08 AM
Posted 30 August 2012 - 04:24 PM
I am trying to get a new COX Ip address.
Posted 14 May 2013 - 10:26 PM
I may be a newbie IT guy, but disconnecting anything is bad for business in terms of waiting for re-establishment of systems, but you do have some options to release and request a new IP from a provider. I know this is an old post, but it kinda irks me that folk are happy to wait for a long period of time so that something happens... Well, lets change that thought path shall we.
According to the original post concerning Cox advice to get a new IP: that will only release and update their addressing if you DO NOT have anything but a cable modem on your end. If you are going from modem to a router then things become complicated. You will have to take care of things on the modem and the router. Modems and routers are kinda a hybrid technology these days. They can play on the first three levels of the OSI format, I know I will not be able to clear up these levels in a simple statement. So for now let me address the issue at hand, with the thought this IP refresh request is based on a baseline Cox broadband internet connection with a possible wireless router switch that has four physical ports.
I will pause here and wait for discussion, obviously there is no reason for me to continue if there is no interest of this topic any longer.
Posted 03 April 2015 - 03:47 AM
Posted 03 April 2015 - 10:27 PM
Wow, damn near two years later someone shows interest. I'm not downing you mmasterson91, but please realize that so much time has passed I'll have to start from scratch in researching this. Also all the notes I had (well my whole hard drive) got destroyed by a botched partition resizing attempt, in fact shortly shortly after making that post is when I made the fatal mistake that killed the drive. I'll spare you such sorrow, when working with a multi OS system, only perform partitioning operations on the initial root system otherwise the secondary OS will overwrite the partition table and leave it unreadable once you change to another OS.
Now with out researching anything and perhaps allow you to start your own research here's what comes to mind currently. Folk forget that the router or switch is not the direct gateway that needs to be reset, the problem is that normally we lose the ability to communicate with the real gateway, which is the modem, overtime. If you want to understand what I'm talking about do a trace route directly to your Cox provider website and you'll quickly see that this reset ain't gonna be a simple thing.
Here is a copy of the route I follow and you'll note I did NOT hit the actual Cox addressing site as they block ping requests.
Tsygen:~ lazerback$ traceroute
Usage: traceroute [-adDeFInrSvx] [-A as_server] [-f first_ttl] [-g gateway] [-i iface]
[-M first_ttl] [-m max_ttl] [-p port] [-P proto] [-q nqueries] [-s src_addr]
[-t tos] [-w waittime] [-z pausemsecs] host [packetlen]
Tsygen:~ lazerback$ traceroute www.cox.com
traceroute to www.cox.com (22.214.171.124), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 2.552 ms 1.282 ms 1.126 ms
2 10.132.24.1 (10.132.24.1) 9.221 ms 11.627 ms 9.875 ms
3 126.96.36.199 (188.8.131.52) 10.516 ms 16.970 ms 11.404 ms
4 184.108.40.206 (220.127.116.11) 10.220 ms 8.249 ms 9.537 ms
5 dukedsrj02-ae4.0.rd.at.cox.net (18.104.22.168) 33.358 ms 35.564 ms 34.869 ms
6 22.214.171.124 (126.96.36.199) 34.838 ms 36.989 ms 38.642 ms
7 * * *
8 * * *
9 * * *
traceroute to www.google.com (188.8.131.52), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.616 ms 1.266 ms 1.186 ms
2 10.132.24.1 (10.132.24.1) 10.709 ms 9.472 ms 9.921 ms
3 184.108.40.206 (220.127.116.11) 10.796 ms 10.044 ms 10.685 ms
4 18.104.22.168 (22.214.171.124) 9.024 ms 12.068 ms 9.473 ms
5 dalsbprj02-ae2.0.rd.dl.cox.net (126.96.36.199) 34.042 ms 50.023 ms 25.110 ms
6 188.8.131.52 (184.108.40.206) 20.400 ms 21.589 ms 21.829 ms
7 220.127.116.11 (18.104.22.168) 22.989 ms
22.214.171.124 (126.96.36.199) 27.011 ms
188.8.131.52 (184.108.40.206) 21.717 ms
8 220.127.116.11 (18.104.22.168) 56.542 ms
22.214.171.124 (126.96.36.199) 57.296 ms 57.030 ms
9 188.8.131.52 (184.108.40.206) 55.376 ms
220.127.116.11 (18.104.22.168) 61.553 ms
22.214.171.124 (126.96.36.199) 57.493 ms
10 188.8.131.52 (184.108.40.206) 71.899 ms 54.590 ms
220.127.116.11 (18.104.22.168) 56.159 ms
11 22.214.171.124 (126.96.36.199) 55.163 ms 61.380 ms 55.505 ms
12 lax02s21-in-f4.1e100.net (188.8.131.52) 57.675 ms 57.627 ms 55.710 ms
Oh, just ran across an interesting link while I was trying to ensure I was discerning the line item paths above and while I have not read it entirely (getting tired, almost midnight) I found it interesting enough to share: https://www.whatismyip.com/how-to-change-your-ip-address/
G'night mon, we'll have another go at this tomorrow or whenever.
Edited by cheawick, 03 April 2015 - 11:38 PM.
Posted 04 April 2015 - 01:16 AM
Some of the higher end IP adds had me perplexed and I had to follow my curiosity, traditionally the main Google server is listed as a hard (static) IP of 184.108.40.206 (which is an IPv4 listing), however it appears they are now utilizing dynamic IPv6 listing and if you don't click on the link I'm providing at this very moment I'm posting it yer probably gonna get something else than Google:http://www.speedguide.net/ip/220.127.116.11
That link actually looks like a pretty useful site that I never encountered before...
An additional note, should you really be concerned about your TCP/IP and UDP traffic you need to download Wireshark, it's a free network analysis tool, and if yer using an Windows system you can actually configure it to monitor router traffic and possibly direct gateway traffic.
Thanks for making me think, I haven't had a decent mental challenge since I messed up my knees and lost my mechanic job back in 2011.
Edited by cheawick, 04 April 2015 - 01:26 AM.
Posted 05 April 2015 - 12:35 AM
Wow, I must have been deliriously tired when posting that last one and sadly by the time I got here again I'm pretty pooped out.
I can validate that Wireshark is a super tool for understanding all data traffic as long as you actually record samples of activity to compare with a freshly recorded sample.
Again however, it appears that this will probably be the end of this thread, another restart of a conversation has come to no conclusion.
FYI to everyone here, give feedback PLEASE!!!
When I get no response I ask myself why the heck I'm providing to folk on the internet advice for free. Seriously, think about it.
Posted 01 March 2018 - 07:48 PM
Cheawick, not to bring you down or be mean, but almost nothing you have said is correct. And spreading false information is worse than being silent in my opinion.
Getting a new "internet facing" IP address does not concern your router at all. Modems don't have IP addresses. And the modem only operates on the physical(1st) layer of the OSI model while the router is on layer 3. These are basic networking facts.
The traceroute simply returns all of the layer 3 networking "hops" that your packets go through to reach their destination. They care nothing about your IP address and don't store it in their IP tables, such that they prevent you from changing your IP.
Also, we aren't talking about DNS at all, so why would anyone clear their DNS? And I'd wager that most of these devices listed in the traceroute rely on an actual DNS server for their DNS needs.
http://www.speedguide.net/ip/18.104.22.168 That is still an IPv4 address.
This is an example of IPv6: 1200:0000:AB00:1234:0000:2552:7777:1313
And nothing about IPv4 or IPv6 is static or dynamic. Both protocols utilize static and dynamic addressing.
Resetting your IP is as simple or as difficult as your ISP makes it. But it's not a complex feat technologically. Your router just gets a new one. Simple as that. Whether you have the ability to change it yourself, you request a new one, your ISP uses DHCP to allocate them as they're requested, or the IP is tied to the modem's MAC address. But changing it is simple, easy, and completely voluntary.
As soon as you have a new IP address, all requests go out like normal and everyone responds to your web requests like you're a new person. Because they don't care who you are/were. Their job is to serve content to whoever requests it.
Edited by ActualNetworkingGuy, 01 March 2018 - 07:52 PM.
0 members, 0 guests, 0 anonymous users