I'm setting up diald 0.99.1 on a Linux-Mandrake 6.0 system to service an NT
4.0 based network of about 25 Wintel PCs. The network runs TCP/IP as its
primary protocol and uses WINS for name resolution. The objective is to
provide a reliable proxy server for connection to the Internet. (We are
currently using Wingate for this -- it basically works, but both it and the
Windows system it runs on tend to crash frequently.) The Linux box is also
running Samba server and a caching name server.
The problem I'm having with diald is that it immediately starts dialing out as
soon as it initializes. This is apparently in reponse to Netbios name
resolution requests sent out by the Windoze systems, as evidenced by
messages such as the following in the system log file:
diald[1381]: Trigger: udp 172.16.0.201/1024 128.9.0.107/53
This seems to be a very common problem, judging from the very large
number of Usenet articles found on this topic via Deja News. I've tried just
about every suggestion I've found so far to no avail.
I expect that using Linux as an Internet gateway for Windoze networks is a
pretty common application and someone must have found a way to do this.
Therefore I thought I'd ask here, how have others dealt with this problem of
getting diald to dial out only on "legit" requests for external connections in
this kind of environment?
I know in the larger sense that it must be possible since every Windoze-
based proxy server that supports demand dial (Wingate, Sygate, etc.)
seems to manage this quite well. In fact, as far as knowing when to dial and
when to disconnect is concerned, Wingate handles this almost perfectly
right out of the box by default.
What arcane combination of mystical incantations will allow diald to do the
same thing?
--
Roger Blake
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
