Problem with IP network routes from containers - different than from host (StrongSwan)

[ZW3B (LAB3W.ORJ 🇫🇷 🇪🇺)]

I opened the same topic on the forum :

Problem route table 220 (strongswan) from a container

Hello everyone. I have a routing problem from an LXC container. After setting up a VPN, StrongSwan, it uses a particular table, routing table 220. For information, Linux routing tables are configured in this file: root@pve:~ $ cat /etc/iproute2/rt_tables # # reserved values # 255 local 254 main 253 default 0 unspec # # local # #1 inr.ruhep So, as I pointed out, Containers do not query table 220 (strongSwan). I’ll run the procedure that makes me say this …

Good day to all.