Thomas,
I had a similar problem with some Win95 machines that had the
"client for Microsoft Networks" loaded. Apparently, the MS client
tries to do a DNS lookup every x minutes whether it's needed or
not. There's probably a way to filter this in the filter file, but I was
never able to do it completely. I finally removed the Netbios service
from my /etc/services file, which seemed to help. I swear the MS
client caught on to what I had done and still managed to get diald to
dial out, but without Netbios packets. I finally removed the MS client
from the offending machine, and voila, no more phantom dials.
Obviously, not a complete solution, especially for those needing MS
peer functions or running Samba. But it worked for me.
I'd be interested in hearing other solutions that allow the MS client
to be active.
Bill
> Ok I know it's not diald causing the problem (phoning up my ISP when it
> would appear to have no reason to) but I want to trace the origin of the
> problem. I'm pretty sure the NT4 or Win95 machines are to blame because
> when they're switched off, there has never been a "phantom" call.
>
> My problem is this: Can I log every single request to which diald is
> responding ? I know the log file will be huge, but I get these calls
> even when there's nothing much going on!
>
> If I can identify the offending request, maybe I can tell diald to
> ignore it in future (?) Or maybe fix it at source.
>
> PS I have 'named' (as a DNS cache mainly) on the linux IP_MASQ machine,
> and it's the default gateway etc.
>
> Regards,
> Thomas
>
> -
> 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]
