PCI modem, request-route

"Verwalter Dr.Betz" (kla@fh-landshut.de)
Fri, 26 Nov 1999 18:26:23 +0100



> > 2) I use dial-on-demand via kerneld and /sbin/request-route
> > (as I had interference problems, when using diald together with
> > dial-in via mgetty). For some days now (after a kernel rebuild)
> > <something> is dialing every hour or so. Nothing in crontab or
> > <ps aux> or <messages>. How would you find out the program responsible
> > for the dialouts?
> 
> Look with "tcpdump" on the interface (ppp0?) what's going out.

But then ppp0 has to be established first.
After establishing a ppp0-connection I get with 'tcpdump -i ppp0 -l'
something like:

18:01:17.969883 ta1-pc14.fh-landshut.de.1489 > s1.fh-landshut.de.domain:
3839+ A? www.eu.microsoft.com. (38)
18:01:17.999883 ta1-pc14.fh-landshut.de.1490 > s1.fh-landshut.de.domain:
45636+
(45)

tcpdump -i lo -l shows:
18:15:00.489883 localhost.732 > localhost.sunrpc: udp 56
18:15:00.489883 localhost.sunrpc > localhost.732: udp 28

(interface 'dummy' shows nothing, there are no further devices)

What should I do with this? (localhost.732 ? not in 'ps ax' ?)
My problem is rather, why ppp0 is established so often (every
1 to 2 hours)? 
Which kernelcode or program has to be silenced? 
How would tcpdump catch this? 
 
Symptomatic to my problem seems the start of a second pppd,
immediately after the first ppp0 connection is established (via
/sbin/request-route), as shown in /var/log/messages:

Nov 26 18:14:47 INET pppd[966]: local  IP address 193.175.140.211
Nov 26 18:14:47 INET pppd[966]: remote IP address 193.175.140.190
Nov 26 18:14:47 INET pppd[974]: pppd 2.3.5 started by root, uid 0
Nov 26 18:14:47 INET pppd[974]: Device modem is locked by pid 966
Nov 26 18:14:47 INET pppd[974]: Exit.

Thanks again for your help and response to a problem not concerning mgetty
...

H. Betz