From: Chris Gianelloni <wolf31o2@gentoo.org>
To: "André Ventura Lemos" <tux@tuxslare.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] IPV6
Date: Mon, 19 Apr 2004 18:47:07 -0400 [thread overview]
Message-ID: <1082414827.7968.1.camel@localhost> (raw)
In-Reply-To: <1082409501.10050.4.camel@lapy.tuxslare.org>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Mon, 2004-04-19 at 17:18, André Ventura Lemos wrote:
> Hi!
>
> I'm having some truble setting up an internal IPV6 network, what I have
> so far is:
>
> -> have the IPV6 module loaded (2.6.5 in one end, 2.6.4 on another)
>
> -> have emerged dhcpv6 on both machines
>
> -> the configuration files have the same as stated on the Gentoo's IPV6
> guide
>
> My problems are:
>
> On the server: invalid interface /etc/dhcp6s.conf
> this interface (eth1) has inet6 addr: fe80::204:e2ff:fe80:d5aa/64
>
> On the client: interface eth1 iaid failed to be created
>
>
> help?
Personally, I use freenet6 and radvd to get IPv6 on my internal (and to
the world) network. I found radvd to be pretty good at handing out IP
addresses. They aren't nearly as pretty as ones you can get otherwise,
but it works very well and is quite simply to setup/configure.
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-19 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 21:18 [gentoo-dev] IPV6 André Ventura Lemos
2004-04-19 22:47 ` Chris Gianelloni [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-31 18:04 [gentoo-dev] IPv6 Hannes Mehnert
2002-06-01 21:03 ` Paul Fleischer
2001-06-29 14:20 Jonas Berlin
2001-06-30 6:33 ` Achim Gottinger
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=1082414827.7968.1.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=tux@tuxslare.org \
/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