Manuals/authstepbystep

From Minux Wiki
Jump to navigation Jump to search

This is a step-by-step manual for installing a minux dhcp and auth server set.


requirements:

- 2 advanced computers with a rednet cable or wireless connection for the servers.

- 1 computer (basic or better) that is also connected to the same network as test client.

- Write down or remember the computer ID of the AUTH server, this will matter during configuration. run "id" on that computer to find it's number.

Example Picture

- optional for serverwide setup : 1 more computer (basic or better), ender modem, connection to the other computers.


Prepairing the systems - installing

Start by installing minux on all computers, so repeat this for all systems,

get the netinstaller by running "wget run https://minux.cc/netinstall". example

Select "install minux" in the menu. example

Select "latest-minimal", the basic software is enough for our purpuse, you can always install more software later. example

Minux will start up and show you the boot screen and system status.


Prepairing the systems - setting local login/root password.

(only for 1.2.9 and up!) we should enable encryption for local passwords, type "config encrypt enabled", this will encrypt the local passwords.

Now we need to set the system to local login and configure a root password for both servers. "config login local". example

The system will ask you to create a root password, enter and then confirm your choice. example

It will now reboot, log in with username "root" and your chosen password. example


Installing the DHCP server

log in to your dhcp server and enter the command "apt install dhcp-server". example

Let it finish and then restart the computer. example

now configure what system ID is going to be the AUTH server, this is to prevent false servers from pretenting to be the real one.

you can do this by entering the following command: "dhcpd auth ID", replace ID with the number. example

reboot the DHCP server, once restarted you can see on top there's a new tab for the server process, open it.

it should state it's running and what AUTH server is set, if it does, we are can proceed with the AUTH server. example


Installing the AUTH server

log in to your auth-server and enter the command "apt install auth-server". example

restart the system so the server process starts,

check the new process tab to see if AUTH is running, it should state it's on but no encryption, so let's set encryption to enabled.

run the command "auth-server encrypt enabled", this will encrypt user passwords when saving them, making it a bit more secure. it remains optional.

now we can create first an admin and then a user account.

enter the command "auth-server addadmin username password", replace username and password with those of your choice. example

follow this up with "auth-server adduser username password", again replace username and password with those of your choice. example

You now have a working AUTH/DHCP pair with an admin and user account, create as many users and admins as you like, when ready, we can set up our client.


Configuring the client

we need to change the client's login system to network, do this by entering the following command: "config login network". hit enter to confirm. example

the system will install dependency's as needed an restart, if it already has all the software it will not do this and you'll have to restart it manually.

log in with your network user or admin account, example


Optional - Making it server wide

to make this setup server wide, you can use a seperate computer with ender modem.

1) place down the computer, standard should be enough.

2) (skip if all are wireless) connect the computer to the network with a modem

3) attach an ender moden to this computer

4) start the computer and "edit /startup", add the following:

repeat

os.reboot()

5) save and exit the file

6) run /startup

7) install a computer with a wireless modem anywhere and test this!


That's it! you can set as many clients and users to it as you wish, as long as they can actually reach the server pair.

More information on user/group rights and ownership can be found here.