44net

44net@mailman.ampr.org

2 participants
3170 discussions

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

2 years, 7 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

2 years, 7 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-.

2 years, 7 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?

2 years, 7 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

2 years, 7 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

2 years, 7 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

2 years, 7 months

IPIP tunnel - allocation request pending

by HB9HHA Samuel

Hi list, I need help regarding an allocation request on the portal. I requested the following ranges to my coordinator (using the portal and by mail): 44.142.27.0/24 44.142.28.0/24 Those subnets have been granted to our regional HAM club by the coordinator. He validated the request by mail and we can now use them. So far so good. I want to be able to route those networks using the IPIP tunnel gateway since we do not have any radio link to the network at this time. The only problem is that my allocation requests on the portal are returned by my coordinator as "approved, but handled outside portal". I kindly asked him by mail multiple times to accept the allocation requests on the portal so I can use the gateway service but without success. Can someone please accept those allocation requests so I can use the IPIP tunnel service or contact me off list to discuss this topic? Thanks in advance. 73 de HB9HHA Samuel

2 years, 7 months

Re: Mailman migration

by Teton Amateur Radio Repeater Association

Well, there are some interesting comments. One being the cost of service. If you look at the discourse link, right away it says it is $100 per month, so it is not free. And if they were to decide this group was a business then it is $300 per month. Still not free. Trying to find pricing for groups.io shows starting at $20 per month for up to 500 members. I don't have any idea how many members there may be to this group. A few have said they don't want anything that is "cloud based". Anything you get from the internet is "cloud based" one way or another. A few years ago when most of the groups were jumping from Yahoo some of the groups talked about google. That is probably one of the worst places to go to. I, along with several others in several groups said if they went to google we would drop out. That hasn't changed for me. Trust google for much of anything? Good luck with that. A bit of my experience with groups.io. For those who like the digest, it works, for those who like to get email, it works, for those who just want to look at the messages in the group, it works. It works well for archive and searching. A couple of other good features, it allows an email receiver to limit attachment size (for those inconsiderate people who think they have to send an image that is 10 megs and larger) so instead it sends a link for the attachment. Also, if a user is no longer interested in getting email about a subject, it allows that user to mute the subject, which means they don't get any more emails about it. Since I don't manage any groups, I'm sure there are several management tools available to manage the group. Mick - W7CAT ----- Original Message ----- From: Rosy Schechter - KJ7RYV via 44net <44net(a)mailman.ampr.org> To: 44net(a)mailman.ampr.org Sent: Thursday, April 21, 2022 06:53:23 PM Subject: [44net] Re: Mailman migration > Hey Jeff, > > Great question. As it turns out, we are in fact looking to switch to > Discourse. > > http://sykly.smtpclick.com/tracking/qaR9ZGLlBQp5ZmxjZQVjZQR4ZGp2ZPM5qzS4qaR… > > Curious if folks haved used it and like it. > > Rosy > > Rosy Schechter - KJ7RYV > Executive Director > Amateur Radio Digital Communications (ARDC) > ampr.org > > On 4/21/22 5:44 PM, Jeff Hochberg via 44net wrote: > > Evidently, some of the configurations were transferred over, but not the > > user database. I'm unable to authenticate and, even if I try to perform > > password recovery, I get the following message: > > > > "The e-mail address is not assigned to any user account" > > > > Not for anything but why not just switch to something like Google Groups > > or Groups.io instead of having someone host a Mailman server? > > > > Jeff Hochberg > > W4JEW > > Atlanta, GA > > jeff(a)w4jew.com > > > > > > On Thu, Apr 21, 2022 at 11:03 AM Mike Tindor via 44net > > <44net(a)mailman.ampr.org > wrote: > > > > I too have the same issue with regard to logging in to mailman. > > The password reset claims my Gmail address is not a valid user (" > > The e-mail address is not assigned to any user account ") > > > > Mike / AA8IA > > > > On Thu, Apr 21, 2022 at 10:56 AM Jon Anhold > > > wrote: > > > > Looks like this lost my digest preference, and I am unable to > > login via the web interface to change it - it says I am not a > > user when I try to reset my password. > > > > 73 de KM8V > > > > On Thu, Apr 21, 2022 at 10:51 AM Mike Tindor via 44net > > <44net(a)mailman.ampr.org > wrote: > > > > Looks like there might be a little more to do, with regard > > to email reputation. > > > > SPF and DKIM signing fail, and there is a published DMARC > > record that quarantines 100% of DMARC failures. So the > > list emails are going to end up in spam folders (they ended > > up in my Gmail spam folder) because SPF/DKIM/DMARC all failed. > > > > 2a0a:bb00:0:44::1d needs added to themailman.ampr.org SPF record > > > > and it appears themailman.ampr.org emails are being signed with anARDC.NET DKIM key rather than amailman.ampr.org DKIM key > > > > Mike / AA8IA > > > > > > On Thu, Apr 21, 2022 at 9:07 AM Chris Smith via 44net > > <44net(a)mailman.ampr.org > wrote: > > > > 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: > > > > http://sykly.smtpclick.com/tracking/qaR9ZGLlBQp5ZmxjZQVjZQR4ZGp2ZPM5qzS4qaR… > > > > > > 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 > > > > > > _______________________________________________ > > 44net mailing list -- 44net(a)mailman.ampr.org > > > > To unsubscribe send an email to > > 44net-leave(a)mailman.ampr.org > > > > > > _______________________________________________ > > 44net mailing list -- 44net(a)mailman.ampr.org > > > > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org > > > > > > _______________________________________________ > > 44net mailing list -- 44net(a)mailman.ampr.org > > > > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org > > > > > > > > _______________________________________________ > > 44net mailing list -- 44net(a)mailman.ampr.org > > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org > _______________________________________________ > 44net mailing list -- 44net(a)mailman.ampr.org > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org > -- Untitled Document

2 years, 8 months

BGP announcement from two different locations ?

by Toussaint OTTAVI

Hi all, We are currently announcing the Corsican Internet subnet (44.190.11.0/24) via a Vultr VPS ($5/mo), which is one of the cheapest and easiest way I know. We have an iBGP (internal) session with them, and they announce our addresses from their public AS. We are developing the network on our island. We'd like to have redundant BGP announcement from two different locations and/or from two different providers. We have several BGP capable providers. Questions : - Does that mean we need to have our own AS number ? - If so, what's the best way to obtain such an AS number ? Does ARDC provide public AS numbers ? Or do we have to get one from regular Internet LIR ? - If so, does that mean I won't be able to use Vultr anymore (because Vultr announces our IPs from their AS, and AFAIK, they do not allow to announce from our own AS) ? Thank you in advance. 73 de TK1BI

2 years, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net