>When I boot machine #2 into this situation, the gateway dials up. This
>happens during the boot-up sequence, when AMD(auto mount daemon) is
>called. I believe the machine is making a dns lookup, and therefore dials
>to satisfy what is in it's /etc/resolv.conf file. 

If the MASQ'ed machine is a Windows box with Microsoft File & Printer
sharing or NT running WINS, Diald will ALWAYS dial out every 15 minutes.

But.. you and configure Diald to ignore this traffic.  For explict
Diald and PPP setup configs, check out one of my precursor docs to
the TrinityOS doc:

        http://www.ecst.csuchico.edu/~dranch/PPP/linux-masq-ppp-setup.txt


Also.. I completely disagree with the use of PPPD's dial-on-demand
feature.  Yes.. it does work but it can't touch Diald's flexibility.
Yes.. setting up the SLIP interface requires a kernel re-compile
but it just isn't very hard.  Try it!


>Also, does machine #2 need ppp enabled in the kernel? 

Unless it is using PPP, no, leave it out or compile it in as a 
module.

--David
.----------------------------------------------------------------------------.
|  David A. Ranch - Remote Access/Linux/PC hardware      [EMAIL PROTECTED]  |
!----                                                                    ----!
`----- For more detailed info, see http://www.ecst.csuchico.edu/~dranch -----'
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]

Reply via email to