This question gets answered on here at least once a week.
WIN95 and NT machines do a DNS lookup for their workgroup name at intervals.
That's what's causing the dials. To fix it, you can:
1) Put the workgroup name in the lmhosts file on the windows box pointing to
any valid address on your LAN.
2) Set up a local name server on your linux box with your local hosts
defined and have it forward unknown hosts to your ISP.
3) Set diald not to dial for dns lookups.
I don't know about logging diald requests, but you can watch what's going on
with dctrl if you have X running.
I use the local nameserver (option 2) and log all requests to that. It
solves the problem nicely and has the added bonus of logging every internet
site my kids hit. A couple of weeks ago my son's friend stayed over and was
up all night examining every adult site on the planet.
We talked.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Thomas Andrews
Sent: Thursday, December 03, 1998 9:29 AM
To: [EMAIL PROTECTED]
Subject: Diald and the Ghostly phantom phone-call
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]
