lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 3 Nov 2006 11:58:33 -0800
From:	Stephen Hemminger <shemminger@...l.org>
To:	"roland" <devzero@....de>
Cc:	<yoshfuji@...ux-ipv6.org>, <linux-net@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: unregister_netdevice: waiting for eth0 to become free

On Fri, 3 Nov 2006 20:53:09 +0100
"roland" <devzero@....de> wrote:

> > The ipv6 module cannot be unloaded once it has been
> > loaded.
> 
> sorry,  i thought i could rmmod evey module which was insmod/modprobe'd 
> before and i didn`t know that there are exceptions
> 
> > I'm not sure what is happened with vmware.
> 
> i think this is not completely related to vmware - but maybe this is being 
> triggered more often by vmware ?
> http://www.google.de/search?hl=de&q=%22unregister_netdevice%3A+waiting+for+eth0+to+become+free
> 
> it`s really strange, but after taking a look,  vmware seems to recommend 
> disabling ipv6 for _every_ linux based guest OS in general:
> http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/common/html/wwhelp.htm?context=gos_ww5_output&file=choose_install_guest_os.html
> 
> since there are already running millions of  linux based VMs in this world, 
> i think this isn`t very good "promotion" for ipv6, if vmware recommending 
> disabling it.
> ok, there are not that much people already needing ipv6 NOW, but the later 
> they are running it and the later outstanding bugs being fixed, the harder 
> it will be to convert from ipv4 to ipv6....
> 
> roland
> 
> 

Vmware has there own pseudo ethernet device and unless you have the source for it.
It would be hard to tell if it correctly manages itself.


-- 
Stephen Hemminger <shemminger@...l.org>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