44net January 2013

44net@mailman.ampr.org

25 participants
14 discussions

44.133.48.66 !!!
by Maiko Langelaar 12 Apr '14

12 Apr '14

Good afternoon, It would see that 44.133.48.66 is popping, snmpding, and other amounts of traffic from time to time to various ampr.org systems and doing so *without warning* type of thing. I just got hit with a bunch of SNMP requests, others have been hit with POP requests. Can anyone find out who the owner of that particular system or network is, so that I can contact the entity or person. Or perhaps a bit more draconian, can someone deal with it. Thanks in advance. Maiko Langelaar VE4KLM

4 5

Re: [44net] Gateways Unreachable after Dynamic IP Update
by lleachii＠aol.com 07 Apr '13

07 Apr '13

Dear Bob VE3TOK (and thanks to VE3ZDA and N2NOV), Your entry is on my route table, I'm using rip44d (not encap), so my updates are live. The IP of my gateway is correct in the Portal. I use the -a switch to remove my own route (and have updated it to the correct IP); and I still receive rip44d updates over AMPR (showing that I have not lost connectivity to the Main AMPRGW). From testing connectivity to your subnet, I have determined that my 44GW is operational; and that some gateways may not have yet updated their encap. Thanks for your help; I waited a few days to to be sure that was not the case; as I know all stations do not have dynamic routing updates, I'll wait longer next time. 73, Lynwood KB3VWG http://44.60.44.10/tools @kb3vwg-015:~$ ping 44.135.85.1 -c 10 PING 44.135.85.1 (44.135.85.1) 56(84) bytes of data. From 44.135.85.30: icmp_seq=7 Source Quench From 44.135.85.30: icmp_seq=8 Source Quench From 44.135.85.30: icmp_seq=9 Source Quench From 44.135.85.30: icmp_seq=10 Source Quench --- 44.135.85.1 ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 9003ms @kb3vwg-015:~$ traceroute 44.135.85.30 traceroute to 44.135.85.30 (44.135.85.30), 30 hops max, 60 byte packets 1 kb3vwg-001.ampr.org (44.60.44.1) 0.724 ms 0.238 ms 0.218 ms 2 linux.ve3mch.ampr.org (44.135.85.151) 51.890 ms 55.835 ms 60.720 ms 3 port.ve3mch.ampr.org (44.135.85.30) 63.642 ms 62.613 ms 66.477 ms @kb3vwg-015:~$ ping 44.135.85.30 -c 5 PING 44.135.85.30 (44.135.85.30) 56(84) bytes of data. 64 bytes from 44.135.85.30: icmp_req=1 ttl=39 time=53.9 ms 64 bytes from 44.135.85.30: icmp_req=2 ttl=39 time=51.8 ms 64 bytes from 44.135.85.30: icmp_req=3 ttl=39 time=87.4 ms 64 bytes from 44.135.85.30: icmp_req=4 ttl=39 time=52.7 ms 64 bytes from 44.135.85.30: icmp_req=5 ttl=39 time=51.9 ms --- 44.135.85.30 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 51.899/59.607/87.406/13.919 ms

5 6

ip updating
by K7ILO 02 Feb '13

02 Feb '13

Hello gang. Could an ip coordinator send me via direct email the email robot's address for adding and updating amprnet ip addresses? Thanks Harold K7ilo (formerly KB7RSI) Southern Nevada Ip Coordinator

13 25

Re: [44net] gateway file
by kb9mwr＠gmail.com 31 Jan '13

31 Jan '13

I have one from Sept 2012 if anyone wants it. I second the importance of the data in that file. It's really the only thing we had to tell what is on the amprnet, in terms of services, and the speeds of the connected radio subnets, etc. > Date: Thu, 31 Jan 2013 11:05:14 -0800 > From: Jack Eifer <jeifer(a)cwo.com> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] ip updating > > Chris, > > While we're on the subject of TODO's, > Has any consideration or thought been given to resurrecting the 'GATEWAY' file that Fuller maintained ? > > I found the information in file useful and easy to access. Perhaps the new website has the same info embedded, but somewhere I've yet to discover. > > Jack, AA6HF

2 1

reminders
by Brian Kantor 31 Jan '13

31 Jan '13

Just a reminder for everyone, especially address coordinators, to please register with the portal. https://portal.ampr.org/ And a big thank you to those thoughtful folks who have donated to keeping the organization running. If you haven't yet sent in a donation, it's as easy as clicking on the donate link at the bottom of this message or on our web page. Even $25 would be a great help. Thank you! - Brian

1 0

the next step in portal deployment
by Brian Kantor 26 Jan '13

26 Jan '13

