why do i have two global ipv6 addresses

mpyusko · 12-03-2013, 11:21 AM

Recently I've been experiencing an issue with my laptops. They seem to be assigning themselves (or some way) multiple global IPv6 addresses. Hal9000 currently has 8 assigned and pinky has 2. If I run ifconfig eth0 down;ifconfig eth0 up then they will clear and I will be back to 2 each again. But not just 1. I use HE.net for my ipv6 tunnel and have several other machines funtioning properly, it is just these two laptops that aren't. It seems to have started a few weeks ago after an update but since I only saw it in one machine i figured it was just a compatibility issue and ignored it. Now I have a clean install of wheezy on another newer laptop and I have the same problem.

Hal9000 runs 32-bit testing - Inspiron 8600
pinky runs 64-bit wheezy - Inspiron 1564
(abacus runs 64-bit testing with two GigE nics but does not have this issue)

ideas? Thanks.

Dutch Master · 12-04-2013, 01:46 PM

What does the file /etc/network/interfaces tell you?

mpyusko · 12-04-2013, 04:03 PM

Code:

root@hal9000:~# cat /etc/network/interfaces                    
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5). 
                                                                     
# The loopback network interface                                     
auto lo                                                              
iface lo inet loopback                                               
root@hal9000:~#

Dutch Master · 12-04-2013, 04:47 PM

That's odd. All network interfaces should be named in that file. Including the IPv6 ones...

/me confused

What's the result of the command

Code:

ifconfig -a

mpyusko · 12-07-2013, 01:53 AM

Code:

root@hal9000:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:0f:1f:1f:a6:e6  
          inet addr:192.168.1.31  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2001:470:1f11:7ae:4431:10fb:7502:b8d1/64 Scope:Global
          inet6 addr: 2001:470:1f11:7ae:20f:1fff:fe1f:a6e6/64 Scope:Global
          inet6 addr: fe80::20f:1fff:fe1f:a6e6/64 Scope:Link
          inet6 addr: 2001:470:1f11:7ae:6520:79a7:3389:96c0/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:108997447 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59850293 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:148421765943 (138.2 GiB)  TX bytes:5074852720 (4.7 GiB)
          Interrupt:11 

eth1      Link encap:Ethernet  HWaddr 00:0e:35:4e:16:aa  
          inet addr:192.168.1.30  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2001:470:1f11:7ae:20e:35ff:fe4e:16aa/64 Scope:Global
          inet6 addr: fe80::20e:35ff:fe4e:16aa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:31 errors:0 dropped:0 overruns:0 frame:0
          TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4599 (4.4 KiB)  TX bytes:12945 (12.6 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:17049022 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17049022 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:24983132910 (23.2 GiB)  TX bytes:24983132910 (23.2 GiB)

root@hal9000:~#

Dutch Master · 12-07-2013, 06:56 AM

Odd. According to the interfaces file you'd only have the lo device, but clearly the kernel thinks otherwise. I wonder where both eth network adapters get their configuration from.

mpyusko · 02-05-2014, 08:47 AM

I just bought a new laptop (hal9000 in signature) and it is doing the same thing. Both hal9000 and abacus run the same distro. I carried over /home from the old Inspron 8600, every other file is new.