From: Russ Cox <rsc@swtch.com>
To: Sergey Reva <rs_rlab@mail.ru>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] network bridge
Date: Wed, 2 Nov 2005 10:30:18 -0500 [thread overview]
Message-ID: <ee9e417a0511020730y4f7a0328rb57ba014131114cb@mail.gmail.com> (raw)
In-Reply-To: <1673419921.20051102092852@mail.ru>
> 1. Put 2 adapter
> 2. run ip/config for one of them, as cpurc or termrc do
> 3. bind -a '#l1' /net - bind secondary adapter
> 4. bind -a '#B' /net - bind bridge device into some folder
> 5. setting up bridge device
> echo 'bind ether outer 0 /net/ether0' >/net/bridge0/ctl
> echo 'bind ether inner 0 /net/ether1' >/net/bridge0/ctl
That looks believable. I've never been impressed with
devbridge's usability. It was written for an embedded VPN
app and worked great there but I used to get kernel panics
on unbind (or not be able to unbind at all) when I tried to
use it on a regular machine. (The VPN app never unbound.)
> Where is man page for bridge???
Doesn't exist, sorry. I would consider devbridge very much
a work in progress.
Russ
prev parent reply other threads:[~2005-11-02 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 7:28 Sergey Reva
2005-11-02 15:30 ` Russ Cox [this message]
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=ee9e417a0511020730y4f7a0328rb57ba014131114cb@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
--cc=rs_rlab@mail.ru \
/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).