[SOLVED] Absolute Minimum Netbooting problems

[Akane]

Hi Zendrael!

Oh! Sorry.
Please restart NFS daemon after 'exportfs -ra'ing.

Regards,
Akane.

[gerald_clark]

Unless you have installed and started the nfs-client service on the client, you will need to add the -o nolock mount option.

mount -o nolock 192.168.56.103:/tftpboot/nfs/ws1 /tmp/nfs

[Zendrael]

Hi all!

Good news: the client booted up and the /mnt/nfs is the nfs share on the server, it even can write to it and I can see the files in the server!

What still didn't worked: the extensions are not loaded!

Almost there!!!

[Akane]

Hi Zendael!

Great!

Then append 'tce=nfs' to the command line of the client.
It would work soon!

Regards,
Akane.

[Zendrael]

Hi Akane!

Added, restarted and not loading extensions yet... The extensions are in the server, inside /tftpboot/nfs/ws1/tce/optional/

Gerald_clark, thanks by your help, just didn't test because the nfs mount in the boot worked.

Yeah, I believe it will work soon!

Thanks!

[Akane]

Hi Zendrael!

Hmmm...
Something is wrong.

Could you add 'pause' boot option for the client, boot him(her) and show us the boot messages?

Regards,
Akane.

[gerald_clark]

Does your tce directory have a valid onboot.lst?

Post the output of 'showbootcodes' on the client.

[Zendrael]

Hello!

@Akane, attached is the result after adding 'pause' to the boot of the clients.

@Gerald_clarck, attached is also the result of 'showbootcodes'

In the /tftpboot/nfs/ws1/tce (in the server) I have an onboot.lst that contain:

Code: [Select]

/nfs/ws1/tce/optional/<extension_names>.tcz(one extension per line)

Maybe the problem is this file?

[curaga]

onboot.lst should not contain paths.

[Akane]

Hi Zendrael!

It seems that the extensions are loaded normally.

Are the extensions you want to load listed in the onboot.lst?

If they are listed, append 'showapps' command line option for the client and show us the boot messages.

Regards,
Akane.

[Zendrael]

WOW, IT WORKED!

I copied the onboot.lst from the server, and it booted up and even loaded the Xvesa, wbar... =)

Last step (i guess) the internet connection!

The server has two interfaces, one eth0 connected to the internet and the second eth1 used to share the dhcp to the clients. BUT the server only works online if the second is disabled... the clients are using the server IP as Gateway.

[Akane]

Congratulations!

To set true gateway(TRUEGATEWAY), run these commands AS ROOT:

Code: [Select]

# route del default
# route add -net default gw TRUEGATEWAY

Regards,
Akane.

[Zendrael]

Hi Akane!

Did the commands in the server, it still did not get online, neither the clients.

Do I have to run these commands on every reboot of the server?

If I disable the eth1 (from hardware) in the server, he gets online. With the two network cards, seems like he gets lost... and didn't get online (even getting the right IP)

[gerald_clark]

If you intend to use 2 ethernet adapters, you will need to set them up manually in bootlocal.sh.
If you intend to use the server as a router/gateway you will need to do a lot more work, including installation and configuration of
iptables, and enabling forwarding.

To be honest, someone with your experience should not be building internet facing servers.
Buy a consumer DSL/CABLE router and install your servers behind it.
Use it to share your internet connection with your home network.

[Zendrael]

Hi Mr. Gerald_Clark!

I'm used to build LTSP servers with Ubuntu and Debian, LAMP servers and File Servers for small business... But even using Core since version 2, I wasn't feeling confortable to change the working servers replacing the existing distros by Core so I never tryied it before...
Now I have a new project (a charity project) for a small room for children to access internet and learn how to use computers, all machines were donated and my intent is to use Core because in the few years that I use Linux (about 12 years) it's the best distro in many ways following the KISS method.

Maybe you are right, I should not be build servers as I'm more a programmer than a Network Adm... But, well, I'll keep trying!

Thanks again for the help!