44net

44net@mailman.ampr.org

2 participants
3205 discussions

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

AMPRNet Wiki
by Chris Smith 16 Jan '13

16 Jan '13

Hi Folks, A new Wiki was setup a little while ago: http://wiki.ampr.org Unfortunately it got vandalised and there were only a couple of minor contributions. I've reset it, this time with restricted edit rights. If you wish to contribute ( and the hope is that many will ), please drop me an email and I will set you up a login. All I need is your preferred username and email address, I will assign a random password and email it back to you. Thanks, Chris - G1FEF

1 0

Zconvers Map
by Kutche, Jerry (Mitchell) USA 11 Jan '13

11 Jan '13

I was lost and now I am found! 73 Thanks everyone for the help.. And push to try again.. Jerry Kutche Electrical Supervisor Lehigh Cement Company LLC 180 N. Meridian Road Mitchell, IN 47446 Phone: (812) 849-2191 ext. 251 Fax: (812) 849-5007 Cell: (812) 583-0445 jkutche(a)lehighcement.com<mailto:jkutche@lehighcement.com> www.lehighcement.com<file:///C:\Documents%20and%20Settings\kmundy\Application%20Data\Microsoft\S…> This e-mail may contain confidential and/or legally privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

1 0

WWconvers Node Registry
by Charles Hargrove 10 Jan '13

10 Jan '13

The sysops of the following WWconvers nodes need to contact SP1LOP, by registering at http://www.wwconvers.ampr.org/wwcbook/addwwc.html, with station details to be accurately placed on the map at http://www.wwconvers.ampr.org (or else your station will be lost at sea in the South Pacific). :-) BWATER_NS LAXNET_US N9LYA WARDCOVE2 -- Charles J. Hargrove - N2NOV NYC ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Net Mon. @ 8:30PM 147.360/107.2 PL http://www.nyc-arecs.org and http://www.nyc-skywarn.org NYDXA SWL & Scanner Net Wed. @ 9PM 147.360/107.2 PL http://www.n2nov.net "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan

5 5

[cisarnet.ampr.org] - Filtering OSPF Hellos from CisarNet solved
by renzorossi＠libero.it 01 Jan '13

01 Jan '13

Ciao Don, we are tuning CisarNet for managing directly delegated CIDR 44.208/16...So I missconfigured our main gateway.. Now it should be OK. Please let us know. Sorry ;-) Ciao from Italy. IW0SAB Renzo. >----Messaggio originale---- >Da: ve3zda(a)gmail.com >Data: 31/12/2012 17.51 >A: <44net(a)hamradio.ucsd.edu> >Ogg: [44net] (no subject) > >(Please trim inclusions from previous messages) >_______________________________________________ >Whoever owns station iq0rf.cisarnet.ampr.org. please top transmitting >to ve3zda.ampr.org. >It's been repeatedly sending encapped lines since yesterday and getting >nowhere of course.... > >here's an example of the line I'm getting...ever second or two..... > >16:37:34.478957 IP 94.101.48.134 > 192.168.1.150: IP 44.208.0.1 > >224.0.0.5: OSPFv2, Hello, length: 56 (ipip-proto-4) > >73, Don - ve3zda >_________________________________________ >44Net mailing list >44Net(a)hamradio.ucsd.edu >http://hamradio.ucsd.edu/mailman/listinfo/44net >

1 0

(no subject)
by Don Moore 31 Dec '12

31 Dec '12

Whoever owns station iq0rf.cisarnet.ampr.org. please top transmitting to ve3zda.ampr.org. It's been repeatedly sending encapped lines since yesterday and getting nowhere of course.... here's an example of the line I'm getting...ever second or two..... 16:37:34.478957 IP 94.101.48.134 > 192.168.1.150: IP 44.208.0.1 > 224.0.0.5: OSPFv2, Hello, length: 56 (ipip-proto-4) 73, Don - ve3zda

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net