Date: Mon, 11 Apr 2011 07:10:12 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: freebsd-net@freebsd.org Subject: Diskless booting issues Message-ID: <20110410211012.GA82480@server.vk2pj.dyndns.org>
next in thread | raw e-mail | index | archive | help
--ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable For various reasons, I occasionally boot my netbook as a diskless client of my main server (this is a quick/easy way to test upgrades without needing to install them). Since I still like to use it as a netbook in this mode (ie, wander around the house), I've run into a couple of issues that I haven't been able to resolve myself and would like some assistance with. I'm running FreeBSD-8.2 i386 from the beginning of March on an original Acer Aspire One. First problem: If it loses network connectivity (ie, I unplug the network cable) for more than a minute or so, it seems to lockup and need a hard reboot, even if the network is restored. I'm a bit vague on this because it's been running X on the occasions I've seen this and I just get a blank screen with no responsiveness from the keyboard and it isn't pingable, though the ethernet link light is on. Second problem: When running on the local SSD, I have lagg setup so it seamlessly switches between wired and wifi (this is really nice). Partially to resolve the above and partially to improve portability, I'd like to do the same when running diskless but can't work out how to make it work. The relevant bits of my native rc.conf look like: ifconfig_re0=3D"up" ifconfig_ath0=3D"ether XX:XX:XX:XX:XX:XX" wlans_ath0=3D"wlan0" ifconfig_wlan0=3D"WPA" cloned_interfaces=3D"lagg0" ifconfig_lagg0=3D"SYNCDHCP laggproto failover laggport re0 laggport wlan0" Gluing this in the diskless rc.conf gives me a hang during startup, as does changing 'SYNCDHCP' to 'inet MYHOST' and adding 'up'. Adding a 'set -x' to the startup shows that it executes: ifconfig lagg0 inet MYHOST laggproto failover laggport re0 laggport wlan0= up ifconfig lagg0 up and hangs at this point (though the kernel reports lagg0 up). ^T shows it in "connect" state. I've tried working through the commands manually and basically, any "disk" access after the first ifconfig above will hang. In diskless mode, re0 is "up" with the correct IP address when init(8) starts and I presume the kernel is getting upset at the IP address migrating from re0 to lagg0. I have considered trying to use lagg0 (made up only of re0) as the boot device but I can't work out how to achieve this (in particular, how to "up" re0 when that's not part of the diskless boot sequence). Does anyone have any suggestions? --=20 Peter Jeremy --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk2iHLQACgkQ/opHv/APuIdoKACffQ1GjfBPhdE5H5AbJ8SaK4Qt zn4AnjMBGxz53Oh1AaB0o+IlF3BA+t2t =aM+j -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110410211012.GA82480>