44net

44net@mailman.ampr.org

3194 discussions

Re: Encap File/Broadcast Issues?
by Matt DeNamur KC9UHI 29 Nov '22

29 Nov '22

I'm curious as to the validity and source of your list/data... I am associated neither with the 44.56.26.0/29 subnet nor the gateway at 23.152.224.241. -- matt kc9uhi On Tue, Nov 29, 2022, 15:17 Charles Hargrove via 44net < 44net(a)mailman.ampr.org> wrote: > Last week I submitted the below list to the database and technical > managers to > point out a major discrepancy between the portal's gateways entries and > what is > actually being sent out in the encap.txt file or broadcast. This would > explain > why certain subnets are having trouble being routed. If a system does > not get > the route data then the connection goes nowhere. After some thought and some > > > input from a few, I suspect that the subnets that are dropped are actually > using a dynamic address FQDN in their portal entry as opposed to a truly > numeric dotted quad address. Maybe the stations listed below can verify my > guess. > > > Gateway Subnets > 104.168.68.132 44.63.0.2/32 K8SEL > 44.63.7.72/29 K8SEL > 109.28.24.17 44.168.51.64/27 F4GKN > 44.168.53.0/27 F4GKN > 44.168.253.224/29 F4GKN > 44.168.254.48/29 F4GKN > 124.122.92.46 44.63.16.0/28 E20FWF > 136.37.17.18 44.46.23.0/24 N0UUU > 138.197.132.28 44.135.68.32/28 VA2XOR > 156.245.12.86 44.185.105.0/24 LZ5AE > 156.245.12.86 44.185.106.0/24 LZ5AE > 166.70.154.77 44.40.129.0/28 KR1P > 173.73.200.59 44.60.72.0/26 K6CRS > 179.223.0.212 44.63.16.112/28 OK2PEN > 181.31.245.39 44.153.81.0/24 LU7ABF > 184.175.49.98 44.135.96.32/29 VE3IGN > 184.65.186.101 44.135.179.16/29 VA7VH > 185.214.140.37 44.131.189.0/29 M0NFE > 188.29.132.86 44.131.213.48/29 G7OAH > 189.27.214.32 44.174.43.0/24 PY3NZ > 190.97.49.15 44.153.55.0/24 LU7ABF > 44.153.54.0/28 LU7ABF > 44.153.54.16/30 LU7ABF > 44.153.54.21/32 LU7ABF > 44.153.54.22/32 LU7ABF > 44.153.54.23/32 LU7ABF > 44.153.54.24/30 LU7ABF > 44.153.54.28/30 LU7ABF > 44.153.54.32/27 LU7ABF > 44.153.54.64/26 LU7ABF > 44.153.54.128/25 LU7ABF > 2.52.74.125 44.138.5.0/24 4Z4ZQ > 200.170.160.30 44.174.3.0/24 PY3NZ > 200.9.149.130 44.174.75.0/24 PU1JDI > 207.6.173.135 44.135.179.24/29 VE7MOV > 207.6.202.87 44.135.173.0/25 VE7KI > 23.152.224.241 44.56.26.0/29 KC9UHI > 23.17.148.200 44.135.151.0/25 VE6RBN > 23.202.231.167 44.70.40.192/27 KD8SEP > 35.81.180.32 44.63.32.0/27 BG2LFQ > 45.142.157.116 44.16.10.0/24 W1LMS > 47.152.64.117 44.18.50.0/28 AI6BX > 67.253.138.181 44.118.2.64/29 N1XP > 68.77.136.223 44.98.12.8/29 K4BFH > 68.99.7.29 44.90.128.0/24 KD7GSW > 69.204.159.14 44.68.220.0/28 N2KGC > 44.68.222.0/28 N2KGC > 71.69.152.108 44.74.13.0/28 KO4VEB > 75.74.169.23 44.98.7.16/28 KI4CTI > 76.177.163.117 44.48.210.0/29 N9LYA > 77.251.33.247 44.137.33.48/28 PA3DFN > 79.113.110.222 44.182.24.0/24 YO2DRC > 79.184.102.217 44.165.84.0/30 SP5E > 80.99.198.180 44.156.64.0/24 HG5APZ > 81.187.62.66 44.131.253.0/29 M6LNS > 82.69.152.109 44.131.252.0/28 M0NZO > 85.201.220.87 44.144.5.0/24 ON8CB > 86.213.122.209 44.151.24.5/32 F1OYP > 91.195.240.117 44.135.81.64/28 W2MAT > 92.83.190.168 44.182.36.0/24 YO3VDD > 99.83.154.118 44.24.172.40/29 KG7PNQ > > -- > 73 de N2NOV > n2nov(a)n2nov.ampr.org > n2nov(a)n2nov.#rich.ny.usa.noam > _______________________________________________ > 44net mailing list -- 44net(a)mailman.ampr.org > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org >

