> > Here is the format of the masq file: > > eth0 10.0.0.0/24 x.x.x.123 > > eth0 10.0.0.80 x.x.x.117 > > eth2 10.1.1.40 x.x.x.97 > > #eth4:0 10.1.4.4 x.x.x.113 > > eth0 10.0.0.5 x.x.x.118 > > eth0 10.0.0.35 x.x.x.118 > > eth0 10.0.0.150 x.x.x.118 > > I think we're going to have to see a 'shorewall dump'. You reported that the > server's IP address was 10.4.4.4 yet that host isn't mentioned in your masq > file. So I don't know if you are trying to obfuscate (which just annoys > those of us who are trying to help you and delays a solution to your > problem) or whether this is the problem.
I understand. On my previous shorewall setup the eth4 was not listed in the masq file either. So the above snippet excluding "eth4" is what was in the previous server's masq file. The point being that neither eth4, web4 nor the ip 10.4.4.4 was listed in the masq and they are not listed in my new server's masq file. I tried adding it, but maybe I don't understand the syntax or usage. Brad B. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
