Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Network\s+namespace\,\s+ipvlan\s+and\s+IPVS\s+source\s+NAT\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Network\s+namespace\,\s+ipvlan\s+and\s+IPVS\s+source\s+NAT\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: Network namespace, ipvlan and IPVS source NAT (score: 1): Author: Mahesh Bandewar ( ) <maheshb@xxxxxxxxxx>; Date: Tue, 20 Oct 2020 21:41:34 -0700; Unfortunately iptables and IPvlan don't do well together, especially the L3* modes. L3s mode is a little better but please keep in mind iptables functionality that involves "forwarding" path, is simp; /html/lvs-devel/2020-10/msg00024.html (13,673 bytes)
2. Re: Network namespace, ipvlan and IPVS source NAT (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Tue, 20 Oct 2020 21:00:59 +0300 (EEST); Hello, Make sure /proc/sys/net/ipv4/vs/conntrack is set to 1 to allow IPVS to keep the netfilter conntracks for its packets. This is supported with the CONFIG_IP_VS_NFCT=y kernel option. Regards -- J; /html/lvs-devel/2020-10/msg00023.html (12,170 bytes)
3. Network namespace, ipvlan and IPVS source NAT (score: 1): Author: Damien Claisse <d.claisse@xxxxxxxxxx>; Date: Tue, 20 Oct 2020 12:32:25 +0000; Hi, I'm trying to understand a limitation in ipvlan/netfilter that prevents doing routed IPVS with source NAT inside a namespace. Setup is the following: there is an "lvs" namespace, with an ipvlan i; /html/lvs-devel/2020-10/msg00021.html (10,841 bytes)

Current List: 1 - 3
Page: [1]