44net March 2016

44net@mailman.ampr.org

52 participants
87 discussions

Re: [44net] was Verifying the identities of IP coordinators
by Steve L 02 Feb '17

02 Feb '17

First I wanted to mention I am glad to read Bjorn's message about adding some content to the network. Keeping in contact is key. Be that a coordinator or any host on the amprnet. Seems every few months on here we are discussing how someone is sending out random packets, and a straight forward way to get a hold of people would be helpful. Some time back it was brought up to have a whois server or something like that. I bet I can guess the status of that. As for everyone having an ampr.org email address, perhaps a forwarding service like the arrl.net addresses? Then there is the possible spam problem, and the fact that someone would need to set up such a service. Overall a lot of good ideas are brought up on this list, so few ever happen. The only solution I am offering is everyone should help spread the word and try and get more people involved with moving this network forward. I wish I had better coding skills. One of the core problems at least in my country where the ampr/44net space is not well utilized is the lack of higher speed equipment to build a network. You really have to be part of a well organized club with site connections to do anything microwave on any big scale from what I have seen.

7 7

rip down ?
by Maiko Langelaar 17 Sep '16

17 Sep '16

Did we loose the rip broadcast ? Maiko

5 5

Suspend routing
by Assi Friedman 29 Mar '16

29 Mar '16

Is there a simple way to suspend routing from mirrorshades to my segments? Without putting an invalid IP (BAD), or canceling the allocation, I don't see a simple option. I am currently doing a network upgrade and will looe AMPRNet support for a while. Obviously, I can just leave it as is and the host machines will just ignore the traffic. Thanks, Assi

2 1

Re: [44net] IP assignment history
by Rob Janssen 29 Mar '16

29 Mar '16

> I don't think git or subversion existed back then According to Wikipedia, SCCS was developed in 1972 and RCS in 1982. However, in those days most of us could not afford a Unix machine. It was only end 1992 when I built a system running Linux and all of this became much easier. I became coordinator in 1996, and my predecessor PA0GRI had used Unix at home much earlier than me. (I think he had a Unix system on packet radio in 1988 or so) He developed the scripts used to send update mails to the robot, which I continue to use. These just save a copy of the mails sent to the robot. That is about 5MB now. Does not seem much, but there have been times this was most of the harddisk capacity of a computer... :-) Rob

1 0

IP assignment history
by Bill Vodall 29 Mar '16

29 Mar '16

Is there any history maintained of the address assignments? I've been thinking it would be interesting if I could pick up the date of my first use back around 1990 in Colorado. 73 Bill, WA7NWP

4 5

Testers/Consideration/Inquiry - Coordinating the Private AS Numbers
by lleachii＠aol.com 27 Mar '16

27 Mar '16

