Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am running the latest Kubuntu, Feisty, and have some networking trouble. The network does not come up at boot time, when I bring the network up manually it comes up fine. Its a simple wired network card configured as a dhcp client. I have a wireless network card which works but I have disabled.
Dmesg tells me:
Code:
[ 70.610355] lo: Disabled Privacy Extensions
[ 71.074538] /dev/vmmon[5320]: Module vmmon: registered with major=10 minor=165
[ 71.074847] /dev/vmmon[5320]: Module vmmon: initialized
[ 71.338447] /dev/vmnet: open called by PID 5358 (vmnet-bridge)
[ 71.338743] /dev/vmnet: hub 0 does not exist, allocating memory.
[ 71.338904] /dev/vmnet: port on hub 0 successfully opened
[ 71.339061] bridge-eth0: enabling the bridge
[ 71.339198] bridge-eth0: up
[ 71.339317] bridge-eth0: already up
[ 71.339495] bridge-eth0: attached
[ 71.385483] /dev/vmnet: open called by PID 5373 (vmnet-natd)
[ 71.385747] /dev/vmnet: hub 8 does not exist, allocating memory.
[ 71.385912] /dev/vmnet: port on hub 8 successfully opened
[ 71.430213] /dev/vmnet: open called by PID 5374 (vmnet-netifup)
[ 71.430484] /dev/vmnet: hub 1 does not exist, allocating memory.
[ 71.430651] /dev/vmnet: port on hub 1 successfully opened
[ 71.436409] /dev/vmnet: open called by PID 5375 (vmnet-netifup)
[ 71.436681] /dev/vmnet: port on hub 8 successfully opened
...
[ 72.009793] /dev/vmnet: open called by PID 5403 (vmnet-dhcpd)
[ 72.010011] /dev/vmnet: port on hub 8 successfully opened
...
[ 72.107587] /dev/vmnet: open called by PID 5450 (vmnet-dhcpd)
[ 72.107791] /dev/vmnet: port on hub 1 successfully opened
[ 80.699984] eth0: no IPv6 routers present
[ 81.855069] vmnet1: no IPv6 routers present
[ 82.106868] vmnet8: no IPv6 routers present
...
[ 200.962744] bridge-eth0: disabling the bridge
[ 200.973325] bridge-eth0: down
[ 200.991466] bridge-eth0: enabling the bridge
[ 200.991865] bridge-eth0: up
[ 203.210154] CIFS VFS: Send error in SETFSUnixInfo = -5
[ 203.215597] CIFS VFS: Send error in SETFSUnixInfo = -5
[ 203.220916] CIFS VFS: Send error in SETFSUnixInfo = -5
[ 203.226664] CIFS VFS: Send error in SETFSUnixInfo = -5
[ 211.401001] eth0: no IPv6 routers present
As you can see I have some vmnet stuff there, well I don't want it. It could be the problem, but I dont know how to get rid of it... Also you see the cifs mount not working, that would be because the eth0 is not up. Manually the cifs shares work fine.
I hope someone can help me out with this, perhaps someone knows how to remove those vmnet interfaces.
Thanks in advance for any help on this.
Edit: OK, I managed to remove the vmnet interfaces, no joy though..
You should be able to disable that random MAC address setting in your motherboard bios..
Quote:
There's a setting in the BIOS on these newer nForce chipsets with the Award BIOS...
"Machine MAC(NV) Address"
For some reason, there's a setting in there to have the machine randomly report a different MAC address on reboot. Disabling it, or setting it to on - then manually entering a MAC address to be used every time seems to work for now.
Ugh, well last reboot the issue came up again so the ipv6 is not to blame. I've checked my bios, no MAC address settings there. My board is quite old like 2 or 3 years.
Also I have reserved a ip address in my router based on MAC address for this machine. So the variable MAC issue does not seem to happen with my NIC.
...Uhm I'm not sure what to do about this now. Perhaps I'll wait a few days for the new Kubuntu release and hope that solves it(?).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.