Hi Rob,
I agree 100%. Having two networks that really don't talk to each other
but with a common address space is ridiculous.
Along the lines you mention, perhaps ARDC should consider a "grant", or
perhaps a better word, RFQ from various ISP's who could set up such a
thing and run it. This would eliminate all the bickering/discussion of
what is the best way/protocol to do something like this as well as
determining where to locate POP's around the world.
Vultr comes to mind simply because they are doing it for a number of
AMPR users already. Of course, other ISP's could do it, but Vultr is the
most often mentioned company.
I would think that the chosen ISP would set up one AMPR network with
connectivity to all 44 network addresses and give an option to any
subscriber to have his segment BGP announced or not.
73, Mark, N2MH
On 7/19/22 14:16, Rob PE1CHL via 44net wrote:
> I hope that, rather sooner than later, we can offer a new connectivity
> option for AMPRnet that does not require tricks in your router, does
> not depend on a static address, works with CGNAT, etc.
> The objective is to use a modern standard VPN instead of IPIP
> (wireguard, openvpn, l2tp/ipsec or whatever) to connect to a
> relatively local point of presence that will handle the further
> routing towards other users and the internet for you, with good
> latency and reliability.
> That will end the continuous battling with the IPIP mesh that
> unfortunately is the reality of today.
> Software would run on a standard router (not the router from your ISP,
> more like a MikroTik or UBNT or openwrt device), or e.g. a Raspberry Pi.
>
> We need to lower the bar for making connections. Like you, most
> people want to put applications online rather than fighting with
> protocols that are not easy to deploy anymore.
>
> Rob
>
> On 7/19/22 19:48, Mark Herson, N2MH via 44net wrote:
>> Thanks to everyone who replied.
>>
>> Nobody actually directly answered the question that I posed of having
>> actually used this router and/or having some experience with it.
>> Thus, I'll take that as a collective "no".
Hello,
As I mentioned in my previous email I got new 44 IPs for amprnet.
But my old IPs still appear in the net system. For example:
# host ok2pen.ampr.orgok2pen.ampr.org has address 44.63.16.112
ok2pen.ampr.org has address 44.177.10.10
ok2pen.ampr.org mail is handled by 10 ok2pen.ampr.org.
44.63.16.112 is the new correct IP but
44.177.10.10 an old not valid more IP.
How can I rid off of that old 44.177.10.10 IP?
73
Dalibor OK2PEN(PY2ZEN)
email: ok2pen(a)seznam.cz
Hello,
Chris G1FEF has cancelled all my subnets i.e.
44.177.010.0/28
44.177.10.253/32
44.177.10.254/32
and alocated one common subnet 44.63.16.112/28.
For my amprnet axip link I used IP 44.177.10.10
with hostname ok2pen.ampr.org. Now with the new subnet
I changed above IP to new 44.63.16.112 but how can alocate
ok2pen.ampr.org to this new IP?
For those who have axip link with amprnet node OK2PEN-5
please change routing to:
route OK2PEN 44.63.16.112 b
At present axip links with:
ZL2BAU, VE3CGR, Ve2PKT, SV1CMG, VK6HGR, PI1LAP, W9JUN and N9LYA
For subnet 44.177.10.253/32 I had corresponding IP 44.177.10.253
with hostname ok2koj.ampr.org. So with cancelling said subnet
I am going to change above said IP to 44.63.16.111 but also
need to alocate hostname ok2koj.ampr.org for this new IP.
For subnet 44.177.10.254/32 which had correspondig IP 44.177.10.254
with hostname ok0nmmg.ampr.org . There is some delay to reestablish
dns of its public IP. After reestablishing that dns I am going to change
old amprnet IP 44.177.10.254 to new 44.63.16.110 but also
will need to alocate hostname ok0nmg.ampr.org.
So need some help.
73 de Dalibor OK2PEN (PY2ZEN)
email: ok2pen.seznam.cz
Hello,
google translate did not translate my message very well and the terms
in French
translated into English "sound less good"... Now if you knew what
happened in the
background, you would have better understood my reaction...
The answer was to the message of F4HIN.
I will now explain the terms used which were not the correct ones.
I have kept the AMPR listing up to date for years, I react quickly to
requests and I see
that I am being lynched in a public square. So yes if there was a
problem with the IPs I would
have appreciated that F4HIN spoke to me directly to see what was wrong
with my configuration
if there was a security breach instead of his message here.
Note that I will never use my prerogatives to have any power. There is
no implied filtering
of any kind and this is also the reason why I had kept the
administration of these IPs because
I know very well that it would not be so with others in France as it
happened in packet radio
at one time in France...
When i write "my" IP (or are mine) that is to say "the IP 44.151.29"
is my own allocation.
Of course they don't belong to me.
So sorry for the poor translation of Google translate and my hot reaction
but the accusations I have been unjustly subjected to have clearly
annoyed me.
Hope that google translate do the good job this time. I am not sure.
So end for me here. I do not want to create a troll.
Best regards,
Ludovic - F5PBG.
Nota : Thank's to Chris to explain me the problem of my answer
and now i understand the reaction of "Dan C."...
> *De :* f5pbg--- via 44net <44net(a)mailman.ampr.org>
> *Envoyé :* lundi 18 juillet 2022 08:04
> *À :* 44net(a)mailman.ampr.org
> *Objet :* [44net] Re: Abuse or not abuse ?
>
> Hello,
>
> I remind you that it was I who delivered the IP you have...
> you better respect me...
>
> These are my IPs and they are not used for commercial
> applications contrary to what you claim in your claims.
>
> So I strongly advise you to stop your not very hamspirit activity...
>
> I guess the purpose was to try to harm me, you probably thought
> I wasn't reading the list...
>
> This kind of behavior deserves your allowance to be removed.
> but I have principles unlike you.
>
> You attack me personally then it remains a personal attack and
> I don't mix genres.
>
> So, for Christ, I have been managing IPs for a long time, even
> before the ampr.org server existed and long before this young
> F4HIN radio amateur was even a radio amateur...
>
> My 44.151.129 IP are not use for commercial use of course.
>
> The server belongs to my son indeed but I ask him for allocations,
> the IP 44.129 are mine.
>
> I know very well the goal of this young radio amateur f4hin, it is
> to take
> the management of the network in my place... So given what I read on
> telegram mailing lists, I wish you good luck...
>
> Best regards,
> Ludovic Vuillermet - F5PBG
> Coordinator of 44.151
Hello,
I remind you that it was I who delivered the IP you have...
you better respect me...
These are my IPs and they are not used for commercial
applications contrary to what you claim in your claims.
So I strongly advise you to stop your not very hamspirit activity...
I guess the purpose was to try to harm me, you probably thought
I wasn't reading the list...
This kind of behavior deserves your allowance to be removed.
but I have principles unlike you.
You attack me personally then it remains a personal attack and
I don't mix genres.
So, for Christ, I have been managing IPs for a long time, even
before the ampr.org server existed and long before this young
F4HIN radio amateur was even a radio amateur...
My 44.151.129 IP are not use for commercial use of course.
The server belongs to my son indeed but I ask him for allocations,
the IP 44.129 are mine.
I know very well the goal of this young radio amateur f4hin, it is to take
the management of the network in my place... So given what I read on
telegram mailing lists, I wish you good luck...
Best regards,
Ludovic Vuillermet - F5PBG
Coordinator of 44.151
Le 17/07/2022 à 12:50, F4HIN via 44net a écrit :
> Hello
> I'm going to tell you a story that does not makes me laugh at all.
> I am part of an nonprofit ISP in France.
> This ISP offers internet access, but also BGP tunnels to announce your own IP on the internet.
>
> Some time ago, by several discussions, I found that a person member of the association and not ham had an allocation /24 Hamnet announced via its own AS via the AS of the association.
> Afterwards, after several information gathering, I noticed that this person was using it to propose hosting of small virtual machines and was allocating a Hamnet IP on these hosted VM.
> I warned this person that he did not have to have a Hamnet block, and that he should not do this type of use since he is not a ham
> His answer was clear "it's free, and I don't care".
>
> In reality, after searching on the AMPR portal, this block was assigned to a ham. This ham is the national Hamnet coordinator of a country, and the person using and misusing it is none other than his son who is not a ham!
> I did not say anything until now, out of respect for the national coordinator.
>
> Today, there is a member of the association who complains about receiving scans from a Hamnet IP belonging to the block used by the non-amateur.
> jul/15/2022 0l:02:56 system, error, critical login failure for user root from 44.151.129.214 via ssh
> jul/15/2022 0l:02:56 system, error, critical login failure for user msfadmin from 44.151.129.214 via ssh
> jul/15/2022 0l:02:57 system, error, critical login failure for user root from 44.151.129.214 via ssh
> jul/15/2022 01:02:57 system, error, critical login failure for user root from 44.151.129.214 via ssh
> jul/15/2022 0l:02:57 system, error, critical login failure for user postgres from 44.151.129.214 via ssh
> jul/15/2022 01:02:58 system, error, critical login failure for user service from 44.151.129.214 via ssh
> jul/15/2022 01:02:58 system, error, critical login failure for user vagrant from 44.151.129.214 via ssh
> jul/15/2022 01:02:58 system, error, critical login failure for user admin from 44.151.129.214 via ssh
>
> To summarize, this person:
> - Has a hamnet block without being a ham radio operator,
> - Has obtained a legitimate hamnet block from another amateur radio operator,
> - makes a "commercial" use of it by assigning IP to VMs for clients or friends of his,
> - Let the VMs get drilled and scan/hacked with a hamnet IP.
>
> I think it's time to set the record straight, stop assigning blocks to people who use them for commercial or non-amateur use.
> What do you think about it?
>
> --
> Gary
> F4HIN
> _______________________________________________
> 44net mailing list --44net(a)mailman.ampr.org
> To unsubscribe send an email to44net-leave(a)mailman.ampr.org
Hello
I'm going to tell you a story that does not makes me laugh at all.
I am part of an nonprofit ISP in France.
This ISP offers internet access, but also BGP tunnels to announce your own IP on the internet.
Some time ago, by several discussions, I found that a person member of the association and not ham had an allocation /24 Hamnet announced via its own AS via the AS of the association.
Afterwards, after several information gathering, I noticed that this person was using it to propose hosting of small virtual machines and was allocating a Hamnet IP on these hosted VM.
I warned this person that he did not have to have a Hamnet block, and that he should not do this type of use since he is not a ham
His answer was clear "it's free, and I don't care".
In reality, after searching on the AMPR portal, this block was assigned to a ham. This ham is the national Hamnet coordinator of a country, and the person using and misusing it is none other than his son who is not a ham!
I did not say anything until now, out of respect for the national coordinator.
Today, there is a member of the association who complains about receiving scans from a Hamnet IP belonging to the block used by the non-amateur.
jul/15/2022 0l:02:56 system, error, critical login failure for user root from 44.151.129.214 via ssh
jul/15/2022 0l:02:56 system, error, critical login failure for user msfadmin from 44.151.129.214 via ssh
jul/15/2022 0l:02:57 system, error, critical login failure for user root from 44.151.129.214 via ssh
jul/15/2022 01:02:57 system, error, critical login failure for user root from 44.151.129.214 via ssh
jul/15/2022 0l:02:57 system, error, critical login failure for user postgres from 44.151.129.214 via ssh
jul/15/2022 01:02:58 system, error, critical login failure for user service from 44.151.129.214 via ssh
jul/15/2022 01:02:58 system, error, critical login failure for user vagrant from 44.151.129.214 via ssh
jul/15/2022 01:02:58 system, error, critical login failure for user admin from 44.151.129.214 via ssh
To summarize, this person:
- Has a hamnet block without being a ham radio operator,
- Has obtained a legitimate hamnet block from another amateur radio operator,
- makes a "commercial" use of it by assigning IP to VMs for clients or friends of his,
- Let the VMs get drilled and scan/hacked with a hamnet IP.
I think it's time to set the record straight, stop assigning blocks to people who use them for commercial or non-amateur use.
What do you think about it?
--
Gary
F4HIN
Hey,
I am wondering who I need to contact to move my request for ip space along.
AddedNetworkWaiting for
2022-06-02 07:58:15 44.135.0.0/24 coordinator
73,
VE7OOT - Clayton
Hello all,
So I have been assigned a block of IPs and have successfully created a gateway. I am able to pass traffic trough it as expected and it works as one would expect. However...
My intended use case for amprnet includes a lot of VOIP traffic, which as we all know is heavily dependent on latency and bandwidth. I am currrently utilizing the IPIP tunnel approach to connect my gateway into the system.
My questions are,
1. If I deploy my VOIP services on 44Net with my current configuration, what are the pitfalls?
2. If I announce my gateway via BGP will my throughput then be limited to uscd gateway, or will it be based on my connection speed?
3. I know some vpn capabilities have been introduced into the system, I presume that my connection will then be rated based on the connection at the VPN server location.
Thank you so much! I appreciate the opportunity given here to learn and expand my knowledge.
73,
de KC2IDB
Hello,
Maybe someone can help me with below mentioned problem:
I am starting amprnet net with that ampr-ripd using a script bellow
#! /bin/bash
# dotun.sh script written by N1URO on June, 2013
AMPRIP='44.177.10.10'
IPMASK='255.255.255.255'
HOST="medvidek.ddns.net"
COMMIP=`host $HOST 2>/dev/null | head -n 1 | awk '{print $4}'`
AMPRSERVER='169.228.34.84'
echo $COMMIP
modprobe ipip
echo "1" > /proc/sys/net/ipv4/ip_forward
ifconfig tunl0 $AMPRIP netmask $IPMASK
ip tunnel change ttl 64 mode ipip tunl0
ip link set dev tunl0 up
ifconfig tunl0 multicast
/usr/sbin/ampr-ripd -t 1 -a $COMMIP -i tunl0 -p pLaInTeXtpAsSwD -f wlan0
-v -s -r
ip route add default via $AMPRSERVER dev tunl0 onlink table 1 src $AMPRIP
ip rule add from 44/8 pref 1 table 1
ip rule add to 44/8 pref 1 table 1
exit 0
And it worked well but now (and sometimes) I cannot receive packets from
that
AMPRSERVER to my tunl0 device on udp port 520 which is open (see below):
root@raspberrypi:/usr/sbin# netstat -lntup | grep 520
udp 1152 0 0.0.0.0:520 0.0.0.0:* 14076/ampr-ripd
and:
root@raspberrypi:/usr/sbin# ifconfig tunl0
tunl0: flags=4289<UP,RUNNING,NOARP,MULTICAST> mtu 1480
inet 44.177.10.10 netmask 255.255.255.255
tunnel txqueuelen 0 (IPIP Tunnel)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 35280 bytes 9295234 (8.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Port 520 is also opened in net router and using:
# tcpdump -i wlan0 port 520
I cannot see amprnet sevrver response.
TKS/73 Libor, sysop of node OK2PEN-5
