On 11.04.2014 03:17, Bart Kus wrote:
Having said all that, I haven't actually implemented/tested this design since my AMPR allocation is announced via BGP. Please do let me know if it works out for you! It should retain present functionality and make you 44net-anycast compatible going forward.
I'm pretty sure it will work like you described for normal Linux/Mikrotik Gateways.
However I still see an issue with my Gateway which it seems is not easy to solve: - My Gateway is speaking to !44/8 using the ISP with its commercial IP address.
- My Gateway is speaking to other AMPR IPIP Gateways using IPIP tunneling with its 44 ip address.
- My Gateway is speaking to 44/8 (which will include the direct BGP connected 44 Gateways) using another IPIP tunnel to a special Gateway (which is able to send source44 packets to the internet) using its 44 ip address. <- I will do this since I want to use my 44net IP address while I'm speaking to other 44net amateur radio stations...
So far everything is fine. Now I have a new requirement to use 44.24.221.1 as an IPIP gateway for 44.24.240.0/20. In this case I *don't* want to use IPIP in IPIP :) Challenge accepted ;)
As for now I did put a static route to 44.24.221.1 via my ISP gateway. I think the best way might be to patch Marius ampr-ripd if we will ever see 44.24.240.0/20 via 44.24.221.1 on the RIP-broadcasts we get from AMPRGW.
73, Jann