44net May 2022

44net@mailman.ampr.org

26 participants
11 discussions

by Rosy Schechter - KJ7RYV

Hello 44Net Mailing List, There has been a lot of discussion on this list about the state of 44Net. Some people like how it works, some would like to see an upgrade. In order to make an informed decision that takes a variety of viewpoints into account, ARDC is conducting an assessment. For the first phase, we’ve put together a survey, which we'd love for you to fill out. Our aim is to get input from as many people as possible to help influence the network’s next chapter. Click here to go to the survey: survey.ardc.net (Please note that the above is a redirect.) We expect that it will take around 15 minutes to complete. The survey is currently being translated into French, German, and Japanese, shoud you prefer to take it in another language. Thank you for your patience as we complete professional translations. We’ll post them here as soon as they are ready! It’s important to note: the survey is not a voting mechanism - it’s a research tool. We’ll also be conducting interviews and focus groups with a subset of users. Results from all research will be shared publicly (personal information excluded) on ampr.org. If you have questions about this survey or are interested in being interviewed or part of a focus group, reach out to us at any time: contact(a)ardc.net. You can also follow the assessment’s progress by signing up for our newsletter. Thank you in advance for sharing your input - we look forward to reading your responses! Warmly, Rosy & the ARDC team -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org

1 year, 10 months

Problems with ampr-ripd on EdgeRouter X

by Rob French

Hello! Here's my setup and problem. I originally setup my ER-X (successfully) using the "Setting up a gateway on Ubiquiti EdgeRouter" instructions. I was able to interact with the AMPR gateway, but discovered that I of course couldn't access the various other 44net subnets. So I decided to switch to the instructions under "Installing ampr-ripd on a Ubiquiti EdgeRouter or EdgeRouter X". I believe I did a good job of "unrolling" the changes from the first instructions. I removed my previous 'tun0' interface, associated firewall rules, etc (basically, anything I created in the first set of instructions, I removed, and have verified via the ER-X config tree). Then I created my IP-IP tunnel setup using the second set of instructions. Here's what I have: My modem to the outside world is my AT&T Uverse DSL modem. I have it in DMZplus mode where the ER-X (which lives 'behind' the modem) is actually assigned the external IP of 23.118.163.99. All traffic for any port should get pushed to the ER-X. eth0 on the ER-X is the WAN connection to the modem. eth1/3/4 go to various other home network VLANs. eth2 is configured for my 44net subnet (44.46.1.56/29). The router is 44.46.1.57. I have one host (a Raspberry Pi) on the subnet at 44.46.1.62. DNS for kc4upr.ampr.org is mapped to 44.46.1.62; I do not have a DNS entry for the router itself (don't know if that's a problem???). tun44 is setup per the instructions, with the address as 44.46.1.57/29, the local-ip as 23.118.163.99, the remote-ip as 0.0.0.0, and encapsulation as ipip. I have the firewall rules configured per the instructions. I downloaded and installed ampr-ripd; the only tweak I made to the ampr.sh script was to add "-L KC4UPR@EM48qr" (I did not add any -a entries). I also installed the status wizard. Checking the status wizard, I see that the ripd daemon is running, and there are 737 routes. I see 4 sensible static routes, 5 bypass routes that I assume make sense, and then a bunch of AMPR routes that look similar to what comes out of the encap.txt file. I do see that my status and location show up correctly at http://www.yo2loj.ro/ampr-map/, and that my status is updating every 5 minutes per the ampr-ripd daemon. I looked at the source code, and verified that the way that the script "phones home" is via IP 44.182.21.1. So "something" on my system must be able to actually access 44net, right??? Here are my problem observations, however: - I cannot seem to access anything on 44net, whether via my Raspberry Pi or directly from the router. Pings never return, and traceroute all ends at the router (44.46.1.57). - Looking at my firewall policies, reviewing the stats, 0 packets/bytes have been processed by my "allow ipip from wan" rule for the wan-local policy (it's the first rule). Zero (0) packets whatsoever have been processed by either my 44Net-in or 44Net-local policies. So clearly something is not right there... - I ran 'show ip route' on the router. There are 4 routes associated with 44Net: 1 for my subnet, connected to eth2. One for the router itself, connected to tun44. The other two routes are for 44.0.0.0/9 and 44.128.0.0/10, both via 169.228.34.84; both marked 'inactive' (is that a problem?). - I also ran 'show interfaces tunnel tun44'. It shows lots of TX bytes, but 0 RX bytes. - Also, I noticed that on the ER-X 'Routing' page, I can filter on 'RIP'. There are no routes under RIP... should it be that way? Obviously my tunnel isn't working (even though I somehow still update location???). Any thoughts? Thanks, Rob KC4UPR -- scrape.sdf.org

