Network not coming up at boot time

CRX · 10-14-2007, 06:15 AM

Hi,

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..

aus9 · 10-15-2007, 04:46 AM

until you get a better reply.

how are you bring it up manually?

ifconfig eth0 up (or)

ufup -a (or)

what?

2) do you have 2 eth cards otherwise why are you attempting bridge?

3) your dmesg should show your eth card eg

r8169 Gigabit Ethernet driver 2.2LK loaded
ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 18 (level, low) -> IRQ 17
eth0: RTL8169s/8110s at 0xf882e000, 00:0f:ea:53:32:06, IRQ 17

can you see yours as I could not.

does that mean you are having to modprobe your ethernet card?

CRX · 10-15-2007, 11:10 AM

I do a "/etc/init.d/networking restart", that takes care of my cifs mounts too.

The bridge was from the vmnet (vmware stuff) interfaces, a updated dmesg:

Code:

[   34.594475] forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.59.
...
[   35.512335] eth0: forcedeth.c: subsystem: 01043:80a7 bound to 0000:00:04.0
...
[   81.545350] lo: Disabled Privacy Extensions
[   92.051317] eth0: no IPv6 routers present
[  114.825699] ISOFS: changing to secondary root
[  176.405276]  CIFS VFS: Send error in SETFSUnixInfo = -5
[  176.411380]  CIFS VFS: Send error in SETFSUnixInfo = -5
[  176.417130]  CIFS VFS: Send error in SETFSUnixInfo = -5
[  176.423320]  CIFS VFS: Send error in SETFSUnixInfo = -5
[  183.071758] eth0: no IPv6 routers present

Edit: Ah, think I solved it, I have disabled ipv6. I've rebooted a few times so far so good.

I guess ipv4 and ipv6 will never learn to play nice ;-p

farslayer · 10-15-2007, 11:24 AM

nforce.. we discovered the nforce ethernet changes it's mac address on every boot. I wonder if that is partially to blame for your network issues.
http://www.linuxquestions.org/questi...y-boot-569576/

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.

One of those "features" I could do without.

I would start there and see what happens. .

CRX · 10-15-2007, 05:56 PM

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(?).

aus9 · 10-15-2007, 07:09 PM

well I don't change mine, but I do have a script in rc.local to set my mtu

/sbin/ifconfig eth0 mtu 1492 (I have a wired router)

2) but it can be used to fix ip

/sbin/ifconfig eth0 address xx.yy.etc

dunno if that helps or not

CRX · 10-16-2007, 04:14 PM

Ok, I put "/etc/init.d/networking restart" in my rc.local, again so far so good, and I'm knocking on wood just to be on the save side ;p