All,
Checking the portal, there are no call sign details for this endpoint/subnet pair. I ask that the Canadian operator at the route below - properly configure their clients to use 44net IPs to query the DNS server at 44.60.44.3.
Thanks and 73,
- Lynwood
KB3VWG
--------------------
44.135.179.16/29 via 184.65.186.101 dev tunl0 proto 44 onlink window 840 44.135.179.24/29 via 184.65.186.101 dev tunl0 proto 44 onlink window 840
2019-09-27 11:14:36.019 0.004 UDP 184.65.186.101:50202 -> 44.60.44.3:53 6 438 1
2019-09-27 11:14:36.169 0.012 UDP 184.65.186.101:15513 -> 44.60.44.3:53 27 1971... 1
Hi all,
We are migrating our TKNet network to AMPRNet addressing. For machines
directly connected to Internet (ie : XLX, DMR), we are using
44.190.11.0/24 range. Those addresses are geo-located in Chicago. This
has funny consequences. F/ex, when doing speed tests with online
services such as nperf.com, the automatically-selected "nearest" server
is very far from here :-)
I have absolutely no idea about how geolocation works. Just for
curiosity, where is this information taken from ? The Whois database ?
But Brian's address is in San Diego, not in Chicago...
Is there an easy way to change geo-location information for a specific
AMPR subnet ?
Thank you in advance. 73 de TK1BI
Hi Brian,
Thanks for answer. It's strange because of this host has IP registered in AMPR DNS. I suppose it is a routing trouble: ICMP packet cannot find a way back to tunnel (because of I can ping Raspberry PI connected to this interface).
It's not a big problem but I would like to know why id doesn't work.
Regards,
Tomek
--- 2019-09-25 15:31:00 +0200 CEST 44net-bounces+hf8n=winlink.org(a)mailman.ampr.org wrote: ---
>On Wed, Sep 25, 2019 at 02:23:06PM +0100, Alistair Mackenzie via 44Net wrote:
>> Are you running rip to tell the amprgw of your prefix?
>
>Amprgw doesn't listen for RIP. All its routing information comes
>from the encap file published by the portal, which contains the route
>44.165.1.48/28 via 91.199.89.253
>
>However, only the addresses 44.165.1.49 and 44.165.1.50 are entered
>in the DNS, so only they will be pingable from outside 44net. Any
>other address on that subnet will not due to /32-level filtering on
>amprgw. If it is desired to be able to ping 44.165.1.48, for example,
>there must be an entry in the DNS for it to enable the ingress filter.
> - Brian
>
>_________________________________________
>44Net mailing list
>44Net(a)mailman.ampr.org
>https://mailman.ampr.org/mailman/listinfo/44net
Hi,
I joined to ampr network recently, set up IPIP tunnel on Cisco router and directly connected Raspberry Pi 3 (44.165.1.50/28) to one of its interfaces (44.165.1.49). It works great, I can ping and connect to and from this Pi device from outside.
The problem is that I cannot ping this Cisco's 44.165.1.49/28 interface from outside. It should work as 44 packet leaves a tunnel, finds this internal interface and should get back to tunnel. I have PBR route who directs all packets from this interface directly to tunell.
Each host has a valid 44 DNS address.
Interfaces:
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 91.199.89.253 YES NVRAM up up
FastEthernet2/0 44.165.1.49 YES manual up up
Tunnel0 unassigned YES unset up up
Routing table:
44.0.0.0/8 is variably subnetted, 244 subnets, 12 masks
C 44.165.1.48/28 is directly connected, FastEthernet2/0
L 44.165.1.49/32 is directly connected, FastEthernet2/0
Config:
interface Tunnel0
no ip address
tunnel source GigabitEthernet0/0
tunnel mode ipip
tunnel destination 169.228.34.84
route-map AMPR-ROUTE permit 10
match ip address 11
set default interface Tunnel0
access-list 11 permit 44.165.1.48 0.0.0.15
ARP:
Protocol Address Age (min) Hardware Addr Type Interface
Internet 44.165.1.49 - 001e.f7af.4cd9 ARPA FastEthernet2/0
Internet 44.165.1.50 27 b827.eb7e.840a ARPA FastEthernet2/0
Any ideas?
Regards,
Tomek
Hello,
I’ve some errors with startampr script. Any idea to help me for resolve these mistakes?
73
F1SXO Frédéric
------------------------------
fred@f1sxo:/ampr-ripd $ sudo ./startampr
cannot determine tunnel mode (ipip, gre, vti or sit)
Error: Nexthop has invalid gateway.
---------------------------------
Ifconfig :
tunl0: flags=4289<UP,RUNNING,NOARP,MULTICAST> mtu 1480
inet 44.151.31.6 netmask 255.255.255.255
tunnel txqueuelen 1000 (IPIP Tunnel)
---------------------------------
Extract from startampr script :
### ENABLE IP FORWARDING ###
sysctl -w net.ipv4.ip_forward=1
## Allows traceroute to respond using 44net IP of tunl0 or br-amprlan ##
echo 1 > /proc/sys/net/ipv4/icmp_errors_use_inbound_ifaddr
################### AMPRNet IPENCAP UBUNTU SYNTAX
modprobe ipip
ip tunnel add tunl0 mode ipip
###NUMBER tunl0 with a /32 from your allocation
###(you may reuse this IP on an Ethernet interface
ip addr add 44.151.31.6/32 dev tunl0
ip link set tunl0 mtu 1480 up
ip tunnel change tunl0 ttl 64 tos inherit pmtudisc
################### OPTIONAL - DEFAULT ROUTE FOR INTERNET ACCESS
ip route add default dev tunl0 via 44.151.31.6 onlink proto 44 table 44
################### POLICY-BADED ROUTING #######################
###OPTIONAL LOCAL RULES
ip rule add from 44.151.31.6 to 192.168.1.0/24 table main priority 22
#REQUIRED RULES
ip rule add to 44.151.31.6 table main priority 44
ip rule add dev tunl0 table 44 priority 45
ip rule add dev 44.151.31.6 table 44 priority 46
ip rule add from 44.151.31.6 table 44 priority 47
###SOME OF THIS MAY BE NEEDED TO RUN ampr-ripd from another folder than the compile option
73
F1sxo
Frédéric ZULIAN
https://www.ampr.org/grants/
ARDC has now given 110k to ARISS. I've asked ARISS if they condone ARDC by
accepting this fraudulently obtained funding.
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
Is anyone experiencing a flood of pings from 44.4.92.50 (ke6i.ampr.org).
I'm seeing pings every second. The pings are flowing from the amprnet
server via encap.
root@linux:/jnos3/# tcpdump -n -i sl0 src 44.4.28.50
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sl0, link-type RAW (Raw IP), capture size 262144 bytes
03:01:43.969910 IP 44.4.28.50 > 44.17.0.128: ICMP echo request, id 27171, seq 25514, length 64
03:01:44.972033 IP 44.4.28.50 > 44.17.0.128: ICMP echo request, id 27171, seq 25515, length 64
03:01:45.975101 IP 44.4.28.50 > 44.17.0.128: ICMP echo request, id 27171, seq 25516, length 64
03:01:46.975808 IP 44.4.28.50 > 44.17.0.128: ICMP echo request, id 27171, seq 25517, length 64
03:01:47.976128 IP 44.4.28.50 > 44.17.0.128: ICMP echo request, id 27171, seq 25518, length 64
73 Jack AA6HF (44.17.0.128)
Hi,
Anyone out there familiar with adding the 44net to a Ubiquiti USG via the UniFi controller....??? I had it working by forwarding IPIP to a Linux box on my inside network, but it quit working after a few days. At first, I thought Comcast was blocking Protocol 4, but running tcpdump on the WAN interface shows the packets are there, but not being forwarded to the inside network.
Because the USG has the same OS as the EdgeRouter, I followed the AmprNet setup steps for the EdgeRouter. The rub there is the config does'nt get saved in the USG because it's over-written by the UniFi controller. In order to store the config, you have to add a config file (config-gateway-json). It works...but it's not pretty (one example is my internal network is not nat'ing outgoing packets to the 44 network).
So long story short...has anyone else done this or had experience with it....???
Feel free to reply here...or reply via my email listed on QRZ...
73's
-Albert
I am trying to configure the tunnel on Ubuntu 18 on a cloud VM just to figure out how the configuration works.
I am looking at http://wiki.ampr.org/wiki/Ubuntu_Linux_Gateway_Example and have trouble configure the interface.
I have configure
auto ens4
iface ens3 inet static
address {my allocated IP}
netmask 255.255.255.252
However, the ifup ens4 command will failed to bring up ens4 interface. And of course when running ampr-run.sh and find_pass.sh will resulted in Setting SO_BINDTODEVICE: No such device.
Any advices on how to set it up on Ubuntu 18?
Thanks
Kun
To: Marius
I tried to compile that ax25-patch and it is terminating with the error:
make[2]: *** [scripts/Makefile.build:279:
/opt/ax25_patch/ax25/ax25_route.o] Error 1
make[1]: *** [Makefile:1601: _module_/opt/ax25_patch/ax25] Error 2
make[1]: Leaving directory '/usr/src/kernels/5.2.13-200.fc30.x86_64'
make: *** [Makefile:26: ax25.ko] Error 2
The compiler is in fedora 30 (gcc-9.2.1-1)
73
Libor OK2PEN (PY2ZEN)
