44net

44net@mailman.ampr.org

3191 discussions

by Demetre SV1UY

Hi, Any news about support for Dynamic IP Gateways yet without having to pester other Gateways having static IPs via AXUDP links? -- 73 de SV1UY Demetre Ch. Valaris e-mail: demetre.sv1uy(a)gmail.com Radio e-mail: sv1uy(a)winlink.org http://www.qsl.net/sv1uy

13 years, 2 months

ip updating

by K7ILO

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 years, 2 months

AMPRNET Donations

by Paul Delaney - K6HR

Exactly how will any donated funds be used, accounted for etc? Paul Delaney - K6HR paul.hamradio(a)verizon.net http://k6hr.dyndns.org:8080

13 years, 2 months

Re: [44net] gateway file

by kb9mwr＠gmail.com

What you have for a network over there makes me jealous. I guess I'd like to know what in terms of content is on the amprnet. I know there are some AXIP BBS style feeds and that sort of thing. Is anyone running a mailman mailing list of anything interesting? For higher speed radio connections are there any SIP/Asterisk conference servers, or at least FTP repositories of ham stuff? Stuff that is exclusive to the network. I have some point to point 802.11 links over here that I have been using 44 addresses on for a few years. But they haven't been connected to the rest of the amprnet. Is there a compelling reason to setup a gateway to the rest of the amprnet. 73' Steve ----Original--- Btw: We are currently deploying our IP management system for the HAMNET network: http://hamnetdb.net/?m=as&q=&as=-All-&tab=map You should be able to do a traceroute to all "green" sites... Click on a site and you get the description. 73, Jann DG8NGN On 31.01.2013 21:09, kb9mwr at gmail.com wrote: > 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.

13 years, 2 months

Re: [44net] gateway file

by kb9mwr＠gmail.com

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

13 years, 2 months

reminders

by Brian Kantor

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

13 years, 2 months

the next step in portal deployment

by Brian Kantor

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 _________________________________________

13 years, 2 months

AMPRNet Logo

by Chris Smith

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

13 years, 2 months

Re: [44net] Gateways Unreachable after Dynamic IP Update

by lleachii＠aol.com

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

13 years, 2 months

Re: [44net] 44Net Digest, Vol 2, Issue 8

by kb9mwr＠gmail.com

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

13 years, 2 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net