Bug 14964
| Summary: | Network Interface Configuration Problem and how it relates to lo0, portmap and rpc.statd. | ||
|---|---|---|---|
| Product: | Base System | Reporter: | nschein <nschein> |
| Component: | misc | Assignee: | Mike Heffner <mikeh> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
On Wed, 17 Nov 1999 15:36:18 PST, nschein@prisa.com wrote: > >Fix: > > Do not have sysinstall place a network interface in /etc/rc.conf the > standard "auto" in /etc/defaults/rc.conf works well or put lo0 in the > /etc/rc.conf netw ork_interface line. Or read the online ERRATA.TXT before installing. :-) http://www.freebsd.org/releases/3.3R/errata.html Ciao, Sheldon. State Changed From-To: open->feedback Is this still a problem with a recent version? Responsible Changed From-To: freebsd-bugs->mikeh I'll followup. State Changed From-To: feedback->closed Feedback timeout. |
Durring the installation process the network_interfaces line in /etc/rc.conf is set to "`interface` auto" I have found that this incorrectly configures "lo0" and does not allow rpc.statd to register with portmap. I have tested this across two installations 3.2-stable and 3.3-release. If network interfaces are set to just auto this is the ifconfig: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 If network interfaces are set to "ep0 auto" this is the ifconfig: lo0: flags=8008<LOOPBACK,MULTICAST> mtu 16384 Fix: Do not have sysinstall place a network interface in /etc/rc.conf the standard "auto" in /etc/defaults/rc.conf works well or put lo0 in the /etc/rc.conf network_interface line. How-To-Repeat: In /etc/rc.conf nfs_server_enable="YES" nfs_client_enable="YES" network_interfaces="ep0 auto"