Re: Setting route destination for DNAT addresses

2019-04-12 Thread Brian Topping
> On Apr 12, 2019, at 4:34 AM, Ondrej Zajicek wrote: > > On Sun, Apr 07, 2019 at 10:52:23PM -0600, Brian Topping wrote: >> The problem is when a service on the same host as the container needs >> to connect to the DNAT address presented for the container. Because the >> local kernel routing

Re: Setting route destination for DNAT addresses

2019-04-12 Thread Ondrej Zajicek
On Sun, Apr 07, 2019 at 10:52:23PM -0600, Brian Topping wrote: > The problem is when a service on the same host as the container needs > to connect to the DNAT address presented for the container. Because the > local kernel routing table is set to blackhole for an address, the > traffic is

Setting route destination for DNAT addresses

2019-04-07 Thread Brian Topping
In this thread[1], I realize I created a new problem in the BIRD BGP configuration with `dest = RTD_BLACKHOLE`. Setting a destination to blackhole works great when the routes are being propagated (no ICMP unreachable is sent by the kernel) and an address being managed by Kubernetes DNAT