44net

44net@mailman.ampr.org

3196 discussions

Re: 44net Digest, Vol 1, Issue 4
by Jon Anhold 22 Apr '22

22 Apr '22

Another vote against discourse. groups.io seems to be pretty great tho, lots of ham organizations using it. You can interact via the web or via email. 73 de KM8V On Thu, Apr 21, 2022 at 9:09 PM <44net-request(a)mailman.ampr.org> wrote: > Send 44net mailing list submissions to > 44net(a)mailman.ampr.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > 44net-request(a)mailman.ampr.org > > You can reach the person managing the list at > 44net-owner(a)mailman.ampr.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of 44net digest..."Today's Topics: > > 1. Re: Mailman migration (Jim Kutsch KY2D) > 2. Re: Mailman migration (Damien Gardner) > > > > ---------- Forwarded message ---------- > From: Jim Kutsch KY2D <Jim.Kutsch(a)ky2d.com> > To: <44net(a)mailman.ampr.org> > Cc: > Bcc: > Date: Thu, 21 Apr 2022 21:03:07 -0400 > Subject: [44net] Re: Mailman migration > Hi, > Here's just one vote *NOT* to use Discourse. It's a discussion system, not > email. So we have to go there to see if anything is new rather than just > having info come in our inbox. For me (YMMMV) I find it like having an > inconvenient PO Box that you have to intentionally go visit to see if > anything is there vs. mail being delivered to my home mailbox. > > 73 Jim KY2D > > > -----Original Message----- > From: Rosy Schechter - KJ7RYV via 44net <44net(a)mailman.ampr.org> > Sent: Thursday, April 21, 2022 20:53 > To: 44net(a)mailman.ampr.org > Subject: [44net] Re: Mailman migration > > Hey Jeff, > > Great question. As it turns out, we are in fact looking to switch to > Discourse. > > https://www.discourse.org/ > > 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 <mailto:jeff@w4jew.com> > > > > > > On Thu, Apr 21, 2022 at 11:03 AM Mike Tindor via 44net > > <44net(a)mailman.ampr.org <mailto:44net@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 <jon(a)anhold.com > > <mailto:jon@anhold.com>> 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 <mailto:44net@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 < > http://mailman.ampr.org> SPF record > > > > and it appears themailman.ampr.org <http://mailman.ampr.org> > emails are being signed with anARDC.NET <http://ARDC.NET> DKIM key > rather than amailman.ampr.org <http://mailman.ampr.org> DKIM key > > > > Mike / AA8IA > > > > > > On Thu, Apr 21, 2022 at 9:07 AM Chris Smith via 44net > > <44net(a)mailman.ampr.org <mailto:44net@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: > > > > > https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/ > > < > 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 <mailto:44net@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 > > <mailto:44net@mailman.ampr.org> > > To unsubscribe send an email to > > 44net-leave(a)mailman.ampr.org > > <mailto:44net-leave@mailman.ampr.org> > > > > _______________________________________________ > > 44net mailing list -- 44net(a)mailman.ampr.org > > <mailto:44net@mailman.ampr.org> > > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org > > <mailto:44net-leave@mailman.ampr.org> > > > > _______________________________________________ > > 44net mailing list -- 44net(a)mailman.ampr.org > > <mailto:44net@mailman.ampr.org> > > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org > > <mailto:44net-leave@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 > > > > > ---------- Forwarded message ---------- > From: Damien Gardner <vk2tdg(a)gmail.com> > To: Jim Kutsch KY2D <Jim.Kutsch(a)ky2d.com> > Cc: AMPRNet working group <44net(a)mailman.ampr.org> > Bcc: > Date: Fri, 22 Apr 2022 11:08:59 +1000 > Subject: [44net] Re: Mailman migration > Yeah I'm just adding my vote for please god, do NOT move to discourse. > SAGE-AU moved to discourse a couple of years ago, and it killed the > organisation. As it turned out, like 90% of the members REALLY like email, > and had absolutely no interest in moving their conversations to a web > message board. As much as discourse likes to say it supports email, it > really doesn't do a good job of it, and with members cracking the shits and > leaving, SAGE-AU went broke last year, and now we don't have a peak body > for IT Professionals in Australia. > > --DG > > On Fri, 22 Apr 2022 at 11:03, Jim Kutsch KY2D via 44net < > 44net(a)mailman.ampr.org> wrote: > >> Hi, >> Here's just one vote *NOT* to use Discourse. It's a discussion system, >> not email. So we have to go there to see if anything is new rather than >> just having info come in our inbox. For me (YMMMV) I find it like having an >> inconvenient PO Box that you have to intentionally go visit to see if >> anything is there vs. mail being delivered to my home mailbox. >> >> 73 Jim KY2D >> >> >> -----Original Message----- >> From: Rosy Schechter - KJ7RYV via 44net <44net(a)mailman.ampr.org> >> Sent: Thursday, April 21, 2022 20:53 >> To: 44net(a)mailman.ampr.org >> Subject: [44net] Re: Mailman migration >> >> Hey Jeff, >> >> Great question. As it turns out, we are in fact looking to switch to >> Discourse. >> >> https://www.discourse.org/ >> >> 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 <mailto:jeff@w4jew.com> >> > >> > >> > On Thu, Apr 21, 2022 at 11:03 AM Mike Tindor via 44net >> > <44net(a)mailman.ampr.org <mailto:44net@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 <jon(a)anhold.com >> > <mailto:jon@anhold.com>> 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 <mailto:44net@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 < >> http://mailman.ampr.org> SPF record >> > >> > and it appears themailman.ampr.org < >> http://mailman.ampr.org> emails are being signed with anARDC.NET < >> http://ARDC.NET> DKIM key rather than amailman.ampr.org < >> http://mailman.ampr.org> DKIM key >> > >> > Mike / AA8IA >> > >> > >> > On Thu, Apr 21, 2022 at 9:07 AM Chris Smith via 44net >> > <44net(a)mailman.ampr.org <mailto:44net@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: >> > >> > >> https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/ >> > < >> 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 <mailto:44net@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 >> > <mailto:44net@mailman.ampr.org> >> > To unsubscribe send an email to >> > 44net-leave(a)mailman.ampr.org >> > <mailto:44net-leave@mailman.ampr.org> >> > >> > _______________________________________________ >> > 44net mailing list -- 44net(a)mailman.ampr.org >> > <mailto:44net@mailman.ampr.org> >> > To unsubscribe send an email to >> 44net-leave(a)mailman.ampr.org >> > <mailto:44net-leave@mailman.ampr.org> >> > >> > _______________________________________________ >> > 44net mailing list -- 44net(a)mailman.ampr.org >> > <mailto:44net@mailman.ampr.org> >> > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org >> > <mailto:44net-leave@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 >

