I've omitted the network diagram you provided (nice diagram. BTW!) and list
only your specific questions and such answers as I can provide. Hope this helps.
(I won't try to answer your other questions about the M4 file because it is
really outside my expertise; someone else will have to help you with that part.)
At 09:35 AM 5/20/99 -0600, Jacob (Mettavihari) wrote:
[deleted]
>If the files above are ok
>then I have a question:
>
>1 What is the Gateway number of the client "Col7.metta.lk"
172.16.1.11, I believe. The "defaultroute" option in pppd should handle this
part, though.
>2 Does metta.lk forward the mail when a ppp connection is established
Depends on how you are forwarding. If, for example, you are using sendmail
to get mail via SMTP on the Col* hosts, and metta.lk is acting as post
office via MX records, then its sendmail would process its mail queue every
15 minutes (or whatever you set it for). If it can reach any of the Col*
machines when it processes the queue, it will send the mail on to them. You
might also set it up to pass the mail metta.lk --> 172.16.1.10-11 (unnamed
server) --> Col*, but I don't actually know how to set this up.
But if you are planning for the Col* machines to collect mail via POP3, none
of this would apply. See next answer in that case.
>
>3 or does the client collect its mail using some agent (fetchmail)
> I presume from what I have seen on this list that this would be the case
This would be the case if you are using POP3 or IMAP to deliver mail from
metta.lk to the Col* hosts. If I understand your setup correctly, this is
the better way to do it.
>
>4 if 2 is yes then how does metta.lk know who is loging in
What do you mean by "who"? In this case, it would forward all mail to all
accounts on each machine that it can reach, and the copy of sendmail on the
Col* machine would sort the mail to individual mailboxes.
>
>5 what will be my DNS of the client "Col7.metta.lk"
> pls note that the client "Col7.metta.lk" is the main gateway
> to another smaller net.(for later setup)
Depends on what you mean.
It needs to be *listed* on a nameserver. Its DNS record (an A record,
possibly some CNAME records, and probably an MX record ... and a
reverse-lookup entry) would be on whatever DNS servers are listed with your
country's root servers (that is, the root servers for lk) as authoritative
for your domain.
It also needs to know what nameservers to *use*. In resolv.conf, you supply
a list of nameservers that it can look to when asking for information via
DNS. These can be any servers running the BIND package (named) that are
willing to accept your queries. You can even run the named package on the
Col* clients themselves, probably as cache-only servers. All that said, in
practice you would most likely use the nameservers of your ISP and, for your
own domain only, a copy of named running on 172.16.1.10-11 (so the hosts can
find one another without having to make a call to your ISP). Depending on
what the LAN that Col7 is gateway for looks like, you may want a local
nameserver on it somewhere (or you may just put a complete /etc/hosts file
for it on every host, if it is small and stable).
>
>6 where do I set default route
> is it in my pppd where i dial up with /etc/ppp/ppp-on
> I read somewhere to set it to default route, but I cannot find it again
> and I do not trust my own RAM
I always do it as one of the command-line options in ppp-on . You can also
do it in /etc/ppp/ppp-options (or whatever the default options file is
called). BTW, the actual option is defaultroute (one word, not two).
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
