To be honest it looks as though my susefirewall config file has got mashed,
as im sure that was originally 192.168.0.0/255.255.255.0
Would that be correct?
-----------------------------------------------
Sent by freemail.servebeer.com
Signup for your free 100mb Mail account today!
Full pop3/smtp accounts available!!
-----------------------------------------------
-----Original Message-----
From: Togan Muftuoglu [mailto:toganm@dinamizm.com]
Sent: 27 February 2005 11:43
To: 'Suse Mailing List'
Subject: Re: [SLE] Problems with susefirewall2
* Stephen Furlong;
Ok here goes ; FW_FORWARD="0/0,0/0,udp152:49159" FW_FORWARD_MASQ="192.168.0.0/49152:49159,192.168.0.10,tcp,49152:49159"
there can not be a netblock with this mask 192.168.0.0/49152:49159 A forward masquerade rule consists of 1) source IP/net, 2) destination IP (dmz/intern), 3) a protocol (tcp/udp only!) and 4) destination port, seperated by a comma (","), e.g. "4.0.0.0/8,1.1.1.1,tcp,80" Optional is a port after the destination port, to redirect the request to a different destination port on the destination IP, e.g. So you need to define the Source IP/net correctly depending on your configuration -- Togan Muftuoglu | Unofficial SuSE FAQ Maintainer | Please reply to the list; http://susefaq.sf.net | Please don't put me in TO/CC. Nisi defectum, haud refiecendum -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com