172.16.0.101

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,812
Reaction score
268
Location
A nearby event horizon
So, has anyone else noticed that we now have a new iBurst Blackhole Gateway?

I guess this means that 196.30.31.100 was "retired"...
 
ppp0 Link encap:Point-to-Point Protocol
inet addr:196.46.66.censored P-t-P:196.30.31.100 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:1432 Metric:1
RX packets:87276 errors:0 dropped:0 overruns:0 frame:0
TX packets:87057 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:27752762 (26.4 Mb) TX bytes:8262452 (7.8 Mb)

Nope, I'm still on the same gateway...
 
you are smarter than most, ic. certainly smarter than me. will reconnect after I trade some stocks ;-)
 
Thanks, but I know I'm not that smart ;-)

Anyways, here is a tracert I did after having had [more than the usual] problems [this evening] with my previous [to this] connection via 196.30.31.100:
Code:
[size=3]D:\Documents and Settings\...>tracert www.mybroadband.co.za

Tracing route to mybroadband.co.za [196.35.73.169]
over a maximum of 30 hops:

  1    50 ms    80 ms   150 ms  172.16.0.101
  2   220 ms   150 ms   120 ms  196.30.31.193
  3   351 ms   861 ms   160 ms  fe6-1.gw10.jnb6.alter.net [196.30.31.254]
  4   110 ms   180 ms    61 ms  fe1-0.br1.jnb7.alter.net [196.31.17.162]
  5   351 ms   140 ms   130 ms  as3741.rba.is.co.za [196.30.228.242]
  6   310 ms    80 ms   952 ms  196.26.0.20
  7    80 ms    70 ms    60 ms  drax.co.za [196.35.73.169]

Trace complete.[/size]
http://ws.arin.net/cgi-bin/whois.pl said:
Search results for: 172.16.0.101


OrgName: Internet Assigned Numbers Authority
OrgID: IANA
Address: 4676 Admiralty Way, Suite 330
City: Marina del Rey
StateProv: CA
PostalCode: 90292-6695
Country: US

NetRange: 172.16.0.0 - 172.31.255.255
CIDR: 172.16.0.0/12
NetName: IANA-BBLK-RESERVED
NetHandle: NET-172-16-0-0-1
Parent: NET-172-0-0-0-0
NetType: IANA Special Use
NameServer: BLACKHOLE-1.IANA.ORG
NameServer: BLACKHOLE-2.IANA.ORG
Comment: This block is reserved for special purposes.
Comment: Please see RFC 1918 for additional information.
Comment:
RegDate: 1994-03-15
Updated: 2002-09-12

OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName: Internet Corporation for Assigned Names and Number
OrgAbusePhone: +1-310-301-5820
OrgAbuseEmail: [email protected]

OrgTechHandle: IANA-IP-ARIN
OrgTechName: Internet Corporation for Assigned Names and Number
OrgTechPhone: +1-310-301-5820
OrgTechEmail: [email protected]

# ARIN WHOIS database, last updated 2005-02-20 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
 
hokay - here is my updated ifconfig -

ppp0 Link encap:Point-to-Point Protocol
inet addr:196.46.66.1337krw P-t-P:196.30.31.100 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:1432 Metric:1
RX packets:415 errors:0 dropped:0 overruns:0 frame:0
TX packets:647 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:79429 (77.5 Kb) TX bytes:59461 (58.0 Kb)


still the same gateway - I would think the difference comes from using alternate towers, but I heard that absolutely no ip work is done at the base station - perhaps they are testing the new gateway on a specific test subnet?
 
Very odd, I had been wondering if they were still going to be doing this "New Port Shaping" today, perhaps this is yet another experiment, and despite our UT's both being connected to the same base-station (or so we both presume)...

Can you confirm that 196.30.31.100 is still your 1st hop on a tracert?

(for control purposes tracert www.mybroadband.co.za)
 
Hey ic.... this is my ifconfig... same addy

ppp0 Link encap:Point-to-Point Protocol
inet addr:196.46.66.253 P-t-P:196.30.31.100 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1432 Metric:1
RX packets:136963 errors:0 dropped:0 overruns:0 frame:0
TX packets:104156 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:175881852 (167.7 Mb) TX bytes:7806935 (7.4 Mb)

