Unexpected dialouts e-smith/win2K

Rob Adams

Unexpected dialouts e-smith/win2K

« on: January 10, 2001, 07:20:21 AM »

I have a e-smith 4.0.1 box at a clients site, he is rather cost concious regarding his ISDN charges.

The system is configured to check for mail never; nobody is running IE or Outlook etc.. Network consists of e-smith box, win2K server and about 6 or so Win2k workstations, and one win95 box.

DNS and DHCP is NOT installed on 2k server, dhcp and DNS is setup on e-smith.. connection for office hours is set for medium but the average connection time for these transaction is about 30 secs..

We get the following message from diald in /var/log/messages

Jan 10 11:19:47 gw diald: diald startup succeeded
Jan 10 11:20:01 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:20:01 gw diald[380]: Calling site 0.0.0.0
Jan 10 11:20:04 gw diald[380]: connector: chat: Jan 10 11:20:04 CONNECT 115200
Jan 10 11:20:04 gw diald[380]: Connected to site 0.0.0.0
Jan 10 11:20:04 gw diald[380]: Running pppd (pid = 630).
Jan 10 11:20:06 gw diald[380]: New addresses: local 139.134.149.232, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:20:06 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:21:38 gw diald[380]: Closing down idle link.
Jan 10 11:21:38 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:21:39 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:21:41 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:21:49 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:21:51 gw diald[380]: connector: chat: Jan 10 11:21:51 CONNECT 115200
Jan 10 11:21:51 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:21:51 gw diald[380]: Running pppd (pid = 756).
Jan 10 11:21:51 gw diald[380]: New addresses: local 139.134.149.237, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:21:51 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:22:23 gw diald[380]: Closing down idle link.
Jan 10 11:22:23 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:22:24 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:22:25 gw diald[380]: Trigger: udp 139.134.2.10/53 192.168.1.1/1024
Jan 10 11:22:35 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:22:37 gw diald[380]: connector: chat: Jan 10 11:22:37 CONNECT 115200
Jan 10 11:22:37 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:22:37 gw diald[380]: Running pppd (pid = 850).
Jan 10 11:22:38 gw diald[380]: New addresses: local 139.134.149.241, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:22:38 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:23:07 gw diald[380]: Failed to received first packet within 30 seconds. Closing Link down.
Jan 10 11:23:07 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:23:08 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:23:30 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:23:30 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:23:32 gw diald[380]: connector: chat: Jan 10 11:23:32 CONNECT 115200
Jan 10 11:23:32 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:23:32 gw diald[380]: Running pppd (pid = 929).
Jan 10 11:23:33 gw diald[380]: New addresses: local 139.134.149.243, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:23:33 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:36:29 gw diald[380]: Closing down idle link.
Jan 10 11:36:29 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:36:30 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:36:49 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:36:49 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:36:52 gw diald[380]: connector: chat: Jan 10 11:36:52 CONNECT 115200
Jan 10 11:36:52 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:36:52 gw diald[380]: Running pppd (pid = 1364).
Jan 10 11:36:52 gw diald[380]: New addresses: local 139.134.149.33, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:36:52 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:37:27 gw diald[380]: Closing down idle link.
Jan 10 11:37:27 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:37:28 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:38:25 gw diald[380]: Trigger: udp 139.134.5.51/53 192.168.1.1/1024
Jan 10 11:38:25 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:38:28 gw diald[380]: connector: chat: Jan 10 11:38:28 CONNECT 115200
Jan 10 11:38:28 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:38:28 gw diald[380]: Running pppd (pid = 1443).
Jan 10 11:38:28 gw diald[380]: New addresses: local 139.134.149.38, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:38:28 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:49:32 gw diald[380]: Closing down idle link.
Jan 10 11:49:32 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:49:34 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:49:43 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:49:43 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:49:45 gw diald[380]: connector: chat: Jan 10 11:49:45 CONNECT 115200
Jan 10 11:49:45 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:49:45 gw diald[380]: Running pppd (pid = 1525).
Jan 10 11:49:46 gw diald[380]: New addresses: local 139.134.149.63, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:49:46 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:50:21 gw diald[380]: Closing down idle link.
Jan 10 11:50:21 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:50:22 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:50:50 gw diald[380]: Trigger: udp 139.134.5.51/53 192.168.1.1/1024
Jan 10 11:50:50 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:50:53 gw diald[380]: connector: chat: Jan 10 11:50:53 CONNECT 115200
Jan 10 11:50:53 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:50:53 gw diald[380]: Running pppd (pid = 1606).
Jan 10 11:50:53 gw diald[380]: New addresses: local 139.134.149.70, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:50:53 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:51:38 gw diald[380]: Closing down idle link.
Jan 10 11:51:38 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:51:39 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:53:39 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:53:39 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:53:41 gw diald[380]: connector: chat: Jan 10 11:53:41 CONNECT 115200
Jan 10 11:53:41 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:53:41 gw diald[380]: Running pppd (pid = 1685).
Jan 10 11:53:42 gw diald[380]: New addresses: local 139.134.117.18, remote 139.134.22.220, broadcast 0.0.0.0
Jan 10 11:53:42 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:54:22 gw diald[380]: Closing down idle link.
Jan 10 11:54:22 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:54:23 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:55:05 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:55:05 gw diald[380]: Calling site 139.134.22.220
Jan 10 11:55:07 gw diald[380]: connector: chat: Jan 10 11:55:07 CONNECT 115200
Jan 10 11:55:07 gw diald[380]: Connected to site 139.134.22.220
Jan 10 11:55:07 gw diald[380]: Running pppd (pid = 1764).
Jan 10 11:55:08 gw diald[380]: New addresses: local 139.134.149.84, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:55:08 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:55:46 gw diald[380]: Closing down idle link.
Jan 10 11:55:46 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:55:47 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:56:10 gw diald[380]: Trigger: udp 139.134.5.51/53 192.168.1.1/1024
Jan 10 11:56:10 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:56:13 gw diald[380]: connector: chat: Jan 10 11:56:13 CONNECT 115200
Jan 10 11:56:13 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:56:13 gw diald[380]: Running pppd (pid = 1843).
Jan 10 11:56:13 gw diald[380]: New addresses: local 139.134.117.22, remote 139.134.22.220, broadcast 0.0.0.0
Jan 10 11:56:13 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:56:42 gw diald[380]: Failed to received first packet within 30 seconds. Closing Link down.
Jan 10 11:56:42 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:56:43 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:57:51 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:57:51 gw diald[380]: Calling site 139.134.22.220
Jan 10 11:57:54 gw diald[380]: connector: chat: Jan 10 11:57:54 CONNECT 115200
Jan 10 11:57:54 gw diald[380]: Connected to site 139.134.22.220
Jan 10 11:57:54 gw diald[380]: Running pppd (pid = 1922).
Jan 10 11:57:55 gw diald[380]: New addresses: local 139.134.149.93, remote 139.134.22.221, broadcast 0.0.0.0
Jan 10 11:57:55 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument
Jan 10 11:58:29 gw diald[380]: Closing down idle link.
Jan 10 11:58:29 gw diald[380]: start sl0: SIOCSIFMTU: Invalid argument
Jan 10 11:58:30 gw diald[380]: Delaying 10 seconds before clear to dial.
Jan 10 11:58:39 gw diald[380]: Trigger: udp 192.168.1.1/1024 139.134.5.51/53
Jan 10 11:58:41 gw diald[380]: Calling site 139.134.22.221
Jan 10 11:58:44 gw diald[380]: connector: chat: Jan 10 11:58:44 CONNECT 115200
Jan 10 11:58:44 gw diald[380]: Connected to site 139.134.22.221
Jan 10 11:58:44 gw diald[380]: Running pppd (pid = 2001).
Jan 10 11:58:44 gw diald[380]: New addresses: local 139.134.117.27, remote 139.134.22.220, broadcast 0.0.0.0
Jan 10 11:58:44 gw diald[380]: start ppp0: SIOCSIFMTU: Invalid argument

Logged

Charlie Brady

Re: Unexpected dialouts e-smith/win2K

« Reply #1 on: January 10, 2001, 04:32:19 PM »

Rob Adams wrote:

> I have a e-smith 4.0.1 box at a clients site, he is rather
> cost concious regarding his ISDN charges.
...
> We get the following message from diald in /var/log/messages
>
> Jan 10 11:19:47 gw diald: diald startup succeeded
> Jan 10 11:20:01 gw diald[380]: Trigger: udp
> 192.168.1.1/1024 139.134.5.51/53

As you can see here, port 53 UDP is the dialup trigger, and as you know (I guess), that is a DNS lookup. You'll have to view other logs, and work out what is doing the DNS lookup.

There are

Regards

Charlie

Logged

alejandro

Re: Unexpected dialouts e-smith/win2K

« Reply #2 on: January 13, 2001, 05:04:02 PM »

taking apart the dns lookup matter.. I see you have this line many times in your message file
"start ppp0: SIOCSIFMTU: Invalid argument"
I have this same message, and i dont know what does it mean, but it looks to be an error ....
Have you filtered out some messages or it is the exact extract from your var/log/messages file?
I have 4.0.1 and there is a lot of aditional messages of expanding templates thing etc, etc.

alejandro

Logged