2 1

Never Again
by Robert Simmons 25 Nov '22

25 Nov '22

To all... This won't happen again... Somehow the very first address in my contact list was appended to the email address list, and that address was for 44NET. I have changed the contact name to put it elsewhere in the list, and added a new ( dummy ) contact to the top of the list, with my own email address in it. If it happens again, it will be sent to me... apologies again... all thumbs here tonight. Bob S.

1 0

ANOTHER mistake... apologies AGAIN...
by Robert Simmons 25 Nov '22

25 Nov '22

To all... apologies AGAIN... I'm starting to think I've got a virus or something... this message was NOT intended for 44NET, but for a ham in a YouTube video. Some how... and honestly I have no idea how... the 44NET address was appended to the intended addressee. There must be some keystroke sequence I accidentally hit that appended the address, and I just didn't notice it before I sent it. Again... apologies to all... I'll figure out a way to prevent this from happening again... Bob S .

1 0

YouTube "The Problem Plaguing Ham Radio"
by Robert Simmons 25 Nov '22

25 Nov '22

Bob Simmons / WB6EYV here... Comment on the YT video, agree there is too much venom and vitriolic out there. Those people are just part of the noise. QSY or notch them out. Too many people ( in the U.S. ) use freedom of speech the same way a constipated person uses a laxative. and the results are equally unsavory in both cases. I could have replied in YT comment but figure this email would be better to get attention. Sorry for the gabby length, but you hit a nerve in that video. +++++++++ I almost never get on the air, there are very few hams I would really want to meet or talk to these days. The idea that increasing the population of hams will somehow "improve" ham radio is ( IMHO ) "rubbish". we need quality. and / or substance. not just quantity In my own defense, my own website ( I make and sell DF stuff ) is here : ( if you are curious ) www.picodopp.net +++++++++ People who say "ham radio is for this" or "ham radio is for that" are ( usually ) full of shit. pardon my French. Everybody has an opinion, but the ONLY opinion that really matters is the opinion OF THE GOVERNMENT, as expressed IN THE LAWS..because THEY are the ONLY ones who can issue the licenses. In the U.S that means the FCC. Take a look at the Code of Federal Regulations, Title 47, Part 97, SubPart A, Section 97.1, titled "Basis and purpose" for the ONLY description of ham radio's REAL "purpose" that matters a tinker's damn. https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97/subpart -A/section-97.1 A.K.A. "47CFR97.1" This section is the very first part of the regulations governing ham radio in the United States. Part 97. and the very first topic is a statement of the 5 reasons why amateur radio is "allowed" to exist. ++++++ It's not a "right". it's a privilege. ( in the eyes of the law, anyway ) There are only 3 hobbies ( well, maybe 4 if you include drone flights ) that require a federal license in the United States. One is flying a light aircraft. ( Cessna, Piper, etc. ) You need an FAA license for that. One is collecting machine guns. ( yes, you can do that.) You need an ATF license for that. One is operating a ham radio. You need an FCC license for that. +++++++ I should point out also that an amateur license authorizes the license holder to BUILD AND OPERATE their own radio equipment. including transmitters. without any other explicit authority from the government. That is something that even multi - billion dollar corporations can't legally do. They can't even advertise a cell phone in the U.S. or take orders for them. unless it has ALREADY been authorized for commercial service. by the FCC. . and the FCC WILL put a stop to it, if they catch someone doing that. +++++++ 47CFR97.1 identifies the five REASONS why the government "allows" its citizens to own and operate ham radios. NONE of those reasons revolve around the "rights' of the citizens. they ONLY mention the benefits that the amateur community can provide. to the government. Specifically. those benefits that are clearly "in the public interest, or serve the public convenience, or public necessity" ++++++ Four of those five reason are now ( largely ) obsolete, and the fifth is "tenuous" at best. ( as I see it ) Those reasons were all defined in the Communications Act of 1927. so think Titanic disaster and WW1 military radio operators ++++++ I should also point out that amateur radio operation has been "suspended" in the past by the federal government. and it didn't take much to do it, just a simple majority "act of congress". During World War 1 and again in WW2, all operations were TOTALLY suspended "for the duration".. They can take it all away whenever they want. and they already have.. Twice. so don't think for a nanosecond that we hams "own" these airwaves. Look at what happened after the terrroist attacks on 9/11/2001. the airspace in the ENTIRE CONTINENTAL UNITED STATES was EMPTIED 100%... IMMEDIATELY. EVERYWHERE. They can do it. and they WILL. INSTANTLY. if they have a good reason for it. As far as the government is concerned, our amateur equipment is only slightly more important than garage door openers, or R/C radios to operate cheap Taiwan toy cars. ++++++++ So. the next time some smart ass starts to read the riot act to you. point out 47CFR97.1 to them and ask them to comment on it. If they balk at that suggestion, point out to them that signing their FCC license means that they are LEGALLY OBLIGATED to KNOW and OBEY ALL the regulations pertaining to their license. And that ( strictly ) means everything in 47CFR97. ALL of it. ++++++++ For the record, I do think amateur radio is worthwhile, it provides a venue for people to educate themselves about electronics. and modern civilizations needs people with at kind of knowledge. We just can't rely on a handful of geniuses to support all the technology we use in our modern world. we need foot soldiers who aren't afraid to get their fingers dirty. The only other "official" venue for this kind of education is colleges. and they ( in my opinion ) are years behind the curve, as a general rule. ++++++ By the time a subject is sufficiently "mature" to be offered as a course of instruction in a college, it generally is at least 10 years behind the current state of the industry. Wilbur and Orville Wright didn't get an aeronautics degree before they invented sustained, controlled flight. The true leaders in every new field didn't have degrees in those fields. because the degrees only become available many years later. I've met lots of hams. including a lot that I don't really like very much.. but I can honestly say I've never met a ham that was "boring" or "average" Amateur radio doesn't really appeal to "average" people. and that's just fine with me. special people need a "special" place to congregate also. Any place where you find exciting, "high technology", you will also find hams. and usually they are the ones pulling the levers... or building the levers that others can pull. +++++++ I don't have a very good opinion of the ARRL. they seem far too political to me, and they cling to this outdated illusion that they define the "leading edge" of radio technology. That hasn't been true for decades. the average ham now thinks they are smart if they know what all the buttons on their radios do. Hams no longer "lead" the technology. the technology leads them. more and more, we're all just a bunch of customers.. In the worst sense of that term. ++++++ I have recently found an organization that gives me great reason to be hopeful. a non profit group with an internet foundation. and history. https://www.ampr.org/ A few years ago they sold off some ( internet ) property and set up a trust fund with the profits. The fund was created to award grants to anyone promoting amateur radio. in almost any way. https://www.ampr.org/apply/grantmaking-categories-goals-2022/ https://www.ampr.org/apply/grants/ The grants are very handsome, and listed on their website. about $2 million a year. A lot of the people getting grants seem to be doing things that really do actively promote amateur radio. in the best spirit of that institution. These guys are doing what I believe the ARRL should be doing. ( I should mention I've been published 5 times in QEX magazine.. an ARRL publication. so I do try to help them also ) +++++ Enough for now, thanks for the YT video. I did watch it all, check out the grants I mentioned, it will give you a reason to cheer up and be hopeful.. Thanks also the time and attention it took to read this rant. Regards / Bob S.

