On 9/3/19 6:37 AM, Matt Darfeuille wrote: > On 9/3/2019 11:37 AM, Noboby is Perfekt via Shorewall-users wrote: >> Hi ! I have a problem with zones after update from 4.4.19.4 to 4.4.20-3 >> or older. >> under 4.4.19.4 it's working but after upgrade to 4.4.20-3 ... >> >> Sep 3 11:20:06 router kernel: Shorewall:FORWARD:REJECT:IN=bond0 >> OUT=bond0.33 SRC=172.30.12.6 DST=192.168.255.128 LEN=84 TOS=0x00 >> PREC=0x00 TTL=254 ID=30916 DF PROTO=ICMP TYPE=0 CODE=0 ID=27875 SEQ=102 >> >> Sep 3 11:20:07 router kernel: Shorewall:FORWARD:REJECT:IN=bond0 >> OUT=bond0.33 SRC=172.30.12.6 DST=192.168.255.128 LEN=84 TOS=0x00 >> PREC=0x00 TTL=254 ID=37328 DF PROTO=ICMP TYPE=0 CODE=0 ID=27875 SEQ=103 >> >> >> >> Any Hints ? >> > > 4.4 is EOL, see one for the currently-supported releases. > > Is this issue still present in Shorewall 5.2.3.4? > > 1) http://shorewall.org/support.htm#First >
As Matt says, you are dealing with two Shorewall releases that are both more than 8 years old (4.4.20.3 was released in June of 2011). But it appears that the IN interface in the messages that you posted above is bond0 which probably isn't defined to Shorewall. Given that, I suspect that the problem isn't with Shorewall at all, as the IN interface is determined by the IP stack and not Shorewall. -Tom -- Tom Eastep \ Q: What do you get when you cross a mobster with Shoreline, \ an international standard? Washington, USA \ A: Someone who makes you an offer you can't http://shorewall.org \ understand \_______________________________________________
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