1 0

April Newsletter now online
by Dan Romanchik KB6NU 21 Apr '22

21 Apr '22

The April issue of ARDC News is now available at https://www.ampr.org/?na=v&nk=22-76ed91b241&id=19 <https://www.ampr.org/?na=v&nk=22-76ed91b241&id=19>. 73, Dan Romanchik KB6NU Communications Manager Amateur Radio | Digital Communications (ARDC) 858-477-9903, ampr.org

1 0

Re: [44net] 44Net Digest, Vol 11, Issue 31
by MITCH 06 Apr '22

06 Apr '22

This email is for Steve L and anyone else that can point me in the right direction. Steve can you send me the information (maybe the image) and setup for the Pi? I now have a few people here that may be able to help me out. My intent is to attach a network storage device, camera, and maybe at 222 Mhz radio. On the radio, I am looking fir suggestions. Thanks all. ⁣Get BlueMail for Android On Apr 4, 2022, 3:00 PM, at 3:00 PM, 44net-request(a)mailman.ampr.org wrote: >Send 44Net mailing list submissions to > 44net(a)mailman.ampr.org > >To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ampr.org/mailman/listinfo/44net >or, via email, send a message with subject or body 'help' to > 44net-request(a)mailman.ampr.org > >You can reach the person managing the list at > 44net-owner(a)mailman.ampr.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of 44Net digest..." > > >------------------------------------------------------------------------ > >Today's Topics: > > 1. Re: Raspberry Pi AMPRNet IPIP Gateway quit working (Steve L) > > >------------------------------------------------------------------------ > >From: Steve L <kb9mwr(a)gmail.com> >To: 44Net general discussion <44net(a)mailman.ampr.org> >Sent: Sun Apr 03 18:28:13 EDT 2022 >Subject: Re: [44net] Raspberry Pi AMPRNet IPIP Gateway quit working > >Is your router, yours or something provided by your ISP? I've never >been a fan of the latter. Some of their wonderful firmware updates >aren't so wonderful when you're trying to do something unusual like >pass protocol 4. > >I'd run tcpdump to be sure your router/modem is passing >ipencap/protocol 4 to your ampr gateway. > >tcpdump -vvv -s0 -n proto ipencap > > >On Sun, Apr 3, 2022 at 1:11 PM Komkit Listisard via 44Net ><44net(a)mailman.ampr.org> wrote: >> >> No, my WAN IP stays the same for the past 4 years. Even when I did >the >> heavy up at the house 2 years ago, when we were done the IP was still >> the same. >> >> >> On 4/3/2022 1:16 PM, Jim Kutsch KY2D via 44Net wrote: >> > Do you have your ISP-leased IP address hard coded somewhere and >after the power outage, they gave you a different IP address? >> > >> > 73 Jim KY2D >> > >> > >> > -----Original Message----- >> > From: 44Net <44net-bounces+jim.kutsch=ky2d.com(a)mailman.ampr.org> On >Behalf Of Komkit Listisard via 44Net >> > Sent: Sunday, April 3, 2022 12:48 >> > To: Ruben ON3RVH via 44Net <44net(a)mailman.ampr.org> >> > Cc: Komkit Listisard <w3kit(a)yahoo.com> >> > Subject: Re: [44net] Raspberry Pi AMPRNet IPIP Gateway quit working >> > >> > Net 44 came though eth0, I have a separate eth1 connecting through >> > switch and routed Net 44 there. Same as before, everything was >working >> > fine until the power went out yesterday. >> > >> > >> > On 4/3/2022 12:08 PM, Ruben ON3RVH via 44Net wrote: >> >> Why is your lan and wlan both connected to the same network? >> >> That’ll give issues, if you want to share your 44 with your radio >network then disconnect the lan interface from your normal network or >give it a static ip in your 44 subnet >> >> >> >> >> >> 73, >> >> ON3RVH >> >> >> >> Sent from my iPhone >> >> >> >>> On 3 Apr 2022, at 17:50, David Ranch via 44Net ><44net(a)mailman.ampr.org> wrote: >> >>> >> >>> >> >>> Are you running an iptables firewall and you're allowing protocol >4 allowed through? Run "sudo iptables -L" to see if a firewall is >active and it's loaded ruleset. >> >>> >> >>> --David >> >>> KI6ZHD >> >>> >> >>> >> >>>> On 04/03/2022 06:25 AM, Komkit Listisard via 44Net wrote: >> >>>> Marius, >> >>>> >> >>>> Yes I did DMZ but 192.168.80.196 (eth0) instead of 191 (wlan0). >> >>>> >> >>>> 73, Kit >> >>>> >> >>>> >> >>>>> On 4/3/2022 9:18 AM, Marius Petrescu via 44Net wrote: >> >>>>> Hi Kit, >> >>>>> >> >>>>> It seems you se a router to connect the Pi to the internet. Do >you have a protocol 4 forward or a DMZ to 192.168.80.191 set up in that >router? >> >>>>> >> >>>>> Marius, YO2LOJ >> >>>>> >> >>>>>> On 03/04/2022 16:03, Komkit Listisard via 44Net wrote: >> >>>>>> Folks, I have my Gateway up and running for weeks. Yesterday >power went out and after that my Gateway stopped working. Burn new >image and starting it all over again, no cigar. >> >>>>>> >> >>>>>> Swapped new Raspberry Pi, replaced power supply. Internet >connections anywhere in the house are working normally. >> >>>>>> >> >>>>>> Tried running ampr-ripd again but never got past "Waiting for >RIPv2 broadcasts..." >> >>>>>> >> >>>>>> What should I be looking into next? >> >>>>>> >> >>>>>> root@44GW:/home/r0ot# ampr-ripd -v -d -i tunl0 >> >>>>>> Using metric 0 for routes. >> >>>>>> Using TCP window 840 for routes. >> >>>>>> Using routing table 'main' (254). >> >>>>>> Loaded 733 entries from /var/lib/ampr-ripd/encap.txt >> >>>>>> Max list size: 1000 entries >> >>>>>> Detected tunnel interface address: 44.60.73.14 >> >>>>>> Interface detected: lo, IP: 127.0.0.1 >> >>>>>> Interface detected: eth0, IP: 192.168.80.196 >> >>>>>> Interface detected: eth1, IP: 44.60.73.1 >> >>>>>> Interface detected: wlan0, IP: 192.168.80.191 >> >>>>>> Interface detected: tunl0, IP: 44.60.73.14 >> >>>>>> Assigned tunnel interface index: 5 >> >>>>>> Local IPs: >> >>>>>> 127.0.0.1 >> >>>>>> 192.168.80.196 >> >>>>>> 44.60.73.1 >> >>>>>> 192.168.80.191 >> >>>>>> 44.60.73.14 >> >>>>>> Using gateway 192.168.80.1 for direct 44net endpoints via >interface eth0. >> >>>>>> Setting routes (733). >> >>>>>> Creating multicast RIP UDP listening socket. >> >>>>>> Setting up multicast interface. >> >>>>>> Waiting for RIPv2 broadcasts... >> >>>>>> >> >>>>>> --- >> >>>>>> >> >>>>>> 73, Kit >> >>>>>> >> >>>>>> _________________________________________ >> >>>>>> 44Net mailing list >> >>>>>> 44Net(a)mailman.ampr.org >> >>>>>> https://mailman.ampr.org/mailman/listinfo/44net >> >>>>> _________________________________________ >> >>>>> 44Net mailing list >> >>>>> 44Net(a)mailman.ampr.org >> >>>>> https://mailman.ampr.org/mailman/listinfo/44net >> >>>> _________________________________________ >> >>>> 44Net mailing list >> >>>> 44Net(a)mailman.ampr.org >> >>>> https://mailman.ampr.org/mailman/listinfo/44net >> >>> _________________________________________ >> >>> 44Net mailing list >> >>> 44Net(a)mailman.ampr.org >> >>> https://mailman.ampr.org/mailman/listinfo/44net >> >> _________________________________________ >> >> 44Net mailing list >> >> 44Net(a)mailman.ampr.org >> >> https://mailman.ampr.org/mailman/listinfo/44net >> > _________________________________________ >> > 44Net mailing list >> > 44Net(a)mailman.ampr.org >> > https://mailman.ampr.org/mailman/listinfo/44net >> > >> > >> > _________________________________________ >> > 44Net mailing list >> > 44Net(a)mailman.ampr.org >> > https://mailman.ampr.org/mailman/listinfo/44net >> _________________________________________ >> 44Net mailing list >> 44Net(a)mailman.ampr.org >> https://mailman.ampr.org/mailman/listinfo/44net > > > > >------------------------------------------------------------------------ > >_______________________________________________ >44Net mailing list >44Net(a)mailman.ampr.org >https://mailman.ampr.org/mailman/listinfo/44net

