>> sbin/SuSEfirewall2: line 687: test: 192.168.120.24: integer expression
>expected
>
>Is there something written what is expected at this line (maybe
>something like "192.168.120.24,tcp"?)?
>Look what the descriptions in the script that tells you what to put
>there.
>Sometimes it is a littlebit "short".

the whole line is:
FW_MASQ_NETS="192.168.120.22 192.168.120.24 192.168.120.49 192.168.120.191"

This worked in SuSE 7.3...

>> and a lot of:
>>
>> iptables v1.2.7a: host/network 'ippp0' not found
>
>This is because ippp0 is maybe not up or does not have an ip-address.
>Hm there must be a setting to tell ippp0 is "static" ip or fake as it is
>static.
>It seems that this is missing in SuSEfirewall2 but was present in
>SuSEfirewall1!
>Then you will not have problems to start the firewall at boottime.
>Otherwise you can start SuSEfirewall at the time you login to your
>Provider.
>At this time the firewall will "know" the ip of your dialin device.
>
>> and yes: i did update the firewall to the latest version ;-)
>
>The best method is to start the dialup at boottime (dsl) and then init
>the SuSEfirewall at S99 instead of S21 in the /etc/init.d
>At this time dialin should be done already and ippp0 got an address from
>the provider.

I will put it at the end. I hope that a link to the
SuSEfirewall2_setup will do and leave the other two firewallscripts
untouched.

dirk

-- 
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-helpsuse.com
Security-related bug reports go to securitysuse.de, not here

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]