As the next step in deployment of the AMPRNet Portal, we're going to begin using it to refer people to their coordinators. How this works is this: A ham wanting an address assignment will register with the portal and click on the NETWORKS selection. He'll be presented with a list of countries; for some countries, clicking on that entry will get him to a list of regions within the country, etc. If there isn't a coordinator registered with the portal for his particular area (or country), he'll have to pick the enclosing region. Eg, if there isn't an entry for say, Alabama, he'll pick the USA entry and I'll get the request. I can then allocate a block for Alabama (rather, I'll use the one that's already set aside for that state) and assign him an address from that block. I'll probably ask him if he'd like to become the coordinator too. (Always looking for volunteers.) Once his region is selected, he'll be presented with a simple form that asks what netwidth he wants (/32 for a single host, /24 for the typical 256 host subnet, etc), how he's planning on connecting to the greater internet, and a Notes area in which he can explain anything special about his request. This will generate an email to the coordinator registered for the subnet he clicked on above, who can request further particulars if needed. The above procedure is mentioned in the FAQ on the www.ampr.org website. What's the advantage to doing it this way? Among other things, it means that there is no longer the problem of finding the email address of a coordinator from an always-outdated list. It's less work for me to handle referrals, and the portal mechanism will ensure that there is consistent data for everyone. It's very important that every coordinator get registered with the portal for this system to work. I urge everyone on this mailing list to register, and those of you who are coordinators should contact Chris to get your registration listed as the coordinator for your region. Thank you! - Brian To replay Chris's instructions: _______________________________________________ Now is probably a good time to ask everyone that is currently using an IP or IPs from the 44/8 to register on the portal: https://portal.ampr.org Click on the "Register" link to the right of "Home" in the top menu. Fill in the details requested and hit the "Register" button, you will be sent an email with a link you need to click on to verify your email address. When you click the link the web page will ask you to enter the username you entered on the original request, click the "Confirm" button and your login details will be emailed back to you. Use the details to login to https://portal.ampr.org Your first job should be to change your password to something secure that you will remember: Click on the "Profile" menu link, to the right of "Allocations". Here you can update your details, including your login password. If you already operate a gateway, please drop me an email and I can assign it to your account. If you already have subnets allocated to you within the 44/8 please drop me an email and, as per the gateways, I can assign them to your account. If you are a country co-ordinator or a regional co-ordinator, please get in touch asap, so you can be setup on the portal to manage the allocations of your subnets. Thanks, Chris - G1FEF _________________________________________

7 10

AMPRNet Logo
by Chris Smith 25 Jan '13

25 Jan '13

A plea to all you graphic design artists out there... It would be good if we could come up with a logo to use across the main ampr.org website, the portal, the wiki, etc. I've attached one I did and one derived from one that Jim Fullers had on his site when it was active. Food for thought, but if anyone can come up with a really cool logo that we all like... Thanks, Chris

1 0

Re: [44net] Gateways Unreachable after Dynamic IP Update
by lleachii＠aol.com 24 Jan '13

24 Jan '13

Don and Marius, I can reach you both, with no issues. From those who have offered their Subnet information: - I can reach all 3 of you (Don, Bob and Marius) [from 44.60.44.0/24 to you] therefore, encapsulation must be working at all stations, and our routes are up-to-date - Don 44.135.90.0/24 is unable to reach me or Bob - Marius 44.182.21.0/24 can reach Bob; he cannot reach me Don and Marius, defnately keep us up-to-date about why you cannot ping me. What Network OS are you using for AMPRnet (*nix/rip44, JNOS, TNOS)? ~Lynwood

11 33

Re: [44net] 44Net Digest, Vol 2, Issue 8
by kb9mwr＠gmail.com 20 Jan '13

20 Jan '13

I have noticed there is something with 44 addresses and Windows too. I have never been able to ping a 44 address from Windows, while they work proper from a Linux terminal. All pings to 44 address from Windows result in "Destination host unreachable" (even 44.0.0.1) It's no big deal for me, but have never really figured out why this is. > Date: Sun, 20 Jan 2013 00:34:06 +0200 > From: "Marius Petrescu" <marius(a)yo2loj.ro> > To: <n2nov(a)n2nov.net>, "'AMPRNet working group'" > <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] Gateways Unreachable after Dynamic IP Update > > Hi, > > I'm running debian 6, updates via RIP. Working from a windows PC behind the > server acting as router. > > Check the route your response packets take on their way out. > If you initiate the ping you get the response correctly back due to > connection tracking mechanisms. > This doesn't mean that responses to icmp requests necessarely do the same. > E.g. responses may go via a default gateway which is not correct. > Make sure your answers go out on the same interface they came in. > > sooo... > > Pinging 44.2.10.1 with 32 bytes of data: > Reply from 44.2.10.1: bytes=32 time=226ms TTL=222 > > Pinging 44.68.41.1 with 32 bytes of data: > Reply from 44.68.41.1: bytes=32 time=160ms TTL=28 > > But then... > > C:\Users\Marius>ping 44.60.44.1 > > Pinging 44.60.44.1 with 32 bytes of data: > Request timed out. > Request timed out. > Request timed out. > Request timed out. > > Ping statistics for 44.60.44.1: > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), > > 73's > Marius, yo2loj

2 1

Gateways Unreachable after Dynamic IP Update
by lleachii＠aol.com 18 Jan '13

18 Jan '13

All, I'm experiencing a technical issue that began when my dynamic WAN address obtained a new lease. I am no longer able to communicate with other 44 subnets after my WAN obtained a new IP address. My gateway is saved in the Portal with a dynamic domain name, and the IP is correctly displayed on the portal.ampr.org website. In addition, I have also updated my IP under the rip44d -a parameter. I am still able to receive the RIP44 announcements from 44.0.0.1 and communicate with the Internet via the tunnel thru AMPRGW; but I am no longer able to reach other AMPR networks. My WAN IP changed on 11JAN2013. Please feel free to perform any of the following, or let me know if I am reachable via AMPR: Ping/traceroute Router 44.60.44.1 Ping and DNS 44.60.44.3 Ping and HTTP at 44.60.44.10, 44.60.44.11 and 44.60.44.12 Regards, Lynwood KB3VWG 44.60.44.0/24

4 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net January 2013