Roland Dreier wrote:
Tom Would you really bring both interfaces up? If this is a
Tom problem, the spec should have the pkey be part of the link
Tom local address.
It actually seems to work fine to bring up multiple IPv6 interfaces
that end up with the same link local address
signed off by: Nitin Hande [EMAIL PROTECTED]
I would appreciate if someone can review my patch to enable inet6
address on ib interface. This is the first cut, will like to hear from
all. I plan to setup a bugzilla account and append this patch to the bug
that Tom has created for inet6.
diff
Nitin I would appreciate if someone can review my patch to enable
Nitin inet6 address on ib interface. This is the first cut, will
Nitin like to hear from all. I plan to setup a bugzilla account
Nitin and append this patch to the bug that Tom has created for
Nitin inet6.
This
signed off by: Nitin Hande [EMAIL PROTECTED]
By the way, the proper format for
signed off by: Nitin Hande [EMAIL PROTECTED]
is really
Signed-off-by: Nitin Hande [EMAIL PROTECTED]
(see Documentation/SubmittingPatches).
- R.
___
On Thu, 2004-11-11 at 13:27 -0500, Hal Rosenstock wrote:
What's S10 ?
Solaris 10. Which has IPv6oIB.
-tduffy
signature.asc
Description: This is a digitally signed message part
___
openib-general mailing list
[EMAIL PROTECTED]
Hal IBTA GUIDs are EUI-64. The only issue I recall was whether
Hal the polarity of the U/G bit was consistent with IEEE. This
Hal was updated at IBA 1.2. It now says manufacturer assigns
Hal EUI-64 with global scope set. May also assign additional
Hal EUI-64 with local scope.
On Thu, 2004-11-11 at 13:46, Roland Dreier wrote:
Hal IBTA GUIDs are EUI-64. The only issue I recall was whether
Hal the polarity of the U/G bit was consistent with IEEE. This
Hal was updated at IBA 1.2. It now says manufacturer assigns
Hal EUI-64 with global scope set. May
All,
Thanks for your comments,
Roland Dreier wrote:
Nitin I would appreciate if someone can review my patch to enable
Nitin inet6 address on ib interface. This is the first cut, will
Nitin like to hear from all. I plan to setup a bugzilla account
Nitin and append this patch
OK, with the patch below all the correct IPv6 groups seem to be
created and used. Ping works at least...
One question about IPv6 and IPoIB: currently the IPoIB driver joins
the IPv4 broadcast group and then uses those parameters to join or
create (as needed) the other groups, including all IPv6
By the way, can anyone explain the following to me (an IPv6 rookie):
# ping6 -I ib0 fe80::202:c901:78c:e461
PING fe80::202:c901:78c:e461(fe80::202:c901:78c:e461) from
fe80::202:c901:7fc:c711 ib0: 56 data bytes
64 bytes from fe80::202:c901:78c:e461: icmp_seq=1 ttl=64 time=32.2 ms
Roland Dreier wrote:
By the way, can anyone explain the following to me (an IPv6 rookie):
# ping6 -I ib0 fe80::202:c901:78c:e461
PING fe80::202:c901:78c:e461(fe80::202:c901:78c:e461) from
fe80::202:c901:7fc:c711 ib0: 56 data bytes
64 bytes from fe80::202:c901:78c:e461:
IPoverIB at ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib
-Forwarded Message-
From: Hal Rosenstock [EMAIL PROTECTED]
To: Roland Dreier [EMAIL PROTECTED]
Cc: Nitin Hande [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [openib-general] [PATCH] Enable inet6 on ib interface
Date
Roland Dreier wrote:
By the way, can anyone explain the following to me (an IPv6 rookie):
# ping6 -I ib0 fe80::202:c901:78c:e461
PING fe80::202:c901:78c:e461(fe80::202:c901:78c:e461) from
fe80::202:c901:7fc:c711 ib0: 56 data bytes
64 bytes from fe80::202:c901:78c:e461:
Tom With the updated patch (and with Nitin's original patch),
Tom when I bring up ipv6, I am not getting the correct link local
Tom address. I can assign it a global address and ping just
Tom fine, but the lower 64 bits of the IPv6 address are NULL
Tom (except for the set link
I think we just need to copy our address to the child interface. This
patch seems to fix it for me (already checked in).
(By the way, how does IPv6 handle autoconfig for VLAN interfaces?
With this change you can get duplicate autoconfig'ed addresses,
although they will be in different
Nitin Based on some googling I found that for linux, since Link
Nitin Local addresses are not routable, you need to provide the
Nitin scope (by specifying an outgoing interface) to ssh in
Nitin linux. This is very different from Solaris implementation
Nitin where it still
16 matches
Mail list logo