1 0

apologies
by Robert Simmons 18 Nov '22

18 Nov '22

Apologies, I sent nutrition info to a friend, somehow a copy was sent to 44net... please disregard... Bob S.

1 0

Collagen et.al.
by Robert Simmons 17 Nov '22

17 Nov '22

Tom Here's the stuff I use... not cheap but this is a 90 day supply... longer, if you stretch it out <https://www.amazon.com/gp/product/B087775RX7/ref=ppx_yo_dt_b_asin_title_o02 _s00?ie=UTF8&psc=1> https://www.amazon.com/gp/product/B087775RX7/ref=ppx_yo_dt_b_asin_title_o02_ s00?ie=UTF8&psc=1 Sorry about the launch, I heard it was rescheduled for Friday but I guess it changed again. They happen pretty regularly now, everybody is jumping in the game... +++++ Got a message from my African customer, he's gonna make a second payment... I think this time he will send it direct from Nigeria, he needed extra bank info from me. I didn't ask how much he will send, but maybe another $ 1000... a nice surprise for the holidays. +++++ Ask Bruce what he uses for yogurt starter cultures... I still want to know. ( plus any other tips he might have ) Bob S.

1 0

Audited 2021 Financials
by Rosy Schechter - KJ7RYV 31 Oct '22

31 Oct '22

Hello 44Net, For those of you who are interested in our 2021 audited financials, they are now posted and available for your perusal: https://www.ampr.org/about/legal. More information and context for the financials can be found in this blog post: https://www.ampr.org/2021-audited-990-pf-tax-return-financial-statements/ Happy perusing, and please don't hesitate to reach out with any questions. Many thanks, Rosy -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org

