Re: routing to ping automatically via the correct network

tincanteksup <[email protected]> Wed, 05 Aug 2020 22:28:47 +0000
Newsgroups org.kernel.vger.lartc
Message-ID <[email protected]>
Email has threading as well .. try it.

On 05/08/2020 23:20, Marc Roos wrote:
>   
> This is how my test environment looks like. The 'host route' which I
> create with 192.192.168.114 is so health checks reach the container.
> This route is only set if the ip range is different from the range of
> the host.
> 
> 
> 
> 
> ip netns add testing
> 
> ip link set testeth0 netns testing
> ip link set testeth1 netns testing
> 
> ip netns exec testing bash
> 
> ifconfig testeth0 192.168.10.232
> ifconfig testeth1 cc.cc.cc.43
> 
> # until this, enough to ping networks
> # can ping 192.168.10.333, 192.168.10.2, cc.cc.cc.1
> # not: own ip's?? cc.cc.cc.43, 192.168.10.232
> 
> ip route add default via cc.cc.cc.1 dev testeth1 table 81
> 
> # necessary for the host 192.192.168.114 to ping cc.cc.cc.43
> ip route add 192.168.10.114 dev testeth1 scope global table 81
> 
> ip rule add from all to cc.cc.cc.43 table 81
> ip rule add from cc.cc.cc.43 table 81
> 
> # can ping dd.dd.dd.130
> 
> 
> 
>