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.
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
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
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
> - 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
> 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
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
