44net

44net@mailman.ampr.org

4 participants
3196 discussions

Re: [44net] Tunnel issues with rip44d
by Pieter Luteijn 05 Aug '13

05 Aug '13

By default rip44d is using the interface tunl0, it seems: my $tunnel_if = 'tunl0'; You seem to be using tun0 in your networking scripts, so i suppose you either need to adjust the default, use the -i option to change the interface used by rip44d, or change the tunnel interface name to match so the rip44d is listening on the right interface. Pieter. Sent from a mobile, sorry for any typoes...

8 10

rip44d problem
by Demetre SV1UY 05 Aug '13

05 Aug '13

Hi all, After running ripp44d for about I see in my routing table that my own subnet 44.154/18 is routed to 87.202.40.155 (my ADSL router's dynamic IP) via tunl0 interface. Is this right? -- 73 de SV1UY Demetre Ch. Valaris IP Coordinator for AMPRnet in Greece e-mail: demetre.sv1uy(a)gmail.com Radio e-mail: sv1uy(a)winlink.org (to use my radio e-mail put //WL2K in the beginning of the subject line) http://www.qsl.net/sv1uy

5 9

Anyone know who's using .....
by Mark Phillips 03 Aug '13

03 Aug '13

44.64.192/24 44.64.193/24 I noted that these networks were in the gateways encap list. It would be nice to know whom has them so that I can update my NJ co-ordinator records. Thanks Mark NI2O

3 2

Gateway updates
by Neil Johnson 03 Aug '13

03 Aug '13

How long does it take after updating a gateway for it to take effect ? Just curious. -Neil -- Neil Johnson -N0SFH http://erudicon.com

2 1

Re: [44net] 44Net Digest, Vol 2, Issue 107
by Rob Janssen 03 Aug '13

03 Aug '13

> Subject: > Re: [44net] IP address management > From: > Mark Phillips <g7ltt(a)g7ltt.com> > Date: > 08/02/2013 10:57 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > TeemIP > > > Me like!!!! > > Might grab this for use at work. > > Mark Indeed, this looks like what we need as a module within portal.ampr.org! And it saves a lot of work to have something like this. Rob

1 0

IP address management
by Rob Janssen 02 Aug '13

02 Aug '13

> Subject: > Re: [44net] question regarding amprgw.sysnet.ucsd.edu > From: > Brian Kantor <Brian(a)UCSD.Edu> > Date: > 08/01/2013 03:25 AM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > On Wed, Jul 31, 2013 at 06:16:32PM -0700, Blaine Forbort wrote: >> >My DNS request is still waiting for coordinator approval. I guess I'll >> >be waiting for that until I can finish off this first step of my >> >experiment. > Does that mean that you submitted it via the portal.ampr.org DNS > function? I'm sorry, that function isn't working yet. I've asked > for it to be taken off the portal menu until it*is* working as it > confuses people. It also needs to be discussed what functionality is required here for both the users and the coordinator. Sometimes I get requests for approval, and I just looked in the portal.ampr.org again, but it does not really cover the requirements. What we need is a request from a user to get one or more addresses allocated, accompanied by information like region where they live. The coordinator then must be able to look into the already assigned list of addresses and find an available address in the correct region (subnet), assign it, and return the address to the requester. As it is now, I get requests for 44.137.0.0/16 which makes little sense. Until now I have a hosts file and I make the assignment by browsing through it in the editor, and copy/pasting a line. Then I send the corresponding update to the ampraddr robot. How can we do this in the portal when we abandon the hosts files? Rob

6 6

Re: [44net] gateways sunset
by kb9mwr＠gmail.com 02 Aug '13

02 Aug '13

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 1

Re: [44net] question regarding amprgw.sysnet.ucsd.edu
by lleachii＠aol.com 02 Aug '13

02 Aug '13

Blaine, Here are some tools that may be helpful to you in the future for troubleshooting: http://kb3vwg-010.ampr.org/tools/ping/php-ping.php http://kb3vwg-010.ampr.org/tools/trace/php-trace.php http://whatismyip.ampr.org/ http://speedtest.ampr.org/ DNS: dns-mdc.ampr.org (44.60.44.3 kb3vwg-003.ampr.org) Also, I cannot ping you, but traceroue is working: traceroute to 44.4.36.1 (44.4.36.1), 30 hops max, 60 byte packets 1 kb3vwg-001.ampr.org (44.60.44.1) 0.480 ms 0.924 ms 0.889 ms 2 k1qv.ampr.org (44.4.36.1) 91.696 ms 95.844 ms 100.637 ms -Lynwood KB3VWG

3 5

Отн.: Re: ipip tunnel
by Miroslav Nikolov 02 Aug '13

02 Aug '13

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/44net http://www.ampr.org/donate.html

1 0

gateways sunset
by Brian Kantor 01 Aug '13

01 Aug '13

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

6 6

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net