Gerzon , Charles, Mark and Cliff
Gerzon-
> Put this into /etc/named.conf:
> =============snip===
> logging {
> category queries { default_syslog; };
> };
> =============snip===
Would not work, checked the diald info and didn't see that particular
command. all I saw was accounting-log, so tried that and it basically told
me what I already knew.
However the log info made it very clear as who was calling. It is the lines
in diald.conf that say:
local xxx.xxx.xxx.xxx
remote yyy.yyy.yyy.yyy
when I first bootup the call is initiated by the remote address of
yyy.yyy.yyy.yyy I would change it and next time the log would indicate the
new and changed remote address.
Now I'm using dynamic addressing and the info I have on local/remote values
is that it has to be something but not real. meaning that I use an internal
network address. My RH6.0 box has a LAN address of 192.168.0.1 and my Win98
box has 192.168.0.2
I did have for remote 192.168.0.4..even changed it to 192.168.0.1, machine
still dialed out to find itself :)) oh well.
Charles-
My diald.conf does not have "accept any" rule in it, therefore the
*.filters files does its job and I do have the accept any for the last rule.
Thanks
Mark -
I do not have forwarders defined and forward only defined in my
named.conf options section. Would this help or am I not supposed to :))
Cliff-
Not to sure what you mean (newbie) but the concept is good. :) How do I
stop the link from coming up on the address that I specify in diald.conf for
remote??
Thanks Guys..
-Randall
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
