Trouble configuring LTSP Autologin with ssh-keys
Running LTSP Server (from Ubuntu repositories) on Ubuntu 12.04.
I had successfully configured LTSP for Autologin using ssh-keys. Today I decided that I was going to change my network's internal ip address range. Previously the address range was in the 192.168.2.0/24 subnet. For no real good reason, other that I am a tad obsessive compulsive about some things, I changed to the 10.0.0.0/8 subnet. I am well aware that I will never use that many ips. I play around with VirtualBox a great deal, and it is generally my practice to allow my dhcp server to automatically assign addresses to these virtual machines. The idea was that I would configure dhcpd to issue ips to these virtual machines (and any wireless devices that my family/friends bring into the home) in a block off to themselves and not clutter up the space around the machines that I do some web hosting off of.
I drew from the guide on Ubuntu's website to do the original configuration.
When using LTSP's autologin with ssh-keys, the thinclient used to get assigned a login name of 'ltspx' where x is the number in the last octet of the ip address. For example, say the thinclient's ip address was 192.168.2.3. It's login name would then be 'ltsp3' It was then easy to create a user on the LTSP server named 'ltsp3' and do the necessary ssh configuration to allow authentication via ssh-keys. Let me repeat for clarity, this was a working configuration that had been banging along providing my children with a nice cheap computer for about 7 months now. (If it ain't broke, don't fix it, huh?)
The problem I am having is figuring out what logon name to use now that the thin client is being assigned an address from the 10.0.0.0/8 subnet. I can login using username/password just fine. It is only a no-go when I switch to trying to use ssh-keys again (I would just stick with the username/password login, but my children are young and only one is able to read/write well enough to remember and type said username/passwords).
I am about cross-eyed from pouring over configuration files, and I have even rebuilt the client in the off-chance that that may fix the problem (it did not). I read that it was necessary to do 'ltsp-update-sshkeys' and 'ltsp-update-image --arch i386' after changing the server's ip, but that has made no noticable difference.
nbd_server: connect from x.x.x.x, assigned file is /opt/ltsp/images/i386.img
nbd_server: Can't open authorization file (null) (Bad address).