On 12/1/2009 1:22 PM, Rowan R. wrote:
192.168.1.0/24(masq)zone:int (eth0)-------[f/w ]----108.***.***.60 (eth2) zone:ext
[box]-----68.***.***.234(eth1) zone:dmz
for some reason my masq net cannot connect to eth1 �doesn't matter if it's zone:ext or zone:dmz
I ran the following
Dec 1 13:16:45 linux-fw kernel: [104035.169151] martian source 68.164.***.234 from 192.168.1.22, on dev eth0 Dec 1 13:16:45 linux-fw kernel: [104035.169162] ll header: 00:c0:9f:19:da:3f:00:21:70:b8:ff:c9:08:00
I remember seeing a but report somewhare about martian source message with regard to suse firewall. One solution was to set a flag to turn off the messages, but this seemed like a bandaid, as an outbound connection should never show martian source. This nonsense is why I run shorewall instead of suse firewall. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org