Thanks for replying--I feel like there's light at the end of the tunnel now.
This has been really panicking me since the system its on belongs to family.
And I have another family member who has Cupsd and who should also be on
Diald now, but isn't--until i know how they can co-exist on a 2.4pre kernel
with iptables (yikes) . I can't get at the system in question again to try
this for a few days.
Jeff Licquia wrote:
> On Thu, Apr 20, 2000 at 04:21:21PM -0400, hazzmat wrote:
> > Ok, I made the change
>
(snip)
>
> > and still the link comes up.? here is how I define ipp in /etc/services:
> > ipp ? ? ? ? ? ? 631/udp ? ? ? ? ipp ? ? ? ? ? ? # cupsd PrintPro
> > ipp ? ? ? ? ? ? 631/tcp ?? ? ? ? ipp ? ? ? ? ? ? # cupsd PrintPro
>
> What are the question marks for?
Yeah they're obnoxious, sorry...Apparently they are an artifact of X-pasteing
lines with tabs in them in the email client of NS6-pre or Mozilla-M15. I
don't see them while I'm writing the message, only in the email coming back
to me from the mailinglist.
(snip)
> But you don't need to mess with /etc/services to get this to work.
>
(snip)
> > Here is the message from diald about the trigger:
> > Apr 20 16:08:32 localhost diald[1529]: Trigger: udp ?? ? ? ?
> > 10.0.0.1/631 ?? 255.255.255.255/631
>
> Ah, there's the trouble. Edit your cupsd.conf file and add a line:
>
> Browsing Off
>
> This will stop the broadcasts which appear to be bringing your link
> up.
>
God i hope so. I tried to reconfigure cupsd to listen only locally
127.0.0.1/631--which made no difference. Mostly i have desperately been
trying to get Diald to ignore the packets--and i still don't know why it
doesn't. But then again, if it did ignore the packets, I wouldn't really
understand why it was doing that either... Bob Chiodini suggested that maybe
I left "accept any 300 any" in diald.conf, or that maybe that I defined the
filter afterwards in the .conf file. Being really on the ball i forgot to
email myself a reference copy of the diald.conf and filter so I can't confirm
anything for about a week. Given the haste with which i initially set
everything up (months ago) those can't be ruled out...
>
> > There is a huge amount of garbage produced by diald on startup-
(snip)
> It would seem that your diald.defs file is either corrupted or not
> being loaded.
Could be that the .defs come from an outdated .rpm for diald-config. I
thought I compiled everything fresh. Probably I had leftovers from an rpm
based install from way back, and didn't copy the .defs from /usr/lib/diald
over to /etc/diald/diald.defs.
>
I can't thank you guys enough for the help. I'll know more next weekend
hopefully.
-hazzmat
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
