Another problem might be that it's getting "generic" windows trafic and
dialing out. If you're using ipfwadm you could stop this by setting up
general "deny" rules for tcp and udp traffic first and then modifiying
them with rules for your lan after. Example:
ipfwadm -F -a deny -P tcp -S 0.0.0.0/0 -P 137:137
ipfwadm -F -a deny -P udp -S 0.0.0.0/0 -P 137:137
I'm not sure how ipchains would make the rule, but it's probably
something similar.
----------
From: Thomas Andrews
Sent: Tuesday, December 01, 1998 8:54 AM
To: LKLawson; Santosh Narayanan
Cc: 'LINUX-DI@SMTP <[EMAIL PROTECTED]>'
Subject: Re: Setting diald link disconnect time
Santosh Narayanan wrote:
>
> Hi,
>
> Can anyone tell me how I can set the options for diald to disconnect
the
> line (eg: how many minutes to wait before disconnection) and also the
> redial delay time (where would I change the default of 30 seconds)?
>
'man diald' gives you a whole bunch of timeouts - just look for
"-timeout". I can't remember right now - I'm not near a linux box.
> Also I find that when diald starts up for the first time its just
dialing
> out even when there's no outbound traffic. Is there any way I can stop
this?
>
I got rid of this problem last night - my linux PC is the default
gateway for a win95 PC which seems to want to ping (?) its first
configured DNS at startup. The DNS address I had was not on my LAN so
diald decided to connect. I reconfigured win95 to see the cache DNS on
the linux PC instead, and the problem went away.
> Thanks in advance,
> -- Santosh
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
