Christian Vieser wrote: > Hi all, > > after a half day searching for an error, sniffing and upgrading to the > newest shorewall version I give up and the problem to you. I have > following configuration in my /etc/shorewall/masq: > > #INTERFACE SOURCE ADDRESS > vlan7::10.231.0.0/16 192.168.222.0/24 10.231.113.30 > vlan7 192.168.222.0/24 10.1.0.38 > > Towards a special network I need a masking of all outgoing traffic to > 10.231.113.30, in all other cases I use the basic address of the > interface for masking. What happens? Nothing - no packet towards an > address in 10.231.0.0 leaves the interface. If I swap the entries in the > config file, the packets go through the interface, but are masked with > the wrong IP (what would be the expected behavior). So I'm sure that > there is no fault in the other config files. > > I know that I had the same construction working some month ago. Only > difference is, that there it was a "real" eth interface and now it's a > vlan. > > Any idea?
Please forward the information requested at http://www.shorewall.net/support.htm#Guidelines (case 3). We need it in order to see what Netfilter rules are being generated. -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: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
