44net January 2016

44net@mailman.ampr.org

62 participants
47 discussions

Re: [44net] was Verifying the identities of IP coordinators
by Steve L 02 Feb '17

02 Feb '17

First I wanted to mention I am glad to read Bjorn's message about adding some content to the network. Keeping in contact is key. Be that a coordinator or any host on the amprnet. Seems every few months on here we are discussing how someone is sending out random packets, and a straight forward way to get a hold of people would be helpful. Some time back it was brought up to have a whois server or something like that. I bet I can guess the status of that. As for everyone having an ampr.org email address, perhaps a forwarding service like the arrl.net addresses? Then there is the possible spam problem, and the fact that someone would need to set up such a service. Overall a lot of good ideas are brought up on this list, so few ever happen. The only solution I am offering is everyone should help spread the word and try and get more people involved with moving this network forward. I wish I had better coding skills. One of the core problems at least in my country where the ampr/44net space is not well utilized is the lack of higher speed equipment to build a network. You really have to be part of a well organized club with site connections to do anything microwave on any big scale from what I have seen.

7 7

rip down ?
by Maiko Langelaar 17 Sep '16

17 Sep '16

Did we loose the rip broadcast ? Maiko

5 5

NTP Server Test
by lleachii＠aol.com 05 Feb '16

05 Feb '16

All, I have an NTP Server online at kb3vwg-001.ampr.org. Let me know if it's reachable from your hosts. This is currently in testing (the domain may move perhaps to tick.ampr.org.). 73, KB3VWG

9 10

Re: [44net] NTP Server Test
by lleachii＠aol.com 01 Feb '16

01 Feb '16

All, - Time - NTP UDP/123 - This is odd, I'm able to reach the server and 44.60.44.1 from AMPR and the Public Internet (what exactly are you trying to 'reach' at 44.60.44.1 to determine its status, as I've only announced NTP as being available there) - using 'ntpdate -q 44.60.44.1' or 'ntpdate -q kb3vwg-001.ampr.org' works for me anywhere on the Internet kb3vwg@kb3vwg:~$ ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 2, offset 0.001173, delay 0.02589 30 Jan 18:00:19 ntpdate[1058]: adjust time server 44.60.44.1 offset 0.001173 sec - I have now permitted access from the Public Internet (previously, it was only available to 44 hosts), let me know - Lynwood KB3VWG

7 11

Just received allocation... next steps?
by Stephen - K1LNX 01 Feb '16

01 Feb '16

Hi guys, I just received an allocation for 44.34.96.0/24 to begin experimenting with. I plan on doing mesh networking as well as offering services as time permits. I have two questions regarding connectivity to the network: - I understand most folks are doing IPIP tunneling, has anyone ever done this on a Ubiquiti Edgerouter Lite or VyOS? Anyone in or near Tennessee that can accomodate a tunnel for me? - BGP... thinking entirely out loud here, but are there any VPS providers anyone is aware of that will accept announcements from 44 net that I could handle with say BIRD or another BGP daemon under linux? This would be my ideal setup and I could tunnel my own connectivity, but not sure this is possible.. looking for ideas here. 73, and glad to be a part of AMPR, I love networking :) Stephen K1LNX

4 4

Re: [44net] NTP Server Test
by Rob Janssen 31 Jan '16

31 Jan '16

> - This is odd, I'm able to reach the server and 44.60.44.1 from AMPR and the Public Internet > (what exactly are you trying to 'reach' at 44.60.44.1 to determine its status, as I've only announced NTP as being available there) > > - using 'ntpdate -q 44.60.44.1' or 'ntpdate -q kb3vwg-001.ampr.org' works for me anywhere on the Internet Maybe you are suffering the problem with some types of cable router that I noticed when trying to reach another US amprnet station. Those routers claim to support a DMZ mode and you set the IPIP tunnel server as the DMZ host, but in reality they do not forward new incoming IPIP packets to the DMZ host, they only forward "replies" to outgoing IPIP tunnel packets just like they do for normal NAT traffic. So, you configure your IPIP tunnel host, you test connectivity with other systems by pinging or telnet or whatever, and all appears to be fine. However, when anyone else attempts to connect to you from the outside, your system is just unreachable. When you do a ping to one of them and they try to reach you, it works OK. But when there is no traffic for a few minutes, the gate closes again and you are unreachable. The DMZ feature probably only works for TCP and UDP. For IPIP, you are just relying on the standard NAT feature which of course is causing the problem described above. Rob

1 0

Re: [44net] NTP Server Test
by Rob Janssen 30 Jan '16

30 Jan '16

> Subject: > [44net] NTP Server Test > From: > lleachii(a)aol.com > Date: > 01/30/2016 09:13 AM > > To: > 44net(a)hamradio.ucsd.edu > > > All, > > I have an NTP Server online at kb3vwg-001.ampr.org. Let me know if it's reachable from your hosts. This is currently in testing (the domain may move perhaps to tick.ampr.org.). > > > 73, > > > KB3VWG > Like the others, I cannot reach your server. However, when people want to have an NTP server from AMPRnet, we are running one on our gateway in Amsterdam at 44.137.0.1 It is referenced off 8 stratum-1 GPS-locked servers that are part of our co-channel diversity FM repeater network. remote refid st t when poll reach delay offset jitter ============================================================================== *44.137.8.140 .PPS. 1 u 414 1024 377 4.918 -0.052 0.079 -44.137.41.97 .PPS. 1 u 689 1024 377 13.387 -1.770 0.104 +44.137.72.10 44.137.72.16 2 u 490 1024 377 8.022 0.037 0.045 -44.137.72.16 .PPS. 1 u 842 1024 377 7.952 0.036 0.077 -44.137.72.130 .PPS. 1 u 123 1024 377 8.604 -0.122 0.036 +44.137.72.131 .PPS. 1 u 489 1024 377 8.756 -0.135 0.055 -44.137.73.3 .PPS. 1 u 993 1024 377 13.443 0.128 0.022 -44.137.73.4 .PPS. 1 u 674 1024 377 13.358 0.158 0.064 -44.137.73.50 .PPS. 1 u 158 1024 377 18.075 0.249 0.173 Only (S)NTP. So no Time/TCP, Time/UDP or other time protocols. Rob

