From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs sntp fix for multiple interfaces
Date: Thu, 3 Oct 2002 15:03:40 +0100 [thread overview]
Message-ID: <80441836657c213f00946e930fc74ac3@9fs.org> (raw)
> Shouldn't IP routing take care of this?
>
It would if there was any.
Before sntp was added, no IP routing was required in the fileserver.
It did not route. It did not originate calls, as all it had to do was
reply to messages. It did this by sending the reply to the interface
it received the request from. There is inherent security and
simplicity in the server being passive.
When I added sntp, I just chose the first interface, out of laziness.
Essentially Geoff has just implemented routing, and very useful it is
too.
next reply other threads:[~2002-10-03 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 14:03 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 9:53 Geoff Collyer
2002-10-03 12:48 ` Artem Letko
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=80441836657c213f00946e930fc74ac3@9fs.org \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).