I've been having this problem since I updated to 9.2 Professional from 9.1:

I configured my firewall through Yast to open TCP 4662, UDP 4672 and 4665 ports (so aMule p2p would have a HighID but I get a LowID). When I looked at the start up log I see the following:

WARNING: Error inserting ipfwadm (/lib/modules/2.6.8-24.3-default/kernel/net/ipv4/netfilter/ipfwadm.ko): Device or resource busy
SuSEfirewall2: Warning: FW_ALLOW_INCOMING_HIGHPORTS_UDP=DNS no longer supported

Any ideas?

Cheers,

Brian

I've been wandering on the web for 3 days to find a solution to the same problem... to no avail. Any way, somehow, I manage to restore my highID just after I found your post with Google. ;-)

I changed 2 things: First, the interface/device isn't ppp0 any more.

FW_DEV_EXT="dsl0"

Second, --I think that's the important part.-- I copied the ports numbers from:

FW_SERVICES_EXT_TCP="****"
FW_SERVICES_EXT_UDP="****"

into:

FW_ALLOW_INCOMING_HIGHPORTS_TCP="****"
FW_ALLOW_INCOMING_HIGHPORTS_UDP="****"

(Just the port numbers, nothing else.)

Edit your /etc/sysconfig/SuSEfirewall2 by hand then configure your firewall with YaST. Don't change anything, just click "Next" until the end in order to restart the firewall.

That's what I did and no timeout and no lowID any more. :-D

Hope it helps,

(For my friend Google: SuSE 9.2, aMule, peer-to-peer, firewall)