|
Shorewall version = shorewall-5.1.2.1-1.el7.noarch uname = 3.10.0-514.10.2.el7.x86_64 Tied 2 of 3 interfaces together using "Channel Bonding" described
at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/4/html/Reference_Guide/s2-modules-bonding.html
[not to be confused with Bridging] Interfaces: mails enp5s0 logmartians=1,arp_filter,arp_ignore=2,nosmurfs,tcpflags,blacklist loc bond0,enp4s0f+ nosmurfs,tcpflags Once shorewall is started, "shorewall clear" has no effect, loc interface remains blocked. Even "systemctl restart NetworkManger.service" has not impact. Appears that shorewall is not playing nice with the bonding configuration hardwired into /etc/sysconfig/network-scripts/ifcfg-bond0 and the two interfaces. Technically, the interfaces are each a "slave" of the master "bond0" with the slaves loosing their IP Address to the bond0 and only one address is assigned. I am guessing that shorewall is reading the ifcfg-enp4s0f* files directly rather that after the bond is set up??? |
------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
