Hi,
A bit of background first :) I have a netbook which connects to my LAN
via a Wifi connection and I've configured autofs to pull it's maps from
an LDAP directory. The network connection is working exactly as expected
and receives a reserved IP address assigned by DHCP. The network
connection is handled by NetworkManager and is configured as the default
connection, to connect automatically and importantly an IPv4 address is
required in order for the connection to be considered "successful".
Autofs also works as expected if I manually (re)start the service, it
pulls it maps and I can mount NFS exports.
Autofs is configured to start on boot. The problem is at the point when
it starts on boot it does not work because the netbook has not been
assigned an IP address yet, (although the wifi interface is up).
eth1 Link encap:Ethernet HWaddr 90:A4:DE:49:42:31
inet6 addr: fe80::92a4:deff:fe49:39ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16
(Yes eth1 is the Wifi interface)
The autofs init script seems to require the network to be working before
it starts, ie:
# Required-Start: $network $ypbind
and in order for the network connection to be successful it needs an
IPv4 address. So my question is, why does autofs get started before an
IPv4 address has been made available? Is there a reasonable way to fix this?
--
Ian Chapman.
--
users mailing list
[email protected]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
