Simon Matter wrote: >> Shorewall 3.4.3 is not able to handle interfaces option proxyarp. >> >> I attach smallest possible fix patch I could find out. >> >> This should fix because there is code to check if lib.proxyarp meed to >> be loaded and load if necessary. So replacing older check with >> -n $LIB_proxyarp_LOADED check should fix situation. > > I can't reproduce your problem, tried it with 3.4.2 and 3.4.3. Did it work > for you with other 3.4.x versions?
Simon, The problem is not that Shorewall rejects the option -- it accepts it but then does not set the interfaces's 'proxyarp' flag in /proc *unless there is also at least one entry in /etc/shorewall/proxyarp*. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
