Hi,

What are you trying to do before timeout is reached? -> just surfing

What happens before timeout is reached? -> some icmp messages from outside and some other requests (i.e. worms, etc.)

What are you trying to do after timeout is reached? -> nothing / just doing some other works and if he hang up he won't dial until I request it ( so my local blocking rules are working correctly.. i.e. netbios, multicast messages, etc. )

What is hapening when timeout is reached? -> nothing - the isdn-int. won't hangup // I saw some icmp messages ( type 8 code 0 // just a ping I think ) and other stuff from worms, etc.

bruno Keith Roberts schrieb am 30.09.2003 12:27:39:

On Tue, 30 Sep 2003 BLeonhardt@analytek.de wrote:

...

Hi,

I'm running a self-made linux-isdn-router at home and wondering that the

idle timeout isn't working correctly. I see several inbound connections ( in the fw-log ) which will be dropped after logging. now, usually the idel- timeout will wait for 300 secon ds until no traffic was gone through the isdn-interface.

...

I am logging Portscans, etc. on the isdn-interface - could this be the

reason why the idle timeout won't work correctly ? I didn't try to not log incoming syn's on the isdn-interface ( it's very important for me to see - who wants to come in .. ).

...

What should / could I else do to prevent that the timeout won't be reached ?

What are you trying to do before timeout is reached?

What happens before timeout is reached?

What are you trying to do after timeout is reached?

What is hapening when timeout is reached?

Kind Regards - Keith Roberts

...

yours, bruno

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