Hello All,
I am new to AMPR NET and I am trying to understand how to connect to AMPR NET from OPEN VPN. I am not sure if I have OPEN VPN correctly configured yet. If someone could please provide some basic setup and instructions how to connect to AMPR NET from OPEN VPN. Thus far I have searched the web and have not found much info besides configuration errors in OPEN VPN that others have encountered.
1. Can anyone please let me know what message I will receive on the OPEN VPN to let me know it is working properly.
2. And once OPEN VPN is configured correctly how do I connect to the AMPR NET?
3. Will I need any kind of 44 address to access the AMPR NET from OPEN VPN or can I still explore AMPR NET just thru the OPEN VPN?
thanks in advance,
Thomas Fuller
KE4QCM
Hello 44Net Mailing List,
There has been a lot of discussion on this list about the state of
44Net. Some people like how it works, some would like to see an upgrade.
In order to make an informed decision that takes a variety of viewpoints
into account, ARDC is conducting an assessment. For the first phase,
we’ve put together a survey, which we'd love for you to fill out. Our
aim is to get input from as many people as possible to help influence
the network’s next chapter.
Click here to go to the survey:
survey.ardc.net
(Please note that the above is a redirect.)
We expect that it will take around 15 minutes to complete.
The survey is currently being translated into French, German, and
Japanese, shoud you prefer to take it in another language. Thank you for
your patience as we complete professional translations. We’ll post them
here as soon as they are ready!
It’s important to note: the survey is not a voting mechanism - it’s a
research tool. We’ll also be conducting interviews and focus groups with
a subset of users. Results from all research will be shared publicly
(personal information excluded) on ampr.org.
If you have questions about this survey or are interested in being
interviewed or part of a focus group, reach out to us at any time:
contact(a)ardc.net. You can also follow the assessment’s progress by
signing up for our newsletter.
Thank you in advance for sharing your input - we look forward to reading
your responses!
Warmly,
Rosy & the ARDC team
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
Chris
For our routing we now have our Static IP address from T-Mobile 5G.
It is: 162.191.104.176
We have tried the Unbuntu Linux info but have had no success for
the IPIP tunnel.
Do you need any further information as the encap(date).txt does not show
our allocation: 44.63.63.128/26 in the encap file?
Previous Email ...
C
44.63.63.128 /26 might be non listed.
We are not up yet.
M
K7MDI
While these might not fit ham radio, is there anyone one this list
familiar with these
who can give me the difference between the sc model and the sc+.
Thanks
Hello!
Here's my setup and problem.
I originally setup my ER-X (successfully) using the "Setting up a
gateway on Ubiquiti EdgeRouter" instructions. I was able to interact
with the AMPR gateway, but discovered that I of course couldn't access
the various other 44net subnets. So I decided to switch to the
instructions under "Installing ampr-ripd on a Ubiquiti EdgeRouter or
EdgeRouter X".
I believe I did a good job of "unrolling" the changes from the first
instructions. I removed my previous 'tun0' interface, associated
firewall rules, etc (basically, anything I created in the first set of
instructions, I removed, and have verified via the ER-X config tree).
Then I created my IP-IP tunnel setup using the second set of
instructions. Here's what I have:
My modem to the outside world is my AT&T Uverse DSL modem. I have it in
DMZplus mode where the ER-X (which lives 'behind' the modem) is actually
assigned the external IP of 23.118.163.99. All traffic for any port
should get pushed to the ER-X.
eth0 on the ER-X is the WAN connection to the modem. eth1/3/4 go to
various other home network VLANs. eth2 is configured for my 44net
subnet (44.46.1.56/29). The router is 44.46.1.57. I have one host (a
Raspberry Pi) on the subnet at 44.46.1.62. DNS for kc4upr.ampr.org is
mapped to 44.46.1.62; I do not have a DNS entry for the router itself
(don't know if that's a problem???).
tun44 is setup per the instructions, with the address as 44.46.1.57/29,
the local-ip as 23.118.163.99, the remote-ip as 0.0.0.0, and
encapsulation as ipip.
I have the firewall rules configured per the instructions. I downloaded
and installed ampr-ripd; the only tweak I made to the ampr.sh script was
to add "-L KC4UPR@EM48qr" (I did not add any -a entries).
I also installed the status wizard. Checking the status wizard, I see
that the ripd daemon is running, and there are 737 routes. I see 4
sensible static routes, 5 bypass routes that I assume make sense, and
then a bunch of AMPR routes that look similar to what comes out of the
encap.txt file.
I do see that my status and location show up correctly at
http://www.yo2loj.ro/ampr-map/, and that my status is updating every 5
minutes per the ampr-ripd daemon. I looked at the source code, and
verified that the way that the script "phones home" is via IP
44.182.21.1. So "something" on my system must be able to actually
access 44net, right???
Here are my problem observations, however:
- I cannot seem to access anything on 44net, whether via my Raspberry Pi
or directly from the router. Pings never return, and traceroute all
ends at the router (44.46.1.57).
- Looking at my firewall policies, reviewing the stats, 0 packets/bytes
have been processed by my "allow ipip from wan" rule for the wan-local
policy (it's the first rule). Zero (0) packets whatsoever have been
processed by either my 44Net-in or 44Net-local policies. So clearly
something is not right there...
- I ran 'show ip route' on the router. There are 4 routes associated
with 44Net: 1 for my subnet, connected to eth2. One for the router
itself, connected to tun44. The other two routes are for 44.0.0.0/9 and
44.128.0.0/10, both via 169.228.34.84; both marked 'inactive' (is that a
problem?).
- I also ran 'show interfaces tunnel tun44'. It shows lots of TX bytes,
but 0 RX bytes.
- Also, I noticed that on the ER-X 'Routing' page, I can filter on
'RIP'. There are no routes under RIP... should it be that way?
Obviously my tunnel isn't working (even though I somehow still update
location???). Any thoughts?
Thanks,
Rob KC4UPR
--
scrape.sdf.org
It was a good survey covering many items of interest and needs.
My only issue was not being able to fill in my email address before submitting. Oh well.
73,
Doug, N6UA
DN71qd, Cheyenne, WY
Douglas Tabor
dtabor(a)estesvalley.net
If K7JLR is present on this list, please could you email me direct?
If anyone knows K7JLR please could you ask them to contact me?
Thank you
Chris - G1FEF
I'm a licensed operator in Mesa, Arizona, and was wondering how I could get into contact with my regional operator? Does anyone here know where I could find his or her contact information?