Hi,
Several weeks ago I requested postal address verification via the new
portal, however it is still set as new (unassigned).
Is there some expected time-span for assignment?
I couldn't really find more info on that on this list, so I decided to
start this thread.
Thanks,
~ SP6KEK
For years, I usually make a DNS request to my coordinator and CC Chris. It takes less than 1 hours. I believe I've been waiting 3 days on 20+ tickets in the new Portal.I should note, I haven't been able to request the DNS changes - because the records are currently in an "unclaimed" status and not assigned to my call. I'm still waiting to "claim" them.Since Chirs and my coordinator have since responded to me here and off-reflector, who should I be contacting regarding tickets in the Portal?Again, I don't wish to seem impatient or entitled - especially given I now realize that others have been waiting months.Thanks and 73,LynwoodKB3VWG
-------- Original message --------From: Jim Kutsch KY2D via 44net <44net(a)mailman.ampr.org> Date: 5/12/24 10:50 (GMT-05:00) To: '44Net general discussion' <44net(a)mailman.ampr.org> Subject: [44net] Re: Postal address verification Unless Maine is an exception, I’m in the U.S. and my address verification request has been pending since April 12. No postcard received yet. . 73 Jim KY2D From: Dave Gingrich via 44net <44net(a)mailman.ampr.org> Sent: Sunday, May 12, 2024 9:59To: 44Net general discussion <44net(a)mailman.ampr.org>Subject: [44net] Re: Postal address verification It is much easier for the team to verify callsigns and addresses for U.S. domestic people. For some non-US locations it is nearly impossible. Tickets and any associated documents are completely deleted when they are acted upon. The team is very paranoid of leaving any personally identifiable information laying around in a database somewhere. — Dave K9DC, K9IP On May 12, 2024, at 08:58, Cara Salter via 44net <44net(a)mailman.ampr.org> wrote: On 5/12/24 08:03, femsci via 44net wrote:Several weeks ago I requested postal address verification via the new portal, however it is still set as new (unassigned).Is there some expected time-span for assignment?I couldn't really find more info on that on this list, so I decided to start this thread.Interesting -- my address verification ticket was approved (from what I can tell) on the same day.Slight tangent -- is there a way to view resolved tickets? When I go to Tickets -> View My Tickets there's nothing listed.73,Cara KC1KZT
Le 05/05/2024 à 11:28, Rob PE1CHL via 44net a écrit :
> I am disappointed that the current system is focused on a completely different
> use-case than we have here
I quite agree.
For subnet 44.151 (France), I have IP creation requests pending and I
still don't know if it's possible.
For BGP France requests, I don't even know where the BGP France IPs
are since they're no longer in 44.151.
I guess we'll have to wait, so I'll wait.
That's all I can do.
😉
What would be a step forward is if coadmins could themselves create
requestor IPs and manage their associate dns/reverse dns.
Best regards,
Ludovic - F5PBG
Does ns.ardc.org have an access policy restricting traffic to only IPs with a DNS entry (i.e. Intra-AMPRNet only)?
That differs from what I've been told, so I wish ask.
I'm having a difficult time with one of my valid AMPRNet IPs and have been struggling for days. I only have success with IPS having DNS entries.
73,
LynwoodKB3VWG
All,
I have 22 "unassigned" tickets in the Portal. I assume these have tasks I usually emailed my coordinator about. how do they get resolved?
I don't want to sound "entitled" - I just don't understand what's occurring-since I've been responded to and assumed over 1 year notice (I've been told ARDC had 2 year notice). I noted I'd have a DNS matter soon and and as understand coordinators don't know what to do.
Forgive me if this is the wrong channel to communicate, but I've noted this before publicly and privately with no response.
Also, my trust, IPv4 and IPv6 request trust level are incorrect.
Thanks and 73,
KB3VWG
I rebooted my AMPRNet router after an upgrade earlier today, and now
IPENCAP traffic doesn't seem to be flowing through the UCSD gateway. I
wonder if this is expected behavior?
I've verified that all interfaces on the router are working as
expected: I can ping the _external_ address of the UCSD gateway from
my router's external interface:
```
marconi# ping -V 23 -I 23.30.150.141 169.228.34.84
PING 169.228.34.84 (169.228.34.84): 56 data bytes
64 bytes from 169.228.34.84: icmp_seq=0 ttl=48 time=86.937 ms
64 bytes from 169.228.34.84: icmp_seq=1 ttl=48 time=85.409 ms
64 bytes from 169.228.34.84: icmp_seq=2 ttl=48 time=90.166 ms
64 bytes from 169.228.34.84: icmp_seq=3 ttl=48 time=90.180 ms
64 bytes from 169.228.34.84: icmp_seq=4 ttl=48 time=82.058 ms
64 bytes from 169.228.34.84: icmp_seq=5 ttl=48 time=83.595 ms
^C
--- 169.228.34.84 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 82.058/86.391/90.180/3.067 ms
marconi#
```
But suppose I try to `ping` an external IPv4 address from a machine
inside of my subnet. Then those messages seem to be dropped. E.g.,
dumping on the encap interface:
```
tcpdump: listening on gif1, link-type LOOP
15:51:46.955189 44.44.48.29 > 142.250.80.4: icmp: echo request
(id:cf3d seq:507) [icmp cksum ok] (ttl 254, id 62634, len 84)
15:51:46.975585 44.44.48.29.34992 > 152.70.159.102.123: [udp sum ok]
v4 client strat 0 poll 0 prec 0 dist 0.000000 disp 0.000000 ref
(unspec)(a)0.000000000 orig 0.000000000 rec -0.000000000 xmt
-501608111.378157913 [tos 0x10] (ttl 63, id 42418, len 76)
15:51:47.955108 44.44.48.29 > 142.250.80.4: icmp: echo request
(id:cf3d seq:508) [icmp cksum ok] (ttl 254, id 6160, len 84)
15:51:48.953556 44.44.48.29 > 142.250.80.4: icmp: echo request
(id:cf3d seq:509) [icmp cksum ok] (ttl 254, id 5705, len 84)
15:51:49.955095 44.44.48.29 > 142.250.80.4: icmp: echo request
(id:cf3d seq:510) [icmp cksum ok] (ttl 254, id 38617, len 84)
15:51:50.955135 44.44.48.29 > 142.250.80.4: icmp: echo request
(id:cf3d seq:511) [icmp cksum ok] (ttl 254, id 13652, len 84)
15:51:51.953550 44.44.48.29 > 142.250.80.4: icmp: echo request
(id:cf3d seq:512) [icmp cksum ok] (ttl 254, id 15767, len 84)
^C
8 packets received by filter
0 packets dropped by kernel
```
(Note: the UDP packet is just an NTP request on the machine that
happens to be running `ping`, but it's unrelated.)
I can see that such packets are being routed out of my external
interface, while properly encapsulated. e.g.,
```
tcpdump: listening on cnmac1, link-type EN10MB
15:52:14.955137 23.30.150.141 > 169.228.34.84: 44.44.48.29 >
142.250.80.4: icmp: echo request (id:cf3d seq:535) (ttl 254, id 35282,
len 84) (ttl 64, id 61599, len 104)
15:52:15.335038 35.203.211.24.57286 > 23.30.150.141.999: S [tcp sum
ok] 4102707815:4102707815(0) win 65535 <mss 1460> [tos 0x20] (ttl 56,
id 54321, len 44)
15:52:15.335165 23.30.150.141.999 > 35.203.211.24.57286: R [bad tcp
cksum a4a9! -> d8a0] 0:0(0) ack 4102707816 win 0 (DF) [tos 0x10] (ttl
64, id 61784, len 40)
15:52:15.955143 23.30.150.141 > 169.228.34.84: 44.44.48.29 >
142.250.80.4: icmp: echo request (id:cf3d seq:536) (ttl 254, id 27600,
len 84) (ttl 64, id 37135, len 104)
15:52:16.955121 23.30.150.141 > 169.228.34.84: 44.44.48.29 >
142.250.80.4: icmp: echo request (id:cf3d seq:537) (ttl 254, id 62216,
len 84) (ttl 64, id 5987, len 104)
15:52:17.025154 23.30.150.141 > 169.228.34.84: 44.44.48.29.6711 >
152.70.159.102.123: [udp sum ok] v4 client strat 0 poll 0 prec 0 dist
0.000000 disp 0.000000 ref (unspec)(a)0.000000000 orig 0.000000000 rec
-0.000000000 xmt +824494743.794610023 [tos 0x10] (ttl 63, id 64906,
len 76) [tos 0x10] (ttl 64, id 14623, len 96)
15:52:17.955195 23.30.150.141 > 169.228.34.84: 44.44.48.29 >
142.250.80.4: icmp: echo request (id:cf3d seq:538) (ttl 254, id 59942,
len 84) (ttl 64, id 39191, len 104)
^C
20 packets received by filter
0 packets dropped by kernel
```
However, if I try to `ping` a machine I own elsewhere on the network
where I can run `tcpdump`, the traffic never seems to get there.
Further, I can `ping` my external interface from elsewhere on the
network. That all appears to be working. IPv6 works, so I'm fairly
confident in e.g. my firewall rules and so on.
Curiously, I am receiving RIP packets from 44.0.0.1 on the multicast
group, and I can `ping` other machines inside the AMPRNet mesh, but
this all strongly implies that the UCSD gateway is dropping traffic to
and from my subnet.
Is that expected? Thanks!
- Dan C. (KZ2X)
All,
I did some work on restoring my netflow collectors - and the first thing I noticed was the NTP server ns.ardc.net is giving me an error. It seems that it does not allow queries from our Gateway Public IPs as AMPRGW previously did. This provides a chicken-or-the-egg issue on some of my configs if any time-based services are needed (i.e. if I only rely on ns.ardc.net for time). This could be a serious issue if e.g. tunnels were switched to Wireguard (i.e. needing time for encryption).
A SK (I will not name) frowned upon NTP via IPENCAP for obvious reasons (I hope the DNS discussions make clear that a UDP NTP packet with latency or delays from 2 rounds trips is BAD).
I'm looking into the implications for myself and possibly for others by not considering this before the change was made. I'm now working on routes/rules to make an exception for this IP; but it will require some testing as this would be on my main (non-AMPRNet) routing table, which is BAD.
I haven't taken time to determine if this will cause issues for other use cases. I am still run the Stratum 2 server for those who may realize that they are no longer syncing only on AMRPNet's NTP services.
IP: 44.60.44.1Hostname: kb3vwg-001.ampr.orgAccess Policy: (123/udp open to 44net and Public GW IPs)
73,
LynwoodKB3VWG
Hi folks,
In addition to helping to ideally clarify some of the questions that
have come up on the mailing list, given the tone of some of the recent
communications, it seems prudent to remind this group of ARDC’s Code of
Conduct:
https://www.ardc.net/about/legal/code-of-conduct/
The policy outlines examples of unacceptable behavior, the process for
dealing with incident reports, as well as varying types of outcomes.
It is true that the new Portal rollout has caused some confusion, and I
completely understand the frustration that comes with it. At the same
time, ARDC is committed to facilitating a “supportive, productive, and
fun learning environment.” Before sending an email, I ask that everyone
pause, breathe, and re-read, looking for opportunities to remove
language that could be considered accusatory, hostile, or aggressive.
Our goal is to solve problems together, and flaming the fires of
division impedes progress in that direction.
Thank you for your attention,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
Hi everyone,
Just a note to say QSL on many of the recent messages, as well as to
provide some information that hopefully addresses some of the inquiries
and concerns.
In particular, there are many questions about what regional coordinators
can and cannot do with the new portal, as well as requests for more
clarity surrounding the Level of Trust (LoT).
At a high level, here are some brief updates about each of those items:
1. One of the biggest concerns we have heard from coordinators is that
they are not able to administer their address space on the new Portal.
Specifically, members report that they are unable to place requests for
address space in the regional/country allocations. The new portal
defaults to keeping address assignments private, however you can enable
requests by changing the network’s “Mode” from “Private” to “Open,” this
will allow members to place requests within the assignment. If anyone
requires further information on how to manage this, please contact:
newportal(a)ardc.net.
2. As many of you have pointed out, having a single person administering
the Portal also creates a bottleneck. Additionally, it creates a single
point of failure. The new Portal has the facility to assign tasks to
various Administrator roles to address this issue.
3. The Level of Trust (LoT) was established so that we at ARDC can
better ensure a user’s identity with a significant degree of confidence.
In general, there are two major categories: 1) BGP users and 2) non-BGP
users (i.e., “everyone else”). As there is a greater risk associated
with BGP, a higher LoT is required, and thus, more information will be
required for BGP allocations.
For non-BGP users (/25 addresses and smaller), we only verify your email
address, given name, family name, and active call signs. BGP usage
requires additional postal address verification, which takes a few more
steps. Many thanks to BGP users, in particular, for your patience here.
With the Portal and with 44Net in general – the goal is to do what we
can to increase usage and to make our technology better. We're also
evolving as an organization, which means evolving processes to become
more collaborative and streamlined in everything from policy development
to tech releases. We still have some way to go to reach an optimal
state. It's difficult to get there without hitting some snags and bumps,
particularly when working with dozens of intelligent people with varying
ideas about the “right” way to build something. We are committed to
getting there, and we are already learning lessons from this experience
that will make the next rollout better.
In the meantime, to anyone who feels like they aren’t being heard,
please know that you are. We are taking this feedback seriously for
future features and processes.
We’ll also follow up with regional coordinators to find a time for a
group discussion in the coming weeks.
Please also note – as some of you have likely seen – we are down a key
employee due to him becoming SK:
https://www.ardc.net/remembering-john-hays-k7ve-sk/
We had another employee depart a couple of weeks before John’s death.
The loss of these two people means a loss of 20% of our staff. As a
result, we are unexpectedly working through things more slowly than we
would like. I ask everyone for patience while we get our feet back under
us and restaff (which will take at least a couple of months).
I hope this message helps to clarify where we’re at. As always, if you
have any questions and/or would like further clarification, please don’t
hesitate to reach out, and we will help as much as we can. Thank you
again to everyone for your patience, and we also appreciate the
productive components of the feedback received.
73,
Rosy KJ7RYV
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
# Summary
Given that DNS has been a popular topic of discussion lately, I
thought it might be useful to try and put some words about it on the
Wiki. In preparation for this, I was playing around with the recursive
DNS server on my subnet, and I ran into some strange behavior that I
don't understand; perhaps someone else knows what's going on? To my
eye, it looks like some types of PTR queries are being dropped at or
before AMPRGW; this behavior is repeatable.
# Setup and Context
* I have a machine on my allocated subnet (44.44.48.29) that is
running a recursive, caching DNS server (that is, a resolver).
* The resolver is configured with stub zones that forward requests for
ampr.org, 44.in-addr.arpa and 128.44.in-addr.arpa to the authoritative
servers for those zones listed on the Wiki
* The resolver is configured to respond to requests issued over both
IPv4 and IPv6
* Machines on my subnet are configured to query this server.
* I have configured my firewall to allow access to the `domain` port
(e.g., UDP/53) on that machine from a few places on the Internet ---
but not all.
# Observations
What I observe is inconsistent, but repeatable, failures when issuing
PTR queries for certain IP addresses via IPv4 from the external
Internet.
* Forward queries from all sources seem to work fine. At least, I
haven't observed any that fail (other than for, say, non-existent
hostnames).
* Similarly, PTR queries issued from the hosts on my subnet all seem
to work as expected.
* PTR queries issued over IPv6 seem to work fine from any source.
* PTR queries issued over IPv4 from other networks locally connected
to my home network (I have several ethernets and TCP/IP networks at
home, interconnected with a set of routers and switches) all seem to
work fine.
* PTR queries for _some_ IP addresses issued over IPv4 from external
machines on the Internet work reliably. For example, I can reliably
query for 44.1.1.44, 44.0.0.1, 127.0.0.1, and 8.8.8.8 and I don't
believe I've ever seen any of these queries fail.
* PTR queries for _most_ 44Net IP addresses issued over IPv4 from
external machines on the Internet fail reliably. For example, I
cannot query for 44.44.48.1 (my gateway), or 44.182.21.1 (YO2LOJ's
machine). I don't believe I have ever seen any of these queries
succeed.
Note that the only thing that differs in the last two cases is the
address I'm trying to resolve.
Now the interesting part. For the failing queries, I've observed that
the actual query traffic _never makes it to my gateway from UCSD_.
That is, the encapsulated datagram carrying the UDP packet containing
the query never makes it to the external gateway.
I issued these queries with the `host` tool.
To verify this, I ran `tcpdump` in several places:
1. At the source machine where I issued the DNS queries:
tcpdump -vvn host 44.44.48.29
2. On my gateway, examining the encapsulated traffic on the external interface:
tcpdump -vvni cnmac1 ip proto 4 and 'ip[29:1] == 17 and (ip[42:2]
== 53 or ip[40:2] == 53)'
(Note the `ip[...]` expressions are matching in the encapsulated
IP and UDP headers.)
3. On the DNS server machine itself:
tcpdump -vvn udp port domain or tcp port domain
To verify that everything is working as expected, first I issue a
successful forward query:
```
: gaja; host -4 kz2x.ampr.orgsrv.kz2x.ampr.org
Using domain server:
Name: srv.kz2x.ampr.org
Address: 44.44.48.29#53
Aliases:
kz2x.ampr.org has address 44.44.48.2
kz2x.ampr.org has IPv6 address 2603:3005:b04:8144:48:edff:fe9c:c00
: gaja;
```
Note that the query succeeded (the astute reader may notice that
that's missing an MX record, but ignore that for now), but let's look
at the `tcpdump` output at each stage just to see what it looks like.
Note that the data is in my cache, so I omit the details of recursive
queries down to the roots, etc.
From the local machine where I issue the query, one sees:
```
20:07:31.444583 166.84.136.80.35777 > 44.44.48.29.53: [udp sum ok]
32707+ A? kz2x.ampr.org.(31) (ttl 64, id 18835, len 59)
20:07:31.603276 44.44.48.29.53 > 166.84.136.80.35777: [udp sum ok]
32707* q: A? kz2x.ampr.org. 1/0/0 kz2x.ampr.org. A 44.44.48.2(47) (ttl
40, id 12176, len 75)
20:07:31.605932 166.84.136.80.22717 > 44.44.48.29.53: [udp sum ok]
7616+ AAAA? kz2x.ampr.org.(31) (ttl 64, id 58081, len 59)
20:07:31.761378 44.44.48.29.53 > 166.84.136.80.22717: [udp sum ok]
7616* q: AAAA? kz2x.ampr.org. 1/0/0 kz2x.ampr.org. AAAA
2603:3005:b04:8144:48:edff:fe9c:c00(59) (ttl 40, id 62606, len 87)
20:07:31.762560 166.84.136.80.28977 > 44.44.48.29.53: [udp sum ok]
58832+ MX? kz2x.ampr.org.(31) (ttl 64, id 41619, len 59)
20:07:31.911483 44.44.48.29.53 > 166.84.136.80.28977: 58832* q: MX?
kz2x.ampr.org. 0/1/0 ns: kz2x.ampr.org. SOA[|domain] (ttl 40, id
37627, len 110)
```
From the external interface on my AMPRNet gateway machine, I see:
20:07:31.523609 169.228.34.84 > 23.30.150.141: 166.84.136.80.35777 >
44.44.48.29.53: [udp sum ok] 32707+ A? kz2x.ampr.org.(31) [tos 0x28]
(ttl 49, id 18835, len 59) (ttl 48, id 486, len 79)
20:07:31.524290 23.30.150.141 > 169.228.34.84: 44.44.48.29.53 >
166.84.136.80.35777: [udp sum ok] 32707* q: A? kz2x.ampr.org. 1/0/0
kz2x.ampr.org. A 44.44.48.2(47) (ttl 63, id 12176, len 75) (ttl 64, id
12041, len 95)
20:07:31.683608 169.228.34.84 > 23.30.150.141: 166.84.136.80.22717 >
44.44.48.29.53: [udp sum ok] 7616+ AAAA? kz2x.ampr.org.(31) [tos 0x28]
(ttl 49, id 58081, len 59) (ttl 48, id 6515, len 79)
20:07:31.684262 23.30.150.141 > 169.228.34.84: 44.44.48.29.53 >
166.84.136.80.22717: 7616* q: AAAA? kz2x.ampr.org. 1/0/0
kz2x.ampr.org. AAAA[|domain] (ttl 63, id 62606, len 87) (ttl 64, id
48275, len 107)
20:07:31.836445 169.228.34.84 > 23.30.150.141: 166.84.136.80.28977 >
44.44.48.29.53: [udp sum ok] 58832+ MX? kz2x.ampr.org.(31) [tos 0x28]
(ttl 49, id 41619, len 59) (ttl 48, id 6629, len 79)
20:07:31.837067 23.30.150.141 > 169.228.34.84: 44.44.48.29.53 >
166.84.136.80.28977: 58832* q: MX? kz2x.ampr.org. 0/1/0 ns:
kz2x.ampr.org. SOA[|domain] (ttl 63, id 37627, len 110) (ttl 64, id
12165, len 130)
And on the DNS server machine itself:
```
20:07:31.520610 166.84.136.80.35777 > 44.44.48.29.53: [udp sum ok]
32707+ A? kz2x.ampr.org.(31) [tos 0x28] (ttl 48, id 44358, len 59)
20:07:31.520796 44.44.48.29.53 > 166.84.136.80.35777: [udp sum ok]
32707* q: A? kz2x.ampr.org. 1/0/0 kz2x.ampr.org. A 44.44.48.2(47) (ttl
64, id 33360, len 75)
20:07:31.680599 166.84.136.80.22717 > 44.44.48.29.53: [udp sum ok]
7616+ AAAA? kz2x.ampr.org.(31) [tos 0x28] (ttl 48, id 23293, len 59)
20:07:31.680766 44.44.48.29.53 > 166.84.136.80.22717: [udp sum ok]
7616* q: AAAA? kz2x.ampr.org. 1/0/0 kz2x.ampr.org. AAAA
2603:3005:b04:8144:48:edff:fe9c:c00(59) (ttl 64, id 31261, len 87)
20:07:31.833404 166.84.136.80.28977 > 44.44.48.29.53: [udp sum ok]
58832+ MX? kz2x.ampr.org.(31) [tos 0x28] (ttl 48, id 44916, len 59)
20:07:31.833578 44.44.48.29.53 > 166.84.136.80.28977: 58832* q: MX?
kz2x.ampr.org. 0/1/0 ns: kz2x.ampr.org. SOA[|domain] (ttl 64, id
28444, len 110)
```
These results are all expected. Similarly for a successful reverse query:
```
: gaja; host -4 44.1.1.44 srv.kz2x.ampr.org
Using domain server:
Name: srv.kz2x.ampr.org
Address: 44.44.48.29#53
Aliases:
44.1.1.44.in-addr.arpa domain name pointer ns.ardc.net.
: gaja;
```
As seen from the source host:
```
20:13:37.445021 166.84.136.80.4339 > 44.44.48.29.53: [udp sum ok]
61470+ PTR? 44.1.1.44.in-addr.arpa.(40) (ttl 64, id 34902, len 68)
20:13:37.609712 44.44.48.29.53 > 166.84.136.80.4339: [udp sum ok]
61470 q: PTR? 44.1.1.44.in-addr.arpa. 1/0/0 44.1.1.44.in-addr.arpa.
PTR ns.ardc.net.(65) (ttl 40, id 15635, len 93)
```
From the gateway:
```
20:13:37.523609 169.228.34.84 > 23.30.150.141: 166.84.136.80.4339 >
44.44.48.29.53: [udp sum ok] 61470+ PTR? 44.1.1.44.in-addr.arpa.(40)
[tos 0x28] (ttl 49, id 34902, len 68) (ttl 48, id 13407, len 88)
20:13:37.533691 23.30.150.141 > 169.228.34.84: 44.44.48.29.53 >
166.84.136.80.4339: 61470 q: PTR? 44.1.1.44.in-addr.arpa. 1/0/0
44.1.1.44.in-addr.arpa. PTR[|domain] (ttl 63, id 15635, len 93) (ttl
64, id 52552, len 113)
```
And at the DNS server:
```
20:13:37.520500 166.84.136.80.4339 > 44.44.48.29.53: [udp sum ok]
61470+ PTR? 44.1.1.44.in-addr.arpa.(40) [tos 0x28] (ttl 48, id 22620,
len 68)
20:13:37.520691 44.44.48.29.53 > 166.84.136.80.4339: [udp sum ok]
61470 q: PTR? 44.1.1.44.in-addr.arpa. 1/0/0 44.1.1.44.in-addr.arpa.
PTR ns.ardc.net.(65) (ttl 64, id 59842, len 93)
```
Okay, but what about a failing query? Let's try one:
```
: gaja; host -4 44.44.48.29 srv.kz2x.ampr.org
;; connection timed out; no servers could be reached
: gaja;
```
Uh oh. As seen from the source host:
```
20:15:26.775880 166.84.136.80.29535 > 44.44.48.29.53: [udp sum ok]
39502+ PTR? 29.48.44.44.in-addr.arpa.(42) (ttl 64, id 59475, len 70)
20:15:27.776870 166.84.136.80.29535 > 44.44.48.29.53: [udp sum ok]
39502+ PTR? 29.48.44.44.in-addr.arpa.(42) (ttl 64, id 40687, len 70)
```
But at the gateway, nothing at all is seen; no relevant data is
received from the AMPRGW, and of course, similarly at the DNS server
as well.
So it appears that these queries are being lost, either at AMPRGW or
before. Has anyone seen this before? Is it expected?
- Dan C.
So, everyone out in 44net land, how are things?
After one month since the "cut-over":
- are the coordinators allowed to coordinate fully?
- are the requestors allowed to be assigned a non-.32/.61/63 address?
- is everyone "trusted" enough to use the portal freely/fully again?
Inquiring minds, and those waiting for an allocation, want to know.
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying
(The work praises the man.)
"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan
Hello everyone,
I've had a 44net account for a while now and I've played with both setting up OpenWRT, several Linux VMs, and a Cisco 1900 (with limited knowledge and testing from work when we got fancy ISR4443's) but never actually achieved anything. Previously I read that to achieve BGP connectivity something had to be done with the ISP to allow the AS route to be announced/routed so that may have been another roadblock. Also with the whole IPIP based traffic, you can only have a limited number of devices unless you start working nat-magic and throw everything behind the same ip.
Personally, I'm more familiar with VPN-based tunneling back to an endpoint and the datacenter/carrier-based router would announce the /24 route based on the status of the tunnel/ip and would not actually need to involve the non-rfp'd local carrier at all. As long as traffic could be passed through a tcp port, the connection could be made.
Are there any opportunities with IPSEC/SSL/OpenVPN or even SDWAN endpoints joining the network instead of needing a router and formal networking knowledge to do the same? I just keep running into the same issues with 44net even though I can muster along and setup my work sites with good old IPSEC tunnels and locking the service down.
Thanks,
KD8SEP
Trevor Halsey
Middletown, Ohio
I have been asked to participate in a conference call with ARDC staff
regarding the concerns about the portal cut-over. If there are any items
that you would like me to bring up during the call (not scheduled yet),
please email me directly at n2nov(a)n2nov.net with it.
On 4/19/2024 2:44 PM, Charles J. Hargrove wrote:
> I just received email and then a phone call from a person that wanted
> to join one of our networks in the Northeast USA for the purposes of
> routing Echolink, repeaters and more. When logging onto the "new" AMPR
> portal, they were given only a choice of a few subnets based on a dropdown
> list of intended uses. None of them jived with the networks in any of
> the individual states or countries. I would suggest spreading the word
> that all requests for new or expanded allocations be held up until things
> can be straightened out. It seems that their small volunteer force is
> unable to keep up with the workload since the changeover on April 3rd.
> I personally have over a dozen tickets unassigned and even one from 4/3.
> Everyone just standby and chill until they figure things out. No need
> to expect steak when they are working with hamburger.
>
> I just jumped on the AMPR portal and found only these choices:
> IPIP Tunnel Mesh 44.63.0.0/16
>
> BGP Direct Announce 44.32.0.0/16
>
> Radio 44.61.0.0/16
> Globally Unique 44.61.0.0/16
> General Address 44.61.0.0/16
>
> AREDN - contact AREDN directly
> HAMNET - contact HAMNET directly in Europe
> HAMWAN - contact HAMWAN directly
>
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying
(The work praises the man.)
"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan
I guess it can be called the "Friday Funnies" and full of marketing hype.
On 5/3/2024 2:22 PM, Rebecca Key via groups.io wrote:
> Hey Everyone,
>
> Our latest blog post on ardc.net highlights the launch of the new
> Portal: check it out here
> <https://www.ardc.net/ardc-launches-44net-portal-2-0/>!
>
> 73,
> Rebecca
> KO4KVG
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying
(The work praises the man.)
"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan
Hi
I am wondering if the outgoing traffic can go through the IPIP tunnel
gateway? After adding DNS record to my 44net ip, I can successfully ping
my 44net IP. But when I try to run outbound traffic, for example ping -c
3 -I tunl0 1.1.1.1 It won't work. I am wondering how to initiate
connections on the Debian 12.
Thanks
Kun
I just received this news this morning (nearly 2 weeks after).
-------- Forwarded Message --------
Subject: [OpenDV] John Hays K7VE SK
Date: Sun, 28 Apr 2024 05:54:08 -0700
From: Jonathan Naylor via groups.io <naylorjs=yahoo.com(a)groups.io>
To: OpenDV(a)groups.io
My friend John Hays K7VE died unexpectedly on April 16th. The Facebook
algorithms didn't see fit to show me this information and I had to be
told days later by Jim KI6ZUM. Instead FB insisted on feeding me pages
that I don't follow, rather than stuff that matters to me. Anyway I digress.
I knew John pretty well. He had been an early supporter of my software,
and my first dealing with him were in Autumn 2009 only a few months
after the release of my first D-Star and FM repeater software, and
before it was in widespread use. Many of our emails were about the poor
performance of the then popular GMSK modems and what we could do about
them, as well as more software related items.
Once I had released the ircDDB Gateway in Autumn 2010 he moved his
repeater, then based on an Icom repeater stack, over to use it rather
than Icom's G2 software. The next few years would see many more emails
being eschanged as I enhanced my software and he suggested changes,
reported bugs, etc. John came up with the idea for StarNet which is
still included with the ircDDB Gateway.
I first physically met John in 2014 as I was to attend Hamvention as a
guest of NWDR, which was John and Bryan Hoyer at the time. We manned a
booth at the old Hara arena, and despite being used to Ham Radio in
Friedrickshafen, nothing could prepare me for the onslaught of
Hamvention. I had a great time, and by the time that Sunday rolled
around, I was burned out! Too much of a good thing I suppose.
John backed off a bit with my software with the release of the MMDVM. He
wasn't happy with me supporting purely commercial protocols like DMR. It
was indeed ironic that I got my first DMR radio at that very Hamvention
from Jerry Wanger of CSI, and I also crossed swords with the DMR-MARC
guys, which strongly encouranged me to go down the route that would
become the MMDVM a little while later.
Since then I would see John at various shows, and then after Covid when
things had more or less returned to normal, I saw him at Ham Radio in
2022, and 2023 manning the ARDC stand. I also saw him at Pacificon in
October 2023 which would turn out to be the last time I saw him. We
would sit and have long conversations about development work and
potential projects. I was very much looking forward to seeing him at
Hamvention in a few weeks.
Rest in peace John, it was an honour to be your friend.
Jonathan G4KLX
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying
(The work praises the man.)
"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan
Hello all,
Has anybody else requested a new IPv4 subnet space allocation via BGP since the new portal has been released?
I'm asking this because I've requested on 18th of this month a new one, and until today no answer or update on the ticket.
I've tried to reach out to Chris directly, but I had no answer on my previous email.
I'm just wondering if anybody else had it's request resolved, since I had another 1-2 tickets opened and resolved after 1-2 days, and this one is still unassigned and in the new state.
I do apologize in advance if this is a stupid question, but since my other tickets were resolved "quickly", I thought to ask if somebody else had requested and received a response.
Have a lovely weekend ahead and 73's!
Thanks,
Razvan - YO6RZV
Web: https://yo6rzv.ro
Hello,
If I use the line from the Wiki below in order to retrieve the file via API
(and convert it back to the text forma), I get a parsing error - presumably
from jq. If I download only the file taking jq out of the equation, it's
not a json file, but rather, a HTML file. I assume that's why there's a
parsing error when jq reads it. Is the info from the Wiki out of date?
Thanks,
Lee K5DAT
curl -s https://user:key@portal.ampr.org/api/v1/encap | jq -r '.[] |
"route addprivate \(.network)/\(.maskLength) encap \(.gatewayIP)"'
Hello,
Being a former director on two 501(c)3's (and who volunteered and heard nothing) - I took time to review the annual reports. I have some questions.
Who would I direct those to?
e.g. (but not limited to)
- I noted the 501(c)3 annual report on the website did not note receipts/donations, only outgoing funds as "granting" "projects"- I'd like to see you Public Filings and any required by California - or the Regents System, etc. as applicable, etc.- Your 2023 IRS Form 990-PF not yet posted to your website - I await viewing it
Thanks and 73,
- LynwoodKB3VWG
I'm not seeing any changes to the RIP broadcasts (seems to be stuck at
843 lines for last couple of days).
Also can't download encap file from portal.ampr.org/api/v1/encap (should
existing API key still work?)
Max
G4FDL
I have previously recorded malicious traffic in the past. It was from a rogue gateway. The endpoint was simply dropped from our RIP44 statements.To Charles' point - the traffic was firewalled, it's that alert which brought it to my knowledge. It also reiterates the need for RFC-documented methods to ensure we don't have stale records.- KB3VWG
-------- Original message --------From: "Charles J. Hargrove via 44net" <44net(a)mailman.ampr.org> Date: 4/25/24 09:40 (GMT-05:00) To: 44net(a)mailman.ampr.org Subject: [44net] Re: DNS AXFR Isn't it more prudent for each user device to have their own security?Maybe that is where a more useful discussion should take place. Theeducation of the user systems/allocation holders falls into line withamateur radio being a technical hobby/service and those who are moreknowledgeable in our sphere should have more a sense of being an elmerinstead of keeping the information to themselves and be seen as wieldinga cudgel when "upstarts" ask questions to power. Money can sure corruptviewpoints, eh?On 4/25/2024 9:23 AM, Dan Cross via 44net wrote:> While that level of caution is certainly appropriate for the public> Internet, I have a hard time believing it's warranted on AMPRNet> itself. Has anyone done an actual threat analysis for traffic> originating inside the network itself?-- Charles J. Hargrove - N2NOVNYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.NYC-ARECS/RACES Nets 441.100/136.5 PLARnewsline Broadcast Mon. @ 8:00PMNYC-ARECS Weekly Net Mon. @ 8:30PMhttp://www.nyc-arecs.orgNY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PMon 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32"Information is the oxygen of the modern age. It seeps through the walls toppedby barbed wire, it wafts across the electrified borders." - Ronald Reagan"The more corrupt the state, the more it legislates." - Tacitus"Molann an obair an fear" - Irish Saying(The work praises the man.)"No matter how big and powerful government gets, and the many services itprovides, it can never take the place of volunteers." - Ronald Reagan_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org
Chris,There's no need to jump into this email chain abouta Wiki. If you don't want to provide the Wiki group email, I'm sure someone else can.I know you're quite busy with other things, the Wiki should be the least of your concerns at this time.73,LynwoodKB3VWG
-------- Original message --------From: Chris <chris(a)ardc.net> Date: 4/25/24 06:09 (GMT-05:00) To: lleachii(a)aol.com Cc: AMPRNet working group <44net(a)mailman.ampr.org> Subject: Re: [44net] Wiki Hi Lynwood,You have my email, please email me off-list if you wish73,Chris - G1FEF—ARDC AdministratorWeb: https://www.ardc.net
On 25 Apr 2024, at 10:42, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote:I've sent an email about emailing the Wiki group. Somehow that email never hit the reflector.Does anyone know how to email them?There's been an edit- whose last change sparked a discussion. Since this edit was made by an administrator, I'd like to discuss it there. Thanks, LynwoodKB3VWG_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org
I've sent an email about emailing the Wiki group. Somehow that email never hit the reflector.Does anyone know how to email them?There's been an edit- whose last change sparked a discussion. Since this edit was made by an administrator, I'd like to discuss it there. Thanks, LynwoodKB3VWG
All,
How do I email the new Wiki Group - as changes have been made by an Admin?
(FYI - I joined them)
While the edits are "OK", they are "grammatical" in nature, and the last edit sparked distinction (funny the discussion was regarding recursive DNS servers).
There are superseding edits after I [finally] removed the SK from the Wiki. I asked about this after the passing of Brian R. - but I was told to be patient by my coordinator,
https://wiki.ampr.org/w/index.php?title=Services&action=history
---
- LynwoodKB3VWG
Hi there,
I would like to rewrite or add my DNS entry for ampr.org.
I'd requested via the new portal as a Ticket, but still unassigned.
I think I must have the authority to modify it.
Can anyone help me ?
regards,
Toshiyuki JF3LGC
--
Toshiyuki MABUCHI
jf3lgc(a)gmail.com
Hi Kun,
The RIP broadcasts are sent as encapsulated multicast packets over the tunnel from the UCSD gateway server on 44.0.0.1 to your tunnel endpoint, so you need the tunnel setup before RIP44d can receive these broadcasts.
I am assuming you are using some flavour of Linux as your gateway machine, if so as a minimum you would need to:
modprobe ipip
ip addr add 44.x.x.x dev tunl0
ip link set dev tunl0 up
where 44.x.x.x is your tunnel endpoint IP.
Then you can run the find_pass.sh script, which is just a one liner:
ampr-ripd -d -v -i tunl0
I use Debian 12 and this is how I have my gateway setup, hope it helps...
I use systemd to start everything up automatically after a reboot: /etc/systemd/system/amprgw.service
[Unit]
Description=AMPRNet
After=network-online.target
Wants=network-online.target
[Service]
Type=oneshot
RemainAfterExit=true
ExecStart=/usr/local/bin/ampr_start.sh
ExecStop=/usr/local/bin/ampr_stop.sh
[Install]
WantedBy=multi-user.target
After creating this file you need to run “systemctl daemon-reload” followed by “systemctl enable amprgw” and “systemctl start amprgw”
Here is the ampr_start.sh script:
#!/bin/sh
PWD=“<the RIP44d password>"
LOCATION="G1FEF@IO91mk"
AMPR_OUR_LAN="44.63.7.208/29"
AMPR_OUR_TUN="44.63.7.215"
EXT_INTERFACE="enp1s0"
INT_INTERFACE="enp2s0"
TUN_INTERFACE="tunl0"
# Enable IP Forwarding
sysctl -w net.ipv4.ip_forward=1
# Enable IPIP tunnel and interface
modprobe ipip
ip addr add $AMPR_OUR_TUN dev $TUN_INTERFACE
# Set some tunnel interface options
# * Give the tunnel its own TTL of 64 hops enabling traceroute over the tunnel
# * Bring up the interface
# * Set the tunnel MTU
ip tunnel change ttl 64 mode ipip $TUN_INTERFACE
ip link set dev $TUN_INTERFACE up
ifconfig $TUN_INTERFACE mtu 1480
# Set AMPRNet routing table rules
# * Any packets from any AMPRNet space use routing table 44
# * Any packets from my AMPRNet space use routing table 44
ip rule add to 44.0.0.0/9 table 44 priority 44
ip rule add to 44.128.0.0/10 table 44 priority 44
ip rule add from $AMPR_OUR_LAN table 44 priority 45
# Set AMPRNet routes
# * Default route out of AMPRNet is 169.228.34.84
# * Set local route for AMPRNet on local AMPRNet interface
ip route add default dev $TUN_INTERFACE via 169.228.34.84 onlink table 44
ip route add $AMPR_OUR_LAN dev $INT_INTERFACE table 44
# Rest of the routes are added dynamically by the AMPR-RIPD routing Daemon.
/usr/sbin/ampr-ripd -s -r -t 44 -i $TUN_INTERFACE -a $AMPR_OUR_LAN -p $PWD -L $LOCATION
and the ampr_stop.sh script
#!/bin/bash
NET_AMP="44.63.7.208/29"
NIC_AMP="enp2s0.44"
NIC_TUN="tunl0"
### DISABLE IP FORWARDING ###
sysctl -w net.ipv4.ip_forward=0
### Take the tunnel offline ###
ifconfig $NIC_TUN down
### Remove the table 44 routes ###
ip route delete default dev $NIC_TUN via 169.228.34.84 onlink table 44
# Deletes local 44 network from Table 44
#ip route delete $NET_AMP dev $NIC_AMP table 44
### STOPS THE ampr-ripd ROUTER DAMEON
killall -KILL ampr-ripd
73,
Chris - G1FEF
> On 23 Apr 2024, at 09:23, KUN LIN <dnwk(a)linkun.info> wrote:
>
> Hi Chris,
> I should setup tunnel interference before running find_password.sh? I was following Linux Gateway Examples on the wiki. I'm not quite sure how to setup the tunnel interference before getting the passwords.
> Could you point me to the right direction?
> Thanks
> Kun
>
>
> From: Chris <chris(a)ardc.net>
> Sent: Tuesday, April 23, 2024 12:33 AM
> To: KUN LIN
> Subject: Re: [44net] Waiting for RIPv2 broadcasts
>
> I can see your gateway is in the encap file, I am also receiving your route entry via RIP
>
> 44.16.2.64/27 via 23.94.xxx.xx dev tunl0 proto 44 onlink window 840
>
> So you should be receiving the RIP broadcasts. Have you run ampr-ripd to get the password? i.e. ampr-ripd -d -v -i ampr0
> “ampr0” should be your tunnel interface.
>
> Leave that running for 10 minutes and you should see the broadcasts coming through with the password in plain text, you can then setup ampr-ripd to receive and process the encap routes.
>
> You can get more information here; https://git.ampr.org/yo2loj/ampr-ripd
> and here: https://wiki.ampr.org/wiki/Setting_up_a_gateway_on_Linux
>
> If you manage to get things running you can ping/traceroute to my gateway for testing: 44.63.7.215
>
> 73,
> Chris - G1FEF
> —
> ARDC Administrator
>
> Web: https://www.ardc.net
>
>
>> On 23 Apr 2024, at 03:32, KUN LIN via 44net <44net(a)mailman.ampr.org> wrote:
>>
>> I am trying to setup IPIP tunnel following instructions on wiki and can't move beyond "waiting for RIPv2 broadcasts". When I run tcpdump, I do have something.
>>
>>
>> tcpdump -nni eth0 proto 4
>>
>> tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
>> listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
>> 18:15:00.559893 IP 169.228.34.84 > 23.94.*.*(my gateway ip): IP 44.0.0.1.520 > 224.0.0.9.520: RIPv2, Response, length: 504
>> 18:15:39.222805 IP 79.190.68.116 > 23.94.*.*(my gateway ip): IP 0.0.0.0.5678 > 255.255.255.255.5678: UDP, length 103
>>
>> So, it looks like I am getting some RIPv2 broadcast, but it doesn't seem like ampr-ripd is processing these broadcasts?
>>
>> Any help would be appricated.
>> Thanks
>> Kun Lin
>> _______________________________________________
>> 44net mailing list -- 44net(a)mailman.ampr.org
>> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
>
>
I am trying to setup IPIP tunnel following instructions on wiki and can't move beyond "waiting for RIPv2 broadcasts". When I run tcpdump, I do have something.
tcpdump -nni eth0 proto 4
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
18:15:00.559893 IP 169.228.34.84 > 23.94.*.*(my gateway ip): IP 44.0.0.1.520 > 224.0.0.9.520: RIPv2, Response, length: 504
18:15:39.222805 IP 79.190.68.116 > 23.94.*.*(my gateway ip): IP 0.0.0.0.5678 > 255.255.255.255.5678: UDP, length 103
So, it looks like I am getting some RIPv2 broadcast, but it doesn't seem like ampr-ripd is processing these broadcasts?
Any help would be appricated.
Thanks
Kun Lin
Charles,On April 6, Chris noted to me that 44.00.0.1 would stop having nameserver functionality in the future. This is a concern, as I don't know of another Authoritative Name Server for AMPR.ORG and 44.in-addr.arpa capable of Zone Transfer.Despite this, I have not yet been given an updated AMPRNet nameserver to reconfigure DNS-MDC.AMPR.ORG before that decommissioning.73,LynwoodKB3VWG
-------- Original message --------From: "Charles J. Hargrove via 44net" <44net(a)mailman.ampr.org> Date: 4/20/24 10:21 (GMT-05:00) To: Chris <chris(a)ardc.net> Cc: 44net(a)mailman.ampr.org Subject: [44net] Re: RIP broadcasts AMPR DNS at 44.0.0.1 has been unresponsive since April 11th.Either something is wrong with it or it has been moved withoutus being notified.On 4/19/2024 2:30 PM, Chris wrote:>> On 19 Apr 2024, at 18:42, Charles J. Hargrove via 44net >> <44net(a)mailman.ampr.org> wrote:>>>> Has anyone noticed anything strange with encap routing and DNS entries >> since 4/10?> > Can you be a little more specific Charles?> > There have been some major changes with encap and DNS in moving to the > new portal, so if you are seeing any issues please let me know so they > can be investigated/fixed-- Charles J. Hargrove - N2NOVNYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.NYC-ARECS/RACES Nets 441.100/136.5 PLARnewsline Broadcast Mon. @ 8:00PMNYC-ARECS Weekly Net Mon. @ 8:30PMhttp://www.nyc-arecs.orgNY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PMon 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32"Information is the oxygen of the modern age. It seeps through the walls toppedby barbed wire, it wafts across the electrified borders." - Ronald Reagan"The more corrupt the state, the more it legislates." - Tacitus"Molann an obair an fear" - Irish Saying(The work praises the man.)"No matter how big and powerful government gets, and the many services itprovides, it can never take the place of volunteers." - Ronald Reagan_______________________________________________44net mailing list -- 44net(a)mailman.ampr.orgTo unsubscribe send an email to 44net-leave(a)mailman.ampr.org
I just received email and then a phone call from a person that wanted
to join one of our networks in the Northeast USA for the purposes of
routing Echolink, repeaters and more. When logging onto the "new" AMPR
portal, they were given only a choice of a few subnets based on a dropdown
list of intended uses. None of them jived with the networks in any of
the individual states or countries. I would suggest spreading the word
that all requests for new or expanded allocations be held up until things
can be straightened out. It seems that their small volunteer force is
unable to keep up with the workload since the changeover on April 3rd.
I personally have over a dozen tickets unassigned and even one from 4/3.
Everyone just standby and chill until they figure things out. No need
to expect steak when they are working with hamburger.
I just jumped on the AMPR portal and found only these choices:
IPIP Tunnel Mesh 44.63.0.0/16
BGP Direct Announce 44.32.0.0/16
Radio 44.61.0.0/16
Globally Unique 44.61.0.0/16
General Address 44.61.0.0/16
AREDN - contact AREDN directly
HAMNET - contact HAMNET directly in Europe
HAMWAN - contact HAMWAN directly
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying
(The work praises the man.)
"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan
Hello all,
I'm using the AMPRnet since the old portal and I have a couple of questions
about how to convert an already allocated /24 subnet under my account,
because the new LoT that blocks the possibility to acquire a new subnet
since the LoT points are just a few (25 in my case).
I already have a /24 allocated to my account, which I'm ready to give up
since it's set up as an IPIP tunnel and I requested it to be changed to a
BGP-routed subnet.
- I received the response that it cannot be converted to a BGP subnet,
but I can give it up and request a new one that will be setup as a BGP from
the beginning.
- My question is, how can I do that? I've requested an update on the
ticket but no update since ±4 days ago.
My current limit is a /28 subnet, which I cannot request via BGP, since the
smallest subnet that can be allocated via BGP is a /24.
I don't know where to reach out and pursue this situation, since the
ticketing area seems to be a dead end on these "non-KB" issues.
I would really appreciate any advice/support or any ideas, since I'm stuck
on "procuring" the new subnet (for the BGP) and giving up the actual IPIP
tunnel-subnet.
--
Thank you,
73's YO6RZV (Razvan)
Web: https://yo6rzv.ro
Mail: yo6rzv(a)gmail.com / razvan(a)yo6rzv.ro
Hi there
I am not so active on this list
I have seen that it mention sub domains (callsign.ampr.org)
I have also got a ticket created by dont know who for me for sub domain
Is it must ?
Must I have all my hosts under my sub domain
any info are welcome
Thanks Forwqard
Ronen - 4Z4ZQ
http://www.ronen.org
Hi 44Net Community,
Over the past week since launch, we've seen some questions come up about
subdomains and DNS. I'm writing to share some information that aims to
address some of those questions.
The new portal allows members to manage their own DNS records. You can
also claim any existing DNS records under ampr.org in the zonefile.
However, there are some caveats to this new functionality. To avoid
confusion, below is some information for managing DNS records and/or
claiming any existing DNS records:
Option 1 (Preferred):
If you already have one or more DNS records in the ampr.org DNS and they
are under a subdomain that consists of your callsign, the quickest and
easiest way to get them assigned to your account is to place a request
for a subdomain. You can do this by selecting "My subdomains" from the
"DNS" menu and then clicking on the "Request a subdomain" button. On the
next page, select "ampr.org" from the list of domains (it's the only one
there at the moment), enter your callsign in the "Subdomain:" field, and
then click "Create request".
This will create a ticket for an admin to check. If your callsign is
already verified, and you have requested a subdomain that is identical
to your callsign, then the admin should simply approve the request,
where any existing DNS records under the subdomain will automatically be
pulled into your account. We advise you to keep an eye out for any
"ticket updated" notifications should the admin have any questions.
Once you receive a notification that your request has been approved, you
can then select "My subdomains" from the "DNS" menu, where you should
see your subdomain listed. If you click on the "Resource records" icon,
you will be able to view all your DNS records as well as add new records
under your subdomain.
Option 2 (Recommended ONLY for certain use cases):
Alternatively, there is another way to claim your existing DNS records;
however, you should *only* use this method if you a) only have one
record, or b) if you have multiple records that are not all under a
callsign subdomain name (i.e., [callsign].ampr.org). If a) or b) apply,
select "Domains" from the "DNS" menu, and then click on the "Resource
records" icon next to the ampr.org domain. This will list all of ~50,000
existing records (don't worry, it will paginate them!). You can then use
the "Search:" box to search for your records, as it performs a real time
search and also works on partial entries.
Once you have found your records, click on the "Claim" icon, which will
create a new ticket for an admin to process. Keep an eye out for ticket
updates, as the admin may wish to ask questions to clarify your request.
If the admin is happy with your request, your request will be approved,
and your DNS record will be assigned to your account. You can view the
record by selecting "My records" from the "DNS" menu.
Please note that this will *not* create a subdomain, just a standalone
record that you can manage.
IF YOU HAVE MORE THAN ONE RECORD UNDER A SUBDOMAIN, PLEASE DO NOT USE
THIS SECOND OPTION, AS IT WILL CREATE A NEW TICKET EACH TIME YOU CLICK
THE "Claim" ICON !!
As always, if you have any questions, please don’t hesitate to reach
out, and please report any bugs you run into at newportal(a)ardc.net,
providing as much detail as you can about the bug.
73,
Rebecca KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hello All,
Now we have the new portal up and running, if you need any help/support with anything 44Net related, instead of emailing me please can you raise a ticket on the portal. That way we can keep track of your request and there may well be others that can assist you, rather than waiting for me!
For general support please select “New support ticket” from the “Tickets” menu then select the most appropriate reason in the first dropdown.
If you would like to see other appropriate options in this selection/dropdown please feel free to open a ticket and let us know!
Thank you,
Chris - G1FEF
—
ARDC Administrator
Web: https://www.ardc.net
Hi all,
my 44 IP addresses are changed. There shouldn't be any impact unless
someone has any AXUDP links with my BPQ Node pointing to the IP Address
directly.
These are the new addresses, FQDN are the same:
iw2ohx.ampr.org - 44.134.24.1 -> (X)net AXUDP links are welcome here /
DXSpider links are welcome here
iw2ohx-vpn.ampr.org - 44.134.27.1 -> (X)net AXUDP links are welcome here
/ DXSpider links are welcome here
iw2ohx-bpq.ampr.org - 44.134.27.17 -> BPQ AXUDP links are welcome here
73 de iw2ohx
Op. Marco
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am
PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give
you a heads-up once we make the switch; expect some downtime starting at
about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
* A new ticketing system to improve support response time
* DNS management
* Modern secure framework
* Improved UI/UX
* Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space
assignment.
Also, along with any new launch – though we have done thorough testing
with the TAC and staff– we expect that folks will find some bugs. We
appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct
them to newportal(a)ardc.net.
73,
Rosy KJ7RYV
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
Hi, 44Net community -
We knew we would find some bugs when we launched the new Portal, and
indeed, we found them! What we didn’t foresee was the 1,000+ logins on
the new site in less than 24 hours – far, far more than expected. It’s
pretty exciting to see how much engagement there is with this new
rollout, even if it did cause us some hiccups.
Meanwhile, we are working as swiftly as possible to move through the
issues and questions that have come up in the past day or so. Below is a
summary of findings, actions taken, and next steps.
# Summary (tl;dr)
* The old Portal is now disabled, and the new portal is now available at
https://portal.ampr.org.
* You should now have access to your address space assignments, and
callsign verification will occur over the next 2-3 months. More details
about what happened and next steps can be found at the bottom of this
email.
* We will continue to stress test among ARDC staff and volunteers – and
in real time with all of you!
# Bugs fixed
Three main bugs have been identified and fixed:
* EULA scrolling / accept button not working in Windows 11
* Wrong email URL / caching issue
* Ticket #274 sent to multiple people without explanation
If you are still experiencing trouble with any of these three items, or
if something new pops up, please make a support ticket on the new
Portal, or send an email to newportal(a)ardc.net.
# Q+A
Here are some questions and answers that came up over the past few days.
Q: Where is my ‘Network’ menu?
A: The ‘Network’ menu is designed to appear once your callsign has been
verified. You should be able to see the menu now. Please let us know if
that is not the case.
Q: Why do I have to verify my callsign?
A: To use 44Net address space, an active amateur radio license is
required. Callsign verification helps to ensure that a user has the
credentials required (i.e., a license / callsign) to request address
space and / or access DNS records.
Q: Do you have any documentation about the new Portal?
A: Yes! You can see it here under ‘HowTo’ here:
https://wiki.ampr.org/wiki/Portal
As always, please bug us with any questions. Thank you for your patience
as we work through these issues.
73,
Rosy KJ7RYV
//
# More info about what happened with callsign verification / assignment
access
Though a small number of 44Net users’ callsigns had been verified in the
old Portal, the vast majority had not. Thus, we created a required step
for admins to verify call signs before granting users the ability to
access assigned addresses. Once verified, users have access to their
address space assignments.
Due to the unexpectedly high volume of sign-ins and the time it takes to
do callsign verification, we were suddenly hit with far more than we
could manage in a timely fashion, and people were suddenly not able to
access their address assignments.
Thus, in the interim, we have changed the settings so that everyone who
had assignments on the old Portal will be able to access their address
assignments immediately.
We will still do call sign verification, but it will now take place over
the next 2-3 months and with the help of a number of volunteers.
Callsigns that cannot be verified (despite best efforts) by that time
will lose access to their addresses until we can get verification.
If you have any questions about this new process, please don't hesitate
to ask in this thread.
73!
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
Greetings!
Is there a good place to find a good explanation of how to implement the 44 network? I’m probably making things more complicated in my head than they really are, but I don’t want to configure things wrong.
Thanks!!
73
Dave, AI7R
Hello 44Net,
As many of you have seen, the new Portal went live earlier today.
It's been so popular, in fact, that we've received much more traffic
than expected, with many hundreds of requests within a short period of
time. Some new bugs have been uncovered as well.
As a result, the new portal has temporarily been reverted to the old one
for <24 hours while we work through these bugs and backlog of tickets.
In the meantime, we ask that folks pause utilizing the portal.
Thank you all for your patience, and for helping us to stress test today.
More as soon as we can share it,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
Hey Everyone,
In an effort to streamline notices regarding ARDC news and updates, I
will continue to only email the link to the monthly ARDC Newsletters
here on the listserv. For other updates, I will post those on Groups.io.
If you're interested in receiving further notices about ARDC news, I
encourage you to check out https://ardc.groups.io/g/main and join the
community.
Thank you all for being a part of this community, and feel free to reach
out to me if you have any questions!
73,
Rebecca KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
If KDØTGF is reading this, or if anyone knows how to contact them, please could they drop me an email, and/or check their spam folder as I think my emails may be getting quarantined somewhere!
Thank you,
Chris - G1FEF
—
ARDC Administrator
Web: https://www.ardc.net
Hey Everyone,
* ARDC Grantees from the National Radio Astronomy Observatory (NRAO)
and the MORE Project will be at the IEEE Integrated STEM Education
Conference tomorrow (3/9): be sure to attend Workshop 5 at 11am led
by Jesse Alexander (WB2IFS, NARO), and check out the radio demos at
the MORE Project booth and learn about their program!
o Link to event: https://ewh.ieee.org/conf/stem/
* ARDC will be at the HamSCI Workshop happening from March 22 - 23. If
you're at the event, stop by our table and say hello. Also, be sure
to attend our talks on Saturday (3/23)!
o Link to event: https://hamsci.org/hamsci2024
* Check out more of our photos from the ARISS 40th Anniversary
Conference on ARDC's Twitter/X, Facebook, and LinkedIn pages.
o Twitter/X: https://twitter.com/ardc_73
o Facebook: https://www.facebook.com/ardc.73
o LinkedIn:
https://www.linkedin.com/company/amateur-radio-digital-communications/
Have a great weekend and 73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hi,
If KD0TGF is seeing this please can you email me direct.
If anyone knows KD0TGF please could you ask them to get in touch.
Thank you!
73,
Chris - G1FEF
—
ARDC Administrator
Web: https://www.ardc.net
Hey Everyone, The Feb. 2024 Newsletter is live! Check it out for our
most recent news and updates: https://www.ardc.net/?na=view&id=69Like
getting updates about ARDC? Subscribe to the Newsletter here:
https://www.ardc.net/about/newsletter/ 73, Rebecca KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hi all,
I’ve been trying off and on over the last few days to set up a VPN connection to amprnet to use my new allocation.
I’m not succeeding on multiple linux machines and a macOS device and seeing a couple of the same errors -
OpenSSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch
Cannot load private key file /etc/openvpn/client.key
Error: private key password verification failed
The first is related to, I assume, my user certificate - is this a fatal error and am I doing something wrong, has the advice changed from `cat certs/user certs/authorities > client.crt`?
Secondly, the password verification is confusing me - I have just imported a new tqsl cert generated this week, and in tqsl it advises me there’s no certificate passphrase. I’m not sure what to do here - if I try and export a .p12 from tqsl, and generate keys from that, I am asked for a password too and that ends in no progress.
I see the same errors in tunnelblick on MacOS.
Is there any reason I’m being asked for a password? My current LoTW password doesn’t resolve this. My concern is that there is some password I’m missing from when the certificate was first generated years ago and that now prevents me from accessing the VPN.
Cheers & 73
Hibby MM0RFN.
Hey Everyone,
* Rosy (KJ7RYV) gave some opening remarks this morning at the
ARISS40th Anniversary Conference, which continues through tomorrow.
* ARDC's 2023 Annual Report is live: check out the associated blog
post for a copy of the report and see our highlights from last year:
https://www.ardc.net/2023-ardc-annual-report-now-available/
* Our first Community Meeting of the year is*TOMORROW*(Saturday,
February 24, 2024) at 10am PST / 6pm UTC. Hope to see you there!
Have a great weekend and 73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
I'm trying to configure a gateway with Debian and ampr-ripd never responds. I tried several tutorials and it never works.
My network structure is as follows;
eth0 (192.168.0.10) --> (192.168.0.1) [router(mkrotik)] (192.168.70.100) --> (192.168.70.1) [router (mikrotik)] --> ISP
(I know, it's a little strange but I need the 2 mikrotiks)
I have configured my external IP (it is in bridge mode) with a dyndns. For this test the firewall is completely open.
First I create the tunnel:
ip tunnel add ampr0 mode ip local 192.168.0.10 ttl 64
ip link set dev ampr0 up
ip addr add 44.153.x.x/32 dev ampr0
ifconfig ampr0 multicast
Then I add the path:
ip rule add to 44.0.0.0/8 table 44 priority 44
Finally I launch ampr-ripd:
ampr-ripd -a 44.153.0.0/16 -i ampr0 -t 44 -d
This process never receives a response.
Is there some configuration missing or am I misunderstanding the process? Maybe the mikrotiks are missing some configuration? (are the connections under NAT)?
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
Hello everyone,
I’ve stumbled on a problem with my 44net connection and I’m hoping someone can shed light on what’s going on.
I’m connected using IPIP, and I can exchange traffic with other hosts that are also using IPIP (and hence appear in the RIP broadcasts).
Where I’m struggling is with a couple of subnets which perform their own BGP advertisements. I can reach them over the internet, but can’t from my 44net-connected system.
I can see traffic leaving my network for the hosts in question, encapsulated with a destination address of 169.228.34.84 (amprgw.ucsd.edu <http://amprgw.ucsd.edu/>), but my packets never reach the remote systems.
Any clues?
Mike Quin
Hey Everyone,
The December 2023 Newsletter is live: check it out for our latest
updates: https://ardc.net/?na=view&id=63
To receive regular updates about ARDC, please subscribe to our
newsletter: https://www.ardc.net/about/newsletter/
Thanks and 73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hey Everyone,
ARDC will be closing for the year beginning on*Saturday, December 16,
2023*, and we’ll return to the office on*Tuesday, January 2, 2024*.
From the ARDC team, we hope that you and yours have a fantastic holiday
season. Thank you all for a great 2023, and we’ll see you in 2024!
73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hey Everyone,
The November 2023 Newsletter is live: check it out for our latest
updates, including how to contribute to the AMPRNet Wiki:
https://www.ardc.net/?na=view&id=61
To receive regular updates about ARDC, please subscribe to our
newsletter: https://www.ardc.net/about/newsletter/
Thanks and 73,
Rebecca
KO4KVG
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hey Everyone,
If you're interested in what some of our grantees have been up to, check out our latest blog post that highlights the work from the folks at SIGNALS: Museum of Information Explosion and VBAS, both located in Huntsville, AL. Link: https://www.ardc.net/grantee-update-visiting-the-signals-museum-and-the-vba…
Have a great weekend and 73!
Rebecca
KO4KVG
Hello, I made an Allocation Request /24(BGP) on 7 Oct. and received a normal response via email.
I sent the ISP information for the announcement and my identity verification documents on Oct. 9th,
but did not receive a response, so I sent the information again on Nov. 1st, and still haven't received a reply from ardc.
I'm not sure if the information was sent to the authorities or not. How can I track the status?
73
E25RJL
Hello, 44Net community!
I'm writing for a couple of reasons. First, I'd like to introduce you to
our Communications Manager, Rebecca Key (KO4KVG), who joined our team
over the summer. She's an alum of Georgia Tech with a Ph.D. in
Chemistry. She's also an avid amateur radio enthusiast, particularly
with POTA, producing a number of related how-to videos. We're excited
that she's on the team and helping to keep our communications humming.
You can read more about her here:
https://www.ardc.net/ardc-welcomes-our-new-communications-manager-rebecca-k…
And you'll likely be hearing more from her for communications like this
one :)
Second - we're looking for new members for our 2024 advisory committees!
In 2024, we'll have 4 of them:
* Grants Advisory Committee (GAC) – reviews grant applications
* Technical Advisory Committee (TAC) – works on 44Net-related projects
and policies
* Conduct Review Committee (CRC) – helps to evaluate Code of Conduct
incident reports
* NEW for 2024: Grants Evaluation Team (GET) – evaluates and analyzes
grant reports
You can read more about each of these here:
https://www.ardc.net/ardc-committee-recruitment-2024/
If you're interested, please send a resume and brief cover letter to
hr(a)ardc.net. Deadline to apply is Wednesday 11/8.
Looking forward to hearing from you! And feel free to ask us any questions.
73,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
All,
I've recently sent emails to a few gateway operators regarding non-stop traffic to the DNS server dns-mdc[dot]ampr[dot]org. The clients make A and AAAA queries for the same domain at a rate that's highly unlikely to be legitimate software.
I first noticed this on another IP. In that instance, the client continued to query the server despite being rejected.
Perhaps the operators can share more information or insight on what they discover as they have time to work out the issue. For others, be mindful, remember to firewall and use good Internet hygiene.
73,
LynwoodKB3VWG
Hello,
Since there is no automated way to request a /24 allocation, I submitted a message to AMPRNET on the portal a few weeks ago and have received no response. Is there someone that handles these that I could contact?
73,
-Sam, KF0ACN
Chris, if I need to contact someone else, please let me know.
I'm needing to update some DNS entries for my subnet.
44.46.15.1 gateway.nr0q.ampr.org
44.46.15.2 airsupply.nr0q.ampr.org
44.46.15.3 eagle.nr0q.ampr.org
44.46.15.4 traffic1.nr0q.ampr.org
44.46.15.5 traffic2.nr0q.ampr.org
44.46.15.6 floyd.nr0q.ampr.org
44.46.15.10 oams.nr0q.ampr.org
44.46.15.194 one.nr0q.ampr.org
44.46.15.195 two.nr0q.ampr.org
Thanks
Matthew 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.
Hello everyone,
A quick question, what is the best solution, if possible, to have reverse DNS on a /24 announced in BGP?
Thank you friends !
--
Gary
F4HIN
Hello all, I’m sorry for contacting the main list, but I’m trying to reach Chris Smith, but I think my direct messages to him are going to spam.
Chris: YES. I would like to continue using the 44.4.57.0/24 BGP allocation. Please help me start the renewal process. I tried contacting you back in August to start the process, but I heard nothing back.
-Jeremy
To whom it may concern.
Greetings.
In my server logs every single hour I see the following entries:
Oct 4 05:21:31 linux conversd[1881152]: info (link Hub_EU): Catham_UK
detected loop with Mitchell: DEST Attica_GR. DEST already via Attica_GR
Oct 4 06:21:34 linux conversd[1881152]: info (link Hub_EU): Catham_UK
detected loop with Mitchell: DEST Attica_GR. DEST already via Attica_GR
Oct 4 07:21:38 linux conversd[1881152]: info (link Hub_EU): Catham_UK
detected loop with Mitchell: DEST Attica_GR. DEST already via Attica_GR
Oct 4 08:21:41 linux conversd[1881152]: info (link Hub_EU): Catham_UK
detected loop with Mitchell: DEST Attica_GR. DEST already via Attica_GR
This situation is going continuously more than a month.
Something, somewhere seem to be definitely misconfigured.
Possibly owner of offending convers server
can take appropriate action to fix this, please?
Best regards.
--
Tom - SP2L
https://www.sp2l.ampr.org
------------------------------------
It is nice to be important.
But it is more important to be nice!
Nobody is mistaken - so do I.
I've just powered on a Mikrotik hAP lite which I believe I had
recently correctly configured, i.e. traffic between the internet and my
44net subnet was flowing on its ether2-4 ports, however appears to now be
dropping incoming traffic to my subnet with Destination Unreachable ICMP
frames. I have checked and re-checked my config steps from scratch with no
success.
Would someone with an IPIP-connected 44net allocation, a working Mikrotik
setup, and 5 minutes of spare time mind please running "/export
hide-sensitive" on their Mikrotik and sending me the output so I can diff
it, to find my inevitably stupid error?
Thanks.
I think we need to understand that the use of the IP space of ARDC 44net, have Nothing to do with the use of the RF space a ham can use in his/her country , and/or the rules that apply to your country/frequency/modulation scheme/3rd party data/Identification and the use of other bands that are not ham radio like the ISM band.
What ARDC give you as rules of use of the IP space is just that, rules about the ip space, and the ip space can be use outside of the RF ham bands and even outside of the RF realms and just on fibers or UTP cable.
Now. If you think you need to put some ssid or mac adress to be able to use the 44net ip allocated to you on RF links, that need to be check with your ruling body in your country. And it will depend witch rules Apply if you are using the ISM band , or the ham bands.
Can a RF link travel from the ism band to the ham band to a fiber and then some cable and back to ham band and back into the ism band, totally.
Can this happen on many different country, totally. Making it very hard to Apply all the rules from every country and multiple bands.
So as I was saying, terms of service of ARDC.
Not mixing the 2 will be of great help to understand all of this.
Pierre
VE2PF
A few things mentioned about WiFI thus far in FCC land were not entirely accurate or could be easily avoided. I wanted to just note some things or offer as suggestions - as not to direct to any person in the chain or discourage healthy, civil (as I've read) and intelligent discussion:* One could change the BSSID (i.e. MAC address) of the Access Point, Ad-Hoc, etc. to a hexadecimal value representing the Callsign - problem solved* If one were using alloted channels and e.g. using an amplifier, such an example would otherwise require it to be licensed. * Another example might be altering the antenna of a [modern] Part 15 device, or experimental devices in WiFi Sensing radarBut with the latter examples, I digress.73,LynwoodKB3VWG
Hi all,
The Terms of Service <https://www.ardc.net/about/legal/terms-of-service/>
states:
*"**Your license permits You to use certain addresses exclusively for the
purpose of Amateur Radio communications and experimentation, or other
special uses as may be agreed to by ARDC"*
I was wondering if this was clarified anywhere with examples of acceptable
use cases? A few examples that I'm curious if they're permitted or not:
- Hosting a radio club website that's accessible from the public
internet, including from non radio amateurs.
- Providing general outbound internet access for radio amateurs
connecting via RF, whether its AX.25 or WiFi operating on the allocated
amateur radio frequencies
- Hosting not strictly amateur radio services such as an IRC server for
discussing cars, but it's *only *reachable from other 44net addresses
and RF users
- Providing general outbound internet access to servers and services
that might need to pull software updates from non-radio amateur servers.
- Providing connectivity to a radio amateur related server such as a DMR
Master, to other radio amateur related servers *outside* of 44net
Any guidance would be appreciated.
Matthew
2E0SIP
Just did a dig on ve6cic.ampr.org and it's returning with an IP that is no where near what I thought it should be. Could someone update my DNS record to point to 44.135.148.131?
Stephen Atkins
VE6CIC/VE6CPU/VE6STA/VE6SU
Sent with [Proton Mail](https://proton.me/) secure email.
Hi
> If there is no DNS A record for a tunneled amprnet destination host, the
traffic is not forwarded in either direction.
Does this mean a single A record for my gateway (44.61.31.1/27), or
multiple A records, one for each IP of my subnet?
Thanks
Tom M0LTE
Hello everyone. I've been playing with my 44 net addresses for a while now. I've got an Edgerouter X setup and I've attached a picture of the main config page for it. The edgerouter has an address of 44.135.148.129 and my computer has 44.135.148.130/27. Default gateway is 44.135.148.29. I've also had my DNS setup so it points ve6cic.ampr.org to 44.135.148.130 and my gateway on the portal points to my internet IP.
I run a CC Cluster and BBS on this machine. Is there a way to route from the internet (not on the 44 Net) to this machine?
[44Net.PNG]
Stephen Atkins
VE6CIC
Sent with [Proton Mail](https://proton.me/) secure email.
Thanks, TCP MSS was the answer!
On my router ( Mikrotik ):
/ip firewall mangle
add action=change-mss chain=forward new-mss=clamp-to-pmtu
passthrough=yes protocol=tcp
tcp-flags=syn
On Sun, Sep 17, 2023 at 4:02 PM Jonathan Lassoff <jof(a)thejof.com> wrote:
> That DNS resolution seems ok, 20.201.28.151 is one of the web frontend
> IPs. (Confirmed with their API's /meta endpoint:
> https://api.github.com/meta)
>
> However, an operation timing out implies that something along the path
> is filtering your TCP connection.
>
> Maybe use `tcptraceroute` to try and tell how far your initial TCP SYN
> packet is making it (to try and tell whom is filtering).
>
> The other thought that comes in mind in the context of TCP breaking
> while traversing VPNs (where small packets like ICMP pings are
> working) is that maybe something along the path is not clamping TCP
> MSS? Maybe try adding a `mssfix` option into the OpenVPN config (maybe
> sized 1420 bytes).
>
> --j
>
> On Sat, 16 Sept 2023 at 11:19, Henrique Brancher Gravina
> <henrique(a)gravina.com.br> wrote:
> >
> > gnutls-cli cannot connect to the host, it give me a timeout:
> >
> > $gnutls-cli github.com:443
> > Processed 137 CA certificate(s).
> > Resolving 'github.com:443'...
> > Connecting to '20.201.28.151:443'...
> > *** Fatal error: The operation timed out
> >
> >
> > But I cant ping the host:
> >
> > $ping www.github.com
> > PING github.com (20.201.28.151) 56(84) bytes of data.
> > 64 bytes from 20.201.28.151 (20.201.28.151): icmp_seq=1 ttl=111
> time=22.3 ms
> > 64 bytes from 20.201.28.151 (20.201.28.151): icmp_seq=2 ttl=111
> time=19.5 ms
> > 64 bytes from 20.201.28.151 (20.201.28.151): icmp_seq=3 ttl=111
> time=22.3 ms
> > 64 bytes from 20.201.28.151 (20.201.28.151): icmp_seq=4 ttl=111
> time=19.8 ms
> > 64 bytes from 20.201.28.151 (20.201.28.151): icmp_seq=5 ttl=111
> time=19.7 ms
> >
> >
> >
> >
> > On Sat, Sep 16, 2023 at 3:33 AM Jonathan Lassoff <jof(a)thejof.com> wrote:
> >>
> >> For what it's worth, I am able to successfully do git clones from IPv4
> >> Github from 44net BGP island space, and even that repo you list.
> >>
> >> That error suggests that something happened with GNUTLS while
> >> establishing a TLS connection. Maybe test just that with GNUTLS and
> >> run "gnutls-cli github.com:443"?
> >>
> >> On Fri, 15 Sept 2023 at 23:08, Henrique Brancher Gravina via 44net
> >> <44net(a)mailman.ampr.org> wrote:
> >> >
> >> > Hello,
> >> >
> >> > I am running a 44 network with bgp announces on Vultr ( mikrotik )
> and a VPN to my home ( mikrotik ) . Everything is working fine inbound and
> outbound traffic are being routed ok.
> >> >
> >> > The problem is that I can use github on the server on my 44 hosts.
> >> >
> >> > For example:
> >> >
> >> > # git clone https://github.com/Henriquegravina/DxccResolver
> >> > Cloning into 'DxccResolver'...
> >> > fatal: unable to access '
> https://github.com/Henriquegravina/DxccResolver/': gnutls_handshake()
> failed: Error in the pull function.
> >> > # root@odc1:/home/henrique/tmp# git clone
> https://github.com/Henriquegravina/DxccResolver
> >> > Cloning into 'DxccResolver'...
> >> > fatal: unable to access '
> https://github.com/Henriquegravina/DxccResolver/': gnutls_handshake()
> failed: Error in the pull function.
> >> >
> >> > Thanks for any help.
> >> > PU3IKE
> >> >
> >> >
> >> > _______________________________________________
> >> > 44net mailing list -- 44net(a)mailman.ampr.org
> >> > To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
>
Dear 44Net Members,
Many thanks to all of you who responded to the ‘44Net + Groups.io’
survey back in June. Thank you also for your patience in our follow-up,
as it’s been a very busy summer here at ARDC.
Here’s what we learned from the 54 folks who responded:
* 90% of you were familiar with Groups.io
* 52% of you were interested in moving from mailman.ardc.net to Groups.io
* The remaining 48% of you either wanted to remain on Mailman or wanted
more information about a move to Groups.io (with a pretty even split
between those two groups)
A nearly 50/50 split is not enough to warrant a migration of this
mailing list to Groups.io. It does, however, tell us that there is a
general interest in making the move, and that many of you would like
more information before making a decision one way or another.
In an effort to provide more information, in the coming months, our team
will put together some educational information about groups.io, so be on
the lookout. Until then, feel free to peruse around ardc.groups.io and
give some of the subgroups a try. Some information about how to join the
subgroups is provided below this email.
Depending on how things go, we may move the full mailing list over to
ardc.groups.io over time. For now, though, please consider this only an
experiment! If you have any questions, please don’t hesitate to reach
out to us at any time at contact(a)ardc.net. You can also post questions
and comments here or on ardc.groups.io.
Looking forward to the discussion!
73,
Rosy + ARDC Staff
/
For those of you who are interested in joining the mentined subgroups,
here’s how:
* Join the ‘Main’ group at ardc.groups.io.
* Once approved, you’ll be automatically added to the Community subgroup
for general discussions (the ‘Main’ group serves as an announcement
group, where only ARDC staff can post).
* From here, you can join many of the other subgroups for special
interest topics.
44Net VPN Subgroup: https://ardc.groups.io/g/net-44-vpn
44Net Wiki Subgroup: https://ardc.groups.io/g/wiki/
Subgroup list (which has some info about each group):
https://ardc.groups.io/g/main/subgroups
If you get stuck, our resident groups.io expert John Hays K7VE is here
to answer any questions. Reach out any time: john.hays(a)ardc.net
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
Hi
Has anyone setup the IPIP tunnel successfully in Mikrotik? I think the instruction in Wiki is written for ROS 2.0. Things has changed a lot and I have trouble following. I created the IPIP tunnel in the interface and not sure what to do next. I added my IP subnet to the IP tab. The RIP configuration menu is very different now.
Kun
Hello,
I am running a 44 network with bgp announces on Vultr ( mikrotik ) and a
VPN to my home ( mikrotik ) . Everything is working fine inbound and
outbound traffic are being routed ok.
The problem is that I can use github on the server on my 44 hosts.
For example:
# git clone https://github.com/Henriquegravina/DxccResolver
Cloning into 'DxccResolver'...
fatal: unable to access 'https://github.com/Henriquegravina/DxccResolver/':
gnutls_handshake() failed: Error in the pull function.
# root@odc1:/home/henrique/tmp# git clone
https://github.com/Henriquegravina/DxccResolver
Cloning into 'DxccResolver'...
fatal: unable to access 'https://github.com/Henriquegravina/DxccResolver/':
gnutls_handshake() failed: Error in the pull function.
Thanks for any help.
PU3IKE
Good Evening,
I noticed that the amprwiki has some information that could use some updating/knowledge additions to make onboarding easier for new end-users.
1. On all gateway setups, there should be notices about having to enter your gateway WAN onto the gateway list on the 44net portal, as well your allocation being broadcasted by your gateway.
2. Explanations on delay times in receiving RIPv2 packets (1 hour to update, 5 mins/announcement). A few of the instruction sets say "wait a few minutes" but dont explain why and don't all explain that your gateway needs to be registered before anything can happen.
3. Additional Documentation for folks who are using coordinator-maintained VPN gateways
4. General cleanup and some additional explanations on how each piece of the IPIP tunnel works for folks who want to learn how to run the system, to ensure that we can have more people using the gateway rather than BGPing out of frustration.
I've worked for several orgs cleaning up documentation so questions can be answered efficiently, I'm more than happy to volunteer my time to help clean things up if needed!
73,
-M.
K1YUU
Hi,
been having a few issues with IPIP tunnels of late. On my original
server (a R-Pi), which I recently resurrected, ampr-ripd suddenly
started segfaulting on startup for no obvious reason. The old system
also had a few limitations and an ageing SD card, so I decided to move
my gateway to a VPS, and updated the gateway IP in the portal accordingly.
I ported my setup to the new server and built the latest (2.41)
ampr-ripd. I've verified that I am receiving the RIP broadcasts, and
ampr-ripd writes the encap.txt file in /var/lib/ampr-ripd. However, I
am not seeing any route updates in table 44 (the routing table I use for
ampr routing - I am using the recommended policy routing). The only
clue I get as to something not being right is a line:
SIGALRM received
I'm guessing that signal has something to do with the routing table not
being updated, but there's no other clues to help me troubleshoot.
Anyone have any ideas?
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
Hi, 44Net!
Following much interest from our grants community, ARDC has created a
forum on groups.io: https://ardc.groups.io/g/main
Here, our grantees and others can discuss specific topics and connect
with one another: https://ardc.groups.io/g/community/topics
We invite you to take a peek and, if you like, join some of the
conversations.
What we like about groups.io: it integrates seamlessly into users' email
accounts, and there is a web interface feature as well. On the admin
side, it provides many tools to support collaboration like file sharing
that are simply not available in our current setup.
For these reasons, and support of fostering cross-pollination between
our grantees and the 44Net community, our team is considering moving the
44Net mailing list from mailman.ampr.org to groups.io. Some 44Net
subgroups – VPN and the Regional Coordinators – are already using it.
Before moving the entire mailing list, we want to get your feedback:
what do you think?
Please let us know by filling out this survey:
https://survey.alchemer.com/s3/7386497/Poll-44Net-Groups-io
And of course, feel free to share your thoughts and any questions in
this thread. John Hays K7VE is our resident groups.io expert, and he’s
standing by to answer any questions you may have.
Many thanks and 73,
Rosy + ARDC Staff
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
Hi there!
Last week I found I was removed from the portal. I followed the
instructions and did a CONTACT US. I haven't heard from anyone yet.
Can someone please followup on this?
many thanks. 73, Leon wa4zlw
One of the subnets that I coordinate (44.60.0.0/24) has been attached to
the AMPR gateway called CENUTA at 213.74.201.250 without my knowledge. I
need to have this released back to me.
Other subnets that are showing as connected to this gateway are:
44.174.100.0/24 PY1EGG
44.165.48.0/24 SQ3C
44.161.220.0/22 LX0BGP
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
44net Coordinator - Northeast USA
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying
(The work praises the man.)
"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan
Hello all,
in case Hessu, OH7LZB is watching this list, just to inform that the amprnet-
vpn-ca.crt referred here https://wiki.ampr.org/wiki/AMPRNet_VPN has expired on
5/5/2023.
This has the following effect:
2023-07-03 11:18:43 VERIFY ERROR: depth=1, error=certificate has expired:
O=AMPRnet, CN=OH7LZB VPN service CA, serial=15176845288007500179
BR
Apostolos
Hello 44Net!
I'm writing with some exciting news: we've updated ardc.net so that it
is responsive and accessibility friendly, with some clearer hierarchy as
well as imagery on the home page.
Please take a look when you have some time: https://www.ardc.net/
Though we've tested on many browsers and devices, as it goes with any
launch, you are likely to find a thing here or there that needs to be
addressed. Please let us know what you find, if anything.
Many thanks to Chris for his work helping us to wrangle this beast, and
also to Dan Romanchik KB6NU (whose last day was yesterday) for his work
implementing and tweaking the new theme, not to mention content updates.
Speaking of modernization, it's also worth noting that we're in alpha
testing for an updated Portal. Looking very forward to sharing more
about that as soon as we're able.
As always, reach out with any questions or thoughts.
Many thanks and 73,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
Hi,
I made an allocation request for a /29 in the 44.132.128.0 subnet a couple
weeks ago but haven't received a reply yet, what should my next steps be?
Regards
Alice
EA4FYQ
Hello everyone!
I am trying to configure 44net in linbpq. Can anyone offer any suggestions on where I have gone wrong?
My network is: 44.98.28.32 / 29
according to the email I received.
My local machine ip address is 192.168.2.225 on adapter enp6s0f0
A free static address on my network is 192.168.2.223
My gateway / router is at: 192.168.2.1
my lbpq32.cfg file includes:
IPGATEWAY
44ENCAP 192.168.2.223 ;LAN address
Adapter enp6s0f0
IPAddr 44.98.28.1
IPNetMask 255.255.255.248
IPBroadcast 193.168.2.255 ; < where X is your IP 1 or 0
IPGateway 192.168.2.1 ; Gateway to Router, may not be
IPPorts 1,3
ARP 44.98.28.1 KO4YAW-2 2 D
ROUTE 44.98.0.0/29 44.92.35.1 D
****
Thanks and '73,
-Chris
KO4YAW
This coming Sunday is the Indianapolis 500 “The Greatest Spectacle in Racing." If you would like to work the iconic W9IMS (Indianapolis Motor Speedway Amateur Radio Club) on 44net, connect your local IRLP repeater to Reflector 9200 beginning at 09:00 eastern (13:00 UTC) Sunday.
Why is this pertinent here? Well, IRLP is making considerable use of 44net for a significant part of our infrastructure including Reflector 9200 at 44.127.48.1. There are just shy of 500 repeaters and other nodes in the network with 44net IP addresses, including mine at 44.127.48.7 over a cellular link.
—
Dave K9DC, K9IP
I'm having trouble running dvswitch allstarlink via ampr's ip connected by IP Tunnel. I am now able to make the acquired ips ping or traceroute externally unless connected with dvswitch allstarling application do you have any suggestions for this problem?