Can someone tell me if the encap.txt file is still available in the portal? I was looking for it today and cannot seem to find it.
Thanks
Jesse - WC3XS
On 3/24/14, 7:22 PM, Robbie De Lise wrote:
> Each link you setup between 2 nodes in the mesh needs a /30.
> You can get 64 /30's in a /24.
/31's are better :)
http://tools.ietf.org/rfc/rfc3021.txt
73's
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
On 3/22/14, 11:14 AM, Geoff Joy wrote:
> What I see above from both of you is "this is a mess, someone needs to
> clean it up, but that someone isn't going to be me". I must boldly
> state that if you have the time to discern a problem and criticize a
> state of affairs, you have the time to take ownership of that problem
> and fix it.
+1
I've said there are numerous things I don't care for with the way 44net is
used and deployed (not a personal attack :).
I've also mentioned I don't have the time to write up proposals and do stuff
to change it. As such I'm not going to bitch about it (or at least try not to).
I'd be happy to start a working group if I have some help, but between my day
job, building a simulcast repeater system, and doing the paperwork to get our
repeater group to to be 501c3 non-profit I just don't have the time to do it
all myself. I for one would like to get away from the IPIP encap, and get
more distributed interconnects to the internet for 44/8.
73's
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
Hi all,
It's a work in progress but the following link should provide a link
to the IP 44/8 address allocation document for NJ.
http://mrprosser.g7ltt.com
We have very little AX.25 traffic in NJ but we do have a growing Mesh
community which would benefit from this space.
Hands up if you want some!
Mark
> From: Robbie De Lise <robbie.delise(a)gmail.com>
> To: AMPRNet working group <44net(a)hamradio.ucsd.edu>
> Subject: Re: [44net] 44net problems - was: 44net cool toys
>
> We announce 44.144.0.0/16 over BGP to the public internet (in Belgium)
> This ip space is then run on our local variant of "hamwan/hamnet" in
> Belgium on 2.4ghz accesspoints and 5ghz and recently 24ghz backbone
> links.
> [....] very interesting read trimmed
Well done! Very nice! I think the best way to set up my local HamWAN is
just to get off this list and go do it your way. Others can also make up
their mind for themselves.
Steve
Hi folks,
Is there a howto available that will tell me how to work the gateways robot?
I am almost done working on the subnet breakdown for NJ (I'm the NJ co-ord)
and will be needing to make some changes in order to put the plan into
place.
I'll be looking to add hosts to the DNS, change some existing hosts and
change the master NJ subnet gateway (currently pointed at my house).
I'm not proposing anything that hasn't already been done before. I'm simply
chopping up the subnet into further subnets and allocating them to each of
the counties with the "spare" numbers then being available for clever data
experiments should there be any.
Ordinarily I'd be doing this via the portal but ......
Thanks
Mark
G7LTT/NI2O
I was wondering if the 44 ip address can be use for ham mesh 2.4 GHz
channel 1 - 6? Reason for the question is from what I understand that is
the amateur radio
frequency and it should be ok? Hey just asking.
K6DLC
--
Daniel Curry
IPV6 Sage Certified
PGP: AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92
San Francisco/Silicon Valley AmprNet Co-coordinator [44.4.0.0/16]
On 3/22/14, 6:10 PM, Neil Johnson wrote:
> - Be sure read up on BCP38 http://tools.ietf.org/html/bcp38 to
> understand why your local ISP won't (and shouldn't) let you source
> traffic from IP addresses other than theirs
It's called peering. I'm not expecting the end users who don't understand
with a /29 to get on with it.
> - Explain how you would justify and obtain stable funding to get (and
> keep) an ASN for the 44-net address space ($500 initial, $100/yr
> maintenance from ARIN). An ASN is necessary for multi-homing and BGP
> routing.
I've stated I'd donate an ASN to AMPR. Money where my mouth is, etc. AFAIK
AMPR is not 501c3 with the IRS, so this is going to hold donations back.
> - Explain to me what financial incentive a commercial ISP has to
> routing (or peering with) 44-net address space for a small number of
> customers.
It's cool, lots of groups would peer with AMPRnet. We'd have to get people to
run gateways in different places around the world. Might need to start
talking to a few more people at NANOG/xNOG's but it's like finding a good
repeater site, you have to pound the pavement and talk to people. Law of
averages we'd find a half dozen companies that would do it.
The legitimacy of a 501c3 status would go a long way to help this.
>
> - As for using VPN's, explain how to pay for and maintain the
> appropriate size server(s) to host CPU-intensive VPN (IPSec and GRE)
> end-points.
Don't know why we'd need IPSEC on the backbone, GRE would be fine. GRE is a
hardware operation in most routers (I can only speak to ALU 7x50), but really
we're not pushing 100mbit/s, so it's a moot point. A linux/bsd box can do it.
> After understanding all the nuances of 44-net, I find that the mesh
> of IP-IP tunnels and the rip44d daemon are actually quite an elegant
> solution to the limitations and constraints we have to work with.
It's a dirty hack IMO. There is no reason we can't build a virtual backbone
that would provide 44net space to end users and give the users redundant (or
better!) routes to the internet.
73's
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
Hello fellows friends, now after an extended test period and when my office
allowed me time, I could achieve put online both YV gateways "
yv5kxe.ampr.org" and "yv5sat.ampr.org"
These systems have access to VHF packet radio network YVNET 145.010 Mhz and
are currently in the capital Caracas in different locations, the systems
are under Linux Slackware (for now), to access them please send my a email
with your login and password to place you in the ftpusers.
The whole problem of the update via RIP2 was the ISP modem that blocks
multicast RIP??? although saw the RIP packets incoming on JNOS monitor
screen from UCSD amprgw. The modem with this problem is SENDTEL ADSL2 +
Router MS8-8817 which I have changed to another ADSL brand (StartBridge)
now working perfect the encapsulation and RIP update.
Other experience to share....thanks and regards
73 de Gabriel YV5KXE.
Venezuela Amprnet
On Sat, 22 Mar 2014 19:33:14 +0100, YT9TP Pedja <yt9tp(a)uzice.net>
wrote:
>On 22.3.2014 16:14, Geoff Joy wrote:
>
>> Wiki's are a collective effort, what have you done to fix the flaws
>> you see there? Have you signed on as a Wiki editor? Have you written
>> articles for inclusion on that Wiki? Links go stale, there has to be
>> an "ugly bag of mostly water" behind the keyboard to keep a document
>> tree fresh and healthy, otherwise off-site links go bad when someone
>> drops dead or an organization folds. What are you doing in YOUR spare
>> time.
>>
>> I see a whole lot of room for improvement and a whole lot of
>> networking experts who can "advance the state of the art" but who
>> don't seem to be inclined to actually publish what they know.
>>
>> What I see above from both of you is "this is a mess, someone needs to
>> clean it up, but that someone isn't going to be me". I must boldly
>> state that if you have the time to discern a problem and criticize a
>> state of affairs, you have the time to take ownership of that problem
>> and fix it.
>
>
>I think you are on wrong track.
>
You might be right.
>Don't you see the pattern. People who consider themselves knowledgeable
>about networking want to get involved in 44net but they cannot
>understand it because there is lack of proper documentation.
>
Those who understand networking would be most likely to be able to
write proper documentation for 44net since the protocols involved are
no different than any other internet. AX.25 is nothing more than a
modified X.25. The only thing that changes is the medium of
transmission and the latencies.
>If they cannot understand and ask for better documentation, so they
>cannot learn, they are the last persons that should be advised to write
>that documentation.
I perceived hams criticizing other hams for not being "friendly" to
newcomers, I have been a victim of unfriendly hams myself in the past
and went out of my way to create a new environment in response to
that. My Elmer was the father of a high school friend who took time
out at the end of his workday to mentor us in Morse code. I didn't go
on to get my license until college, however.
>
>Documentation should be written by people who do have very good
>knowledge and experience with 44net.
>
I agree. And that experience best comes with experimentation. But is
44net so different that it's a completely different environment than
hardwired networking? I learned what I know about the protocols by
installing JNOS on a PC and poking and sniffing packets on air when
Windows didn't have a TCP/IP stack. Why is the reverse so difficult?
Current Wifi technology follows directly from the original wireless
development hams pioneered. Even SSID comes from us. The original
development follows directly from the University of Hawaii's
experiments with RF networking, which was well documented. Most of
this isn't "webified", it's all plain text on the FTP site. But yes,
my generation has let the new generation down, we left a plain text
legacy where everyone wants it all on a searchable Wiki and color
pictures.
>73
>Pedja YT9TP
>
>p.s. I am posting this directly to you, besides sending it on the list
>as my message cannot go through the list - almost all my messages return
>back marked as blacklisted.
>
I'm posting my reply directly and also to the list so perhaps someone
can review the list logs and fix the rejection. Thanks for your input.
--
Geoff Joy - ke6qh -
AmprNet IP Address Coordinator for San Bernardino & Riverside Counties.
geoff(a)windomeister.com
