28 Sep
2022
28 Sep
'22
4:21 a.m.
Harold,
Since the RIPv2 packets are sent IPIP encapsulated from amprgw to your
registered gateway, it has nothing to do with your ISP blocking that port.
If your IPIP tunnels are working, so will the RIP delivery. On the other
hand, if your ISP blocks IPIP (IP protocol 4), none of the tunnels will
work and all efforts are futile.
Marius, YO2LOJ
On 28/09/2022 00:02, Harold via 44net wrote:
Hey gang. Kinda new here for Ive been dabbling with
this for a few years though. I have been trying to use the ampr-ripd daemon without any
luck and have come to the conclusion that my ISP blocks port 520 which I believe is the
port used.
With that said, i have also come to the conclusion that at this time, the encap.txt file
is still accessible via ftp from the portal.ampr.org.
Is "wget ftp://USER:PASSWORD@portal.ampr.org/encap.txt" a valid ftp solution
and if so where is the USER:PASSWORD derived from?
Is it our user:password into the portal?
Thanks all
Harold K7ILO
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org