From: Jim Westfall <jwestfall@surrealistic.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Brian Haley <brian.haley@hp.com>, netdev@vger.kernel.org
Subject: Re: ipv6 secondary ips and default ipv6 ip for new outbound connections
Date: Mon, 21 Mar 2011 17:15:08 -0700 [thread overview]
Message-ID: <20110322001508.GA13831@surrealistic.net> (raw)
In-Reply-To: <m2k4fvbks6.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k.org> wrote [03.19.11]:
> Jim Westfall <jwestfall@surrealistic.net> writes:
>
> > Your patch fixes it for me.
> >
> > # ip addr add 2600:c00:0:1::1101/64 dev eth0
> > ~# traceroute6 www.kame.net | head -0
> > traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2600:c00:0:1::1101, 30 hops max, 16 byte packets
> >
> > ~# ip addr add 2600:c00:0:1::1102/64 dev eth0
> > ~# traceroute6 www.kame.net | head -0
> > traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2600:c00:0:1::1101, 30 hops max, 16 byte packets
> >
> > ~# ip addr add 2600:c00:0:1::1103/64 dev eth0
> > ~# traceroute6 www.kame.net | head -0
> > traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2600:c00:0:1::1101, 30 hops max, 16 byte packets
>
> Does this also affect the selected address if use_tempaddr=2?
>
> Andreas.
>
I am new to using temp addresses, but it appears to be working as
expected.
With the interface down I set use_tempaddr=2, brought the interface up
and added my 2 static ipv6 ips, then ran rdisc6 on the interface.
This resulted in the following
13: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 00:10:18:17:a0:e6 brd ff:ff:ff:ff:ff:ff
inet6 2600:c00:1002:2::101/64 scope global
valid_lft forever preferred_lft forever
inet6 2600:c00:1002:2::102/64 scope global
valid_lft forever preferred_lft forever
inet6 2600:c00:1002:2:210:18ff:fe17:a0e6/64 scope global dynamic
valid_lft 2591996sec preferred_lft 604796sec
inet6 2600:c00:1002:2:ccd2:cf82:efb0:8dc5/64 scope global temporary dynamic
valid_lft 604796sec preferred_lft 85796sec
inet6 fe80::210:18ff:fe17:a0e6/64 scope link
valid_lft forever preferred_lft forever
~# traceroute6 www.kame.net
traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2600:c00:1002:2:ccd2:cf82:efb0:8dc5, 30 hops max, 16 byte packets
It correctly sourced from 2600:c00:1002:2:ccd2:cf82:efb0:8dc5.
I repeated the same steps but reset use_tempaddr=1
~# traceroute6 www.kame.net
traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2600:c00:1002:2::101, 30 hops max, 16 byte packets
For which 2600:c00:1002:2::101 was my first added static ip.
In testing the above I observed that downing the interface resulted in
all ipv6 addressing being removed. Is this expected? I can see
removing the dynamic/temp addresses, but seems weird for the statics I
added.
thanks
Jim
next prev parent reply other threads:[~2011-03-22 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 23:03 ipv6 secondary ips and default ipv6 ip for new outbound connections Jim Westfall
2011-03-19 2:23 ` Brian Haley
2011-03-19 3:35 ` Jim Westfall
2011-03-19 8:02 ` Andreas Schwab
2011-03-22 0:15 ` Jim Westfall [this message]
2011-03-22 2:14 ` Brian Haley
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=20110322001508.GA13831@surrealistic.net \
--to=jwestfall@surrealistic.net \
--cc=brian.haley@hp.com \
--cc=netdev@vger.kernel.org \
--cc=schwab@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).