Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Alex Schaft on May 17, 2001, 12:02:44 AM

Title: Diald not timing out?
Post by: Alex Schaft on May 17, 2001, 12:02:44 AM

Hi,

It's now 9pm local time here, and I just checked our server diald accounting log. According to this, it dialled up at 2:30pm this afternoon and stayed up since then. Could mail coming keep on resetting the diald time out? Is there a way to know for sure? Our mail mx records point to a server at our ISP, so there's no need to stay up for mail.

Alex

Title: Re: Diald not timing out?
Post by: chris on May 17, 2001, 01:36:30 AM

the easiest way to track that sort of thing down is to start unplugging machines from the network and see which holds the connection up, i did this and three machines later it turned out that MS messenger was the problem, so i diabled it...


chris

Title: Re: Diald not timing out?
Post by: Alejandro on May 17, 2001, 03:29:43 AM

Alex:
there are many programs that can keep the line up,
One way to stablish which machine or is keeping connection alive is:  at a root console type: "netstate -N" it will show you all connections alive at moment and the time to die
or you can try "netstat -M" for hidden connections.
Hope this helps
Alejandro

Title: Re: Diald not timing out?
Post by: Alex Schaft on May 17, 2001, 05:44:35 PM

Hi,

Did the netstat -m thing, and came up with ms messenger. I defined msmessenger in the services file as port 1863.

tcp 237:36.96 alex.quicksoftware.co.za msgr-ns22.msgr.hotmail.com 1521 -> msmessenger (61017)

Can a linux guru tell me what the difference is between /etc/diald.filter, and /etc/diald/phone.filter? My gut feel is that the first one determines, what can keep a link up, and the second one is for bringing a link up.

Also, If I put the line below in as one of the first rules in both files, will I stop ms messenger from creating a link, and maintaining a link

ignore tcp tcpdest=tcp.msmessenger

Alex