Re: network deamons starting before network!
# grep REQUIRE /etc/rc.d/ppp # REQUIRE: netif ldconfig ^ i had to add this ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: network deamons starting before network!
On 19/06/2010 11:06, Mark Stapper wrote: On 06/18/10 12:20, Alfred Bartsch wrote: Mark Stapper schrieb: Hello, Since updating to 8.X I noticed that network services were started before the network was up! I use lagg failover configuration on both my FreeBSD boxes. First, boot fails on mounting my nfs-shares. After entering and exiting the rescue shell, the system boots as normal. Hello, adding: synchronous_dhclient=YES to /etc/rc.conf solved some similar issues for me. The default behaviour of getting an IP via dhcp has changed. I'll try that too. That would explain why I didn't have this problem on 7.2 I DO like the whole netwait idea though. But for me, the synchronous_dhclient flag should be sufficient I think. Worked like a charm! Thank you again Regards, Mark signature.asc Description: OpenPGP digital signature
Re: network deamons starting before network!
On 06/18/10 12:20, Alfred Bartsch wrote: Mark Stapper schrieb: Hello, Since updating to 8.X I noticed that network services were started before the network was up! I use lagg failover configuration on both my FreeBSD boxes. First, boot fails on mounting my nfs-shares. After entering and exiting the rescue shell, the system boots as normal. Hello, adding: synchronous_dhclient=YES to /etc/rc.conf solved some similar issues for me. The default behaviour of getting an IP via dhcp has changed. I'll try that too. That would explain why I didn't have this problem on 7.2 I DO like the whole netwait idea though. But for me, the synchronous_dhclient flag should be sufficient I think. signature.asc Description: OpenPGP digital signature
network deamons starting before network!
Hello, Since updating to 8.X I noticed that network services were started before the network was up! I use lagg failover configuration on both my FreeBSD boxes. First, boot fails on mounting my nfs-shares. After entering and exiting the rescue shell, the system boots as normal. uname -a FreeBSD mario 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #4: Fri Jun 18 07:46:01 CEST 2010 *...@mario:/usr/obj/usr/src/sys/mario amd64 What could I do to fix this? Here's an exerpt from /var/log/messages: Jun 18 09:10:25 ntpd[1376]: ntpd 4.2.4p5-a (1) Jun 18 09:10:25 kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Jun 18 09:10:27 ntpd_initres[1412]: host name not found: yoshi Jun 18 09:10:27 kernel: nfe0: link state changed to UP Jun 18 09:10:27 kernel: lagg0: link state changed to UP Jun 18 09:10:27 kernel: nfe1: link state changed to UP Jun 18 09:10:27 ntpd_initres[1412]: couldn't resolve `yoshi', giving up on it Jun 18 09:10:28 dhclient: New Hostname (lagg0): mario Jun 18 09:10:28 dhclient: New IP Address (lagg0): 10.58.235.6 Jun 18 09:10:28 dhclient: New Subnet Mask (lagg0): 255.255.255.0 Jun 18 09:10:28 dhclient: New Broadcast Address (lagg0): 10.58.235.255 Jun 18 09:10:28 dhclient: New Routers (lagg0): 10.58.235.1 signature.asc Description: OpenPGP digital signature
Re: network deamons starting before network!
On Fri, Jun 18, 2010 at 09:34:24AM +0200, Mark Stapper wrote: Hello, Since updating to 8.X I noticed that network services were started before the network was up! This is common/normal. I wrote a script (still working on getting it added to the base system) to deal with this issue. Please see: http://jdc.parodius.com/freebsd/netwait Drop this into /usr/local/etc/rc.d, chmod it 755, and read the descriptions of the variables and add the appropriate settings to rc.conf. Please be aware netwait_if only takes a single interface; you're using lagg, so I hope that when your system boots whichever interface you pick in netwait_if the one which you default to using. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: network deamons starting before network!
On 18/06/2010 10:26, Jeremy Chadwick wrote: On Fri, Jun 18, 2010 at 09:34:24AM +0200, Mark Stapper wrote: Hello, Since updating to 8.X I noticed that network services were started before the network was up! This is common/normal. I wrote a script (still working on getting it added to the base system) to deal with this issue. Please see: http://jdc.parodius.com/freebsd/netwait Drop this into /usr/local/etc/rc.d, chmod it 755, and read the descriptions of the variables and add the appropriate settings to rc.conf. Please be aware netwait_if only takes a single interface; you're using lagg, so I hope that when your system boots whichever interface you pick in netwait_if the one which you default to using. couldn't I use lagg0 on this parameter? thx btw :-) Regards, Mark signature.asc Description: OpenPGP digital signature
Re: network deamons starting before network!
On Fri, Jun 18, 2010 at 10:47:34AM +0200, Mark Stapper wrote: On 18/06/2010 10:26, Jeremy Chadwick wrote: On Fri, Jun 18, 2010 at 09:34:24AM +0200, Mark Stapper wrote: Hello, Since updating to 8.X I noticed that network services were started before the network was up! This is common/normal. I wrote a script (still working on getting it added to the base system) to deal with this issue. Please see: http://jdc.parodius.com/freebsd/netwait Drop this into /usr/local/etc/rc.d, chmod it 755, and read the descriptions of the variables and add the appropriate settings to rc.conf. Please be aware netwait_if only takes a single interface; you're using lagg, so I hope that when your system boots whichever interface you pick in netwait_if the one which you default to using. couldn't I use lagg0 on this parameter? You could, but it won't necessarily work in the way you think it will. netwait explicitly looks for link interface state (status: no carrier) in ifconfig output. This methodology is used in other base system scripts. If lagg devices offer that line in ifconfig, then the script will work but won't necessarily do what you expect. It's very common on FreeBSD for drivers of this sort to lie (please note the quotes) about the state of link. Meaning, lagg0 might show link, but maybe that means Yeah! I'm configured! -- but that doesn't mean the *physical network interfaces lagg0 is associated with* are actually functional. See where I'm going with this? In your situation, assuming lagg0 provides a status line in ifconfig, then yes you can use that -- but *ultimately* you're going to be reliant entirely upon the netwait_ip ping tests to verify network connections are working. That's just the nature of the beast. The bottom line is that the netwait script *cannot* be reliably used in complex network situations (and this may be one of those). Below is my original mail to -stable about the script (then called waitnetwork); see CAVEATS / POINTS OF INTEREST. There is truly no universal way that covers everyone's configuration/setup. http://www.mail-archive.com/freebsd-stable@freebsd.org/msg109853.html -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: network deamons starting before network!
Mark Stapper schrieb: Hello, Since updating to 8.X I noticed that network services were started before the network was up! I use lagg failover configuration on both my FreeBSD boxes. First, boot fails on mounting my nfs-shares. After entering and exiting the rescue shell, the system boots as normal. uname -a FreeBSD mario 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #4: Fri Jun 18 07:46:01 CEST 2010 *...@mario:/usr/obj/usr/src/sys/mario amd64 What could I do to fix this? Here's an exerpt from /var/log/messages: Jun 18 09:10:25 ntpd[1376]: ntpd 4.2.4p5-a (1) Jun 18 09:10:25 kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Jun 18 09:10:27 ntpd_initres[1412]: host name not found: yoshi Jun 18 09:10:27 kernel: nfe0: link state changed to UP Jun 18 09:10:27 kernel: lagg0: link state changed to UP Jun 18 09:10:27 kernel: nfe1: link state changed to UP Jun 18 09:10:27 ntpd_initres[1412]: couldn't resolve `yoshi', giving up on it Jun 18 09:10:28 dhclient: New Hostname (lagg0): mario Jun 18 09:10:28 dhclient: New IP Address (lagg0): 10.58.235.6 Jun 18 09:10:28 dhclient: New Subnet Mask (lagg0): 255.255.255.0 Jun 18 09:10:28 dhclient: New Broadcast Address (lagg0): 10.58.235.255 Jun 18 09:10:28 dhclient: New Routers (lagg0): 10.58.235.1 Hello, adding: synchronous_dhclient=YES to /etc/rc.conf solved some similar issues for me. The default behaviour of getting an IP via dhcp has changed. -- Alfred Bartsch mailto:bart...@dssgmbh.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
