From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: IP masquerading in Linux
Date: Sat, 25 Mar 2000 16:47:32 -0800 [thread overview]
Message-ID: <006a01bf96bd$1f671d60$b6125b80@wang> (raw)
In-Reply-To: <Pine.LNX.4.21.0003251432140.5678-100000@tcx.ro>
Thanks a lot.
Vic
----- Original Message -----
From: "Sebastian Taralunga" <seba@tcx.ro>
To: <speakup@braille.uwo.ca>
Sent: Saturday, March 25, 2000 4:38 AM
Subject: Re: IP masquerading in Linux
> Hello Victor,
>
> You have to specify a nameserver for the clients. IP
> masquerading simply means that the gateway passes all
> requests to the outside world and knows how to handle back
> the responses. If you do not specify a nameserver, the
> clients simply do not know whom to send their
> name-resolution requests...
>
> If you want to have the name-server handle your DNS requests
> as well you will have to either install a name-server on the
> gateway or to use transparent proxy and redirect (using
> ipchains) all the DNS requests from the clients to the
> appropriate name-servers.
>
> Best Regards,
>
> Sebastian
> ___________________________________________________________
> Office: (+40)/1/6.504.430 Mob: (+40)/92/202.086
> Snail: Sebastian Taralunga, C.P. 13-20, Bucharest, Romania
> E-mail: seba@tcx.ro WWW: http://www.tcx.ro
>
> On Sat, 25 Mar 2000, Victor Tsaran wrote:
>
> > Hello, listers!
> > I know some of you already setup IP masquerading on your machines,
therefore
> > a question. Did you have to specify DNS servers for both client and the
> > server or just for the server? Initially, I thought that once the
serverhas
> > a list of search domains, the client shouldn't care about them, it just
> > sends IP packets out to the server. Server forwards them to the output
> > chain. Apparently, it looks as though client also needs to have a DNS
entry
> > to be able to convert names into IP addresses, which are then sent to
the
> > server anyway. WIndows98 Second Edition resolved this problem by letting
the
> > client specify only the address of a gateway, yes, even in the DNS
field,
> > gateway knowing its own search domains, figures out on its own how to
> > convert names into IP's.
> > Perhaps I am doing something wrong here?
> >
> > Regards,
> > Vic
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Victor Tsaran
` Sebastian Taralunga
` Victor Tsaran [this message]
` Geoff Shang
` Victor Tsaran
` Geoff Shang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='006a01bf96bd$1f671d60$b6125b80@wang' \
--to=vtsaran@nimbus.ocis.temple.edu \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).