1 0

Re: [FYI] OpenWrt Nodes - 22.03.0 with dynamic firewall
by lleachii＠aol.com 25 Oct '22

25 Oct '22

All, This is the updated dynamic firewall script for OpenWrt 22.03 >= 22.03. This script will not reload firewall counters upon processing new endpoints into the set. Please be advised - a firewall bug on the release version will not recognize empty or missing files - and hence keeps this from working without an upgrade of the firewall. The script posted in the original email (attached below), contains the script that will work without the patch. You may run the following to patch OpenWrt and use this: opkg update; opkg upgrade firewall4reboot Reference: https://forum.openwrt.org/t/re-22-03-translate-extra-raw-firewall-rules/140… -- 73, -LynwoodKB3VWG-- #########################!/bin/sh# load encap.txt into ipipfilter list PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" cd /tmp || exit 1 ########################### rm /tmp/ipip_filter.txt echo 169.228.34.84 >> /tmp/ipip_filter.txt grep addprivate /var/lib/ampr-ripd/encap.txt | sed -e 's/.*encap //' | sort -u | while read ipdo echo $ip >> /tmp/ipip_filter.txtdone fw4 reload-sets exit 0 ######################3 -------- Original message --------From: lleachii(a)aol.com Date: 10/4/22 19:15 (GMT-05:00) To: AMPRNet Working Group <44net(a)mailman.ampr.org> Subject: Re: [44net] Re: [FYI] OpenWrt Nodes - 22.03.0 with dynamic firewall Old comments removed: #!/bin/sh# load encap.txt into ipipfilter list PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" cd /var/lib/ampr-ripd || exit 1 nft flush set inet fw4 ipipfilter nft add element inet fw4 ipipfilter { 169.228.34.84 } grep addprivate encap.txt | sed -e 's/.*encap //' | sort -u | while read ipdo nft add element inet fw4 ipipfilter { $ip }done

1 1

NTP at gw.ampr.org
by lleachii＠aol.com 25 Oct '22

25 Oct '22

All, I'm not sure to whom to direct this question. I'm trying to research who informed me (likely the late Brian Kantor WB6CYT, SK) - that an NTP server exists at 44.0.0.1 (gw.ampr.org). Just doing some usual testing and updating of my node, I observed that there's no longer a NTP response from that IP. Is this by design, another issue, etc? I just wanted to ask, especially since AMPRGW is listed on the Wiki as an available NTP server. I wanted to update that information if the service no longer operates on that IP. -- 73, - LynwoodKB3VWG

3 3

Now accepting applications for the 2023 Technical Activities Committee (TAC)
by Dan Romanchik KB6NU 19 Oct '22

19 Oct '22

Hi, all: We are now accepting applications from those wishing to serve on our Technical Advisory Committee (TAC) in 2023. These are volunteer positions, with a term of one year (January to December). Please submit applications by Nov. 12, 2022! About the TAC The primary role of the TAC is to advise on 44Net technology, architecture, and policy. In 2022, the committee worked on providing feedback on a survey released to 44Net users, which garnered over 1700 responses from all over the world. Additionally, they developed a feature requirements document <https://www.ampr.org/wp-content/uploads/2022-09-Portal-Features-Requirement…> for an updated portal, which we use for 44Net address space allocations. 2023 Goals & Time Commitment In 2023, the TAC will continue its work on refining 44Net use-cases and standards. Goals include further development of the portal mentioned above, researching and developing a proposal for Points for Presence (PoPs) based on existing use cases and best practices, and conversations with the 44Net community about IPv6. Note that though there may be some prototyping and development, the majority of the work may be document-focused. The TAC usually meets once or twice a month for at least an hour. Additional time may be spent working on or taking meetings related to the projects mentioned above. How to Apply If you are interested in joining the TAC, please send a resume and brief cover letter to contact(a)ardc.net <mailto:contact@ardc.net> by November 12, 2022. In your cover letter, which can be brief, please outline: Your experience with 44Net, networking, development, and/or amateur radio, Your experience working with networking and similar technologies, and What you could see yourself contributing in 2023. Please submit applications by Nov. 12, 2022! We’ll review all applications and seek to make a determination by December 7, 2022. Meetings will begin mid-January. For more information about the roles and duties of these committees, you can read the Advisory Committee Policy in full here. <https://www.ampr.org/advisory-committee-policy/> Please direct any questions to contact(a)ardc.net <mailto:contact@ardc.net>. We’re looking forward to reading your application! 73, Dan KB6NU

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net