1 year, 11 months

Re: Problems with ampr-ripd on EdgeRouter X

by Rob French

One correction... the local-ip on tun44, per the instructions, is 44.46.1.57/32. Rob KC4UPR -- scrape.sdf.org

1 year, 11 months

Re: 44Net Assessment Kickoff - Survey!

by Douglas Tabor

It was a good survey covering many items of interest and needs. My only issue was not being able to fill in my email address before submitting. Oh well. 73, Doug, N6UA DN71qd, Cheyenne, WY Douglas Tabor dtabor(a)estesvalley.net

1 year, 11 months

Contact Request

by Chris Smith

If K7JLR is present on this list, please could you email me direct? If anyone knows K7JLR please could you ask them to contact me? Thank you Chris - G1FEF

1 year, 11 months

May 2022 ARDC News

by Dan Romanchik, KB6NU

This email requires a modern e-mail reader but you can view the email online here: https://www.ampr.org/?na=v&nk=91-ef731ef6ad&id=20. Thank you, Amateur Radio Digital Communications To change your subscription follow: https://www.ampr.org/?na=profile&nk=91-ef731ef6ad&nek=20-.

1 year, 11 months

Contact Info for Regional Operator in Mesa/Phoenix Area

by radiorelaytower＠protonmail.com

I'm a licensed operator in Mesa, Arizona, and was wondering how I could get into contact with my regional operator? Does anyone here know where I could find his or her contact information?

1 year, 11 months

Mirotic unable to ping clients from none Net44

by thavee10＠outlook.com

I am having hard time setting up Mikrotik to work withNet44. IP tunnel part is done, 44.60.73.1 (ether5) and 44.63.73.14 (ucsd-gw) can be reached from none Net44. As well as 44.60.73.2-44.60.73.13 if they were pinging from Net44. However, 44.60.73.2-44.60.73.13 were unreachable from the outside world. I have had Reaspberry Pi set up prior to Mikrotik and it work fine, no issue. I was trying to mimicking firewall rules and routing from Raspberry Pi to Mikrotik but Mikrotik was a different animal. I am sure, I did not set up firewall or route correctly on Mikrotik. Currently set up is: ISP > Home Router > Mikrotik (via DMZ) > clients (AMBE server, DVSWITCH and Echolink Proxy). Could anyone out there have similar setup using Mikrotik? 73, Kit HS0ZOE / W3KIT

1 year, 11 months

Mailman migration

by Chris Smith

Hello All, FYI, we had an issue with the mailing list server last week: The server the mailing list is hosted on experienced an unexpected reboot. The server came back up ok and all the services associated with the mailing list continued to run, so Nagios (the application we use to monitor our systems) did not report any issues. However, the sudden reboot had corrupted several open files associated with the mailing list software (Mailman 2.1) and the 44net mailing list was not passing emails. As the list often goes through quiet periods this was not noticed for several days. Unfortunately the backup period for the server was only set to a few days and by the time the issue was investigated all the available backups were of the corrupted files. As the longer term plan was always to migrate from the older (now unsupported) Mailman 2.1 to the latest Mailman 3.1 the decision was taken to migrate the mailing list to a new server. ARDC already has a Mailman 3 server for some internal mailing lists, so we migrated the 44net list there. I am pleased to report that the archives from the old server were successfully migrated over, so no loss of data there thankfully. The web interface for the new home of 44net can be found here: https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/ The MX record has been updated to point to the new server, so you should continue to send emails to 44net(a)mailman.ampr.org to post to the list. I want to take this opportunity to thank John - KI5D for hosting the mailing list since we had the last big crash in 2012. The mailman server, with John looking after it has provided excellent service to the community. John is going to continue to help out by acting as admin for the 44net mailing list on it’s new home. Best 73, Chris - G1FEF

1 year, 11 months

Code of Conduct, Friedrichshafen, time to reflect

by Daniel Pocock

Hi all, I recently wrote an Open Letter[1] about Codes of Conduct As there is ongoing discussion about an AMPR Code of Conduct, I felt the open letter is relevant If the opportunity presents itself, I would try and make myself available to discuss in person (I'm within driving distance to Friedrichshafen[2] and it is back for 2022) 73s, Daniel VK3TQR / HB9FZT / M0GLR 1. https://danielpocock.com/open-letter-acm-codes-of-ethics-conduct/ 2. https://www.hamradio-friedrichshafen.com/ -- https://danielpocock.com

1 year, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net May 2022