Network puzzle
-
Why is there a difference in getting your IP from say IPChicken or What's My IP and using TraceRT?
17x.xxx.210.1What's My IP
17x.xxx.210.1Tracert
2 13 ms 9 ms 8 ms 1xx.25x.154.133 3 249 ms 30 ms 17 ms xx.midwest.rr.com [7x.12x.5.109] -
TraceRT is showing the route, not your IP.
-
@scottalanmiller said in Network puzzle:
TraceRT is showing the route, not your IP.
What the big man said
-
I can get behind that...
However let me toss in a wrench.
Connect to a site, run IPChicken or What's My IP, and I get a FIBRANT IP, but TraceRT gives TWC route.
-
I'm confused.
IPchicken/What's my IP are sites that do little more than tell you the IP source address in the IP packet sent to them.
tracert is a command that finds the path that your packets travel to get to a location on a network.
-
@Dashrender said in Network puzzle:
I'm confused.
IPchicken/What's my IP are sites that do little more than tell you the IP source address in the IP packet sent to them.
tracert is a command that finds the path that your packets travel to get to a location on a network.
Right -
Let me add that I'm showing a Fibrant IP, but I am suppose to have a static TWC IP.
-
@gjacobse said in Network puzzle:
@Dashrender said in Network puzzle:
I'm confused.
IPchicken/What's my IP are sites that do little more than tell you the IP source address in the IP packet sent to them.
tracert is a command that finds the path that your packets travel to get to a location on a network.
Right -
Let me add that I'm showing a Fibrant IP, but I am suppose to have a static TWC IP.
How do you know it's a Fibrant IP? Because IPchicken or What's my IP says so? It's likely that those services have old information, or that the DB of IPs hasn't been updated.
If you are seeing the wrong IP listed on those websites, then you have a firewall issue, or your ISP is translating your IP upstream from you.
-
@gjacobse said in Network puzzle:
@Dashrender said in Network puzzle:
I'm confused.
IPchicken/What's my IP are sites that do little more than tell you the IP source address in the IP packet sent to them.
tracert is a command that finds the path that your packets travel to get to a location on a network.
Right -
Let me add that I'm showing a Fibrant IP, but I am suppose to have a static TWC IP.
Are you saying that 17x.xxx.210.1 from your first post is a Fibrant IP? How did you determine this? We can see from your tracert you are taking a TWC route (the second hop is rr.com (road runner).
Like @scottalanmiller said tracert won't get you your IP, just the routers on the way out.
-
@gjacobse said in Network puzzle:
I can get behind that...
However let me toss in a wrench.
Connect to a site, run IPChicken or What's My IP, and I get a FIBRANT IP, but TraceRT gives TWC route.
So Fibrant is on TWC. Is that surprising?
-
@donaldlandru said in Network puzzle:
@gjacobse said in Network puzzle:
@Dashrender said in Network puzzle:
I'm confused.
IPchicken/What's my IP are sites that do little more than tell you the IP source address in the IP packet sent to them.
tracert is a command that finds the path that your packets travel to get to a location on a network.
Right -
Let me add that I'm showing a Fibrant IP, but I am suppose to have a static TWC IP.
Are you saying that 17x.xxx.210.1 from your first post is a Fibrant IP? How did you determine this? We can see from your tracert you are taking a TWC route (the second hop is rr.com (road runner).
Like @scottalanmiller said tracert won't get you your IP, just the routers on the way out.
IPs shown in the OP are mine and I am on TWC. Just as an example.
-
If you haven't already drop 17x.xxx.210.1 into arin.net and see who owns it.
For more fun once you do the lookup on ARIN take the AS number and drop it into bgp.he.net then look at Graph v4.. Then you can see fun stuff like how your ISP is interconnected with others.
I am not familiar with who Fibrant is, maybe TWC is there upstream/reseller.
-
So, we figured out what the conflict was that caused a Fibrant IP to come back when we knew that only TWC was active...
The old router (powered off) was still connected physically to the old (should have been discontinued) Fibrant service. Somehow, it got turned back on and since no one ever physically removed it, and it had a mirrored LAN config... sudden packet losses galore! It is now powered off, physically disconnected, and removed from the rack. IP searches return a proper TWC IP address now.
-
One of the problems that can arise when you have no smart hands at a remote site: no one to unplug a defunct piece of networking equipment and avoid situations like this!
-
whois.arin.net for North America IP assignment information.
-
@donaldlandru said in Network puzzle:
If you haven't already drop 17x.xxx.210.1 into arin.net and see who owns it.
For more fun once you do the lookup on ARIN take the AS number and drop it into bgp.he.net then look at Graph v4.. Then you can see fun stuff like how your ISP is interconnected with others.
I am not familiar with who Fibrant is, maybe TWC is there upstream/reseller.
My ISP (IP) does not have an AS Number...
-
lol firewall problems.
