Tristram Ellicott wrote:
>
> Hello
> Ive been using samba for ages and now Im trying to use diald
>
> Whenever anynoe browses the local network a link is forced by diald :(
>
> I can minimise this by getting samba to do the domain login thing and then
> there is only one dialup (each time someone starts their computer)
>
> But I don'tknow how to STOP it !
>
> If I change the line in the filter file:
> accept udp 30 udp.dest=udp.domain
> to
> ignore udp udp.dest=udp.domain
>
> the problem goes away BUT so does diald!
> I have spent quite some time fiddling and no other filter option makes a bit
> of difference.
> My questions:
> 1: has anyone else come accross this problem?
>
> 2: if so did you fix it (and how?)
>
> if not mabye i should be talking to the
> samba people? SO:
> 3: can anyone tell me what is happening here so I can talk
> to the samba people with a little understanding?
>
> Thankyou !
>
My solution does not involve diald blockage:
1) Configure a NON-caching DNS server on my gateway machine.
That is, make it know all about my local machines and know how to
query the ISP's name server for everything else, but forget the answers
in about 1 second. This ensures that PC lookups of external names will
always force a diald connection.
2) Configure the samba server as a WINS server and not a dns proxy:
wins support = yes
dns proxy = no
3) Limit samba's use of DNS lookups
## default is 'lmhosts host wins bcast'
name resolve order = wins lmhosts
4) Configure each PC to look to the local DNS server
and to samba for WINS.
All that's straight out of the samba docs, but there was one remaining
gotcha. I found a quirky interaction between samba and amd. Iff I
made the root of the samba machine a share, whenever a PC accessed it
there was a DNS lookup and diald fired up. (NOTE: It is neither safe
nor smart to share the root filesystem of a samba server, but hey, this
is my machine.) This was because the wondrous SMB protocol requires
samba to look for a file DESKTOP.INI in several odd places, including
/NET/DESKTOP.INI. Since /net is where amd mounts remote filesystems,
it calls on DNS for the identity of this unknown "machine". The only
fix I could find was:
5) Restrict the names that amd will mount by editing /etc/amd.conf
to enumerate the permitted machine names instead of using * as a
wildcard, eg:
#* rhost:=${key};type:=host;rfs:=/
datium rhost:=${key};type:=host;rfs:=/
datant rhost:=${key};type:=host;rfs:=/
etc.
--
David A. De Graaf DATIX, Inc. Hilton Head Is., SC
[EMAIL PROTECTED] 843-785-3136, -3156 (fax)
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