2 1

Might be of interest
by Steve L 30 Jan '16

30 Jan '16

If anyone has some new ideas for 44net, then this cloud server offer (One time free) might be of interest. http://www.cloudatcost.com/

1 0

Nevada IP Assignments
by Harold (K7ILO) 22 Jan '16

22 Jan '16

Hello all. I am the ip coordinator for the State of Nevada and responsible for 44.125.0.0/16 I decided to take a look at amprhost file and found many entries that I did not issue and not sure if these were added before I volunteered to handle the region or people have taken upon themselves to create these entries. This includes one that I recently assigned to someone who is actively using his assignment I would like to know if these are in use so that the amprhost file can be update by me getting rid of them if possible. Thanks Harold K7ILO Nevada IP Coordinator 44.125.10.1 kj6ix.ampr.org kj6ix (Just assigned via portal) 44.125.10.1 kmev.ampr.org kmev 44.125.128.1 ke7kd.ampr.org ke7kd 44.125.128.2 kb7llk.ampr.org kb7llk 44.125.128.5 n7ktl.ampr.org n7ktl 44.125.128.6 n7msd.ampr.org n7msd 44.125.128.8 wa1wsx.ampr.org wa1wsx 44.125.128.9 n7rad.ampr.org n7rad 44.125.128.11 w7kju.ampr.org w7kju 44.125.128.13 nr7a.ampr.org nr7a 44.125.128.14 n6whz.ampr.org n6whz 44.125.128.15 kd4iee.ampr.org kd4iee 44.125.128.17 ki7sy.ampr.org ki7sy 44.125.128.18 nt7e.ampr.org nt7e 44.125.128.20 kj7ca.ampr.org kj7ca 44.125.128.128 prg3.router.ampr.org prg3.router 44.125.128.129 dx9600.router.ampr.org dx9600.router 44.125.128.131 hamgate.n8khn.ampr.org hamgate.n8khn 44.125.129.1 wa6ewv.ampr.org wa6ewv 44.125.129.2 kb7pjb.ampr.org kb7pjb 44.125.129.3 wa4ist.nv.ampr.org wa4ist.nv 44.125.129.4 wi7c.ampr.org wi7c 44.125.129.5 kd6ulm.ampr.org kd6ulm 44.125.129.6 kb7mty.ampr.org kb7mty 44.125.129.7 nx6w.ampr.org nx6w 44.125.129.8 kf7go.ampr.org kf7go 44.125.129.32 kb6imj.ampr.org kb6imj 44.125.129.34 kd6mve.ampr.org kd6mve 44.125.129.64 n7vxb.ampr.org n7vxb 44.125.129.103 n8khn.ampr.org n8khn 44.125.129.105 hamgate2.n8khn.ampr.org hamgate2.n8khn 44.125.130.2 n0zte.ampr.org n0zte 44.125.131.2 kb7qbs.ampr.org kb7qbs 44.125.131.3 n7xbm.ampr.org n7xbm 44.125.132.1 kb7eiu.ampr.org kb7eiu 44.125.132.2 n7vle.ampr.org n7vle 44.125.132.3 ke6icy.ampr.org ke6icy 44.125.132.5 nf7v.ampr.org nf7v 44.125.132.6 kb7pux.ampr.org kb7pux 44.125.132.7 w6old.ampr.org w6old 44.125.132.9 kb7pdf.ampr.org kb7pdf 44.125.132.12 ww7e.ampr.org ww7e 44.125.132.13 wb6w.ampr.org wb6w 44.125.132.34 n7npb.ampr.org n7npb 44.125.132.35 kb7no.ampr.org kb7no 44.125.132.36 kb7pde.ampr.org kb7pde 44.125.132.37 n7zfc.ampr.org n7zfc 44.125.132.38 wt8k.ampr.org wt8k 44.125.132.64 kc6rho.ampr.org kc6rho 44.125.132.67 kc7cex.ampr.org kc7cex 44.125.132.68 kc7cey.ampr.org kc7cey

16 37

*.ampr.net mappings
by Jim MacKenzie 21 Jan '16

21 Jan '16

Hi, I've got a subnet (44.135.130.0/23) and with the help of Brian in San Diego (thank you!), I got reverse DNS delegated to me (the subnet is routed via BGP). I got ve5eis.ca and mapped a couple of names in that domain to the IPs that are in service. Should I have a CNAME or some other alias in ampr.net also? Is this desirable practice or just what most people do? I'm pretty Linux- and Internet-savvy so so far I've just been doing my own thing. Thanks, Jim VE5EIS/VA5EIS/VE0EIS

3 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net January 2016