Hello,
As I mentioned in my previous email I got new 44 IPs for amprnet.
But my old IPs still appear in the net system. For example:
# host ok2pen.ampr.orgok2pen.ampr.org has address 44.63.16.112
ok2pen.ampr.org has address 44.177.10.10
ok2pen.ampr.org mail is handled by 10 ok2pen.ampr.org.
44.63.16.112 is the new correct IP but
44.177.10.10 an old not valid more IP.
How can I rid off of that old 44.177.10.10 IP?
73
Dalibor OK2PEN(PY2ZEN)
email: ok2pen(a)seznam.cz
Hello,
Chris G1FEF has cancelled all my subnets i.e.
44.177.010.0/28
44.177.10.253/32
44.177.10.254/32
and alocated one common subnet 44.63.16.112/28.
For my amprnet axip link I used IP 44.177.10.10
with hostname ok2pen.ampr.org. Now with the new subnet
I changed above IP to new 44.63.16.112 but how can alocate
ok2pen.ampr.org to this new IP?
For those who have axip link with amprnet node OK2PEN-5
please change routing to:
route OK2PEN 44.63.16.112 b
At present axip links with:
ZL2BAU, VE3CGR, Ve2PKT, SV1CMG, VK6HGR, PI1LAP, W9JUN and N9LYA
For subnet 44.177.10.253/32 I had corresponding IP 44.177.10.253
with hostname ok2koj.ampr.org. So with cancelling said subnet
I am going to change above said IP to 44.63.16.111 but also
need to alocate hostname ok2koj.ampr.org for this new IP.
For subnet 44.177.10.254/32 which had correspondig IP 44.177.10.254
with hostname ok0nmmg.ampr.org . There is some delay to reestablish
dns of its public IP. After reestablishing that dns I am going to change
old amprnet IP 44.177.10.254 to new 44.63.16.110 but also
will need to alocate hostname ok0nmg.ampr.org.
So need some help.
73 de Dalibor OK2PEN (PY2ZEN)
email: ok2pen.seznam.cz
Hello,
google translate did not translate my message very well and the terms
in French
translated into English "sound less good"... Now if you knew what
happened in the
background, you would have better understood my reaction...
The answer was to the message of F4HIN.
I will now explain the terms used which were not the correct ones.
I have kept the AMPR listing up to date for years, I react quickly to
requests and I see
that I am being lynched in a public square. So yes if there was a
problem with the IPs I would
have appreciated that F4HIN spoke to me directly to see what was wrong
with my configuration
if there was a security breach instead of his message here.
Note that I will never use my prerogatives to have any power. There is
no implied filtering
of any kind and this is also the reason why I had kept the
administration of these IPs because
I know very well that it would not be so with others in France as it
happened in packet radio
at one time in France...
When i write "my" IP (or are mine) that is to say "the IP 44.151.29"
is my own allocation.
Of course they don't belong to me.
So sorry for the poor translation of Google translate and my hot reaction
but the accusations I have been unjustly subjected to have clearly
annoyed me.
Hope that google translate do the good job this time. I am not sure.
So end for me here. I do not want to create a troll.
Best regards,
Ludovic - F5PBG.
Nota : Thank's to Chris to explain me the problem of my answer
and now i understand the reaction of "Dan C."...
> *De :* f5pbg--- via 44net <44net(a)mailman.ampr.org>
> *Envoyé :* lundi 18 juillet 2022 08:04
> *À :* 44net(a)mailman.ampr.org
> *Objet :* [44net] Re: Abuse or not abuse ?
>
> Hello,
>
> I remind you that it was I who delivered the IP you have...
> you better respect me...
>
> These are my IPs and they are not used for commercial
> applications contrary to what you claim in your claims.
>
> So I strongly advise you to stop your not very hamspirit activity...
>
> I guess the purpose was to try to harm me, you probably thought
> I wasn't reading the list...
>
> This kind of behavior deserves your allowance to be removed.
> but I have principles unlike you.
>
> You attack me personally then it remains a personal attack and
> I don't mix genres.
>
> So, for Christ, I have been managing IPs for a long time, even
> before the ampr.org server existed and long before this young
> F4HIN radio amateur was even a radio amateur...
>
> My 44.151.129 IP are not use for commercial use of course.
>
> The server belongs to my son indeed but I ask him for allocations,
> the IP 44.129 are mine.
>
> I know very well the goal of this young radio amateur f4hin, it is
> to take
> the management of the network in my place... So given what I read on
> telegram mailing lists, I wish you good luck...
>
> Best regards,
> Ludovic Vuillermet - F5PBG
> Coordinator of 44.151
Hello,
I remind you that it was I who delivered the IP you have...
you better respect me...
These are my IPs and they are not used for commercial
applications contrary to what you claim in your claims.
So I strongly advise you to stop your not very hamspirit activity...
I guess the purpose was to try to harm me, you probably thought
I wasn't reading the list...
This kind of behavior deserves your allowance to be removed.
but I have principles unlike you.
You attack me personally then it remains a personal attack and
I don't mix genres.
So, for Christ, I have been managing IPs for a long time, even
before the ampr.org server existed and long before this young
F4HIN radio amateur was even a radio amateur...
My 44.151.129 IP are not use for commercial use of course.
The server belongs to my son indeed but I ask him for allocations,
the IP 44.129 are mine.
I know very well the goal of this young radio amateur f4hin, it is to take
the management of the network in my place... So given what I read on
telegram mailing lists, I wish you good luck...
Best regards,
Ludovic Vuillermet - F5PBG
Coordinator of 44.151
Le 17/07/2022 à 12:50, F4HIN via 44net a écrit :
> Hello
> I'm going to tell you a story that does not makes me laugh at all.
> I am part of an nonprofit ISP in France.
> This ISP offers internet access, but also BGP tunnels to announce your own IP on the internet.
>
> Some time ago, by several discussions, I found that a person member of the association and not ham had an allocation /24 Hamnet announced via its own AS via the AS of the association.
> Afterwards, after several information gathering, I noticed that this person was using it to propose hosting of small virtual machines and was allocating a Hamnet IP on these hosted VM.
> I warned this person that he did not have to have a Hamnet block, and that he should not do this type of use since he is not a ham
> His answer was clear "it's free, and I don't care".
>
> In reality, after searching on the AMPR portal, this block was assigned to a ham. This ham is the national Hamnet coordinator of a country, and the person using and misusing it is none other than his son who is not a ham!
> I did not say anything until now, out of respect for the national coordinator.
>
> Today, there is a member of the association who complains about receiving scans from a Hamnet IP belonging to the block used by the non-amateur.
> jul/15/2022 0l:02:56 system, error, critical login failure for user root from 44.151.129.214 via ssh
> jul/15/2022 0l:02:56 system, error, critical login failure for user msfadmin from 44.151.129.214 via ssh
> jul/15/2022 0l:02:57 system, error, critical login failure for user root from 44.151.129.214 via ssh
> jul/15/2022 01:02:57 system, error, critical login failure for user root from 44.151.129.214 via ssh
> jul/15/2022 0l:02:57 system, error, critical login failure for user postgres from 44.151.129.214 via ssh
> jul/15/2022 01:02:58 system, error, critical login failure for user service from 44.151.129.214 via ssh
> jul/15/2022 01:02:58 system, error, critical login failure for user vagrant from 44.151.129.214 via ssh
> jul/15/2022 01:02:58 system, error, critical login failure for user admin from 44.151.129.214 via ssh
>
> To summarize, this person:
> - Has a hamnet block without being a ham radio operator,
> - Has obtained a legitimate hamnet block from another amateur radio operator,
> - makes a "commercial" use of it by assigning IP to VMs for clients or friends of his,
> - Let the VMs get drilled and scan/hacked with a hamnet IP.
>
> I think it's time to set the record straight, stop assigning blocks to people who use them for commercial or non-amateur use.
> What do you think about it?
>
> --
> Gary
> F4HIN
> _______________________________________________
> 44net mailing list --44net(a)mailman.ampr.org
> To unsubscribe send an email to44net-leave(a)mailman.ampr.org
Hello
I'm going to tell you a story that does not makes me laugh at all.
I am part of an nonprofit ISP in France.
This ISP offers internet access, but also BGP tunnels to announce your own IP on the internet.
Some time ago, by several discussions, I found that a person member of the association and not ham had an allocation /24 Hamnet announced via its own AS via the AS of the association.
Afterwards, after several information gathering, I noticed that this person was using it to propose hosting of small virtual machines and was allocating a Hamnet IP on these hosted VM.
I warned this person that he did not have to have a Hamnet block, and that he should not do this type of use since he is not a ham
His answer was clear "it's free, and I don't care".
In reality, after searching on the AMPR portal, this block was assigned to a ham. This ham is the national Hamnet coordinator of a country, and the person using and misusing it is none other than his son who is not a ham!
I did not say anything until now, out of respect for the national coordinator.
Today, there is a member of the association who complains about receiving scans from a Hamnet IP belonging to the block used by the non-amateur.
jul/15/2022 0l:02:56 system, error, critical login failure for user root from 44.151.129.214 via ssh
jul/15/2022 0l:02:56 system, error, critical login failure for user msfadmin from 44.151.129.214 via ssh
jul/15/2022 0l:02:57 system, error, critical login failure for user root from 44.151.129.214 via ssh
jul/15/2022 01:02:57 system, error, critical login failure for user root from 44.151.129.214 via ssh
jul/15/2022 0l:02:57 system, error, critical login failure for user postgres from 44.151.129.214 via ssh
jul/15/2022 01:02:58 system, error, critical login failure for user service from 44.151.129.214 via ssh
jul/15/2022 01:02:58 system, error, critical login failure for user vagrant from 44.151.129.214 via ssh
jul/15/2022 01:02:58 system, error, critical login failure for user admin from 44.151.129.214 via ssh
To summarize, this person:
- Has a hamnet block without being a ham radio operator,
- Has obtained a legitimate hamnet block from another amateur radio operator,
- makes a "commercial" use of it by assigning IP to VMs for clients or friends of his,
- Let the VMs get drilled and scan/hacked with a hamnet IP.
I think it's time to set the record straight, stop assigning blocks to people who use them for commercial or non-amateur use.
What do you think about it?
--
Gary
F4HIN
Hey,
I am wondering who I need to contact to move my request for ip space along.
AddedNetworkWaiting for
2022-06-02 07:58:15 44.135.0.0/24 coordinator
73,
VE7OOT - Clayton
Hello all,
So I have been assigned a block of IPs and have successfully created a gateway. I am able to pass traffic trough it as expected and it works as one would expect. However...
My intended use case for amprnet includes a lot of VOIP traffic, which as we all know is heavily dependent on latency and bandwidth. I am currrently utilizing the IPIP tunnel approach to connect my gateway into the system.
My questions are,
1. If I deploy my VOIP services on 44Net with my current configuration, what are the pitfalls?
2. If I announce my gateway via BGP will my throughput then be limited to uscd gateway, or will it be based on my connection speed?
3. I know some vpn capabilities have been introduced into the system, I presume that my connection will then be rated based on the connection at the VPN server location.
Thank you so much! I appreciate the opportunity given here to learn and expand my knowledge.
73,
de KC2IDB
Hello,
Maybe someone can help me with below mentioned problem:
I am starting amprnet net with that ampr-ripd using a script bellow
#! /bin/bash
# dotun.sh script written by N1URO on June, 2013
AMPRIP='44.177.10.10'
IPMASK='255.255.255.255'
HOST="medvidek.ddns.net"
COMMIP=`host $HOST 2>/dev/null | head -n 1 | awk '{print $4}'`
AMPRSERVER='169.228.34.84'
echo $COMMIP
modprobe ipip
echo "1" > /proc/sys/net/ipv4/ip_forward
ifconfig tunl0 $AMPRIP netmask $IPMASK
ip tunnel change ttl 64 mode ipip tunl0
ip link set dev tunl0 up
ifconfig tunl0 multicast
/usr/sbin/ampr-ripd -t 1 -a $COMMIP -i tunl0 -p pLaInTeXtpAsSwD -f wlan0
-v -s -r
ip route add default via $AMPRSERVER dev tunl0 onlink table 1 src $AMPRIP
ip rule add from 44/8 pref 1 table 1
ip rule add to 44/8 pref 1 table 1
exit 0
And it worked well but now (and sometimes) I cannot receive packets from
that
AMPRSERVER to my tunl0 device on udp port 520 which is open (see below):
root@raspberrypi:/usr/sbin# netstat -lntup | grep 520
udp 1152 0 0.0.0.0:520 0.0.0.0:* 14076/ampr-ripd
and:
root@raspberrypi:/usr/sbin# ifconfig tunl0
tunl0: flags=4289<UP,RUNNING,NOARP,MULTICAST> mtu 1480
inet 44.177.10.10 netmask 255.255.255.255
tunnel txqueuelen 0 (IPIP Tunnel)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 35280 bytes 9295234 (8.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Port 520 is also opened in net router and using:
# tcpdump -i wlan0 port 520
I cannot see amprnet sevrver response.
TKS/73 Libor, sysop of node OK2PEN-5
Hello list,
maybe someone can help me and set a route entry in the RADB,
or knows someone who could help me?
I would like to route a /24 on the internet and for this I need the
entry.
Thanks a lot
DO7IC Christoph
Hi i am seeking advise on what route i should take to setup a AMPRNet GW
on my existing network.
Already have a /25 subnet on 44Net.
Right now i have the Archer 2600 as main router will all my wired and
wifi devices
with 4 access points to cover everything. I have lots of IoT devices,
camera, IP phones, servers etc. over 100 devices.
I am planing to set VLAN for IoT, IP-phone, Wifi Home, Wifi Guest,
Server and hardwired PC and NET44.
Here the possible combinations Main Router and AMPRNet GW.
1. TPLINK Archer 2600 as Main router with Ubiquiti EdgeRouter in the
DMZ for Net44
2. TPLINK Archer 2600 as main router with Mikrotik Router in the DMZ Net44
3. Ubiquiti Edgerouter as main router with a VLAN and Tunel on AMPRNet.
4. Mikrotik router as main router with a VLAN and Tunel on AMPRNet
What is the best one?
Any suggestions are welcome
--
*/73's de VA2DG/* */Daniel/*
Email: va2dg at va2dg dot ca
Hello 44Net -
I'm incredibly pleased to share that ARDC is seeking a Director of
Technology (Tech Director). It's a much needed position at ARDC!
This person's job will be to develop vision for and lead all of our
technology efforts. These include:
* general SysAdmin (with an existing service provider),
* grants management software development (with an existing service
provider) and
* IPv4 network modernization and management.
In addition to having solid technical knowledge and being an excellent
manager, this person must also be an excellent communicator – able to
write policy, wrangle volunteers, and manage open source technology
development that includes both volunteers and contractors. This role
will serve as the technical liaison to the ARDC Board of Directors and
report to the Executive Director.
Some important notes about this role:
* The ideal candidate is a team player and team builder, able to
identify requirements and expertise necessary for each of the above
areas. We don’t expect one person to be able to do it all, but to define
and build our technical capacity.
* Experience and history with amateur radio and the internet is
required. Many of the people we work with, projects we take on, and
communities we make grants to are rooted in amateur radio, which has a
long history and legacy.
* This role is a hands-on job. Our expectation is that this person can
manage our existing contractors and volunteers, while also participating
technically.
For a host of legal and administrative reasons, candidates must be
located and legally able to work in the US.
Full job posting and application instructions can be found here:
https://ardc.applytojob.com/apply/bhhwDEgfza/Director-Of-Technology
Please share with people who you think would be a good candidate, and
feel free to ask any questions that you may have.
Many thanks,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
Hello All,
I am new to AMPR NET and I am trying to understand how to connect to AMPR NET from OPEN VPN. I am not sure if I have OPEN VPN correctly configured yet. If someone could please provide some basic setup and instructions how to connect to AMPR NET from OPEN VPN. Thus far I have searched the web and have not found much info besides configuration errors in OPEN VPN that others have encountered.
1. Can anyone please let me know what message I will receive on the OPEN VPN to let me know it is working properly.
2. And once OPEN VPN is configured correctly how do I connect to the AMPR NET?
3. Will I need any kind of 44 address to access the AMPR NET from OPEN VPN or can I still explore AMPR NET just thru the OPEN VPN?
thanks in advance,
Thomas Fuller
KE4QCM
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
Chris
For our routing we now have our Static IP address from T-Mobile 5G.
It is: 162.191.104.176
We have tried the Unbuntu Linux info but have had no success for
the IPIP tunnel.
Do you need any further information as the encap(date).txt does not show
our allocation: 44.63.63.128/26 in the encap file?
Previous Email ...
C
44.63.63.128 /26 might be non listed.
We are not up yet.
M
K7MDI
While these might not fit ham radio, is there anyone one this list
familiar with these
who can give me the difference between the sc model and the sc+.
Thanks
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
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
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
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?
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
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
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
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
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
Hi all,
I tried to post a message on "44ngn(a)mailman.ampr.org", but I received a
NDR. I think it may have something to deal with recent crash/migration
of the mailman server.
It seems the same occurs for "44net-fr(a)mailman.ampr.org"
Kind regards, 73 de TK1BI.
-------- Message transféré --------
Sujet : Undelivered Mail Returned to Sender
Date : Sun, 24 Apr 2022 09:40:27 +0100
De : Mail Delivery System <MAILER-DAEMON(a)mailman.ardc.net>
Pour : t.ottavi(a)bc-109.com
This is the mail system at host mailman.ardc.net.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<44ngn(a)mailman.ampr.org>: mail for mailman.ampr.org loops back to myself
All,
I starting to like what happened here a little better. I'm now subscribe to this mail list more correctly in that I have a login and 'profile.'
Had to unsubscribe and re-sub to the 44Net here: https://mailman.ardc.net/mailman3/postorius/lists/ after creating a profile (a new login).
Now I am able select digest/no digest and a few other options.
I also have a few as in several mail lists on Groups.io and find it quite useable. But what really defines a usefulness of a list has more to
do with user participation in sharing of their knowledge in a useful manner. A clean and clear user interface can help with that. Also a bad
UX interface can wreck that experience.
73,
David
--
David Billsbrough -- Amateur Radio Callsign: KC4ZVW
Chuluota, Florida * grid square: EL98kp * https://www.kc4zvw.us/
ARRL * AVR * BeagleBone * FreeBSD * Linux * PICmicro * RASPI * TAPR
About a month ago (maybe slightly more now) my gateway stopped working
correctly. It had been running without issues for about a year.
I'm using a Ubiquity erX running ampr-ripd, using Marius's directions
on the wiki. (BTW, ampr.org looks to have a php issue at present)
The erX was connected directly to my modem. Since then I have rebuilt
the setup a few times after it stopped working correctly. Currently I
have two erX's setup. Modem -> erX (DNAT protocol 4 to LAN IP) -> AMPR
erX running ampr-ripd. This way I can mess with the AMPR settings
without annoying the rest of the household!
On the AMPR erX I have 729 routes showing.
44.68.180.14/32 is my tunnel IP
44.68.180.1/28 is erX eth port
traceroutes to these two seem to work correctly.
traceroute to 44.68.180.1 (44.68.180.1), 30 hops max, 60 byte packets
1 gw.k1ymi.ampr.org (44.68.180.1) 159.637 ms
But to 44.68.180.2 & 3 (linux box & JNOS)
I have '-a 44.0.0.1/8' in the ampr-ripd shell script. I have also tried
adding my /28 in there too.
If I have my subnet in the ampr-ripd config the traceroutes try and go
through n2nov's gw in a loop.
Public traceroute
<snip>
13.|-- 132.239.255.50 0.0% 4 145.4 145.4 145.3 145.6 0.1
14.|-- ??? 100.0 4 0.0 0.0 0.0 0.0 0.0
15.|-- 44.68.180.1 0.0% 4 235.1 243.3 235.1 261.6 12.3
16.|-- 162.247.76.189 75.0% 4 190.9 190.9 190.9 190.9 0.0
17.|-- 44.68.180.1 75.0% 4 275.8 275.8 275.8 275.8 0.0
18.|-- 162.247.76.189 0.0% 4 228.6 227.1 224.1 229.6 2.5
19.|-- 44.68.180.1 75.0% 4 324.7 324.7 324.7 324.7 0.0
20.|-- 162.247.76.189 75.0% 4 273.7 273.7 273.7 273.7 0.0
21.|-- 44.68.180.1 75.0% 4 341.9 341.9 341.9 341.9 0.0
22.|-- 162.247.76.189 75.0% 4 298.0 298.0 298.0 298.0 0.0
23.|-- 44.68.180.1 75.0% 4 391.8 391.8 391.8 391.8 0.0
24.|-- 162.247.76.189 75.0% 4 338.0 338.0 338.0 338.0 0.0
25.|-- 44.68.180.1 75.0% 4 449.6 449.6 449.6 449.6 0.0
26.|-- 162.247.76.189 75.0% 4 380.3 380.3 380.3 380.3 0.0
27.|-- 44.68.180.1 75.0% 4 480.6 480.6 480.6 480.6 0.0
28.|-- 162.247.76.189 75.0% 4 455.0 455.0 455.0 455.0 0.0
29.|-- ??? 100.0 4 0.0 0.0 0.0 0.0 0.0
from yo2tm's nettools page
traceroute to 44.68.180.3 (44.68.180.3), 30 hops max, 60 byte packets
1 tun.k1ymi.ampr.org (44.68.180.14) 160.011 ms
2 *
3 tun.k1ymi.ampr.org (44.68.180.14) 209.015 ms
4 *
5 tun.k1ymi.ampr.org (44.68.180.14) 245.680 ms
6 *
7 tun.k1ymi.ampr.org (44.68.180.14) 290.880 ms
8 *
9 tun.k1ymi.ampr.org (44.68.180.14) 331.616 ms
10 *
11 tun.k1ymi.ampr.org (44.68.180.14) 355.260 ms
12 *
13 *
14 *
15 *
16 *
17 *
18 *
19 *
20 *
21 *
22 *
23 tun.k1ymi.ampr.org (44.68.180.14) 565.771 ms
24 *
25 tun.k1ymi.ampr.org (44.68.180.14) 629.763 ms
26 *
27 tun.k1ymi.ampr.org (44.68.180.14) 661.471 ms
28 *
29 *
30 *
If I remove my subnet the traceroute goes nowhere.
Does anyone have a suggestion as to what I am missing ??
73 Andrew, K1YMI
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
>
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
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
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
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
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
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
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
Hi:
The March 2022 issue of the ARDC Newsletter is now online at https://www.ampr.org/?na=view&id=18. Stories include:
$250k grant will enable engineers, researchers, and students better visualize electromagnetic fields
44Net assessment under way
ARDC working on Code of Conduct - give us your thoughts!
ARDC attends (virtually) the QSO Today Virtual Ham Expo
Come see us at Hamvention
If you’re not on the mailing list and would like to be, go to https:/./www.ampr.org/subscribe-to-the-ardc-newsletter/
73,
Dan Romanchik KB6NU
Communications Manager
Amateur Radio | Digital Communications (ARDC)
858-477-9903, ampr.org
Hello,
Just got started on AMPR 44Net. Currently I have a /28 block and using Raspberry Pi 4 as my IPIP gateway at home OTH. My set up is Verizon FiOS > Verizon Router (for all none Ham stuffs) > DMZ from Verizon router to 192.xx.xx.144 (my Raspberry Pi gateway).
Raspberry eth0 is 44.xx.xx.1 as gateway and eth1 is 44.xx.xx.14 as tunl0 for my Ham stuffs. My eth1 is connected to a 16 ports Ethernet switch to supply the connections to all my Ham stuffs.
So far everything is working well. I was able to request an IP in the range of 44.xx.xx.2 – 44.xx.xx.13 no problem. Later a friend will help me setting up a Mikrotik router, I just had to order one first. For right now Raspberry pi is what I will be using.
I have some questions that I was not sure or could not really find the answer to specific questions.
Can I move my gateway over to VPS somewhere? Or the VPS setup is for the larger block not for individual home use.
If I could do this using VPS then I could rent one up, no problem. I would also need some sort of the instruction or guidance on how to set this up using VPS service instead of a Raspberry Pi at home QTH.
The instruction I found is more like the set up for /24 BPG type of thing. I do not have a use for that many IP addresses.
Another question is I have 2 blocks of addresses, obviously they were on a different subnet. Could I use one Raspberry Pi gateway, one gateway address? If that is possible, how do I add the 2nd block of IP range to my existing Raspberry Pi gateway setup or later on Mikrotik box?
73, Kit W3KIT/ HS0ZOE
Sent from Yahoo Mail on Android
Ruben, et. al, you can sign in with _any_ gmail.com <http://gmail.com/> credential. I’m sorry that this is the only option at the moment, but working on getting some more public access of sorts.
> Jeremy, with which account should we log in? Because we are asked to log into the metabase.
>
> 73
>
> Ruben ON3RVH
Hello all, I’m sorry to escalate this back to the list, but I’d like to report that there is still significant commercial abuse of AMPRNet allocated subnets in violation of the AMPRNet Terms-of-Service and nothing appears to have been done about it, despite my repeated attempts to raise the issue with the abuse(a)ampr.org <mailto:abuse@ampr.org> mailbox.
There are some 260 Helium Hotspot miners using the address space 44.144.124.0/23 to earn monetary rewards on the Helium cryptocurrency blockchain. While I am a fan of Helium and have managed to make it my full-time job, I am not a fan of seeing the AMPRNet address allocations be abused this way.
Can we discuss this here, as a group?
73,
Jeremy
While the abuse concerns should be addressed off list, I think there
may be benefit from some basic discussion about this network. I'd be
willing to bet most are unaware of this network, that it mostly uses
LoRA modulation to build a decentralized network for slower speed data
applications.
I feel there is a good amount of overlap to what we do in ham radio
and there could be things learned from it.
I'd be interested in knowing who is using the helium network (package
delivery folks I'd assume, among others) and what light weight
protocols and data they use.
A few years back someone at a DCC meeting did suggest the concept of
just such a network for the internet of things. And there have been a
few papers on LoRA.
I'm not interested in the crypto aspect of the network nor does that
fit the discussion here. But if the hardware entry cost was lower or
there was a way to build your own gateway I'd probably be doing that.
Pity there isn't enough of density of interested hams locally to do
what they are doing.
So is there anyone else doing things with LoRa chipset enabled
hardware with dialup speed applications in or out of ham radio.?
Today our external IP for the IPIP tunnel towards 44.137.0.0/16 has changed from 213.222.29.194 to 145.220.78.2
It appears that some stations have configured this statically, so it has to be changed.
(of course those that use the RIP transmissions from AMPRGW have no issue with this)
Rob
To all.
I've recently been duly scolded for soliciting $ for my DoppSite program,
which is a big no-no here on 44NET.
I'm actually not soliciting $... the program is 100% free... but the
description on the website is very old... and it does mention getting a
custom version for a sum of $.
That description is WRONG... the program is FREE... if you click the
download link, it won't ask you for any $... try it...
===========
Sorry for the confusion... a lengthy explanation follows... but I guess I
better provide it...
At one time ( many years ago ) I had a DEMONSTRATION version of that program
that was FREE, but it only generated DF bearing lines that were one mile
long.
I gave that away "for free", to promote the REGULAR ( commercial ) version,
which I tried to sell ( I think ) for $ 99, and that one had DF bearing
lines 25 miles long.
That REGULAR version plotted at a "fixed" DF location that could NOT be
changed... the customer had to specify that location, when ordering it.
I did that to prevent s/w piracy... so the REGULAR program couldn't be
copied and used at another DF site, just to dodge the $99 fee for the second
site.
Each REGULAR version was "hand carved" for a specific LAT / LONG, so it
would be useless at another DF location.
============
No-one ever responded to that, so a few years later I just upgraded the DEMO
version to display a 25 mile DF bearing line... and gave it away "for
free"... but I never updated the website text that described it.
By that time, I had given up hope that anyone would pay for it... in fact,
it seemed no-one was even looking at it, so I had no reason to update the
text information.
============
>From time to time, I would run into someone who MIGHT have an interest in
that technology, so I would send them a link to the download, so they could
try it.
I figured they better look at the BEST version of that program... that's why
I upgraded it to 25 miles... and that's what you will get NOW, if you
download, install and run it.... for FREE.
============
I've also been chastised for not offering the source code, and embracing the
"open source" model of software...
I'm not averse to sharing the source code, but it's written in VisualBasic 6
which is an obsolete language, no longer supported by MicroSoft.
Despite that, some people still write code with it, and it runs basically on
any PC machine from Windows 95 to Windows 10.
In the spirit of full disclosure, I've zipped the folder containing ALL the
Doppsite_Demo ( VB6 ) source code files, and uploaded it to my website for
others to get...
You will find it HERE :
www.silcom.com/~pelican2/DoppSite_Demo.zip
16 megs zipped, 25 megs unzipped.
=============
I've got more to say, but this is plenty for one day...
I'm not trying to make any $ on this, I'm retired and ( thank God ) I don't
need the $... I'm not rich, but I have enough.
Speaking for myself, I want to see someone create a DF network... even a
simple one... just to prove this technology works...
I won't explain why I've developed it, ( that's a whole other story ) but
it's been a passion of mine for many years...
I've done as much as I can do "alone"... I hope to meet people here ( on
this forum ) who aspire to make DF networks, but who lack the technology to
do it... or even a plan for it.
=============
I've already got almost all the technology for it, and I'll share it... for
folks that are serious about it... I'm 70 YO and it's not doing me any good
sitting here...
This DoppSite program is the first ingredient in such a network... and the
people on this forum are pretty sharp, I hope they can see the potential it
offers...
They offer grants here also. I don't want or need one, but someone making a
network might... I can offer a lot, but I can't offer everything.
Enough for one day... thanks again folks.
Bob S.
Just reminder that the Next ARDC Community Meeting is this Saturday:
• DATE: Saturday, 29 January 2022
• TIME: 1800 UTC (10am PST / 1pm EST / 7pm CET)
• PLACE: Zoom (see Zoom info below)
Topics will include:
• Introduction of new GAC and TAC members
• Looking back at 2021
• Looking ahead to 2022
• Questions from our attendees.
This meeting is open to all interested parties, so please tell your friends!
---------------------------------------------------------------
Zoom URL: https://us02web.zoom.us/j/87882963306?pwd=aXdpY3B1cmFwWlNSVDJFMkpLanIyQT09
Meeting ID: 878 8296 3306
Passcode: 72396
To join by phone, go to https://us02web.zoom.us/u/kcXKMi0QGv to find your local phone number.
73,
Dan Romanchik KB6NU
Communications Manager
Amateur Radio | Digital Communications (ARDC)
858-477-9903, ampr.org
Marius,
This would only apply:
* if there were a malicious node on AMPR sending as 44.0.0.1
* someone "accidentally" configured RIP to broadcast routes on their AMPR interface (though there likely won't be AMPR-routes here and not 44.0.0.1; but this could wipe our tables with a misconfigured SNAT rule lying around)
And yes indeed, I currently use the 2 rules - similar to what you mentioned, and you know I'm ever grateful you made sure ampr-ripd works with it!
It will also ensure that a u32 rule works as ampr-ripd does not "pull the route packets off the wire". ;-)
I had to upgrade my QTH router/AMPR gateway to OpenWrt 20.04.1 running on an x86_64 (I just cross-compiled with the SDK to the musl-based C running on it), so I have some more CPUs to work with for more firewall, logging, IDS/IPS, etc. now.
73,
- Lynwood
KB3VWG
----
Excuse the OpenWrt Syntax:
config rule
option src 'wan'
option name 'Allow-AMPR_IPENCAP'
option family 'ipv4' option proto '4'
option ipset ' ipipfilter'
option target 'ACCEPT'
config rule option target 'ACCEPT'
option proto 'udp' option dest_port '520' option name 'Allow-AMPR_RIP'
option family 'ipv4'
option src 'amprwan' option src_ip '44.0.0.1' option src_port '520'
option dest_ip '224.0.0.9'
To all.
This is a long message, apologies, hope it doesn't break any forum rules....
but it's full of worthwhile information on this topic.
===========
This message will explain how you can create your own "DF plotting" website,
just like the one shown in my YouTube video... and run it on your own PC...
for free.
( it has a TEST mode that can run without any DF hardware attached... that's
what is shown in the video )
===========
For those who haven't seen the YouTube video, it is HERE :
https://www.youtube.com/watch?v=GdJqKNpWG5c
That video has now received 60 views, and 45 of those were done after I
announced it here on this forum.
The DF display shown in that video was generated by a VB6 program, running
here on my home PC. In fact, it's still running... right now.
It could form the foundation of an internet-linked base station DF network,
with one program installed and running at each DF site.
===========
The VB6 program in that video ( called DoppSite ) is FREE. and it's
available NOW, on my website.
Information about it is HERE :
http://www.silcom.com/~pelican2/PicoDopp/PICODOPP.htm#DShttp://www.silcom.com/~pelican2/PicoDopp/DD_MORE.html
NOTES for its installation and use on a PC ( NOTES = MsWord document, 1.1
Mb ) ) can be downloaded HERE :
http://www.silcom.com/~pelican2/PicoDopp/DoppSite_Notes.doc
============
The actual DoppSite program is available as a ( 1.5 Mb ) zipped download,
HERE :
http://www.silcom.com/~pelican2/PicoDopp/DoppSite_Demo_Install.zip
The program installs easily and simply... an installation "wizard" program
is provided, to automate the process.
Some error message will probably appear the first time the ( installed )
program runs, because it needs configuration info the be installed.
( Station LAT/LONG, COM port number, NETWORK port number... stuff like that
)
=============
Some of the links on that website are dead or out of date, but the ones
shown in this forum message are valid.
Some of the information also is out of date, the LIVE DEMO station is
dead... but more than 90% of the info is still valid.
The displayed DF bearing line is 25 miles long, but the website says it is
only 1 mile.... the website is wrong, but I never fixed it.
=============
This program accepts an RS232 input of Agrello Doppler DF messages at 4800
band, and generates a website that can drive a ( remote, internet-linked )
GoogleEarth display, as shown in the YouTube video.
It runs on a regular Windows PC and needs an RS232 COM port ( or equivalent
) and an Ethernet ( or equivalent ) network connection.
( The PC must be located at the DF site, to get the DF bearings from the
RDF... but in TEST mode, it can be anywhere )
The network connection must go to an internet Gateway computer with one
port ( at the PCs address ) configured for PORT FORWARDING, in the Gateway
computer.
=============
Some people might want to see this program... running... before they try it
themselves... and I don't mean a YouTube video, I mean the "real deal", on
a "live" GoogleEarth display.
If you want to see the program that is running ( in TEST mode ) on my own
computer here in California ( Santa Maria ) you can get a GoogleEarth
NETWORK LINK file from my website, HERE :
http://www.silcom.com/~pelican2/PublicIP.kmz
This file must be installed in GoogleEarth, it gives the GE display all the
info it needs to find and display my ( California ) station on your GE
screens. ( and it refreshes every 3 seconds )
Save this file somewhere easy to find ( desktop ? ) it will be a small KMZ
file, about 300 bytes, named "PublicIP.kmz"
Find the file on your computer, double-click it, GoogleEarth will start up
and you will see it has "installed itself" in the GE left sidebar PLACES /
TEMPORARY PLACES box.
Double click on the name in the GE sidebar box, ( PublicIP.kmz ) and GE will
"fly to" the DF station ( at my residence ) in California, near Santa Maria.
You will see a red bearing line, 25 miles long, rotating clockwise at 1 RPM,
moving every 3 seconds. ( it looks just like the video... but this is
LIVE... )
===============
Apologies again for the length of this posting... but there was a lot of
info to convey...
Best way to reach me is e-mail : pelican2(a)silcom.com
Or send a small e-mail message to my SMS on my cell phone :
8055983542(a)txt.att.net
Bob S. / WB6EYV
All,
I thought on some security matters of AMPRNet; and one that could not be mitigated easily was:
* even if you firewall IPENCAP, how to block others except AMPRGW from sending routes to port 520/udp
Someone mentioned previously they saw a MAC that was a hash that contained the outer SRC IP; but after years, I cannot find an OS Kernel that produces it.
I believe have a solution, it required some hexadecimal calculations (see: http://www.stearns.org/doc/iptables-u32.current.html). Using the u32 iptables module for those who can (and a compatible module on on other systems), we need to merely find in the bit/byte positions in the packet:
Outer Header:
* the IP of AMPRGW (0xa9e42254)* Protocol type IPENCAP (IP Protocol No. 4) (0x04)
Inner Header (add 20 bytes to the offset of the first header):
* SRC IP 44.0.0.1 (0x2c000001)
* Protocol UDP (0x06)* UDP - port 520 (0x0208)
I believe this should read as an iptables rule like:
iptables <foo> -m u32 --u32 "12&0xFFFFFFFF=0xA9E42254 && 6&0xFF=0x04 && 32&0xFFFFFFFF=0x2c000001 && 26&0xFF=0x06 && 212&FFFF=0x0208" -j ACCEPT
My question: has anyone already calculated these positions and values or tested before?
I didn't want to have to "reinvent the wheel"...but you can just check my math now before attempting to implement.
73,
Lynwood
KB3VWG
Member W3PGC/K3ERA - APRS Coordinator / Co-SkyWarn Coordinator
All...
I am new to this forum... this topic might not be relevant, but here goes...
Does anyone here have any interest in remote reporting radio direction
finders ? ( RDFs )
I have developed technology for that, using Doppler direction finders..
suitable mostly for VHF and above.
==============
Explaining it takes some time, but I have posted a YouTube video of a single
DF station, running in TEST mode, located at my residence in California.
( video is about 1 minute long )
https://www.youtube.com/watch?v=GdJqKNpWG5c
The DF displays on any PC's GoogleEarth screen, if a suitable PLACEMARK is
installed for it.
( not sure about smart phone versions... )
It "refreshes" once every 3 seconds, and ( in TEST mode ) the DF bearing
line ( 25 miles long ) rotates clockwise at 1 RPM.
==============
This is a YouTube recording, but the real DF station ( still running in TEST
mode ) can be viewed "in realtime" if I provide a KML link for it.
Contact me if you want to see that... I will provide more info "off forum"
about how to install and use the link in GoogleEarth.
Bob Simmons / WB6EYV / pelican2(a)silcom.com
=============
Multiple DF stations can be plotted simultaneously, on multiple displays...
yielding a plot showing the approximate location of the "hunted" station...
literally, "in seconds".
If multiple hunters ( at many different locations ) are watching the same
plot, those "far away" can ignore it... but those "nearby" can jump on it
and maybe find the hunted station.
That's the general idea... a jammer can't even "cough" without revealing
their ( general ) location.
=============
I'll provide more details for those who enquire, I prefer a phone call, (
include your number, if you please ) because e-mails are slow to compose.
This is still in an "experimental" phase, but the basic technology is all
mature and solid...
All the pieces have been individually tested, time for a complete network to
be built.... and I can't do that alone.
More about me here :
www.picodopp.com
TNX DE WB6EYV
More info, sorry I don't know how to reply to posts on this forum yet. it's
not very obvious how that is done.
There have been more than a dozen views of the YouTube video. so there is
some interest in this.
I expected some e-mails sent to me but none yet. then I noticed my e-mail
address on the YouTube page is SPELLED WRONG !
Apologies, a friend posted that page for me, I have asked him to correct it
but in the meantime, this is my CORRECT address :
pelican2(a)silcom.com ( note pelican is spelled with ONE
"L", not two )
===========
I have also posted a PowerPoint show on my website ( 26 slides in it )
describing the proposed DF network, in fairly deep detail...
http://www.silcom.com/~pelican2/DF_Network.ppsx
Some of the info in it is obsolete, the remote control software to run the
Icom PCR radios ( written in Java ) is no longer valid...
Pity, it really worked great, but Oracle made some changes than rendered it
useless. There are alternatives, though.
All the remaining technology ( including the DF stuff and GE webserver )
remain valid.
=============
The program that created that YouTube display is free and available for
download on my website, here :
www.picodopp.com
The program is called DoppSite, you need a DF to actually use it, but there
is a built-in TEST mode that allows the simulation to be run on a Windows PC
without any DF or radio hardware.
( that is what the YouTube video shows )
TNX DE WB6EYV
Frankly, I feel this isn't the forum for you to sell your wares in.
73
On Saturday, January 22, 2022, 03:00:54 p.m. GMT-5, <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. Internet linked RDF networks (Robert Simmons)
----------------------------------------------------------------------
Message: 1
Date: Fri, 21 Jan 2022 13:10:39 -0800
From: "Robert Simmons" <pelican2(a)silcom.com>
To: <44net(a)mailman.ampr.org>
Subject: [44net] Internet linked RDF networks
Message-ID: <000401d80f0b$57a7eef0$06f7ccd0$(a)silcom.com>
Content-Type: text/plain; charset="us-ascii"
All...
I am new to this forum... this topic might not be relevant, but here goes...
Does anyone here have any interest in remote reporting radio direction
finders ? ( RDFs )
I have developed technology for that, using Doppler direction finders..
suitable mostly for VHF and above.
==============
Explaining it takes some time, but I have posted a YouTube video of a single
DF station, running in TEST mode, located at my residence in California.
( video is about 1 minute long )
https://www.youtube.com/watch?v=GdJqKNpWG5c
The DF displays on any PC's GoogleEarth screen, if a suitable PLACEMARK is
installed for it.
( not sure about smart phone versions... )
It "refreshes" once every 3 seconds, and ( in TEST mode ) the DF bearing
line ( 25 miles long ) rotates clockwise at 1 RPM.
==============
This is a YouTube recording, but the real DF station ( still running in TEST
mode ) can be viewed "in realtime" if I provide a KML link for it.
Contact me if you want to see that... I will provide more info "off forum"
about how to install and use the link in GoogleEarth.
Bob Simmons / WB6EYV / pelican2(a)silcom.com
=============
Multiple DF stations can be plotted simultaneously, on multiple displays...
yielding a plot showing the approximate location of the "hunted" station...
literally, "in seconds".
If multiple hunters ( at many different locations ) are watching the same
plot, those "far away" can ignore it... but those "nearby" can jump on it
and maybe find the hunted station.
That's the general idea... a jammer can't even "cough" without revealing
their ( general ) location.
=============
I'll provide more details for those who enquire, I prefer a phone call, (
include your number, if you please ) because e-mails are slow to compose.
This is still in an "experimental" phase, but the basic technology is all
mature and solid...
All the pieces have been individually tested, time for a complete network to
be built.... and I can't do that alone.
More about me here :
www.picodopp.com
TNX DE WB6EYV
------------------------------
Subject: Digest Footer
_______________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
------------------------------
End of 44Net Digest, Vol 11, Issue 11
*************************************
Greetings all,
I am sorry this is off topic but I will keep the noise low.
I have just purchased an MFJ-248 Analyzer and I wonder
if anyone would have a circuit diagram of this unit.
The has been a yellow wire cut off inside going to the top
panel I think and I am also looking for the information on
the rotary Frequency switch, I think it is a 6 position single
pole rotary but I am not sure it is a standard one.
Any info would be very welcome.
Regards ..... Peter ZL2BAU
Interested in what ARDC has been up to in 2021 and will be up to in 2022? Then join us for the next ARDC Community Meeting.
• DATE: Saturday, 29 January 2022
• TIME: 1800 UTC (10am PST / 1pm EST / 7pm CET)
• PLACE: Zoom (see Zoom info below)
Topics will include:
• Introduction of new GAC and TAC members
• Looking back at 2021
• Looking ahead to 2022
• Questions from our attendees.
This meeting is open to all interested parties, so please tell your friends!
See you on January 29!
---------------------------------------------------------------
Zoom URL: https://us02web.zoom.us/j/87882963306?pwd=aXdpY3B1cmFwWlNSVDJFMkpLanIyQT09
Meeting ID: 878 8296 3306
Passcode: 72396
To join by phone, go to https://us02web.zoom.us/u/kcXKMi0QGv to find your local phone number.
73,
Dan Romanchik KB6NU
Communications Manager
Amateur Radio | Digital Communications (ARDC)
858-477-9903, ampr.org
On behalf of the ARDC foundation, its staff, and community, we would like
to express our deep condolences to Brian's many friends and especially his
family.
We are sad to lose him. The benefactors of his work on amateur radio,
especially on packet radio and the Amateur Radio Internet, will long enjoy
the fruits of his labors.
Brian was an address coordinator for AMPRnet and his efforts were greatly
appreciated.
Good signals and Clear To Send ... 73.
*John Hays - K7VE*
📱+1-858-477-9904 <8584779904>
📠866-309-6077
PO Box 311
Kingston, WA 98346
*Grants Committee Chair and*
*Outreach Manager*
I am very sad to hear from about the passing of Brian.
I did not had many discussion with him. But they were always courtuous and he was ready to answer any dumb question I could trow in a very polite and friendly way.
He fighted till the end. And he lived his pation about digital radio communication to the end.
My sympathie to his family, friends, and every one that he touched and helped in the hobby.
We lost a pationate mind, lets hope his legacy still live for ever.
Pierre
VE2PF
________________________________________
De : Donald Gouin <donald.b.gouin(a)gmail.com>
Envoyé : 7 janvier 2022 14:07
À :
It is with sadness I inform you that Brian, n2uro died Tuesday evening Jan 4th.
I have spoken to his sister, and I will meet with her concerning his packet equipment, etc..
The arrangements are;
Friday Jan 14th
5 to 7 pm with a small service at 7 pm
Ahern Funeral Home
111 Main Street
Unionville, Ct
73 & stay safe
Don, k1cmm
860-918-1841
donald.b.gouin(a)gmail.com<mailto:donald.b.gouin@gmail.com>
It is with great sadness that I pass along the news that Brian Rogers N1URO
is now a silent key. He passed on Tuesday evening January 4th, 2022.
Brian was the author of the URONode packet radio software and past president
of the Eastnet Amateur Radio Network (https://www.eastnetpacket.org/). He
was an avid packet user and contributor to various software packages, not
just his own. He was also the AmprNet coordinator for the states of MA, NH,
VT, PA, MD, DE, CT, RI and ME.
Professionally his was an IT consultant and ran his company Network
Continuum Connecticut (https://www.nc-ct.net/).
He was a mentor to many who wanted to operate packet nodes or set up an
apmr.org station. He had a broad knowledge of many other node operating
systems, keeping nodes of all types running at his QTH. He was a wealth of
detailed knowledge and will be missed immensely.
Funeral arrangements are;
Friday Jan 14th
5 to 7 pm with a small service at 7 pm
Ahern Funeral Home
111 Main Street
Unionville, Ct
https://www.ahernfuneralhome.com/
Brian Webster N2KGC - President EastNet Amateur Radio Network
Re: Brian Rogers N1URO - Silent Key
Oh wow! He just put out a EASTNET 44 bull on the 3rd and on the 4th he was
gone.
Talking about walking right up to the line!
Brian was a good guy and shall be missed.
73, JohnF de WQ6N
>
Hi 44net! Today it's 2022, but due to Covid delays and other issues, it
took us until a few months ago to finish our 2020 tax returns. (Future
messages will talk about our 2021 and 2022 finances.)
Back in August, I wrote to 44net:
> The actual situation between ARDC and the IRS rules is far more
> complicated and interesting than what Pete describes. The loss of our
> 501c3 status is not at risk. We are still working out the details with
> our nonprofit tax lawyers. We will publish our first 990-PF (private
> foundation) tax return for 2020 on our website and to the 44net when we
> file it, and then we can talk with more certainty.
ARDC's 2020 tax return and audit are now published! I chair the Audit
Committee, which worked with our accountants and auditors to finalize
these documents. The Audit Committee is, by California law, composed of
people who are not paid by the org and have no financial stake in it.
Most of the work of the audit and tax returns was actually done by Rosy
and Bdale, our executive director and treasurer, and our accounting
firm, AAFCPA.com. All of our public financial information is visible at
this URL, with the 2020 info at the bottom of the page:
https://www.ampr.org/about/legal/
There were no irregularities in our audit. In 2020, ARDC had a great
investment year, funded a lot of worthwhile projects, improved our
internal operations, and learned a few surprises about nonprofit law and
accounting.
2020 was a great year for us, as it was for many steady investors. Our
$109 million in investments gained $22 million, about a 20% gain, with
our assets reaching $128 million. (We simply invest in the broad stock
and bond markets, using exchange-traded mutual funds, while keeping
multiple years' worth of cash available in case of downturns.)
In 2020, we ramped up our grant-making programs, as well as reducing the
volunteer board's workload by hiring Rosy, our first Executive Director
since Brian Kantor died. We spent only about $450,000 in expenses like
salaries, contractors, and taxes. We gave out about $3.2 million in
grants. Those grants are listed on our "Awarded Grants" pages:
https://www.ampr.org/grants/https://www.ampr.org/2020-grants/
They are also listed on pages 11, 15 and 16 of the 990-PF tax return.
These include more than $1 million in scholarships, half a million
dollars toward improved satellite transceiver modulation, and a variety
of both engineering projects and local infrastructure improvements.
2020 was the first year in which ARDC operated as a private foundation.
That is an IRS category for charitable nonprofits that make most of
their income in some way other than with donations from the general
public. The IRS is more suspicious of private foundations than they are
of public charities, since there are more opportunities for mischief
when a broad cross-section of the public isn't watching. Most of what
they look out for is self-serving behavior, like paying ourselves
outrageous salaries, or funding things using non-taxable money that
would pump up a related for-profit business.
Private foundations can't give money to individuals without filing a
detailed plan with the IRS. And to give money to organizations that
aren't US 501c3 nonprofits, there are more controls and hoops to jump
through. For example, when we funded DARC.DE, the German amateur radio
club, to upgrade various parts of the European ham infrastructure, we
and they had to go through a months-long paperwork exercise to prove
that DARC is the German "equivalent" of a US 501c3 public charity. We
have had to do a lot of consulting with lawyers and accountants to do
everything properly. We want to be able to fund ham activities,
education, and digital communications R&D throughout the world, not just
in the United States. And to also be able to help small ham clubs that
aren't organized as charitable 501c3 nonprofits.
Private foundations also pay a small "excise tax" on their investment
income -- about 1.39%. Yes, we're a charitable nonprofit, but Congress
has figured out how to tax us anyway. For 2020, that cost us $33,730.
And the biggest chunk of our $450,000 in expenses was when we accrued a
deferred expense of about $277,000 for the "unrealized" investment gains
that happened when the stock market went up so much. We won't have to
pay that tax until we actually sell the investments that went up, but
the deferred expense reminds us of what we will owe.
In 2020, we failed at one IRS requirement. Luckily, the rules give us
an extra year to make up for it, before we'd have to pay penalties.
That is the requirement that every private foundation has to spend or
give away 5% of the "fair market value" of its investable assets every
year. This has to be calculated on a cash basis (not by accrual), so if
a grant check was not cashed until 2021, it didn't count. This is often
mis-described as a requirement that we give away 5% of our "income" or
"investment returns", but actually a foundation owes it whether or not
it has any income or investment returns. Even if a private foundation
doesn't invest some of its assets, if they aren't directly using those
assets for charitable purposes, they have to give 5% of them away
annually. The whole idea is that to justify their income tax exemption,
nonprofit private foundations have to actually do good in the world,
spreading their wealth around, rather than just sitting pretty and
hoarding their assets. This is a laudable goal, but now see how it
applied to us.
Since our average investment assets throughout the year were almost $117
million, our "distributable amount" was 5% of that, or about $5.8
million. We only spent or gave out about $3.2 million, so that's how we
failed. That calculation is on pages 8 and 9 of our tax return. We
would have done better, but we didn't realize that we would be treated
as a private foundation in 2020; we thought we had another year as a
public charity. Having learned that in 2021, we believe that for 2021
we have met and exceeded that 5% requirement, and we expect to reduce or
eliminate our carried-over shortfall of spending from 2020.
Our ability to follow the 5% rule is only easy because we are not
treating our remaining IP addresses as an investment asset. Instead, we
are using them directly in our charitable works (including both
providing small numbers of addresses to hams, and accomplishing
scientific research using the other addresses via the Network
Telescope). If we did have to treat those addresses as an investment
asset, we would be required to spend 5% of their value every year.
Because the addresses we still have are 3x as many as what we sold off
in 2019, and the value of IP addresses is rising, the IRS would require
us to annually spend about 4x as much as we do today! That would
deplete all of our liquid assets within a small number of years, and
then require us to sell off a new 5% of our addresses every year, just
to create the cash to grant out 5% of their worth every year.
This is what I meant when I said back in August that our situation is
"complicated and interesting". It's a bit like the "use it or lose it"
nature of ham frequency band allocations. If we really didn't use the
IP addresses for charitable purposes, then we would be forced to
gradually lose them.
In summary, in 2020, ARDC had a great investment year, funded a lot of
worthwhile projects, improved our internal operations, and learned a few
surprises about nonprofit law and accounting. With what we learned in
2020, we expect to finish our 2021 audit and taxes much sooner -- in the
first half of 2022.
Any questions?
John Gilmore, chair, ARDC Audit Committee
Hi all,
(Here's my full post, one line disappeared in the previous one)
I'm thinking about building a GPS-disciplined 10 MHz reference
oscillator. Of course, I'd like to add some networking features to it :-)
NTP server is the most obvious, and is well documented.
But I'd like to be able to carry 10 MHz reference signal to various
locations in the shack over network cabling. My first idea is about
using existing converters for TV/SAT :
- RF to Ethernet passive couplers (a F connector tied to pins 1-2 of a
RJ45 connector, $1 on Chinese warehouses).
- RF to fiber adapters (such as those used in FTTH/CATV). But a first
look shows frequency range is 50-1000 MHz.
Anyway, I do not have any idea about whether it will work or not while
maintaining the reference/stability purpose of the 10 MHz signal.
Any suggestions ?
HNY & 73 de TK1BI
Hi all,
I'm thinking about building a GPS-disciplined 10 MHz reference
oscillator. Of course, I'd like to add some networking features to it :-)
NTP server is the most obvious, and is well documented.
But I'd like to be able to carry 10 MHz reference signal to various
locations in the shack over network cabling. My first idea is about
using existing converters for TV/SAT :
- RF to Ethernet passive couplers (a F connector tied to pins 1-2 of a
RJ45 connector, $1 on Chinese warehouses). Will it work at 10 MHz ?
Anyway, I do not have any idea about whether it will work or not while
maintaining the reference/stability purpose of the 10 MHz signal.
Any suggestions ?
HNY & 73 de TK1BI
Good day and I wish you all and Happy New Year 2022.
for the few of you still using encap.txt, I had and IP conflict and had
to change the ip of jnos.ve2pkt.ampr.org from 44.135.49.29 to 44.135.49.9.
--
Best 73's.
....Read you very soon...!!!
Internet E-mail: ve2pkt(a)gmail.com
AMPRNET E-Mail: va2om(a)jnos.ve2pkt.ampr.org
Packet Address: va2om(a)ve2pkt.#trv.qc.can.noam
Trois-Rivieres, Quebec, Canada
147.435 MHZ @1200Bps..........
DE: Jean, VA2OM / VE2PKT
I am attempting to get connected from VyOS, and I seem to have several
pieces in place, but I am not able to ping any hosts across any IPIP
tunnels.
I can ping amprgw.ucsd.edu across the public Internet. I have configured a
`tun44` interface. I have ampr-ripd running, and it receives updates every
five minutes. The resulting routes appear in my routing table, and if I do
`ip route get` on 44-net hosts, it shows them routing through my `tun44`
interface. But if I try to ping 44-net hosts or access them at all, I get
timeouts.
What might I be missing?
My gateway public IP is 155.138.247.113. My allocated subnet is
44.31.64.1/27.
I created a firewall group named ALLOW-ALL with a default rule set to
'accept' just to rule that out for troubleshooting.
Tunnel interface configuration:
tunnel tun44 {
> address 44.31.64.1/32
> description AMPRNET
> disable-link-detect
> encapsulation ipip
> firewall {
> in {
> name ALLOW-ALL
> }
> local {
> name ALLOW-ALL
> }
> out {
> name ALLOW-ALL
> }
> }
> mtu 1450
> multicast enable
> remote 0.0.0.0
> source-address 155.138.247.113
> }
ampr-ripd startup output:
root@vyos:/home/vyos# ampr-ripd -svd -i tun44
> Using metric 0 for routes.
> Using TCP window 840 for routes.
> Using routing table 'main' (254).
> Loaded 738 entries from /var/lib/ampr-ripd/encap.txt
> Max list size: 1000 entries
> Detected tunnel interface address: 44.31.64.1
> Interface detected: lo, IP: 127.0.0.1
> Interface detected: eth0, IP: 155.138.247.113
> Interface detected: tunl0, IP: 0.0.0.0
> Interface detected: tun44, IP: 44.31.64.1
> Assigned tunnel interface index: 5
> Local IPs:
> 127.0.0.1
> 155.138.247.113
> 44.31.64.1
> Using gateway 155.138.246.1 for direct 44net endpoints via interface eth0.
> Setting routes (738).
> Creating multicast RIP UDP listening socket.
> Setting up multicast interface.
> Waiting for RIPv2 broadcasts...
>
Broadcasts eventually start appearing.
Before I run ampr-ripd, here's the route I get for 44.0.0.1 — over the
public Internet:
44.0.0.1 via 155.138.246.1 dev eth0 src 155.138.247.113 uid 0
And I can ping 44.0.0.1 in this state.
After I run ampr-ripd, here's the route to 44.0.0.1 — over the tunnel:
44.0.0.1 via 169.228.34.84 dev tun44 src 44.31.64.1 uid 1003
And I can no longer ping 44.0.0.1 — it just times out:
vyos@vyos:~$ ping 44.0.0.1 interface tun44
> PING 44.0.0.1 (44.0.0.1) from 44.31.64.1 tun44: 56(84) bytes of data.
> ^C
> --- 44.0.0.1 ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 88ms
This is all on VyOS 1.3 equuleus (Debian buster), hosted at Vultr.
Any ideas, or other troubleshooting suggestions?
Thanks very much!
It would be most helpful if the amprnet BOD could post in writing an
official statement regarding using common secure communications (https. TLS
etc.) over the 44. IP network.
This email list is used for communications regarding the use of the IP
address space. I'm not asking about the use of encryption over part 97 RF
radio, just the 44 network IP address space. I am not aware of any portion
of the Part 97 rules that apply to the wired internet at large.
Everyone has an opinion, but it's time for the amprnet Board to clarify the
muddy waters around the use of the amprnet IP space and publish those rules.
Please!
73,
Kevin Walsh
W8KHW
>
> Thanks for sharing. I see this has been around a while, but I hadn’t run
into it myself yet.
Apple is currently doing something like this with IPSEC and IPv6 for iCloud
users; pretty much any iCloud user is always on a private VPN with all
their other iCloud devices. And there are commercial enterprise SD-WAN
products and cloud providers that offer a similar approach for SMBs and
branch offices. Azure and AWS offer almost exactly this between virtual
networks, data centers, and regions, down to the private ASNs.
It’s nice to see a project built on open standards for the express purpose
of playing with it and learning about it. Seems very much like something
44net could benefit from studying carefully.
From: KUN LIN <dnwk(a)linkun.info>
> To: "44net(a)mailman.ampr.org" <44net(a)mailman.ampr.org>
> Cc:
> Bcc:
> Date: Thu, 2 Dec 2021 18:48:49 +0000
> Subject: [44net] DN42 for 44net?
>
>
> https://dn42.dev/Home
>
> Just discover this new thing where it will create mesh networks and even
> BGP via VPN tunnels. This maybe an interesting way for 44net to considering
> implement.
>
> dn42 is a big dynamic VPN<
> https://en.wikipedia.org/wiki/Virtual_private_network>, which employs
> Internet technologies (BGP<https://en.wikipedia.org/wiki/Bgp>, whois
> database, DNS<https://en.wikipedia.org/wiki/Domain_Name_System>, etc).
> Participants connect to each other using network tunnels (GRE<
> https://dn42.dev/howto/GRE-on-FreeBSD>, OpenVPN<
> https://dn42.dev/howto/openvpn>, WireGuard<
> https://dn42.dev/howto/wireguard>, Tinc<https://dn42.dev/howto/tinc>,
> IPsec<https://dn42.dev/howto/IPsec-with-PublicKeys>) and exchange routes
> thanks to the Border Gateway Protocol. Network addresses are assigned in
> the 172.20.0.0/14 range and private AS numbers are used (see registry<
> https://dn42.dev/services/Whois>) as well as IPv6 addresses from the
> ULA-Range (fd00::/8) –
>
>
>
Another suggestion I'll make is that beyond support Dynamic DNS for
various use cases, to allow end users to manipulate thier own forward
and reverse DNS records and tie that functionality in with dynamic DNS.
--
Kris Kirby, KE4AHR
Disinformation Architect, Systems Mangler, & Network Mismanager
Hi all, I’d like the ARDC to investigate and possibly revoke the assignment for 44.144.50.0/25 due its use for commercial purposes.
I’m a long time member of the group here but I’m also heavily involved in the Helium radio-based blockchain. I’ve noticed three Helium “hotspots” or “miners” that are using this allocation. While I am personally a fan of Helium, I don’t think its use is permissible on the AMPRNet as Helium hotspots do earn monetary compensation for being connected to the Internet. As a responsible AMPR block recipient myself, I feel it’s important that we continue to honor the ARDC’s rules for the AMPR space, and this is one of them.
The hotspots in question are:
* zany-pecan-kitten at 44.144.50.71 (https://explorer.helium.com/hotspots/112en278X7KpSMfgH9JMnEfkfLSsi2osRjJ1mL…)
* petite-flint-bird at 44.144.50.73 (https://explorer.helium.com/hotspots/11bkMgWVDYSteuq1fLvowC9z4BVReQrXNGCq4F…)
* furry-pine-raccoon at 44.144.50.74 (https://explorer.helium.com/hotspots/112TRAzGUMNvEYEtHawWymZTA4cX9BWu9QFw1v…)
Sincerely,
Jeremy Cooper (KE6JJJ)
> A reply by the ARDC IT director specifically requesting that abuse reports be sent to abuse at ardc.net <https://mailman.ampr.org/mailman/listinfo/44net> <mailto:abuse at ardc.net <https://mailman.ampr.org/mailman/listinfo/44net>> and you decide to double down and list more potentially offending addresses publicly?
>
> Interesting approach.
>
> Ian VE7BST
Ian, I thought I was in a private conversation with Chris when I had replied. It wasn’t until I had already sent the message that I saw that the entire list was still CC’d. My apologies, but also a modicum of understanding is also deserved, too.
Hi, 44net!
Writing with a few updates that may interest you.
First, I’d like to introduce you to our Administrative Coordinator,
Merideth Stroh – KK7BKI. She comes from a family of hams and is helping
us with everything administrative. Please join me in welcoming her to
the team!
In advance of our upcoming board retreat in early December, Meredith and
I will be interviewing folks one-on-one about the future of amateur
radio and digital communications. If you would like to take part in one
of these interviews, you can sign up here:
https://calendly.com/ardc-rosy/30min
If you want to participate but can’t find a time listed, please reach
out and we’ll do our best to find a time that works. Note that we have
some times available in early December, but if you want your thoughts
brought to the board, please find a time by Dec. 2.
If so moved, you are also invited to apply to join either our Technical
or Grants Advisory Committees (GAC & TAC). Note that, for 2022, the role
of the TAC is going to change a little bit. In addition to focusing on
PoP development, we may also call upon TAC members to help evaluate
particularly technical in-progress grants. Learn more on our blog here:
https://www.ampr.org/now-accepting-applications-for-grants-advisory-committ…
Speaking of PoPs, we’ve been working on a plan to develop PoPs for the
address space, which incorporates a lot of the feedback and thoughts
we’ve heard on this list and through private mails from some of you.
When it’s in a better place to share (it’s so close!) I’ll do so. Thanks
for your patience on this – we’ve taken in a lot of info and are working
with volunteers to review, so it’s not a fast process, but it’s a
thorough one.
Last but not least, some of you have asked to see our 2020 tax return
(IRS Form 990-PF). You can see all our public financial documents here:
https://www.ampr.org/about/legal/
Specific links for the 2020 documents are:
* Audited financial statements:
https://www.ampr.org/wp-content/uploads/Amateur-Radio-Digital-Communication…
* 990-PF:
https://www.ampr.org/wp-content/uploads/Amateur-Radio-Digital-Communication…
Thank you for your patience here as well. As Bdale shared in an earlier
mail, with the extra time allotted for filing tax returns, many
accountants have been running behind this year, including ours. Here’s
hoping that we get this filed earlier next year.
As always, please don’t hesitate to reach out with any thoughts and
questions.
73,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
Hi
Does AMPRnet have any policy around allocating /24s to individual hams for
the purpose of experimenting with BGP/etc?
My local coordinator says this used to be a "yes, but you'd have to be a
club not an individual." However I note looking through AMPR allocations
there are some in e.g. 44.31 listed as educational/tinkering BGP. Which is
what I want to do. Should I be requesting in 44.31 instead of my country's
allocation?
Regards
Donald Gordon (ZL2IP)
I have been trying to configure the AMPRtunnel for a while without success. Could someone please point me to the right direction.
I am running Debian 11 with public IP. I have configured the public IP in the AMPR portal as gateway.
I am trying to follow this document https://wiki.ampr.org/wiki/Ubuntu_Linux_Gateway_Example
When I try to run find_password.sh in ampr-ripd-2.4, I am stopped at Waiting for RIPv2 broadcasts... and never retrieve a password.
Here is what I have done so far.
in /etc/network/interfaces, I added
auto ens3:1
iface ens3:1 inet static
address 44.26.0.168
netmask 255.255.255.248
Then I created ipip tunnel using following commands
ip tunnel add ampr0 mode ipip local 209.141.42.9 ttl 255
ip link set dev ampr0 up
ifconfig ampr0 multicast
ip rule add to 44.0.0.0/8 table 44 priority 44
ip rule add from 44.26.0.168/29 table 44 priority 45
ip route add default dev ampr0 via 169.228.34.84 onlink table 44
ip route add 44.26.0.168/29 dev ens3 table 44
Then, I run ampr-ripd -d -v -i ens3 to get the password in order to plug into lat command
ampr-ripd -s -i ampr0 -a 209.141.42.9-t 44 -p <SecretPassword>
However, the find_password.sh stopped at waiting for ripv2 broadcast. Here is the logs for command
Using metric 0 for routes.
Using TCP window 840 for routes.
Using gateway 209.141.42.1 for direct 44net endpoints via interface ens3.
Waiting for RIPv2 broadcasts...
Any idea on what am I doing wrong?
Thanks
Kun
Hi,
As I have heard, it is not allowed for ARDC to create route objects in
ARIN's IRR and for that reason, RADb is used.
I am just curious why this is the case?
(It seems in general, creating IRR objects is possible via IRR-online [1])
Best,
Nick
[1] https://www.arin.net/resources/manage/irr/userguide/
Hi list,
I hope I am not spamming this list; I would like to express my sinciere
gratitude to AMPR (everyone who made and makes 44/8 for hams possible)
and especially to Chris who helped me a lot in the process for a BGP
routable network.
Thank you for gifting me an enormous time sink.
It was always a dream of mine to connect directly to the "core" of the
internet, play around with BGP and, in some ways, completely independent
of an ISP. I had given up this dream long time ago until recently my
friend told me about AMPR. It's a privilege that hams are given the
opportunity to experiment with something that would otherwise be out of
reach for hobbyists, similar as radio would be without ham. (while the
same with IPv6 is 'somewhat' still accessible, /24 prefixes meanwhile go
for 15k and since this is the smallest for anything interesting [BGP,
AS], it's just out of reach for experimentation)
There are so many exciting things to play with. Subnetting the /24,
using /30 or /31 networks for example is something I knew in theory but
never really applied in that intensity because with RFC1918, there is no
need. BGP I knew in theory but setting up bird and seeing how a session
is established, a prefix is announced and watching via looking glass how
it propagates through the global interconnected network brings this to a
whole new level.
I am currently trying to implement a "real" multi homing setup. I have
two cheap consumer grade internet links: DSL and 5G. The latter one is
CGNAT. Normally there is no way to make anything useful out of this
(other than having a manual backup connection). For the first line, I
created an ipip tunnel, for the second one a wireguard (due to CGNAT)
and connect a third network over them. This network is now accessible
straight from the internet on two lines. Exactly as the internet was
originally conceived, the packets can now flow on either connection!
In next steps I would like to set up OSPF (or maybe iBGP?) and possibly
adding more tunnels to create realistic routing networks.
And further down, I'd like to see if I can find something interesting to
implement anycast. Maybe some spectrum sensing via RTL2832 at two
different locations accessible via the same address? Let me know if you
have any good ideas.
Nick, KM6RDV
This may be beyond the scope of some since I mentioned JNOS, but the
basics should be the same. I have been running the n2nov.ampr.org JNOS
system since the late 90s, but recently any emails that I send to GMAIL
and some other services are being rejected. The same happens when any
email is sent to me from those same commercial SMTP services. This is
all boiling down to the modern SMTP security functions are not part of
JNOS. It has been mentioned that I should use the Postfix on the CentOS
server that it sits on as it is already servicing various accounts that
I maintain for clients and amateur radio groups. If someone else is
using this arrangement already, I would like to see how you are doing it
and what the limitations are. I believe the Santa Clara group was going
to implement something like this a few years ago. Thanks in advance.
--
de N2NOV
n2nov(a)n2nov.ampr.org
n2nov(a)n2nov.#rich.ny.usa.noam
The upgrade to a 10Gb/s link to the gateway machine went ahead at 10:30pm last night (UK time), 2:30pm Pacific.
I am pleased to report that the upgrade was successful, we also took the opportunity to reboot the machine: previously it has been difficult to reboot the gateway machine as it messed up the switch it was connected to (the switch was configured with mirrored ports for the CAIDA telescope and a reboot stopped it working). The gateway machine is now connected to a different switch and I can reboot it without it causing any detrimental effects.
You can see the transition here: http://mrtg.portal.ampr.org
73,
Chris - G1FEF
—
ARDC IT Director
Web: https://www.ardc.net
FYI
The gateway machine at UCSD has been under a sustained DDOS attack now for over 24 hours, so if anyone is seeing heavy packet loss through the gateway, that’s why. The 1Gb/s interface is max’d out. You can view the interface stats here:
http://mrtg.portal.ampr.org
73,
Chris - G1FEF
—
ARDC IT Director
Web: https://www.ardc.net
All,
I see a slight increase in traffic inbound toward my /24 at my tunl0 interface (0.6 kbps to 1.1 kbps) - most still appearing to be blocked by my firewall. From netflow data, the majority of this traffic appears to be: TCP, GRE and pings.
73,
- Lynwood
KB3VWG
Hi all,
I'm looking to get back on the 44net after many many years. There used
to be a hamgate in Muskegon MI run by WB8I, and is also listed on the
AMPR.ORG site - however my several attempts to contact him have gone
unanswered. I also haven't heard anything on the radio local....
Does anyone have any information on a hamgate in the Muskegon / Grand
Rapids area in Michigan?
Any info is appreciated!
73
Chris KC8BAT
So I have a linBPQ node running on a Debian VM at Google and it's
working on my assigned public IP there. I found that while they can do
BGP announce of a 44 net subnet but it'd take a bit futzing around that
I'm reserving for if I can't do an IPIP tunnel from there.
My bpq32.conf has this for my IPGateway config
IPGATEWAY
# My Pub IP 35.209.142.98
# My Int IP 10.128.0.56
ADAPTER ens4
44ENCAP 10.128.0.56
IPAddr 44.46.15.1/24
IPPorts 1,2,3
NAT 44.46.15.5 10.128.0.56
****
and I have 2 firewall rules setup besides the ones I need for BPQ stuff
(telnet and AXIP links)
ACCEPT IP 169.228.34.84 all protocols
ACCEPT IP 0.0.0.0/0 IPIP
I'd think the 2nd one would cover everything I'd need but I decided to
go ahead and make one to accept anything from the 44net Gateway at
169.228.34.84 just in case.
Anyone else attempted anything like this? I know I could go setup
something with vultr but I'm trying to keep all my VMs in once place if
possible (and avoid a 2nd hosting bill)
--
--
Matthew Chambers, NR0Q
--
The content of this email is confidential and intended for the
recipient
specified in message only. It is strictly forbidden to share
any part of
this message with any third party, without a written consent
of the
sender. If you received this message by mistake, please reply to
this
message and follow with its deletion, so that we can ensure such a
mistake
does not occur in the future.
Please do not print this email unless it is
necessary. Every unprinted email helps the environment.
Hi all,
Some friends from south of France submitted the idea of a 5 GHz link
between France and Corsica. The distance is 200-250 km, mostly over the
sea. It's far longer than what I could see on HamNetDB, for example. But
it's shorter than WiFi world records (some of them attempted more than
10 years ago between Italy and Sardinia). I never attempted links longer
than 40km, so I don't have any experience. And we don't have any SHF
expert locally...
1/ Do you think a permanent and stable 250 km link over the
Mediterranean sea is doable ? Are some of you using such long links in 5
GHz ? If so, could you share your technical experience here ?
2/ Are there any people from Italy on this list ? Are there any
volunteers between Genova and Roma to attempt a link with the East coast
of Corsica ? If it works, would there be an interest in establishing a
permanent link ?
Thank you for your comments,
73 de TK1BI
Hi,
I often talked with French 44net guys, and it appears there's no current
forum or mailing-list for communications between us, without polluting
the world-wide 44net list.
A long time ago, I planned to create a dedicated mailing-list 44net-fr
on our mail server, but I never finished it, HI :-) The current project
of a link between Corsica and France shows the need of such a tool,
because private mails are becoming too bulky.
My primary idea was to create a group on groups.io.
As AMPR has now fundings and technical team, would it be possible to
host such a 44net-fr mailing-list directly at ampr.org ?
73 de TK1BI
If we've got a TAC working new possible opportunities for 44net, I
strongly recommend developing and deploying a Dynamic DNS (DDNS)
service, and extending the portal so that end users may edit thier own
DNS records.
--
Kris Kirby, KE4AHR
Disinformation Architect, Systems Mangler, & Network Mismanager
(Sorry for repost. Chris kindly informed me that my messages are empty.
I think it could be because GPG sig. Another attempt without it)
Hi,
I am aware there will be a slim chance for this to happen but having a
44net subnet directly routed would be super amazing. I am aware that
"normal" providers likely won't do this except for business customers
(at many $$$/months) and likely the subnet needs to be large (>=/24?)
I could imagine though that small providers may be up for it (as an
example, in a place I lived many years ago, I had a small provider; I
contacted the CEO directly and he immideately agreed to assign+route me
a /29 at no cost!).
Are there any known providers (US, California) who could route a 44net
subnet?
To everyone who has their 44 routed directly: How does it work for you?
Finally: The whole 44net is announed only by the UCSD gateway (as far as
I understand). Wouldn't it be great to improve the connectivity,
reliability, redundancy by having 44 announced by multiple people who
route their subnet directly and then forwarding them to the mesh network
via ipip? Is there a reason this is not done, other than nobody besides
UCSD volunteered ?
Thanks,
KM6RDV
(Sorry for repost. Chris kindly informed me that my messages are empty.
I think it could be because GPG sig. Another attempt without it)
Hi all,
I am new to 44net and I haven't found much about DNS. I have the
following questions:
1. In order to get traffic routed through the 44 gateway, does a forward
or reverse DNS entry need to exist? Does it need to satisfy certain
format/conditions? (from a technical standpoint, existance of reverse
would make sense as it's done in SMTP servers, but I don't know how this
information is queried by the gateway).
2. I run my own bind (also accessible over 44net). I'd love to handle my
DNS entries on my own (not least because every request on the portal can
take well over a year to be answered, at least for me). Is it possible
to request classless in-add.arpa delegation (RFC2317) for my subnet?
3. If the ampr.org domain is used, are there any requirements on the
format/hierarchy? Can it be a subdomain <myname>.ampr.org? Or does it
need to be <callsign>.ampr.org? Can all entries and hierarchy under this
subdomain be freely chosen?
4. Is there any way in the portal to keep track of DNS related
requests/messages as it is for subnets? I am not sure any more if, when,
what and who I have asked about DNS and I want to avoid sending the
request again if it's still "pending".
Thanks,
Nick