25 Jan
2020
25 Jan
'20
9:01 p.m.
Additionally, it seems to be working from 44.182.21.1:
root@vps62907:~# ping 44.131.170.1
PING 44.131.170.1 (44.131.170.1) 56(84) bytes of data.
64 bytes from 44.131.170.1: icmp_seq=1 ttl=64 time=47.6 ms
64 bytes from 44.131.170.1: icmp_seq=2 ttl=64 time=47.6 ms
64 bytes from 44.131.170.1: icmp_seq=3 ttl=64 time=48.0 ms
64 bytes from 44.131.170.1: icmp_seq=4 ttl=64 time=48.0 ms
64 bytes from 44.131.170.1: icmp_seq=5 ttl=64 time=47.6 ms
64 bytes from 44.131.170.1: icmp_seq=6 ttl=64 time=49.1 ms
64 bytes from 44.131.170.1: icmp_seq=7 ttl=64 time=47.3 ms
64 bytes from 44.131.170.1: icmp_seq=8 ttl=64 time=47.9 ms
64 bytes from 44.131.170.1: icmp_seq=9 ttl=64 time=48.0 ms
root@vps62907:~# traceroute -I 44.131.170.1
traceroute to 44.131.170.1 (44.131.170.1), 30 hops max, 60 byte packets
1 m1bkf.ampr.org (44.131.170.1) 53.323 ms 54.589 ms 56.038 ms
root@vps62907:~#
On 26.01.2020 04:55, Marius Petrescu via 44Net wrote:
BTW, if using the parameter
rip_password =
you should enter the password, or just delete/comment the parameter
for the default value.
Leaving it like that would assume an empty password, which doesn't work.
On 26.01.2020 04:42, Marius Petrescu via 44Net wrote:
For use with amprd (not ampr-ripd), the interface
is correctly
subnetted (/8, meaning the whole ampr network is reachable by that
interface, as per before the /10 sale).
Also, the routes are internal to amprd, and not in any routing table
as expected when using ampr-ripd.
There may be another issue when using recent kernels (4.9 and newer):
Because of the changes in the kernel, ipip protocol handling by the
kernel is done incorrectly in case of raw sockets, and will result in
sending a icmp protocol unreachable back to the communication partners.
This can be solved by filtering outgoing icmp messages, or use the
latest amprd version which features a kernel plugin to work around
this problem.
I would strongly recommend to drop amprd and switch to the native
ipip tunnel handling and ampr-ripd.
Marius, YO2LOJ
On 25.01.2020 18:54, lleachii--- via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net Bill,
Also, I noticed your interface is Ethernet with a 1500 MTU?
Also, your interface is improperly subnetted as /8 (255.0.0.0). Your
network is a /30 (or 255.255.255.252).
root@OpenWrt:~# ip route show table 44 | grep
90.155.50.144.131.170.0/30 via 90.155.50.1 dev tunl0 proto 44 onlink
window 840
Are you certain that you have the tunnel setup?
Feel free to message me offline if you're running Linux/OpenWrt.
- KB3VWG
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net