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
