Ubuntu ltsp server can't connect to internet

[rfurgy]

Ok, I have currently undertaken a project of setting up an Ubuntu ltsp server to use for booting thin clients. Upon install from the Ubuntu 9.04 Alternate CD, everything seems to go as needed till I boot the system and it has no connection on the internet side. I also tried to install the standard server version without the ltsp option then install the ltsp packages on the already working desktop. I get better control of the network devices but end up with internet connection but no connection on the client side.

I've been trying many different suggestions and settings on how to get this working but still haven't gotten it to work. As far as I can tell, the easier way of the two is for me to install Ubuntu Server with the ltsp option from the CD and try to get the internet side set up correctly to connect and complete the install (which is the way it has been installed and am currently working with). But ltsp installed from the CD won't allow the server to connect to the internet and allow me to build the i386 client on my AMD64 server.

I am starting to think that somewhere along the install process for the ltsp from the CD there is either an incorrect/missing network setting that won't allow me to connect to the internet.

I have a router on the internet side which the server connects to, then a switch connected on the client side. I've switched back to the CD install because I'm able to get the client an IP and it will request the boot files (which aren't in place because I am out the internet connection in order to complete the ltsp-build-client). I can run the ifconfig and see both network cards working and there they seem to be working just fine. From the network icon in the system tray, the server sees both cards but only the one I chose as the primary shows connection and the other says it's not managed.

Sorry for the long post and because I don't have internet connection on the server, I will have to transfer any results to my other OS in order to get them up here. So I'll be back in here to post the attachments from the commands on the first page of bug reporting where I typed all this in.

[rfurgy (rfurgy)]

found a lead

[rfurgy (rfurgy)]

With the big release of 9.10 Karmic coming, I decided to install the LTSP version from a fresh burnt install CD of Ubuntu 9.10

I got further out the door than trying to use it with 9.04 (which wouldn't give me any internet for the server what so ever)
LTSP on Ubuntu 9.10 Beta at least allowed me to boot to the desktop with internet the first try. So I did my hardware driver and updates install, which both required a reboot. Unfortunately upon reboot, my inter net was gone like 9.04 was doing to me. Tried a couple reboots but nothing changed.

So I started searching around the net from Windows and had come across a page that had some things close to what was happening to me and wrote down some Terminal commands to take back to Ubuntu and try.

Things I tried:
route -n
route add default gateway 192.168.0.1

Last but not, I did a gedit from root and added two command lines to /etc/network/interfaces file and did a SEARCH > REPLACE all instances of 192.168.0 with 192.168.100 while editting the /etc/ltsp/dhcpd.conf file.
The two lines I added under auto eth1 section: gateway=192.168.0.1 and gatewaydev=eth1

After that I did a reboot and I now am updating this from Ubuntu. Not sure what in there actually did the trick, but from what I was reading on the posts, it would seem that the network settings that are setup during install are missing a little something. I figure it's either with the specific device chosen during install or the network bridge that gets built.

This is now what my interfaces file looks like:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth1
gateway=192.168.0.1
gatewaydev=eth1
#iface eth1 inet dhcp

auto eth0
iface eth0 inet static
    address 192.168.0.254
    netmask 255.255.255.0
    network 192.168.0.0
    broadcast 192.168.0.255

Next I'll have to see if I can get the thin client side up and running.