>
> I've just installed diald-0.16.5a-1 on a RH5.2 system and every time i
> bootup diald dials out. I've isolated the problem to nfs, and smb which are
> all configured to run on system startup. Another problem is that when
This is _probably_ a dns lookup from one of these services. This
might be sendmail also -- sendmail loves to do dns lookups. One thing
you could try is to run tcpdump and bring these services up and down
and see what domain lookups happen.
I.E.
tcpdump -s 512 -i ppp0
And
/etc/rc.d/rc3.d/*smb stop
/etc/rc.d/rc3.d/*smb start
And do the same w/ nfs and sendmail.
> browsing with Netscape, the modem connection times out unless I am
> constantly surfing (I entered the domain name server in resolve.conf which
> helped some.)Any suggestions? I have a small network, the linux server
> running ip-masq, a dual boot linux-win95 workstation and an nt
> server-workstation.
>
You need to look at the standard.filter file in the diald setup. This
tells diald how long to keep the link up for different kinds of connections.
I've changed mine to
1) Not bring lines down when tcp connections are dropped.
# Once the link is no longer live, we try to shut down the connection
# quickly. Note that if the link is already down, a state change
# will not bring it back up.
#keepup tcp 5 !tcp.live
#ignore tcp !tcp.live
2) Leave the link up longer for unspecified traffic (in this case www)
# If we don't catch it above, give the link 10 minutes up time.
accept tcp 600 any
One way to understand this is to run dctrl, and look at the packet queue.
This will show you what is keeping the line up and for how long.
-- cary
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
