Ruben,
It won't enter trough the internet unless your tunnel GW address is BGP announced. And if the system is BGP announced, it won't need the tunnels.
For those also providing tunnel endpoints on BGPd systems using 44. endpoints, a simple addition of the on the 169.228.34.84 address to the -a parameter will restore the previous situation.
On tunnel only systems, the behavior would be the same as the ubiquitous default route via amprgw on most setups. Just that we have those individual routes to play with.
Marius, YO2LOJ
On 24.02.2019 16:28, Ruben ON3RVH wrote:
Won’t that break things? Exit through ampr gateway but entry through the internet? I know some statefull firewalls that won’t like that very much.. Where ampr router is on one interface and the internet on another
Ruben - ON3RVH
On 24 Feb 2019, at 15:03, Brian Kantor Brian@bkantor.net wrote:
Marius,
I know I said this would take quite a bit of time/work, but I dreamed up a clever way to get it done, and I'm ready to turn that on if you think it really won't hurt any existing installations. - Brian
On Sat, Feb 23, 2019 at 09:15:34PM +0200, Marius Petrescu wrote: So, wouldn't it make sense to publish BGP routed networks that do not have 'tunnel ' set in the portal as RIP routes using amprgw as gateway?
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net