IPv6 stops working after ethtool diagnostic

IPv6 stops working after ethtool diagnostic

[Tantilov, Emil S]

We ran into a problem on net-next where IPv6 traffic fails after running ethtool -t:

Steps to reproduce:
1. ip addr show eth0
170: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:1b:21:53:0a:d6 brd ff:ff:ff:ff:ff:ff
    inet 190.0.15.5/16 brd 190.0.255.255 scope global eth0
    inet6 fec0::1505/112 scope site 
       valid_lft forever preferred_lft forever
    inet6 fe80::21b:21ff:fe53:ad6/64 scope link 
       valid_lft forever preferred_lft forever

2. ping6 -I eth0 fec0::1314
PING fec0::1314(fec0::1314) from fec0::1505 eth0: 56 data bytes
64 bytes from fec0::1314: icmp_seq=1 ttl=64 time=0.130 ms
64 bytes from fec0::1314: icmp_seq=2 ttl=64 time=0.119 ms
64 bytes from fec0::1314: icmp_seq=3 ttl=64 time=0.167 ms

3 ethtool -t eth0 (ifconfig eth0 down/up has the same effect)

4. ping6 -I eth0 fec0::1314
connect: Network is unreachable

5. ip addr show eth0
170: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:1b:21:53:0a:d6 brd ff:ff:ff:ff:ff:ff
    inet 190.0.15.5/16 brd 190.0.255.255 scope global eth0
    inet6 fec0::1505/112 scope site 
       valid_lft forever preferred_lft forever
    inet6 fe80::21b:21ff:fe53:ad6/64 scope link 
       valid_lft forever preferred_lft forever

Thanks,
Emil

Re: IPv6 stops working after ethtool diagnostic

[Ben Hutchings]

On Tue, 2010-06-15 at 12:05 -0600, Tantilov, Emil S wrote:
> We ran into a problem on net-next where IPv6 traffic fails after running ethtool -t:

Are you going to report which driver is responsible for eth0 or are are
you going to let us guess?

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

RE: IPv6 stops working after ethtool diagnostic

[Tantilov, Emil S]

Ben Hutchings wrote:
> On Tue, 2010-06-15 at 12:05 -0600, Tantilov, Emil S wrote:
>> We ran into a problem on net-next where IPv6 traffic fails after
>> running ethtool -t: 
> 
> Are you going to report which driver is responsible for eth0 or are
> are you going to let us guess?

Yeah - should've mention that. In my tests so far this does not appear to be driver specific issue. I was able to reproduce with e1000e, igb, ixgbe and bnx2.

Thanks,
Emil

Re: IPv6 stops working after ethtool diagnostic

[Shan Wei]

Tantilov, Emil S wrote, at 06/16/2010 02:05 AM:
> We ran into a problem on net-next where IPv6 traffic fails after running ethtool -t:

When you execute "ethtool -t" or "ifdown", the router entry to fec0::1314 will be
deleted.

Try to add the router using the following command:
#ip -6 route add fec0::1314 dev eth1

-- 
Best Regards
-----
Shan Wei