From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: ot, configuring ipv6 routing to tap device
Date: Mon, 18 May 2009 18:43:05 -0700 [thread overview]
Message-ID: <20090519014305.GA15729@localhost.localdomain> (raw)
In-Reply-To: <20090518064939.GA15357@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, May 17, 2009 at 11:49:39PM -0700, Gregory Nowak wrote:
> I think I actually figured out a solution though by bridging the eth1
> interface for my lan to the vm's tap0 interface on the host. I'll make
> the config changes tomorrow, and will report back if it works, though
> I think chances are very high that it's going to. We'll see I guess.
Well, turns out I was right, and I now have the uml talking to my lan
and world over ipv4, and ipv6, and my lan and the world talking to the
uml over ipv6. So basically what I did is to install the bridge-utils
package under debian, read the docs, and configure things in
/etc/network/interfaces, all on the host of course. The config on the
uml wasn't touched at all. For a generic config method, the brctl(8)
manual page describes how to set things up. Hth someone else, and
thanks to Jason for his suggestions.
Greg
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkoSDqkACgkQ7s9z/XlyUyDVtwCdGptbS8XeUkks9O8JSoyQtpEz
YL0AniC/fwQXIs52wuig9ho+AZbtWNMW
=8k6P
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Jason White
` Gregory Nowak
` Gregory Nowak [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=20090519014305.GA15729@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).