NFS does not start after creating a bridge

[f.gruber]

Suse 10.2 as host.
I successfully configured a bridge for to enable virtual networking.
This is the configuration file of the bridge:

Code: Select all

BOOTPROTO="dhcp"
NAME="Bridge_0"
NETMASK="255.255.255.0"
DHCLIENT_TIMEOUT=30
STARTMODE="auto"
USERCONTROL="no"
BRIDGE="yes"
BRIDGE_PORTS="eth0"

Now I have the problem that the nfs client does not work automatically after reboot.
I have to switch to a text terminal and enter

Code: Select all

rcnfs start

Then the NFS drives are mounted correctly and I am able to start KDE because the home directory is on a NFS share.
/var/log/boot.msg says:

Code: Select all

Starting RPC portmap daemon done
Importing Net File System (NFS)mount server reported tcp not available, falling back to udp
mount: RPC: Remote system error - Network is unreachable
mount server reported tcp not available, falling back to udp
mount: RPC: Remote system error - Network is unreachable
done

How can this be configured so that nfs works after reboot?

[starfry]

Hello,

Just jumping on this post here as I have a similar issue.

I'm running Hardy and have successfully got a bridged network running and it works just fine. Except that nfs does not start unless I restart it after boot.

I believe the culprit is NetworkManager. I don't want to disable NetworkManager as I'd like to retain for Wireless use but I'd like to fix this break with nfs.

Has anyone else noticed this problem ?

[Sasquatch]

It could be the issue where the brigde waits for 32 seconds to become ready. You can change this time using the correct info in your network config. As I have Ubuntu as Host, I have listed a line with bridge_maxwait 0 in the bridge config.

As for the need to restart it, you could put the command in rc.local or whatever file is used at the end of the boot on RPM based distro's.