From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 and full ipv6 - will it happen?
Date: Tue, 27 Aug 2002 01:48:04 +0200 [thread overview]
Message-ID: <20020826234804.GA13520@lina.inka.de> (raw)
In-Reply-To: <20020826215123.GA22750@alcove.wittsend.com>
On Mon, Aug 26, 2002 at 05:51:23PM -0400, Michael H. Warfield wrote:
> My only other annoynance right now is the default ip6 route on my
> ipv6 router (RedHat 7.3). It's not working (or doesn't seem to be)! I
> have a 6bone allocation from Freenet6 (3ffe:b80:c84::/48) with about a
> half a dozen SLA subnets and several routers. If I assign a default route
> (::/0) on the main router back down my Freenet6 tunnel, weird things happen.
the linux kernel does ignore the ::/0 route if it is in forwarding not, I
guess this is since it is asumed, that the user knows what he is doing and
does not want to do that. You can use 2000::/2 instead.
> This has been noticed and mentioned by others on the 6bone and freenet6
> lists. Seems to be peculiar to Linux.
it is by intention, yes.
> The default routers on the leaf workstations (autoconfigured from
> router advertisements) seem to work fine though.
yes it deoeds on the ipforward setting.
BTW: i am working a bit on net-tools and ipv6, like:
calista:~# netstat -tl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:1024 *:* LISTEN
tcp 0 0 *:5269 *:* LISTEN
...
tcp 0 0 calista.inka.de:domain *:* LISTEN
tcp6 0 0 *:auth *:* LISTEN
tcp6 0 0 *:ssh *:* LISTEN
tcp6 0 0 *:smtp *:* LISTEN
i am not yet sure about the wildcard address and the port separator, but I
like the tcp6 :)
ifconfig may get a more BSDish look, also:
# ./ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
inet 10.0.0.3 netmask 255.255.255.0 broadcast 10.0.0.255
inet6 3ffe:400:4f0:ffff::3 prefixlen 112 scopeid 0x0<global>
inet6 fe80::2e0:7dff:fe92:1f0b prefixlen 10 scopeid 0x20<link>
ether 00:e0:7d:92:1f:0b txqueuelen 100 (Ethernet)
RX packets 2581434 bytes 1632512018 (1.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2031678 bytes 1202569629 (1.1 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 9 base 0x9000
Greetings
Bernd
next prev parent reply other threads:[~2002-08-26 23:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 4:39 Tomasz Torcz, BG
2002-08-19 4:37 ` David S. Miller
2002-08-19 5:16 ` Tomasz Torcz, BG
2002-08-19 5:12 ` David S. Miller
2002-08-19 23:34 ` Thunder from the hill
2002-08-19 23:23 ` David S. Miller
2002-08-19 23:49 ` Daniel Berlin
2002-08-19 23:54 ` Alan Cox
2002-08-20 0:32 ` Rik van Riel
2002-08-20 13:54 ` kuznet
2002-08-20 6:56 ` Thunder from the hill
2002-08-21 20:24 ` Kelsey Hudson
2002-08-21 21:31 ` Bernd Eckenfels
2002-08-21 21:44 ` Thunder from the hill
2002-08-21 22:03 ` Bernd Eckenfels
2002-08-21 23:13 ` Russell King
2002-08-22 0:05 ` Bernd Eckenfels
2002-08-22 6:08 ` Thunder from the hill
2002-08-26 18:55 ` Kelsey Hudson
2002-08-26 19:44 ` Bernd Eckenfels
2002-08-26 21:51 ` Michael H. Warfield
2002-08-26 23:48 ` Bernd Eckenfels [this message]
2002-08-27 16:07 ` Michael H. Warfield
2002-08-28 19:14 ` Bernd Eckenfels
2002-08-29 2:05 ` Michael H. Warfield
2002-08-29 18:47 ` Bernd Eckenfels
2002-08-21 22:08 ` Alan Cox
2002-08-22 6:12 ` Thunder from the hill
2002-08-22 12:27 ` Rik van Riel
2002-08-22 18:22 ` Alan Cox
2002-08-22 18:26 ` Bernd Eckenfels
2002-08-22 19:19 ` Russell King
2002-09-12 15:06 ` Petr Baudis
2002-09-13 1:47 ` David S. Miller
2002-08-19 7:27 ` Chris Wedgwood
2002-08-19 12:25 ` Alan Cox
2002-08-19 22:39 ` Kelsey Hudson
2002-08-20 6:17 ` Val Henson
2002-08-19 23:56 Leif Sawyer
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=20020826234804.GA13520@lina.inka.de \
--to=ecki@lina.inka.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®