On 8/15/07, David Mohr <[EMAIL PROTECTED]> wrote: > On 8/15/07, David Mohr <[EMAIL PROTECTED]> wrote: > > Did you check your masquerading settings? Sounds like that is not > > turned out for eth4 anymore. > > Of course I meant "turned on"
Right! Well, that's part of the confusion I have. Because on the old system, everything worked as needed, so I copied everything exact config to the new system. Except for the fact that I upgraded Shorewall. I have 3 dmz's each with only one machine behind them. They all exhibit the same behavior. They are using their own 10.x address when the source of communicating with machines on the internet starts from the machine. So, I didn't change the masq file. But I tried, I put different things there, but it didn't help. I also changed the nat file which didn't seem to help either. 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 bb ------------------------------------------------------------------------- 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
