From: Gregory Maxwell <greg@linuxpower.cx>
To: "Carlos Parada (EST)" <est-c-parada@ptinovacao.pt>
Cc: linux-kernel@vger.kernel.org, 6bone@ISI.EDU
Subject: Re: IPv6 routing
Date: Fri, 20 Apr 2001 13:43:37 -0400 [thread overview]
Message-ID: <20010420134337.E13249@xi.linuxpower.cx> (raw)
In-Reply-To: <25CCC6566D01D411885B00A024559FB701486CC3@EXCHANGE_GERAL>
In-Reply-To: <25CCC6566D01D411885B00A024559FB701486CC3@EXCHANGE_GERAL>; from est-c-parada@ptinovacao.pt on Fri, Apr 20, 2001 at 06:37:05PM +0100
On Fri, Apr 20, 2001 at 06:37:05PM +0100, Carlos Parada (EST) wrote:
> Hi,
>
> I'm trying to set up an IPv6 network in Linux kernel 2.4.0-test10. In this
> network I'm using just 3 boxs and I would use static routes.
> _____ _____ _____
> | A |____| B | ____| C |
> |_____| |_____| |_____|
>
> The problem is that I cannot access from A to C machines and vice-versa. But
> the routing problem is a bit strange because, A can access to the two
> interfaces of B, even to B interface in the same network as C. Also C can
echo -n 1 > /proc/sys/net/ipv6/conf/all/forwarding
next prev parent reply other threads:[~2001-04-20 17:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 17:37 IPv6 routing Carlos Parada (EST)
2001-04-20 17:43 ` Gregory Maxwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-30 10:26 Jonathan Tripathy
2010-08-30 10:37 ` Jonathan Tripathy
2010-08-30 10:43 ` Jan Engelhardt
2010-08-30 10:45 ` Jonathan Tripathy
2010-08-30 11:10 ` Jonathan Tripathy
2010-08-30 12:24 ` Thomas Jacob
2010-08-30 12:33 ` Jonathan Tripathy
2010-08-30 12:42 ` Jozsef Kadlecsik
2010-08-30 12:54 ` Thomas Jacob
2010-08-30 13:18 ` Jozsef Kadlecsik
2010-08-30 13:43 ` Thomas Jacob
2010-08-30 12:47 ` Thomas Jacob
2010-08-30 12:48 ` Jonathan Tripathy
2010-08-30 17:17 ` Pascal Hambourg
2010-08-30 12:07 ` Jan Engelhardt
2010-08-30 12:08 ` Jonathan Tripathy
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=20010420134337.E13249@xi.linuxpower.cx \
--to=greg@linuxpower.cx \
--cc=6bone@ISI.EDU \
--cc=est-c-parada@ptinovacao.pt \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.