Re: [44net] PKTerrors.

On 26/01/2020 03:01, Marius Petrescu via 44Net wrote: Yep and I can: piver - [~] $ ping -c3 -Iampr0 44.182.21.1 PING 44.182.21.1 (44.182.21.1) from 44.131.170.1 ampr0: 56(84) bytes of data. 64 bytes from 44.182.21.1: icmp_seq=1 ttl=64 time=48.1 ms 64 bytes from 44.182.21.1: icmp_seq=2 ttl=64 time=47.5 ms 64 bytes from 44.182.21.1: icmp_seq=3 ttl=64 time=49.8 ms --- 44.182.21.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 47.581/48.503/49.803/0.979 ms Still can't ping 44.92.21.35 or 44.92.21.50 I've had this working a while back, but might have been pre-raspian upgrade, what could that have done? And any suggestions what I should do about leaking non-44 packets over ampr0? Thanks. Bill (M1BKF) OK, zapped that. Running "amprd -d" gets me: Default gateway: 192.168.1.1 via dev 2. Creating tunnel: ampr0 Prefix for ampr0: 44.131.170.1 Network prefix length not set - assuming "/8" Receiving RIPv2 for ampr0: yes Saving routes for ampr0: yes Setting routes received by ampr0: no RIPv2 gateway ignore list for ampr0: 90.155.50.1 Call home set to M1BKF@JO02pp Loaded 753 entries from /var/lib/amprd/ampr0.txt Setting all routes on ampr0. Set host route to 44.130.237.0 on dev 2. Set host route to 44.130.236.0 on dev 2. Set host route to 44.130.235.0 on dev 2. Set host route to 44.130.234.0 on dev 2. Set host route to 44.130.107.0 on dev 2. Set host route to 44.94.17.128 on dev 2. Set host route to 44.130.104.0 on dev 2. Set host route to 44.130.105.0 on dev 2. Set host route to 44.130.106.0 on dev 2. Set host route to 44.136.150.0 on dev 2. Calling home for tunnel ampr0 on port 59002: M1BKF@JO02pp