All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Ikebe <ikebe.takashi@lab.ntt.co.jp>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: netdev@oss.sgi.com, davem@davemloft.net, akpm@osdl.org,
	ctindel@users.sourceforge.net, fubar@us.ibm.com,
	bonding-devel@lists.sourceforge.net
Subject: Re: [Bugme-new] [Bug 4189] New: IPv6 link local addresses are not assigned correctly on multiple-bonding enviromrnts
Date: Thu, 10 Feb 2005 20:59:18 +0900	[thread overview]
Message-ID: <420B4C96.9010808@lab.ntt.co.jp> (raw)
In-Reply-To: <20050210.182517.55994883.yoshfuji@linux-ipv6.org>

I think this cause by network init script.
network init script always bring up ifcfg-[A-Za-z0-9\._-],
so ifcfg-bond* always bring up before ifcfg-eth*! ("b" is before "e" in
alphabet order!)
I see, this is not a kernel issue, and this is initscript issue.


YOSHIFUJI Hideaki / 吉藤英明 wrote:
> Sorry for typo...
> 
> In article <20050210.182225.07335127.yoshfuji@linux-ipv6.org> (at Thu, 10 Feb 2005 18:22:25 +0900 (JST)), YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org> says:
> 
> 
>>So, currently, you need to do this:
>>
>># ip link set bond0 address 00:01:02:03:04:05
>># ifconfig bond0 up <= here fe80::200:ff:fe00:0/64 is assigned
> 
>                               fe80::201:02ff:fe03:0405 is assigned
> 
>># ifenslave bond0 eth0 ...
> 
> 


-- 
Takashi Ikebe
NTT Network Service Systems Laboratories
9-11, Midori-Cho 3-Chome Musashino-Shi,
Tokyo 180-8585 Japan
Tel : +81 422 59 4246, Fax : +81 422 60 4012
e-mail : ikebe.takashi@lab.ntt.co.jp

  reply	other threads:[~2005-02-10 11:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10  8:23 Fw: [Bugme-new] [Bug 4189] New: IPv6 link local addresses are not assigned correctly on multiple-bonding enviromrnts Andrew Morton
2005-02-10  9:22 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-10  9:25   ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-10 11:59     ` Takashi Ikebe [this message]
2005-02-10 18:17   ` [Bonding-devel] " Jay Vosburgh
2005-02-10 20:27     ` David S. Miller
2005-02-10 21:26       ` Rick Jones
2005-02-11  2:40       ` Jay Vosburgh
2005-02-11  3:44         ` David S. Miller
2005-02-10 20:25   ` David S. Miller
2005-02-11  0:29     ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-11  1:06       ` David S. Miller
2005-02-11  1:40       ` Rick Jones
2005-02-11  2:17         ` YOSHIFUJI Hideaki / 吉藤英明

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=420B4C96.9010808@lab.ntt.co.jp \
    --to=ikebe.takashi@lab.ntt.co.jp \
    --cc=akpm@osdl.org \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=ctindel@users.sourceforge.net \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@linux-ipv6.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.