public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Toscano <pete@research.netsol.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.2.18pre21 and ipv6 problems/questions
Date: Sat, 18 Nov 2000 15:54:41 -0500	[thread overview]
Message-ID: <20001118155441.T11099@tesla.admin.cto.netsol.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

hello,

i'm trying to set up an ipv6 machine.  i got a setup script from
freenet6 complete with an ipv6 address and the ipv6 and ipv4 addresses
of my tunnel endpoint.  i'm seeing some strange behavior, so i have a
few questions.  most of these are probably ubd (user brain damage), but
i'd like to have these verified if possibe =).

0. basically, how complete/correct is the ipv6 implementation on
2.2.18pre21?  should i even bother or is it fairly stable and correct?

1. how come i can ping6 ::1 just fine as long as the sit0 device is
down, but as soon as it comes up, i can't?

2. i understand that the sit devices are pseudo devices on top of (well,
in my case) eth0.  afaict, sit0 represents my side of an ipv6-in-ipv4
tunnel and sit1 is the other side of it.  ipv6 packets destined for
removte ipv6 networks should be routed to the like-scoped ipv6 address
of the sit1 device, right?

3. aliased interfaces are in ipv4-only construct right?  i shouldn't be
able to create an alias interface with only an ipv6 address, da?

4. should i be able to delete an address i add to an interface?  when i
"ifconfig add" an ipv6 address to an interface and then try to "ifconfig
del" it, i get "SIOCDIFADDR: Invalid argument".  i've tried to del with
and without the /prefixlen and neither has worked.

thanks,
pete

-- 
Pete Toscano    p:sigsegv@psinet.com     w:pete@research.netsol.com
GPG fingerprint: D8F5 A087 9A4C 56BB 8F78  B29C 1FF0 1BA7 9008 2736

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

                 reply	other threads:[~2000-11-18 21:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20001118155441.T11099@tesla.admin.cto.netsol.com \
    --to=pete@research.netsol.com \
    --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