[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Modem dials without reason



Hi Paul,

cron jobs are ok. The only one running from that you mentioned is exim. And it
should only run every 53 minutes:
# 53 *     * * *     mail   if [ -x /usr/sbin/exim ]; then /usr/sbin/exim -q >/dev/null 2>&1; fi

I commented it out (as shown), but dialing goes on. In the manpages it says, that I won't
have to restart cron after shanging jobs. So it should have worked. 

The logfile stats 
Jan  4 14:56:43 coma diald[169]: Trigger: udp       192.168.0.1/138      192.168.0.255/138
before modem is dialing, but not always.
This port I found in services:
netbios-dgm     138/tcp                         # NETBIOS Datagram Service
netbios-dgm     138/udp

If this is a hint, who is using this port ?

Regards
Klaus.

 

--- Begin Message ---
|>From root  Tue Jan  4 13:34:13 2000
Return-Path: Paul.John.Biciunas@fmr.com
Received: from mail.ngi.de
	by localhost with POP3 (fetchmail-5.1.3)
	for klaus@localhost (single-drop); Tue, 04 Jan 2000 13:34:13 +0100 (CET)
Received: from gw35i.fmr.com (gw35e.fmr.com [192.223.207.77])
	by mail.ngi.de (8.9.3/8.9.3) with ESMTP id NAA40884
	for <klaus_drews@ngi.de>; Tue, 4 Jan 2000 13:14:04 +0100 (CET)
	(envelope-from Paul.John.Biciunas@fmr.com)
Received: (from smtp@localhost)
	by gw35i.fmr.com (8.8.7/8.8.7) id HAA20597
	for <klaus_drews@ngi.de>; Tue, 4 Jan 2000 07:12:19 -0500 (EST)
Received: from msgmmk101nts.fmr.com(172.25.150.20) by gw35i.fmr.com via smap (V2.0)
	id xma020422; Tue, 4 Jan 00 07:11:48 -0500
Received: by msgmmk101nts.fmr.com with Internet Mail Service (5.5.2448.0)
	id <ZYFMBAPN>; Tue, 4 Jan 2000 07:11:48 -0500
Message-ID: <ACCD934AF63ED311A68E0060B0675BAF12BB46@msgbos641nts.vantage.fmr.com>
From: "Biciunas, Paul John" <Paul.John.Biciunas@fmr.com>
To: "'Klaus Drews'" <klaus_drews@ngi.de>
Subject: RE: Modem dials without reason
Date: Tue, 4 Jan 2000 07:11:46 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-UIDL: be14ecc2c02ebf783864c745ec31b820
Status: RO


You might just try looking at cron jobs. IIRC, one of the mail agents
attempts
mail retrieval every five minutes as a default.

-Paul
-- 

Diplomacy is the art of saying "nice doggie" until you can find a rock.
		-- Wynn Catlin

> -----Original Message-----
> From:	Klaus Drews [SMTP:klaus_drews@ngi.de]
> Sent:	Monday, January 03, 2000 10:09 AM
> To:	debian-user@lists.debian.org
> Subject:	Modem dials without reason
> 
> Hi there,
> 
> I configured demand dialing with diald on my machine. Now my modem dials
> every
> five minutes without reason. I increased logging but could not find a hint
> why.
> Does anyone know how to find the event that wants a connection ?
> 
> Another question:
> When I run "route" my modem dials, but the command itself hangs. After a
> while
> (the second or third dial) my routing table looks like this:
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 194.1.1.1       *               255.255.255.255 UH    1      0        0
> sl0
> 194.1.1.0       *               255.255.255.0   U     0      0        0
> sl0
> localnet        *               255.255.255.0   U     0      0        0
> eth0
> default         *               0.0.0.0         U     1      0        0
> sl0
> default         *               0.0.0.0         U     0      0        0
> ppp0
> 
> After that route works fine. The ifconfig output is the following:
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:751 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:751 errors:0 dropped:0 overruns:0 carrier:0
>           Collisions:0 
> 
> eth0      Link encap:Ethernet  HWaddr 52:54:05:DE:DB:4E  
>           inet addr:17.10.10.1  Bcast:17.10.10.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
>           Collisions:0 
>           Interrupt:12 Base address:0xd800 
> 
> sl0       Link encap:Serial Line IP  
>           inet addr:192.168.0.1  P-t-P:194.1.1.1  Mask:255.255.255.0
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3099 errors:0 dropped:0 overruns:0 carrier:0
>           Collisions:0 
> 
> ppp0      Link encap:Point-to-Point Protocol  
>           inet addr:212.184.131.140  P-t-P:193.158.137.77
> Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:9 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
>           Collisions:0 
> 
> Maybe these two questions are one.
> Thanks in advance,
> Klaus.



--- End Message ---

Reply to: