Hello, I've been happily using e-smith on a cable modem for a 1/2 year now with much satisfaction and am venturing off into unchartered water's proposing it to small clients for server and dial-up services. I have a small issue that I cannot seem to get resolved myself, and I must confess I'm a recent Linux convert so I may be missing something very obvious to others.
I have a demo machine for a potential client set up with e-smith 4.0.1 that dials out what I consider an excessive number of times and I'm trying to understand why.
Background: The machine is set up as server & dialup gateway mode. The dialout profile was defined as ling connection during the days, short after hours & on weekends via the console. The web interface has the hours set to hourly during the workday, every two hours otherwise. There are NO other client machines attached to it in any way. The machine is just sitting there running as a standalone unit.
Problem: The server is dialing out at all hours of the day and night for reasons unknown. It will also dialout several times in succession. This concerns me as I was intending on deploying the prototype machine to a client and sharing a fax line and I'm concerned they will never be able to get a fax in or out with all the contention from the e-smith box and the resulting negative press that will get me & my overhyped e-smith solution!
Analysis: The connection attempts are all successfull logins so the re-dials arn't as result of busy signals, bad pwds etc. A search of the mesages file shows the following "trigger"s:
Jan 28 06:44:36 e-smith diald[379]: Trigger: tcp 192.168.1.1/1253 207.136.80.123/110
Jan 28 06:46:06 e-smith diald[379]: Trigger: tcp 207.136.80.123/110 192.168.1.1/1253
Jan 28 06:46:44 e-smith diald[379]: Trigger: tcp 192.168.1.1/1254 207.136.80.123/110
Jan 28 06:48:14 e-smith diald[379]: Trigger: tcp 207.136.80.123/110 192.168.1.1/1254
Jan 28 06:48:47 e-smith diald[379]: Trigger: tcp 192.168.1.1/1255 207.136.80.123/110
Jan 28 06:50:22 e-smith diald[379]: Trigger: tcp 207.136.80.123/110 192.168.1.1/1255
Jan 28 06:50:55 e-smith diald[379]: Trigger: tcp 192.168.1.1/1256 207.136.80.123/110
where there is the IP followed by a sequential number /1254,55,56 this goes on for pages with values in the 1200 range up to 1500-something right now. Can someone please explain what is is?
Secondly, the address next to it followed by the 110, I understand this to be the POP3 port and the mail server IP. Why would this be triggered so many times and during the off-hours?
Is/are there other areas I ought to be checking to determine these dial-out causes?
My expectation was that the machine, running in isolation, should only be dialing out once and a while, as per the configuration settings (ie: once per hours or once evey two hours outside working hours).
Thanks in advance for any assistance.
PS I've searched the forum history, but noticed that the re-org of the forums has dropped other msgs (from the Search function anyway) that were once present. If this topic has been covered please provide a reference and I'll be happy to followup myself.
0 Replies
684 Views