|
to PinkyThePig
Re: [ALL] Cox Router Abbreviationssaid by PinkyThePig:All this joking around reminds me of this tracert:
tracert -h 100 216.81.59.173
which resolves to:
Tracing route to FIN [216.81.59.173] over a maximum of 100 hops:
And now it makes the Register... » www.theregister.co.uk/20 ··· ceroute/ |
|
|
to CoxVegas
Neeerrrrrrrrrddddddd. Been there, done that. Same names, too. |
|
|
to CoxTech1
said by CoxTech1:That's funny, for the wireless stuff in my home I happen to use Ace Combat references. The SSID is B7R and all the devices are named for high value targets in various games in the series. Oh, you poor little mini-geeks.... I name my three servers at home after the supercomputers in Neon Genesis Evangelion (Caspar, Melchior, and Balthazar). My wireless SSID is Magi to go along with the theme. The desktops are named Rei, Shinji (which is a tiny little flaky piece of junk - the name came after that determination) Asuka, Misato and Ritsuko. Yes. Really. |
|
BryanInPHX Premium Member join:2001-03-06 Phoenix, AZ 2 edits |
to eSherlock
said by eSherlock :quote: My guess..
Mcdowell Regional Data Center Phoenix
With my own internet-sleuthing skillz, I found it. 33.713626,-111.66627 It looks like Cox attempts to disguise their high-tech facilities. Check out the microwave technology coming off that tower! That location (Parcel) is listed as Owner:RIO VERDE UTILITIES INC Parcel # 219-43-859A 25202 N Forest Rd, AZ 85263 Rio Verde Utilities Inc in Rio Verde, AZ is a private company categorized under Water and Sewage Companies-Utility. Parcel Info: » mcassessor.maricopa.gov/ ··· 43-859-AMaricopa Co GIS Maps: » maps.mcassessor.maricopa ··· 43-859-A=========================================== Here is the most likely location: Parcel# 117-10-087 Owner: COX COMMUNICATIONS PHOENIX INC 33.466884,-112.030936 1626 N 24th St Phoenix, AZ 85008 » mcassessor.maricopa.gov/ ··· 7-10-087» maps.mcassessor.maricopa ··· 7-10-087My best guess is this is the Cox Chandler Data Center Parcel # 301-89-944 Owner: COX COMMUNICATIONS INC 33.304277,-111.913585 100 N 79TH ST CHANDLER 85226 » mcassessor.maricopa.gov/ ··· 1-89-944» maps.mcassessor.maricopa ··· 1-89-944 |
|
|
to VentShop
That's funny, for the wireless stuff in my home I happen to use Ace Combat references. The SSID is B7R and all the devices are named for high value targets in various games in the series. |
|
VentShop join:2009-08-21 Oklahoma City, OK ARRIS CM8200 (Software) OPNsense Netgear R8000
|
to PinkyThePig
ROFLMAO, Pinky I love it and Obviously someone has a HUGE amount of time on their hands to do something like that.
But yes sometimes it is fun to just mess with people in naming schemes, I worked for a WISP in Oklahoma and his network was originally baseball in origin, first base second base homeplate etc. He picked up other networks over a few years and had to then begin naming the tower locations based off of their physical location just to keep things straight. My home network is done much the same as I name computers based off of characters in a movie so I can keep track of which computer in my head is what. So I can tell my wife to go to a specific computer and reboot it base don it having its own name other than the 3rd one from the left on the desk in the bedroom 0-o |
|
|
eSherlock to Anonguy
Anon
2013-Feb-14 10:23 am
to Anonguy
quote: My guess..
Mcdowell Regional Data Center Phoenix
With my own internet-sleuthing skillz, I found it. 33.713626,-111.66627 It looks like Cox attempts to disguise their high-tech facilities. Check out the microwave technology coming off that tower! |
|
|
to CoxVegas
said by CoxVegas:It tends to vary a fair bit by market - internally our addressing is consistent, but the DNS names can get missed. I'll grant that, but take a look here for instance: » [ALL] Blizzard traceroutes to ChicagoMost Cox equipment has no reverse DNS presented, and some have ancient Cox DNS names like coxinet.net. Granted, it has no impact on service at all, but its nice for power users and helpful when things aren't quite right. Level3 is an example of somebody who does a good job with RDNS. |
|
|
to chrisf8657
My guess..
Mcdowell Regional Data Center Phoenix |
|
|
LOL, Pinky.
CoxVegas, Probably not going to happen though I can wish - cut and paste the info w/o IPs, etc.? ...but do me a favor at least and tell me what mcdldsrj01-ae2.0.rd.ph.cox.net stands for. |
|
|
to chrisf8657
All this joking around reminds me of this tracert:
tracert -h 100 216.81.59.173
which resolves to:
Tracing route to FIN [216.81.59.173] over a maximum of 100 hops:
...
13 70 ms 79 ms 77 ms Episode.IV [206.214.251.1] 14 75 ms 70 ms 70 ms A.NEW.HOPE [206.214.251.6] 15 74 ms 82 ms 71 ms It.is.a.period.of.civil.war [206.214.251.9] 16 75 ms 85 ms 74 ms Rebel.spaceships [206.214.251.14] 17 78 ms 71 ms 70 ms striking.from.a.hidden.base [206.214.251.17] 18 71 ms 70 ms 76 ms have.won.their.first.victory [206.214.251.22] 19 73 ms 71 ms 79 ms against.the.evil.Galactic.Empire [206.214.251.25] 20 91 ms 91 ms 81 ms During.the.battle [206.214.251.30] 21 85 ms 90 ms 84 ms Rebel.spies.managed [206.214.251.33] 22 78 ms 97 ms 102 ms to.steal.secret.plans [206.214.251.38] 23 105 ms 99 ms 81 ms to.the.Empires.ultimate.weapon [206.214.251.41] 24 70 ms 73 ms 67 ms the.DEATH.STAR [206.214.251.46] 25 77 ms 74 ms 69 ms an.armored.space.station [206.214.251.49] 26 67 ms 83 ms 72 ms with.enough.power.to [206.214.251.54] 27 80 ms 71 ms 72 ms destroy.an.entire.planet [206.214.251.57] 28 76 ms 71 ms 71 ms Pursued.by.the.Empires [206.214.251.62] 29 75 ms 71 ms 74 ms sinister.agents [206.214.251.65] 30 81 ms 70 ms 80 ms Princess.Leia.races.home [206.214.251.70] 31 78 ms 73 ms 72 ms aboard.her.starship [206.214.251.73] 32 74 ms 71 ms 72 ms custodian.of.the.stolen.plans [206.214.251.78] 33 81 ms 77 ms 72 ms that.can.save.her [206.214.251.81] 34 74 ms 73 ms 75 ms people.and.restore [206.214.251.86] 35 73 ms 72 ms 74 ms freedom.to.the.galaxy [206.214.251.89] 36 70 ms 70 ms 72 ms 0-------------------0 [206.214.251.94] 37 71 ms 72 ms 78 ms 0------------------0 [206.214.251.97] 38 76 ms 71 ms 81 ms 0-----------------0 [206.214.251.102] 39 74 ms 70 ms 71 ms 0----------------0 [206.214.251.105] 40 72 ms 71 ms 73 ms 0---------------0 [206.214.251.110] 41 75 ms 77 ms 72 ms 0--------------0 [206.214.251.113] 42 72 ms 73 ms 79 ms 0-------------0 [206.214.251.118] 43 75 ms 78 ms 71 ms 0------------0 [206.214.251.121] 44 75 ms 78 ms 72 ms 0-----------0 [206.214.251.126] 45 70 ms 76 ms 73 ms 0----------0 [206.214.251.129] 46 85 ms 76 ms 78 ms 0---------0 [206.214.251.134] 47 75 ms 70 ms 72 ms 0--------0 [206.214.251.137] 48 70 ms 78 ms 76 ms 0-------0 [206.214.251.142] 49 81 ms 72 ms 71 ms 0------0 [206.214.251.145] 50 74 ms 76 ms 72 ms 0-----0 [206.214.251.150] 51 77 ms 77 ms 77 ms 0----0 [206.214.251.153] 52 72 ms 77 ms 73 ms 0---0 [206.214.251.158] 53 74 ms 77 ms 75 ms 0--0 [206.214.251.161] 54 78 ms 75 ms 78 ms 0-0 [206.214.251.166] 55 70 ms 74 ms 84 ms 00 [206.214.251.169] 56 84 ms 75 ms 76 ms I [206.214.251.174] 57 77 ms 77 ms 75 ms By.Ryan.Werber [206.214.251.177] 58 70 ms 87 ms 73 ms When.CCIEs.Get.Bored [206.214.251.182] 59 72 ms 76 ms 75 ms CCIE.38168 [206.214.251.185] 60 77 ms 77 ms 71 ms FIN [216.81.59.173] |
|
1 recommendation |
to bchandler02
said by bchandler02:Why not go all out and really screw with people? "lnksysbefsr11.okc.ok.cox.net" How'd you know the name of our Chicago peering router? |
|
|
to CoxVegas
said by CoxVegas:Mind you, if *I* were running things, I'd name our routers at a major peering center in California something like "cisco2600.fe10.anchorage.ak.cox.net" just to mess with people. Why not go all out and really screw with people? "lnksysbefsr11.okc.ok.cox.net" |
|
|
|
to chrisf8657
said by chrisf8657:CoxVegas,
I don't see any reason it's "super duper secret". Because the lists I have has more than just IPs and hostnames. Anyway, the names are fairly straight-forward, like I mentioned. Using those abbreviations and the other posts on here, you can get a general feel for where things go. Mind you, if *I* were running things, I'd name our routers at a major peering center in California something like "cisco2600.fe10.anchorage.ak.cox.net" just to mess with people. |
|
|
to CoxVegas
CoxVegas, I don't see any reason it's "super duper secret". It's handing out a reverse DNS. Simply knowing what "wsip" stands for doesn't allow me any ability to do anything. It's almost comical to debate it. And, I'm curious because I want to know where the packets go (what each router could be) on their way out to the Internet. It's just a personal computer-tech type interest. BoltPride, Seen that. Like I said some are out of date now. Thanks tho. |
|
|
to BillRoland
said by BillRoland:I believe "ws" stands for Business or "wholesale" IP. Yep. said by BillRoland:I've found Cox is wildly inconsistent in reverse DNS naming for their equipment, when they bother at all. It tends to vary a fair bit by market - internally our addressing is consistent, but the DNS names can get missed. |
|
|
to chrisf8657
I believe "ws" stands for Business or "wholesale" IP.
I've found Cox is wildly inconsistent in reverse DNS naming for their equipment, when they bother at all. |
|
Metal Head Premium Member join:2001-02-15 Escondido, CA |
to chrisf8657
|
|
|
to chrisf8657
said by chrisf8657:Does anyone have a list of the names of the Cox routers? Yes... but not ones I can hand out. Just out of curiosity, what are you wanting to know? The names are FAIRLY explanatory with a little reading and research. I may be able to answer specific questions. |
|
|
Hi again people.
Does anyone have a list of the names of the Cox routers?
Like what is wsip-184-178-205-8.ph.ph.cox.net? mcdldsrj01-ae2.0.rd.ph.cox.net?
Just curious. I found a thread from many years ago about them but it's outdated because the names have been changed.
Many thanks. |
|