I do not think that a DNS entry for the gateway is needed to receive the RIP updates. If you register your gateway and assign a subnet to it, you get the data via the IPIP tunnel from amprgw.

At least it was that way at some point. Maybe Chris could clarify this.

To my understanding, the only moment you need those DNS entries is if your hosts need to pass traffic through amprgw to the internet and back, and only affects the routing/firewall part at amprgw.

An "official" statement on this topic would be useful.

Marius, YO2LOJ

On 28/09/2022 02:15, David Ranch via 44net wrote:

Hello Harold,

The ampr-ripd traffic does go over port 520 but within the IPIP tunnel itself (IP protocol 4).  To receive ampr-ripd traffic, you must have a DNS entry assigned to one of your AMPR IPs. FInally, have you been able to confirm if your ISP allows/forwards IP protocol 4 (IPIP)?

--David
KI6ZHD




On 09/27/2022 02:02 PM, 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@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org



_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org