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
{{ message }}
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
There are some issues using weave on k8s together with shorewall.
I understand my setup is a playground, and the k8s shouldn't be installed on a bare metal with a firewall, so this is for reference in case someone else stumble on those issues, really.
if the "iface" extension is installed on the node, shorewall uses it, but the weave pod doesn have it, resulting in Can't find library for match 'iface'
weave does a iptables -A INPUT -i weave -j WEAVE-NPC-EGRESS, resulting in the rule ending up after the reject from shorewall, ie
Chain INPUT (policy DROP)
num target prot opt source destination
1 KUBE-FIREWALL all -- anywhere anywhere
2 KUBE-SERVICES all -- anywhere anywhere ctstate NEW /* kubernetes service portals */
3 KUBE-EXTERNAL-SERVICES all -- anywhere anywhere ctstate NEW /* kubernetes externally-visible service portals */
[zone related rules]
12 ACCEPT all -- anywhere anywhere
13 Reject all -- anywhere anywhere
14 LOG all -- anywhere anywhere LOG level info prefix "Shorewall:INPUT:REJECT:"
15 reject all -- anywhere anywhere [goto]
16 WEAVE-NPC-EGRESS all -- anywhere anywhere
Solutions:
I ended up removing the extension from my system. Shorewall seems fine without it.
I manually add a iptables -I INPUT 4 -i weave -j WEAVE-NPC-EGRESS to duplicate the rule before the reject
The text was updated successfully, but these errors were encountered:
I'm not sure what to do with this. Generally where two or more pieces of software are trying to manipulate the same iptables chains they run into trouble.
If there is an API for shorewall this could be a feature request to use that API. Or perhaps shorewall defines chains which can be used to add rules without fighting.
There are some issues using weave on k8s together with shorewall.
I understand my setup is a playground, and the k8s shouldn't be installed on a bare metal with a firewall, so this is for reference in case someone else stumble on those issues, really.
Can't find library for match 'iface'
iptables -A INPUT -i weave -j WEAVE-NPC-EGRESS
, resulting in the rule ending up after the reject from shorewall, ieSolutions:
iptables -I INPUT 4 -i weave -j WEAVE-NPC-EGRESS
to duplicate the rule before the rejectThe text was updated successfully, but these errors were encountered: