You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My problem is that my host system (OpenWrt) cannot reach container(s)/pod(s) properly and eventually I was able to fix this by changing the route.. route coming from cni is:
10.129.0.0/24 dev cni-podman0 proto kernel scope link src 10.129.0.1
I can fix this with following:
ip route del 10.129.0.0/24
ip route add 10.129.0.0/24 dev cni-podman0 proto kernel scope link via 10.129.0.1 src $LAN_IP
10.129.0.0/24 is my cni network subnet, and gw is 10.129.0.1
so I am wondering if we could have optional fields to route with via and src - netlink go module used already does support it.
I have requested this change also from containernetworking/plugins
Adding optional fields for src and via shouldn't be that difficult..
The text was updated successfully, but these errors were encountered:
My problem is that my host system (OpenWrt) cannot reach container(s)/pod(s) properly and eventually I was able to fix this by changing the route.. route coming from cni is:
10.129.0.0/24 dev cni-podman0 proto kernel scope link src 10.129.0.1
I can fix this with following:
10.129.0.0/24 is my cni network subnet, and gw is 10.129.0.1
so I am wondering if we could have optional fields to route with via and src - netlink go module used already does support it.
I have requested this change also from containernetworking/plugins
Adding optional fields for src and via shouldn't be that difficult..
The text was updated successfully, but these errors were encountered: