Was trying to determine where this 'honolulu' speedtest was hosted:
Tracing route to honolulu.speedtest.net [74.209.160.12]
over a maximum of 30 hops:
1 22 ms * * 123.87.93.224
2 27 ms 29 ms 25 ms
hawaiian-telcom-inc.gigabitethernet2-17.core1.lax2.he.net
[184.105.134.170]
3 84 ms 90 ms 84 ms gige-g2-17.core1.lax2.he.net
[184.105.134.169]
4 92 ms 98 ms 99 ms 10gigabitethernet7-3.core1.sjc2.he.net
[184.105.213.5]
5 112 ms 114 ms 112 ms 10gigabitethernet4-3.core1.sea1.he.net
[72.52.92.158]
6 113 ms 113 ms 114 ms six.netriver.net [206.81.80.160]
7 113 ms 113 ms 113 ms
static-74-209-160-12.lynnwood.netriver.net [74.209.160.12]
Trace complete.
Well, the DNS name is for a colocation facility in Lynnwood, WA via the
Seattle Internet Exchange. I can confirm that the 6th hop actually does
traverse the SIX, in as much as that IP is correct.
I'm assuming your provider's network engineers (stupidly) assumed 123.x.x.x was a good idea for use in a private setup because it hadn't been assigned from the global pool (yet).
Wouldn't be the first provider or service to not use proper RFC assigned private IP space for their internal networking setup.
Thanks. What concerned me was the first hop...22ms. is ~ the distance
from Maui to Oahu, but why the Chinese IP? Cruel joke?
I"m using Hawaiian Telcom's ADSL service and that first hop has always
been their gateway IP address.
Another TCP trace shows the first hop as 123.74.62.128...another CN
address.
I'm assuming your provider's network engineers (stupidly) assumed
123.x.x.x was a good idea for use in a private setup because it hadn't
been assigned from the global pool (yet).
Wouldn't be the first provider or service to not use proper RFC assigned
private IP space for their internal networking setup.
I'm assuming your provider's network engineers (stupidly) assumed
123.x.x.x was a good idea for use in a private setup because it hadn't
been assigned from the global pool (yet).
Wouldn't be the first provider or service to not use proper RFC assigned
private IP space for their internal networking setup.
They are testing IPTV on Oahu in preperation for roll-out, so maybe they
renumbered in order to more easily identify the segments.(?)
Really, I'd have hoped they'd use their two-year-old 2607:f9a0::/32 for anything that ambitious...but I might be wishing for too much. (Also, that 123 block seems to have been allocated in 2006, so it'd be even more unprofessional to start projects with that space since then.)
Poorly thought out private IP space? Nah...it's part of their security measures. It keeps those pesky Chinese from communicating with their network. Bots, bulletproof spammer hosting, who needs to talk to that?
