Warning: no default firewall zone defined ?

I applied the latest updates, that were signalled as available on Saturday
(NZ Time). Now I have begun to see during the initialisation of the network
card (On a laptop both wireless and LAN card) a Warning message:

SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'

I went into Yast and the Firewall settings in there seem to have the
external interface defined OK. Looking at the SuSEfirewall2 file in
the /etc/sysconfig dir I see the line:

FW_DEV_EXT="'eth0 eth0_rename eth1 eth1' eth2"

Is this syntax correct? Seems strange to have single and double quotes?

Further down the file there is this:

## Type: string
## Default: zone:ext
#
# 6a.)
# You also have to define on which interfaces to masquerade on.
# Those are usually the same as the external interfaces. Most users
# can leave the default.
#
# The special string "zone:" concatenated with the name of a zone
# means to take all interfaces in the specified zone.
#
# Old version of SuSEfirewall2 used a shell variable ($FW_DEV_EXT)
# here. That method is deprecated as it breaks auto detection of
# interfaces. Please use zone:ext instead.
#
# Examples: "ippp0", "zone:ext"
#
FW_MASQ_DEV="zone:ext"

Is this working correctly? Is this worth a bug report?

Jim

--
Pye, James Pye, chmod 007, The Ultimate Open Source

You know it's going to be a bad day when you hear
"Transporter Malfunction" while being demolecularised.

Jim,

I am not aware of a way to set a default zone in Opensuse. Since it assumes ext anyway, you're safe. Actually I'm pretty sure it has been like that for years.

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.

Uwe Buckesfeld wrote:

> Jim,
>
> I am not aware of a way to set a default zone in Opensuse. Since it
> assumes ext anyway, you're safe. Actually I'm pretty sure it has been like
> that for years.
>
> Uwe
>
Uwe

Thanks for that. I am guessing that the rest of the message, which states it
is assuming ext, means it was still working OK. At least it is still
blocking unwanted ports etc.

On my laptop I run a couple of home grown scripts that start and stop the
wireless and wired networks as needed (couldn't get networkmanager to work
as I wanted). It just seemed that after I did the update that this message
started appearing when I did the switch.

Again Tnx
Jim


--
Pye, James Pye, chmod 007, The Ultimate Open Source

You know it's going to be a bad day when you hear
"Transporter Malfunction" while being demolecularised.

On 04/15/2008 Jim Pye wrote:
> It just seemed that after I did the update that this message started
> appearing when I did the switch.

Opensuse does issue that warning regularly, actually I would miss it if it suddenly disappeared :-)

Maybe it was your scripts avoiding the message for a while, no idea.

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.