netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: Add/Delete IPv6 addresses and netlink
Date: Fri, 20 Jun 2008 22:25:18 -0700	[thread overview]
Message-ID: <485C90BE.60301@candelatech.com> (raw)
In-Reply-To: <4857DC95.8000709@candelatech.com>

Ben Greear wrote:
>
> I'm using the 8139too driver.  I notice that it shows full link
> speed (100-FD) when the NIC is admin down.   Maybe that is causing it 
> to not
> go through an expected state change?
>
> I'll work on doing this same test with a vanilla kernel but on this 
> hardware just in case I've
> screwed something up somewhere...
I just re-did this test on the latest FC8 kernel and the same problem 
appears.

ip link set eth1 down; ip -6 addr flush dev eth1;
Nothing to flush.
ip -6 addr add 2000::9:2/112 scope global dev eth1
ip link set eth1 up
ip -6 addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 2000::9:2/112 scope global tentative
       valid_lft forever preferred_lft forever
    inet6 fe80::203:2dff:fe04:65b1/64 scope link
       valid_lft forever preferred_lft forever
uname -a
Linux lanforge-65-AF 2.6.25.4-10.fc8 #1 SMP Thu May 22 23:34:09 EDT 2008 
i686 i686 i386 GNU/Linux

I wonder if it's something to do with the 8139too driver.  Can anyone 
else with that NIC
confirm?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com> 
Candela Technologies Inc  http://www.candelatech.com



      reply	other threads:[~2008-06-21  5:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17  1:33 Add/Delete IPv6 addresses and netlink Ben Greear
2008-06-17 12:18 ` Thomas Graf
2008-06-17 15:47   ` Ben Greear
2008-06-21  5:25     ` Ben Greear [this message]

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=485C90BE.60301@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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).