Jeff,
Check /etc/services for port number/protocol assignments:
$ grep 513 /etc/services
login 513/tcp
who 513/udp whod
So I would suspect you have the whod daemon running, which broadcasts
info for the rwho and ruptime programs (I believe).
-Chris
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jeffrey P.
> Rudnick
> Sent: Thursday, August 26, 1999 11:58 AM
> To: Gyepi SAM; Edward Dekkers
> Cc: [EMAIL PROTECTED]
> Subject: Diald connects full-time
>
>
>
> I greatly appreciate all suggestions...
>
> I still don't know why I am always connected now that I have dctrl
> monitoring the connection queue. This is what is listed on dctrl:
>
> At the top of the screen it says:
> Interface ppp0 from 10.1.1.254 to 10.1.1.253
>
> Under Connection queue it says:
> udp 10.255.255.255/513 207.208.139.88/513 00:06:59
>
> The time at the end of that line decrements until it starts
> back up at 7
> minutes.
>
> I have seen messages passing through this list that suggest
> certain types of
> messages might be ignored, etc... Where do I find out if
> some of those
> messages are being sent to my diald SLIP interface? I
> don't see anything
> like that in dctrl?
>
> Any help you can offer would be great.
>
> Regards,
> Jeff Rudnick
>
>
> > -----Original Message-----
> > Subject: RE: Diald always dials when my system boots, and never
> > disconnects
> >
> >
> > Thanks for the suggestion. I did change my local and remote IP
> > addresses in
> > my diald.conf file. I have corrected this by
> substituting the following
> > class 1 addresses, but regrettably the problem of the persistent
> > connection
> > is unaffected.
> >
> > local 10.1.1.254
> > remote 10.1.1.253
> >
> > As a side note, I am embarrassed that I don't know how
> you calculated my
> > error rate on all interfaces. In reviewing the data that
> I sent to you
> > (ifconfig and route -n output) I do see that errors and
> collisions for all
> > interfaces display 0. Can you please explain the origin
> of the error
> > calculation so that I can assess the impact of this most
> recent change?
> > Thank you.
> >
> > As for the persistent connection problem, any additional
> suggestions are
> > also appreciated as I imagine that I will pay for this
> problem when my
> > month's telephone bill arrives. Thanks.
> >
> > Regards,
> > Jeff Rudnick
> >
> > snipped much of the previous messages
> > > -----Original Message-----
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of
> Gyepi SAM
> > > Subject: Re: Diald always dials when my system boots, and never
> > > disconnects
> > >
> > >
> > > Don't use your real local IP address, use some other IP address.
> > > On my network I have set aside two IP addresses just
> for this purpose.
> > > While the kernel will accept the same IP address for multiple
> > > interfaces, it is bound to break something.
> > >
> > > snipped ifconfig output. I note in passing that you
> have an 80-99%
> > > error rate on all interfaces.
> > >
> > > > > Aug 24 20:44:51 redhat1 diald[1183]: filter accepted rule 1
> > > > > proto17 len 160
> > > > > packet 207.208.139.10,513 => 10.255.255.255,513
> > > > >
> > > > > Regrettably, I don't know if this message is applicable. Or
> > > should I be
> > > This message is symptomatic of the double IP assigment. Diald is
> > > intercepting local packets on sl0 becuase sl0 has the
> same IP as eth0.
> > > Not good.
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> linux-diald" in
> > the body of a message to [EMAIL PROTECTED]
> >
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
