Tom Hendrickx wrote:


my entries are almost exactly  like in the example
www.shorewall.net/3.0/NewBridge.html
only in the hosts I've not used any exceptions
and for interfaces I've used standard options out of leaf and followed
www.shorewall.net/SimpleBridge.html

You can't mix and match between those two articles and expect it to work. You either need to restrict connections through your bridge or you don't -- there's no middle ground.



My interfaces file looks like this:
#ZONE INTERFACE BROADCAST OPTIONS loc br0 192.168.1.255 routeback,dhcp,routefilter,norfc1918 #LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE and my hosts file like this: #ZONE HOST(S) OPTIONS loc br0:192.168.1.0/24 #LAST LINE -- ADD YOUR ENTRIES BEFORE THIS LINE -- DO NOT REMOVE
> thx for the reply!

That configuration makes no sense and Shorewall is telling you that. The entry in /etc/shorewall/hosts is redundant since you have already defined the 'loc' zone to include ALL hosts routed through br0. What possible value could the entry in /etc/shorewall/hosts add? Nothing!

-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

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to