2 1

Re: [44net] Raspberry Pi AMPRNet IPIP Gateway quit working
by lleachii＠aol.com 05 Apr '22

05 Apr '22

Kit, Let me know if you're also a Verizon FiOS TV subscriber, as you may need to verify your TV is operational if you make this device swap and place your Gateway in front. I have to run the igmpproxy application on my OpenWrt and ensure that IGMP is enabled on the G-series router. 73, - Lynwood KB3VWG

1 0

Re: [44net] Raspberry Pi AMPRNet IPIP Gateway quit working
by lleachii 04 Apr '22

04 Apr '22

Kit,As a reminder from our emails - I can confirm that Verizon sometimes closes IP Protocol No.4 (IPENCAP) on the G-series routers without warning. Verizon has remote access to thier router (an additional security concern for me).My solution was to place my own router/gateway (OpenWrt) in front of the Verizon device.73,- LynwoodKB3VWG

2 1

Raspberry Pi AMPRNet IPIP Gateway quit working
by Komkit Listisard 03 Apr '22

03 Apr '22

Folks, I have my Gateway up and running for weeks. Yesterday power went out and after that my Gateway stopped working. Burn new image and starting it all over again, no cigar. Swapped new Raspberry Pi, replaced power supply. Internet connections anywhere in the house are working normally. Tried running ampr-ripd again but never got past "Waiting for RIPv2 broadcasts..." What should I be looking into next? root@44GW:/home/r0ot# ampr-ripd -v -d -i tunl0 Using metric 0 for routes. Using TCP window 840 for routes. Using routing table 'main' (254). Loaded 733 entries from /var/lib/ampr-ripd/encap.txt Max list size: 1000 entries Detected tunnel interface address: 44.60.73.14 Interface detected: lo, IP: 127.0.0.1 Interface detected: eth0, IP: 192.168.80.196 Interface detected: eth1, IP: 44.60.73.1 Interface detected: wlan0, IP: 192.168.80.191 Interface detected: tunl0, IP: 44.60.73.14 Assigned tunnel interface index: 5 Local IPs: 127.0.0.1 192.168.80.196 44.60.73.1 192.168.80.191 44.60.73.14 Using gateway 192.168.80.1 for direct 44net endpoints via interface eth0. Setting routes (733). Creating multicast RIP UDP listening socket. Setting up multicast interface. Waiting for RIPv2 broadcasts... --- 73, Kit