Tracing route to www.is.co.za [196.35.72.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 101 ms 461 ms 187 ms 196.30.31.100
3 241 ms 256 ms 195 ms 196.30.31.193
4 62 ms 111 ms 244 ms fe6-1.gw10.jnb6.alter.net [196.30.31.254]
5 123 ms 239 ms 239 ms fe1-0.br1.jnb7.alter.net [196.31.17.162]
6 121 ms 123 ms 177 ms as3741.rba.is.co.za [196.30.228.242]
7 197 ms 148 ms 286 ms core2a-rba-gi4-0-0.rtr.isnet.net [196.26.0.8]
8 539 ms 315 ms 195 ms 168.209.100.134
9 278 ms 195 ms 329 ms 168.209.217.250
10 173 ms 234 ms 214 ms wsd1-bry.hosting.co.za [196.35.56.10]
11 275 ms 244 ms 160 ms weblive.onsite.hosting.co.za [196.35.72.14]

Trace complete.
 
It came, it tried to conquer, it failed, it went with tail between legs...

Code:
[size=3]D:\Documents and Settings\...>tracert [url]www.mybroadband.co.za[/url]

Tracing route to mybroadband.co.za [196.35.73.169]
over a maximum of 30 hops:

  1   531 ms    70 ms   130 ms  196.30.31.100
  2   140 ms    70 ms    81 ms  196.30.31.193
  3   180 ms    70 ms   361 ms  fe6-1.gw10.jnb6.alter.net [196.30.31.254]
  4   291 ms   210 ms   110 ms  fe1-0.br1.jnb7.alter.net [196.31.17.162]
  5   821 ms   101 ms    60 ms  as3741.rba.is.co.za [196.30.228.242]
  6   300 ms   120 ms   130 ms  196.26.0.20
  7   191 ms    60 ms    60 ms  drax.co.za [196.35.73.169]

Trace complete.[/size]
Looks like it's back to 196.30.31.100. I did catch them in the act of doing something though, I wonder what they were up to...:confused:
 
ic, I mentioned this a week or so ago. I always get time outs on the first hop, whereas I used to get 196.31.30.100.

Code:
Tracing route to mybroadband.co.za [196.35.73.169]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    77 ms   155 ms   186 ms  196.30.31.193
  3    77 ms    93 ms   108 ms  fe6-1.gw10.jnb6.alter.net [196.30.31.254]
  4    77 ms   124 ms    62 ms  fe1-0.br1.jnb7.alter.net [196.31.17.162]
  5   155 ms    93 ms   108 ms  as3741.rba.is.co.za [196.30.228.242]
  6    77 ms   124 ms   108 ms  196.26.0.20
  7    93 ms    93 ms    93 ms  drax.co.za [196.35.73.169]

Trace complete.

Buggered if I know what it means though.
 
Gatecrasher said:
ic, I mentioned this a week or so ago. I always get time outs on the first hop, whereas I used to get 196.31.30.100.
...
I remember you mentioned it, but I think that's an example of fluke, bcos I don't have that problem on the 1st hop, unless it's bcos your connection is always so fast & mine is always incredibly slooooow...
 
On the Cape Town CBD site we have always gone go through two private range ip gateways.

Tracing route to mybroadband.co.za [196.35.73.169]
over a maximum of 30 hops:

1 1 ms 23 ms <1 ms 192.168.1.1
2 74 ms 88 ms 90 ms 172.17.0.100
3 68 ms 89 ms 138 ms 192.168.2.1
4 157 ms 91 ms 83 ms fe2-1-0sub513.gw1.cpt1.alter.net [196.7.3.101]
5 155 ms 125 ms 118 ms fe1-0.br1.jnb7.alter.net [196.31.17.162]
6 132 ms 70 ms 164 ms as3741.rba.is.co.za [196.30.228.242]
7 136 ms 119 ms 180 ms 196.26.0.20
8 89 ms 162 ms * drax.co.za [196.35.73.169]
9 129 ms 116 ms 78 ms drax.co.za [196.35.73.169]

Trace complete.

If no IP work is done at the base station then why waste allocated IP's? It appears it is irrelevant what IP is assigned.
 
Hmmm, very interesting, might not necessarily be the base-station(s) as such, but perhaps these are the "Core Network" and/or "Peering Links".

I think we need more tracert listings, along with base-stations that are within range.
 
They definitely have some routing ability at their first hop.

Tracing route to www.iburst.co.za [196.30.31.120]
over a maximum of 30 hops:

1 1 ms 1 ms 24 ms 192.168.1.1
2 64 ms 91 ms 89 ms 172.17.0.100
3 67 ms 90 ms 88 ms 172.17.0.1
4 * * * Request timed out.
5 127 ms * 132 ms 172.28.1.138
6 131 ms 114 ms 119 ms 196.30.31.102
7 133 ms 118 ms 119 ms www.iburst.co.za [196.30.31.120]

Trace complete.

Iburst has its own route so we can authenticate here in Cape Town.
 
ic must be one of those special case scenarios ;)

ic: "im sick&tired of these slow eye-burst speeds.. dang it when will it be fixed!!1z0r"
WBS: "ahh bugger him, just send him to that blackhole we've secretly been working on, maybe throw in a couple hax and viruses"
:D
 
Oh my ***. 172.* is a reserved IANA address. In other words private. They're obviously trying to do _SOMETHING_ but it's clearly a frigging stupid idea.

Welcome to WBS's capping/traffic management attempts.
 
I cannot pick this address up running a tracert, however I did notice this address popping up the weekend the auth server failed. Since then I could not duplicate the result. I managed to pick it up using the advanced tracert in Tweakmaster.
 
Just noticed - IT IS BACK...

Code:
[size=3]D:\Documents and Settings\...>tracert [url]www.mybroadband.co.za[/url]

Tracing route to mybroadband.co.za [196.35.73.169]
over a maximum of 30 hops:

  1   130 ms   200 ms   841 ms  [b][color=red]172.16.0.101[/color][/b]
  2   100 ms   180 ms   101 ms  196.30.31.193
  3    60 ms    90 ms    90 ms  fe6-1.gw10.jnb6.alter.net [196.30.31.254]
  4   110 ms    50 ms   100 ms  fe1-0.br1.jnb7.alter.net [196.31.17.162]
  5   100 ms    50 ms    50 ms  as3741.rba.is.co.za [196.30.228.242]
  6    60 ms   821 ms    50 ms  196.26.0.20
  7    60 ms   120 ms    90 ms  drax.co.za [196.35.73.169]

Trace complete.[/size]
:eek:
 
also got 172.16.0.101 after a disconnect just now. That brings to mind that disconnections are not always because of bad connections but WBS screwing around with the systems
 
Top
Sign up to the MyBroadband newsletter
X