Hi Tom, I have tried Host file with: inet bond0:0.0.0.0/0!xxx.xxx.128.0/23,xxx.xxx.131.0/24 blacklist
This works and achieves the same result as breaking the 0.0.0.0/0 net into two /1's So I will stick with this method unless you come up with an update to Shorewall so that 'blacklist' is not required in hosts. Thanks, Trent O'Callaghan -----Original Message----- From: Tom Eastep [mailto:[email protected]] Sent: Friday, 2 July 2010 9:59 PM To: Shorewall Users Subject: Re: [Shorewall-users] http://www.shorewall.net/FAQ.htm#faq84 On 7/1/10 10:17 PM, Trent O'Callaghan wrote: > Hi Tom, > > Sorry for the confusing email. > > the attachment is only for your use to check for a Bug. > Happy to receive your findings vi [Shorewall-users] > Thanks, Trent. Your workaround is okay; another approach would be to specify 'blacklist' in the host file entry that includes 0.0.0.0/0 rather than breaking that net into two /1's: inet bond0:0.0.0.0/0!xxx.xxx.128.0/23,xxx.xxx.131.0/24 blacklist I will give some thought toward how to make this work with your original configuration. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