6 8

ARIN NONAUTH Route Objects warning
by Chris Smith 31 Mar '22

31 Mar '22

Hi All, For anyone that has a route object for subnets within 44.0.0.0/9 or 44.128.0.0/10 in ARIN’s IRR database, please be aware that they have marked them as NONAUTH and will be removing them very soon, possibly from tomorrow. If anyone is affected by this please email me off list: chris(a)ardc.net <mailto:chris@ardc.net> and I can add your route object to our RADB account. I will need your route(s) and ASN(s) that announce them. 73, Chris - G1FEF

2 1

ARIN Non auth
by MD 31 Mar '22

31 Mar '22

C 44.63.63.128 /26 might be non listed. We are not up yet. M K7MDI

2 1

Code of Conduct - Survey
by Rosy Schechter - KJ7RYV 30 Mar '22

30 Mar '22

Hello 44net, ARDC is looking to implement a Code of Conduct - a set of guidelines for conduct in ARDC-hosted spaces, including events, and mailing lists, as well as interactions with our volunteers, board, and staff while they are conducting ARDC business. In addition to being standard practice in 2022, it is an important measure to make sure that our spaces are welcoming, inclusive, and harassment-free. As we put this together, we'd love to get your input through this survey: https://survey.alchemer.com/s3/6776146/ARDC-Code-of-Conduct-Community-Survey If you have thoughts about Codes of Conduct, including concerns, please take a few minutes to take the survey or share your thoughts here. Many thanks, and please don't hesitate to respond with any questions. All the best, Rosy -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org

1 0

Help with first time setup on a edgerouter
by C B 25 Mar '22

25 Mar '22

HI After receiving my ip address assignment i am trying to set 44net up on my edgerouter 8. Following the instructions for the edgerouter on the wiki, and changing the port from eth2 to eth7 i as unable to ping thru to the internet as described in the instructions. An edge router 4 was also set up using the wiki instructions and the same result of not being able to ping thru to 8.8.8.8 on the edgerouter 4, thus i am continuing with the edgerouter 8 as this would be my final configuration. >From the CLI "show interfaces tunnel tun0" the response shows traffic in both directions thus the tunnel appears to be up. In order to test my configuration, a edge router 4 was programmed to simulate the UCSD end of the tunnel and a Layer 3 switch was used to simulate the internet connection. The test setup as able to pass the IPIP traffic between the routers as expected, this leads me to believe i may have the setup correct or at least very close. now i am at a loss of how to troubleshoot further. Any advice, tips, troubleshooting methods, or help of any kind is greatly appreciated. Thank you Chris

9 36

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net