All, ASNs 64,512 to 65,534 of the original 16-bit AS range, and 4,200,000,000 to 4,294,967,294 of the 32-bit range are commonly used amongst persons on the same network to coordinate routing, etc. While, it's not yet feasible, there is much research into technologies (e.g. space elevators), willingness of sponsors for satellites/availability/etc., and availability of machines, embedded devices, network cards, etc. tinkering into consumer-grade hardware capable of multi homing and routing. Also, lets recall, some of our operators have access to carrier-grade devices as well. Considerations: - those on BGP'd islands of the Public Internet (announcing their allocations with LOAs/Public ASNs,etc.) would still be so (this is no different than stations with allocations that use their allocations in a manner that would not route back to AMPR anyway), they must be considered as those taking allocations to use without AMPR connection, but there are more options for current and future connectivity with BGP - RIP44 can still remain in use. In addition, there are multiple methods to remove your own routes and those of others. You simply remove the route of those you peer with, change metrics, etc. - My router (and, I would assume those of many others that have been flashed, etc.) are capable of forwarding packets, regardless of source/destination IP. We could test the possibility of switching from a star (reliance on AMPRGW's 100% uptime for 'real-time' route updates) to a mesh, where we peer with those who choose, have a large connection, are physically interconnected to one another, etc. - (in the future) anyone, including those on the Public Internet, could volunteer to announce more specific routes for IPIP allocations (with the proper authorization requested by the allocation holder) and then maintain a tunnel, RF link, etc. - could connect to someone who could provide the AMPRGW. - there is a movement in many areas to establish HSMM in many regions of the world, but there have been many hindrances to their ability to a.) interconnect beyond their island-of-connectivity and 2.) not rely on the same factor/conditions that could cause a loss of commodity Internet connectivity in order to reach other subnets - in these considerations, AMPRNet's 100% reliance on AMPRGW and not devising methods not to rely on the commodity Internet for Islands of interconnectivity could cause issues in a real emergency scenario Goal: - to attempt to alleviate load/reliance on AMPRGW - provide redundancy - test the possibility to geographical alternatives to AMPRGW - consider test the need of issuance of private ASN space for these purposes TEST: I'm looking for anyone currently using IPIP only that's GEOGRAPHICALLY CLOSER (I am connected to the Internet through Verizon via Ashburn/Wash.DC) to me than AMPRGR, AND/OR a BGP's station willing to coordinate establishment of a point-to-point VPN tunnel, over which we will announce our own allocations and/or those in the AMPR test subnet. I am willing to assist with documentation, graphing etc. To-do: - Establish sessions - setup test hosts - test multihoming, availability, etc. - test route prioritization, etc. - lastly, test (with permission) loss of a stations default route via tunl0 and using the other session - test with stations who may be located physically nearby (fiber, RF, etc.) ***Please let me know your thoughts, opinions, etc.*** 73, - Lynwood KB3VWG

6 29

Re: [44net] IP assignment history
by Rob Janssen 27 Mar '16

27 Mar '16

> Subject: > Re: [44net] IP assignment history > From: > Jay Nugent <jjn(a)nuge.com> > Date: > 03/27/2016 08:49 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > Greetings, > I have ALL of my IP Address/Hostname requests (with all contact information for those end users) going back to at least March of 1998 and probably even YEARS further back than that (saved on a different hard disk), from when I was the AMPRnet IP > Address Coordinator for 44.102/16 in the state of Michigan. > > I also have a copy of each and every ENCAP.TXT file saved from the 1st of the every month, also going back to at least March 1998 and probably for years further back that that. > > Doesn't *EVERY* IP Coordinator have good archival records of their activities, and that of their 'customers' for which they serve? Just poking a little fun here... :) I have copies of the mails sent to the DNS robot since January 1994 and also copies of most of the requests received from the users. Unfortunately I have not kept an easily accessible list of contact information. It would be possible to construct it from the request mails, but it would be a lot of work. I'm a bit surprised that the processed robot mails are not saved, but maybe now they are... (disk space has become much cheaper than it was back then) Rob

2 1

can there routers do IPIP ?
by R P 26 Mar '16

26 Mar '16

Hi there I have finally found some shops that sell here MiKroTik Routers May anyone of you tell me if the two models listed here will do IPIP (Gateway) ? by default ? (without need to do custom software flash (as WRT) http://routerboard.com/RB750GL [http://img.routerboard.com/mimg/673_m.png]<http://routerboard.com/RB750GL> RouterBoard.com : RB750GL<http://routerboard.com/RB750GL> routerboard.com RouterBoard RB750GL description. The RB750GL is a small SOHO router in a white plastic case. It has five independent Gigabit Ethernet ports and optional switch chip ... http://www.routerboard.co.il/Product/hap-lite [http://www.routerboard.co.il/sites/3102/images/itempics/133463_large.jpg]<http://www.routerboard.co.il/Product/hap-lite> RouterBoard Israel??? ?????? ?????? MikroTik hAP lite ...<http://www.routerboard.co.il/Product/hap-lite> www.routerboard.co.il The home Access Point lite (hAP lite) is an ideal little device for your apartment, house or office. It supports button triggered WPS, for the convenience of not ... Thanks Forward Ronen - 4Z4ZQ http://www.ronen.org

2 1

Re: [44net] Testers/Consideration/Inquiry - Coordinating the Private AS Numbers
by Rob Janssen 26 Mar '16

26 Mar '16

> I tend to agree that currently when i now go to any Israeli commercial site from the 44 net ip the packet travel to UCSD and then back to UCSD and by tunnel to me again and this is a long trip > If there was a mechanism to allow the traffic to go to any local 44 gateway and then the packet will go to the local Internet the trip would be much shorter > but i dont know how it can be done these days that every IPS block Source 44 Net address from passing through > as for 44 net to 44 net trafic it look ok because it tunnel direct to the gateway and not passing through AMPRGW > the only thing I can think off is to put a secondary portal for redundancy . > Ronen - 4Z4ZQ To solve this you need to talk to people at an ISP who want to announce the 44.138.0.0/16 block on internet on their routers just like they do for the address block you use at home, then forward the traffic on that block to your internet router. Similarly you forward the outgoing traffic to internet via their router. When you have found an ISP who would be prepared to do that, at a cost you can afford, then you write a letter to Brian asking for permission to do that and then you tell them to set it all up. (NOT BEFORE YOU HAVE THE PERMISSION FROM Brian!) Your own router then receives all traffic for that address block directly from internet and you can route parts of it to others via radio, VPN, or whatever you like. Please note you will have a constant traffic of several Mbit/s from only the bad guys that are portscanning and the reflection from the bad guys using your addresses as spoofed source address, and this is increasing all the time. So don't do this from your home, put your router in a datacenter where you have 100 Mbit/s or more. We have done this here for the 44.137.0.0/16 network and there are other places where this is done. I can ping google from a 44-address and have reply times under 10ms. This also enables us to run repeaters with echolink, DMR, D-Star etc etc on 44-net addresses. Rob

1 0

Re: [44net] RIP44... v 2???
by Rob Janssen 26 Mar '16

26 Mar '16

> Perhaps consider ways that RIP44 could be updated: > - to bootstrap one another in the case of a failure of AMPRGW (election > of a master to send RIP44 announcements, participation in elections > disabled by default) > - allow possibility for addition of routes while 'acting AMPRGW' is > offline (re-elections with time-stamping/flagging)? > - ability to resume normal operations (AMPRGW is automatically > elected/flagged/timestamps-recognized as master/signals send end of > elections) > Ideas? This is all completely unnecessary. The only thing you need to do to have redundancy in the RIP announcements is setup another RIP announcer that gets the same database information and sends the same announcements. Currently they are sent at 5 minute intervals, an efficient solution would be to modify the existing announce to use 10 minute intervals and setup a second one to use 10 minute intervals with a 5 minute offset from the first. When both are up, the users see no change. When one is down, the update interval halves but everything remains running. Rob

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net March 2016