Is there anyone who might be able to help me with a DNS entry? I'm trying to replicate something over the weekend that I've been experiencing at home.
I sent a note to hostmaster(a)ardc.net last week but I'm sure whoever answers that has been tied up. Entry I'm looking for is:
wvgw.kc8qba.ampr.org ADD A 44.63.19.14
Thanks in advance,
-Steve
kc8qba
Hey Everyone,
* John (K7VE), Phil (KA9Q), and myself are at HamCation this weekend:
come see us at booth 186 in the North Hall and catch John's forum
today (2/9) at 3:30pm in CS3.
* Our first Community Meeting of the year will be on Saturday,
February 24, 2024 at 10am PST / 6pm UTC. For more details, subscribe
to our newsletter: https://www.ardc.net/about/newsletter/
Have a great weekend and 73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hey Everyone,
Our first Community Meeting of the year will be on Saturday, February
24, 2024 at 10am PST / 6pm UTC. For more details, subscribe to our
newsletter: https://www.ardc.net/about/newsletter/
<https://www.ardc.net/about/newsletter/>Hope to see you there!
73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Somehow the output of the API call must have changed over time. It now
includes a count value before the encap array data, which will lead to an
error when processing it with jq.
Please update wiki the page with a different jq filter, c.f. how I fixed
the script on our system. I am ignoring the count value.
root@host:~# diff -U1 get-encap.sh-orig get-encap.sh
--- get-encap.sh-orig 2024-02-01 11:24:31.725642496 -0800
+++ get-encap.sh 2024-02-01 11:24:53.421227002 -0800
@@ -24,3 +24,3 @@
curl -s https://user:key@portal.ampr.org/api/v1/encap > json-data.out
-cat json-data.out | jq -r '.[] | "route addprivate
\(.network)/\(.maskLength) encap \(.gatewayIP)"' >> encap.txt
+cat json-data.out | jq -r '.encap[] | "route addprivate
\(.network)/\(.maskLength) encap \(.gatewayIP)"' >> encap.txt
root@host:~#
Thanks, andreas K6OTT
Hey Everyone,
* Please join us in welcoming Bob Witte, K0NR, to ARDC's Board of
Directors! To learn more about Bob, check out our recent blog post:
https://www.ardc.net/bob-witte-k0nr-joins-ardcs-board-of-directors/
* The blog post announcing ARDC's 2024 Advisory Committee Members is
also live: check it out to learn more about our new members and see
who's continuing with us this year:
https://www.ardc.net/ardc-welcomes-new-committee-members-for-2024/
Have a great week and 73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hey Everyone,
ARDC will be atOrlando HamCation happening from Feb. 9 - 11. If you're
at the event, stop by our table and say hello. Also, be sure to attend
our Forum (Friday, 2/9, 3:30pm ET), where John Hays (K7VE) will be
presenting/New Adventures using TCP/IP on 44Net (AMPRNet) and an ARDC
Update/.
Have a great weekend and 73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hello to those the list,
I have a VPN server running on a VPS (OpenVPN Access Server). I also have
the packet software XRouter (a.k.a. XRLin) running on the VPS. Normally it
can get the routes from the amprnet RIP broadcasts.
The VPN server uses a tunnel to send packets to my client. In the server to
client direction it takes packets from the internet addressed to the static
WAN address and changes the destination address to the client's VPN address
- pretty standard stuff. The dnat results in the traffic being routed to
the VPN tunnel. The OpenVPN Access Server writes rules to NFTables in order
to handle the forwarding, dnat, etc.
XRouter is set up with its own tunnel - somewhat similar to JNOS. I have
added rules in NFTables to forward all transport protocol 4/encap packets
to the XRouter tunnel. Included is a rule to dnat to Xrouter's address
which is on the Xrouter side of the P2P tunnel. This setup is working for
all encap packets EXCEPT the RIP packets.
Checking things with TCPdump, the RIP packets are being dnat'd to the VPN
tunnel address instead of the XRouter tunnel. I can't find any rules added
by the OpenVPN server that are matching any encap traffic, so I'm baffled
as to why they are not matched by my rules and also how they are matched by
the VPN rules. That said, the VPN Access server creates a very confusing
set of NTFable rules jumping all over the place though different chains, so
it's possible that they lost me. However I asked a question on their forum
a while back about support for protocol 4, and their answer was they don't
support it.
Is there anything about the RIP "IPIP" packets that is different from other
"IPIP" traffic so that they would be handled differently by NFTables?
Thanks,
Lee K5DAT
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
Virus-free.www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Hello!
I've been working on getting my IPIP mesh gateway set up on Debian & feel like I'm almost there. One thing I’ve noticed is every time I reboot the router, it takes around 45-60 minutes before I can start passing traffic to the public internet again via the ucsd gateway. For example, after rebooting the router, once rip44d has retrieved the routes I can:
(a) Ping and curl across tunl0 to n2nov.ampr.org
(b) Use yo2tm’s nettools to successfully ping my ampr ip and see that traffic locally via tcpdump
But cannot:
(c) Ping 8.8.8.8 across tunl0 (via 169.228.34.84) or
(d) Curl to ifconfig.me across tunl0 (via 169.228.34.84)
However, if I just leave everything running and come back 45-60 minutes later, (c) and (d) work fine with no additional configuration changes and (d) returns the assigned 44net ip address.
Just curious if the above is an expected behavior or a sign that I’ve got something misconfigured.
-Steve
kc8qba
Happy New Year, Everyone!
ARDC will be at the Gwinnett Amateur Radio Society TechFest on January
13, 2024 in Lawrenceville, GA. If you're at the event, stop by our table
and say hello!
73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
