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