4 Jun
2012
4 Jun
'12
3 p.m.
O I understand that it is routable but with the current project via USCD it
is not routable it is stopped at Brian's server which in essence is just a
big linksys router with tunnels all over the world to really less than 3000
live addresses at any given time. This is akin to a company network using
internet tunnels. Those networks have 10.x.x.x addresses. While yes the
remote networks could be reached via UCSD. They really can not right now
from a network outside of the 44 network so in essence we are holding
millions of addresses for lets say at most 10,000 active users. That is
a usage rate of <0.7%
Again I say the tunnel project is a great project dont get me wrong. But
s#!t or get of the pot with the addresses already. I am getting impatient
with all the circular logic on this list. Either let others use the space
or let ICANN decide what to do with them full stop! No more we are talking
to lawyers, no more BS. 30 days come up with a plan or get the issue
turned over to ICANN for a decision.
Lin
On Mon, Jun 4, 2012 at 3:14 PM, Marius Petrescu <marius(a)yo2loj.ro> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
44.x.x.x IS routable. The fact that some parts of it are not is a specific
"feature" of 44 usage, implementation and geographic distribution.****
You can reach 44 hosts from the public internet (via ucsd.edu - but this
is nothing special, every subnet has somewhere one or more specific routing
points).****
** **
10.x.x.x (together with 192.168.x.x, 172.16-31.xx.xx and 169.254.0.0) is
not routable. Every provider taropits/drops private and link-local IPs,
since their uniqueness can not be ensured. And this means that 10.x.x.x
addresses will NEVER be reachable except if tunneling is used.****
** **
** **
*From:* 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:
44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu] *On Behalf Of *Lin
Holcomb
*Sent:* Monday, June 04, 2012 19:13
*To:* AMPRNet working group
*Subject:* [44net] 44net is not just for tunneling****
** **
I am still in the holding pattern while ya'll work out things, but I share
Ralphs frustration. I see tunneling as a project that uses 44net not the
whole 44net project. It seems to me that this has been confused by many
and sent the 44net down one road. We need some highways and not 2 lane
dirt roads, sorry but 1200baud or even 9600 baud is a two land dirt road
compaired to 10-300 meg connections I can offer I spoke to several groups
at Dayton and there are many others who would love to have use of the IP
addresses Dstar, highspeed packet ect. (not tunneling all thru UCSD)****
****
The inability to have routeabil addresses from the net back to the
44net( or the lack of desire do to the slow speeds) raises this question
how is it that the current tunneling network would be different if the
44.x.x.x was replaced with a 10.x.x.x and the route point at UCSD was a
44.x.x.x ? Really what advantage does a non-routabile 44 have over a 10
with the way you are currently using the network?****
****
From perspective I see no difference....If I cant see a difference
why would ICANN? Folks this is 1/255 off all of the ipv4 addresses in the
world we are talking about. This is like 220 in the 80s use it or loose
it. ****
****
Lin ****
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
--
Lin Holcomb
Office: +1 404 806 5412
Mobile: +1 404 933 1595
Fax: +1 404 348 4250