Neil,
Can you share these scripts or the links to what you used as a base.
I can see myself doing this once the DNS part of the portal is functional.
Steve, KB9MWR
WI/Upper MI Coordinator
---- Quote ----
Having just volunteered as a coordinator for the state of Iowa (44.50.0.0/16).
I went through the amprhost file and:
- Pulled out all the IP address entries for the state.
- Manually pulled out the call signs from the host names.
- Modified a python script I found on github ( called qrz.py) to get as
many email addresses as I could from qrz.com,
- Used another python script to send a nicely formatted e-mail to each
user asking them to register their IP on the portal or tell me if they no
longer needed it. Stated in the e-mail that if I didn't hear from them in
90 days. I would reclaim their allocation.
- The plan is to send a reminder email at 60, 30, and 7 days.
I'm not sure what I will do with those call signs that don't have e-mails
associated with them (56 out of 175). Possibly send a post card ?
Of the 119 e-mails I sent, I've received 27 responses so far. 20 saying I
can reclaim their allocation, and 7 requests through the portal.
The previous volunteer did a wonderful job of dividing up the state into
regions, sub-regions, and cities, but assumed there would be only one
gateway per city. I'll have to understand the existing network topology
and see if I can fit them into new subnet boundaries.
-Neil
2 hurs after my message all to this ip group is Ok.
73, LZ4NY
Изпратено от Samsung Mobilelleachii(a)aol.com написа:(Please trim inclusions from previous messages)
_______________________________________________
Miro LZ4NY,
No problems on my side; is your AMPR firewall blocking ICMP - Echo Reply?
> ip route get 44.185.1.1
44.185.1.1 via 109.107.73.62 dev tunl0 src 172.31.255.254
traceroute to 44.185.1.1 (44.185.1.1), 30 hops max, 60 byte packets
1 kb3vwg-001.ampr.org (44.60.44.1) 0.380 ms 0.202 ms 0.108 ms
2 lz4ny.ampr.org (44.185.1.1) 128.304 ms 132.677 ms 137.805 ms
PING 44.185.1.1 (44.185.1.1) 56(84) bytes of data.
64 bytes from 44.185.1.1: icmp_req=1 ttl=63 time=130 ms
64 bytes from 44.185.1.1: icmp_req=2 ttl=63 time=128 ms
64 bytes from 44.185.1.1: icmp_req=3 ttl=63 time=131 ms
64 bytes from 44.185.1.1: icmp_req=4 ttl=63 time=133 ms
--- 44.185.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 128.803/130.923/133.714/1.804 ms
-Lynwood
KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44nethttp://www.ampr.org/donate.html
As many of you know, when we set up the portal and moved the gateways
maintenance to it, we imported the legacy gateways file which included
a significant number of dormant or abandoned gateway entries.
Since then we've requested that people operating gateways "take
possession" of them by registering their active gateways.
I believe the time has come to flush all the gateway entries which have
not been registered -- clearly by now if they're not registered they
must be abandoned.
So I propose that we use the month of August to get the last of the
active gateways registered with the portal, and after the last day of
the month we remove all unregistered gateways from the gateways files.
What will remain are the gateways that are still active and being operated
by somebody. This should make the tunnels routing table a bit smaller.
Comments?
- Brian
Hi,
Who is problem ?
If ping (or open) to whatismyip.ampr.org (44.60.44.12) direct from internet
all is ok , if ping via IPIP (RIP44d update) tunnel from 44.185.1.1 is not
ping.
To Germany - ampr or Romania -ampr network proble is not.
73, Miro LZ4NY
-------------------------------------
Завладей лятото със СуперХостинг.БГ!
Само сега 50 GB пространство и неограничен трафик за 6,25 лв. на месец!
http://www.superhosting.bg/SummerPromo2013/?utm_source=Mail.BG&utm_medium=S…
> Subject:
> [44net] gateways sunset
> From:
> Brian Kantor <Brian(a)UCSD.Edu>
> Date:
> 08/01/2013 03:54 AM
>
> To:
> 44net(a)hamradio.ucsd.edu
>
>
> As many of you know, when we set up the portal and moved the gateways
> maintenance to it, we imported the legacy gateways file which included
> a significant number of dormant or abandoned gateway entries.
>
> Since then we've requested that people operating gateways "take
> possession" of them by registering their active gateways.
>
> I believe the time has come to flush all the gateway entries which have
> not been registered -- clearly by now if they're not registered they
> must be abandoned.
>
> So I propose that we use the month of August to get the last of the
> active gateways registered with the portal, and after the last day of
> the month we remove all unregistered gateways from the gateways files.
> What will remain are the gateways that are still active and being operated
> by somebody. This should make the tunnels routing table a bit smaller.
Would it be possible to add the gateway status (actively registered or only imported)
somehow in the gateway list? And maybe to list gateways with a subnet within the
assigned address range for a coordinator?
If so, I could try to contact the gateway operators in my range to get them to register
or abandon their gateway entry.
Rob
Hi all,
I've just set up my net44 gateway using a Debian machine running in the
cloud with a static IP. My plan is to use this machine as an
IPIP-to-OpenVPN adapter so that I can run my subnet from home via my LTE
connection, with will not support IPIP. I set up the machine with Debian
linux and rip44d.
I'm currently receiving the routing table from 44.0.0.1, and I'm able to
ping several net44 machines in my area (44.4.2.153 and 44.4.50.1 for
example), however, my linux machine is not able to ping 44.0.0.1. At first
I assumed that this was a security policy, however, I'm also not able to
access the ampr.org website from that machine now. in addition, I'm unable
to ping my machine's net44 address from the internet.
Is this a result of gw.ampr.org not updating it's gateway list, and thus
not knowing how to route to me, or have I missed something obvious?
Also, if anyone with a properly maintained gateway list could ping me
at 44.4.36.1
and let me know the result, I'd appreciate it.
Thank you,
Blaine
--
Blaine Forbort, K1QV
Vallejo California
I am okay with that.
When or is someone working on cleaning the DNS up next?
Someone mentioned the idea of sorting hosts that are theoretically
reachable via a tunnel. Then possibly purging ones that are not, or
at least further review of these.
I gave it a quick try before, as it seemed simple enough. Look at the encap.txt
file, look for hosts in each CIDR... (checking this file:
ftp://hamradio.ucsd.edu/pub/amprhosts.)
A quick google search yielded this nifty function that is the magic to
the whole thing
http://stackoverflow.com/questions/594112/matching-an-ip-to-a-cidr-mask-in-…http://pastebin.com/rbFuTeVi
It's not quite working, maybe someone who knows more can fix it?
If no one else is working on this, and it would seem helpful, please
let me know, and I'll try and devote some time to it again.
Steve, KB9MWR
