Deploy Xinu - Revision history

Akoehler: /* What to do next? */

2008-12-19T03:35:06Z

What to do next?

Akoehler: HOWTO:Deploy Xinu moved to Deploy Xinu: no need for HOWTO in the title, its a category

2008-12-19T03:25:48Z

HOWTO:Deploy Xinu moved to Deploy Xinu: no need for HOWTO in the title, its a category

Akoehler at 03:25, 19 December 2008

2008-12-19T03:25:06Z

Amallen: /* Configuring the TFTP Server */ reworded the sentence with the link to the "change IP address" tutorial so it didn't use the word "here" as the link

2008-07-14T23:58:57Z

Configuring the TFTP Server: reworded the sentence with the link to the "change IP address" tutorial so it didn't use the word "here" as the link

Amallen: /* Configuring the TFTP Server */ added description of adding iptables accept line to the machine's /etc/rc.local file

2008-07-14T21:51:25Z

Configuring the TFTP Server: added description of adding iptables accept line to the machine's /etc/rc.local file

Amallen: /* Booting XINU on your Backend */ used the term, "tftp server directory" instead of just /tftpboot

2008-06-30T19:32:16Z

Booting XINU on your Backend: used the term, "tftp server directory" instead of just /tftpboot

Amallen: changed the "configuring the tftp server" step to make it simpler

2008-06-26T21:30:29Z

changed the "configuring the tftp server" step to make it simpler

Show changes

Michael: /* What to do next? */

2008-06-26T16:55:13Z

What to do next?

Michael at 16:54, 26 June 2008

2008-06-26T16:54:49Z

Show changes

Michael: Reverted edits by Michael (Talk); changed back to last version by Brylow

2008-06-26T16:51:09Z

Reverted edits by Michael (Talk); changed back to last version by Brylow

← Older revision		Revision as of 03:35, 19 December 2008
Line 218:		Line 218:


−	~~<hr/>~~	+	----
	''This work is supported in part by NSF grant DUE-CCLI-0737476.''		''This work is supported in part by NSF grant DUE-CCLI-0737476.''

← Older revision		Revision as of 03:25, 19 December 2008
Line 1:		Line 1:
		+	[[Category:HOWTO]]
	By this point it is assumed you have [[List_of_supported_platforms\| obtained a supported router]] to use as a back end, have [[HOWTO:Modify_the_Linksys_hardware\| made the necessary modifications]] to use the serial port, have [[HOWTO:Connect_to_a_modified_router\| connected to your backend router]] using serial communication software (such as PICOCOM), and have [[HOWTO:Build XINU#Cross-Compiler\| built a cross-compiler]] (from your host computer's architecture to MIPS) and used it to [[HOWTO:Build XINU#Building the XINU Image\|build a XINU boot image]] to run on the back end (a file called <code> xinu.boot </code> should be in your <code> compile </code> directory). If you have not it is suggested you visit http://mulug.mscs.mu.edu/xinu/ to understand what you need and why.		By this point it is assumed you have [[List_of_supported_platforms\| obtained a supported router]] to use as a back end, have [[HOWTO:Modify_the_Linksys_hardware\| made the necessary modifications]] to use the serial port, have [[HOWTO:Connect_to_a_modified_router\| connected to your backend router]] using serial communication software (such as PICOCOM), and have [[HOWTO:Build XINU#Cross-Compiler\| built a cross-compiler]] (from your host computer's architecture to MIPS) and used it to [[HOWTO:Build XINU#Building the XINU Image\|build a XINU boot image]] to run on the back end (a file called <code> xinu.boot </code> should be in your <code> compile </code> directory). If you have not it is suggested you visit http://mulug.mscs.mu.edu/xinu/ to understand what you need and why.

@@ Line 150: / Line 150: @@
 There are a couple other configurations that you may need to set up in order to get your '''TFTP Server''' running. If your front end is running a ''SE Linux'' firewall (our front end with a fresh install of Fedora 9 came running this firewall by default) you may have to configure it to allow clients to access your front end's '''TFTP Server''' running through ''xinetd''. The simplest solution is to just tell the ''SE Linux'' firewall to allow any activity over the network connection your front end is using to connect to the back end. Our front end machine is set up with two network cards and configured so that <code>eth0</code> is our network connection to the outside world and <code>eth1</code> is our connection to our back end. To tell the firewall to accept all activity over our network connection with the backend we used the command <code> iptables -I INPUT -i eth1 -j ACCEPT</code>. If you do not want to run this command every time you restart your machine you can add the line to the <code> /etc/rc.local </code> file. This will automatically run that command every time the system boots up. '''NOTE:''' this could be very dangerous because the connection between your front end and back end is now '''insecure'''. This should only be done if you trust all possible users of the backend because they now have unchecked access to your frontend machine.
-Also, you may need to configure your frontend's IP address. If you are using a DHCP server for your frontend machine you can simply execute <code> ifconfig eth0 -auto </code> on your backend's CFE prompt to obtain an IP for your backend automatically. However, most likely this is not the case and you will have to make sure that the network connection that your front end machine is using to communicate with the backend is configured with a static IP address in the 192.168.1.[2-255] range because your backend router will have a default IP address of 192.168.1.1 when it reboots. If it is the case that the IP address of your frontend machine's network connection with the backend is set outside of this range, then click [[HOWTO:Change your Frontend's IP Address | here]] for a quick tutorial on changing the IP address of your network connection.
+Also, you may need to configure your frontend's IP address. If you are using a DHCP server for your frontend machine you can simply execute <code> ifconfig eth0 -auto </code> on your backend's CFE prompt to obtain an IP for your backend automatically. However, most likely this is not the case and you will have to make sure that the network connection that your front end machine is using to communicate with the backend is configured with a static IP address in the 192.168.1.[2-255] range because your backend router will have a default IP address of 192.168.1.1 when it reboots. If it is the case that the IP address of your frontend machine's network connection with the backend is set outside of this range, then check out our quick tutorial for [[HOWTO:Change your Frontend's IP Address |changing the IP address]] of your network connection.
 The last step before actually trying to boot your backend with a XINU image, is to copy the actual <code>xinu.boot</code> file to the ''tftp server directory''. This is the directory that the <code> /etc/xinetd.d/tftp </code> file's <code> server_args </code> variable points to. In our example we used the directory <code> /tftpboot</code>. This is the directory where you need to copy the <code> xinu.boot </code> file. This is easily done by using a command like <code> cp xinu.boot /tftpboot/xinu.boot</code>, assuming that your current working directory contains the <code> xinu.boot </code> file and that <code> /tftpboot </code> is your ''tftp server directory''.

@@ Line 148: / Line 148: @@
 If you are going to use our approach you may need to create a <code> /tftpboot </code> directory. To do this execute the following command: <code> mkdir /tftpboot </code>. Anytime you make changes to the <code> /etc/xinetd.d/tftp </code> file you will need to restart your ''xinetd'' daemon again with the command <code> service xinetd restart </code>.
-There are a couple other configurations that you may need to set up in order to get your '''TFTP Server''' running. If your front end is running a ''SE Linux'' firewall (our front end with a fresh install of Fedora 9 came running this firewall by default) you may have to configure it to allow clients to access your front end's '''TFTP Server''' running through ''xinetd''. The simplest solution is to just tell the ''SE Linux'' firewall to allow any activity over the network connection your front end is using to connect to the back end. Our front end machine is set up with two network cards and configured so that <code>eth0</code> is our network connection to the outside world and <code>eth1</code> is our connection to our back end. To tell the firewall to accept all activity over our network connection with the backend we used the command <code> iptables -I INPUT -i eth1 -j ACCEPT</code>. '''NOTE:''' this could be very dangerous because the connection between your front end and back end is now '''insecure'''. This should only be done if you trust all possible users of the backend because they now have unchecked access to your frontend machine.
+There are a couple other configurations that you may need to set up in order to get your '''TFTP Server''' running. If your front end is running a ''SE Linux'' firewall (our front end with a fresh install of Fedora 9 came running this firewall by default) you may have to configure it to allow clients to access your front end's '''TFTP Server''' running through ''xinetd''. The simplest solution is to just tell the ''SE Linux'' firewall to allow any activity over the network connection your front end is using to connect to the back end. Our front end machine is set up with two network cards and configured so that <code>eth0</code> is our network connection to the outside world and <code>eth1</code> is our connection to our back end. To tell the firewall to accept all activity over our network connection with the backend we used the command <code> iptables -I INPUT -i eth1 -j ACCEPT</code>. If you do not want to run this command every time you restart your machine you can add the line to the <code> /etc/rc.local </code> file. This will automatically run that command every time the system boots up. '''NOTE:''' this could be very dangerous because the connection between your front end and back end is now '''insecure'''. This should only be done if you trust all possible users of the backend because they now have unchecked access to your frontend machine.
 Also, you may need to configure your frontend's IP address. If you are using a DHCP server for your frontend machine you can simply execute <code> ifconfig eth0 -auto </code> on your backend's CFE prompt to obtain an IP for your backend automatically. However, most likely this is not the case and you will have to make sure that the network connection that your front end machine is using to communicate with the backend is configured with a static IP address in the 192.168.1.[2-255] range because your backend router will have a default IP address of 192.168.1.1 when it reboots. If it is the case that the IP address of your frontend machine's network connection with the backend is set outside of this range, then click [[HOWTO:Change your Frontend's IP Address | here]] for a quick tutorial on changing the IP address of your network connection.

@@ Line 208: / Line 208: @@
   xsh$
-Congratulations, You now have a working backend running XINU! You can now make changes to the XINU code, recompile it using the <code> make </code> command to get a new <code> xinu.boot </code> image, copy that file into the <code> /tftpboot </code> directory (or whatever directory your '''TFTP Server''' uses to share files), and use the same <code> boot -elf [host ip]:xinu.boot </code> command to run your very own, modified version of the XINU operating system.
+Congratulations, You now have a working backend running XINU! You can now make changes to the XINU code, recompile it using the <code> make </code> command to get a new <code> xinu.boot </code> image, copy that file into the ''tftp server directory'', and use the same <code> boot -elf [host ip]:xinu.boot </code> command to run your very own, modified version of the XINU operating system.
 ==  What to do next? ==

← Older revision	Revision as of 03:25, 19 December 2008
(No difference)

@@ Line 202: / Line 202: @@
 Now that you have successfully booted and ran XINU on your backend router, you might want to try to [[HOWTO:Build_Backend_Pool|build a pool of backends]] to allow multiple users to each run their own version of XINU on a different backend.
-For more information on the XINU operating system check out the Embedded XINU wiki [http://mulug.mscs.mu.edu/xinu/].
+For more information on the XINU operating system check out the [[Main Page|Embedded XINU wiki]].
 <hr/>
 ''This work is supported in part by NSF grant DUE-CCLI-0737476.''

@@ Line 30: / Line 30: @@
 Transaction Summary
-==  What to do next? ==
+=============================================================================
+Install      1 Package(s)
-Now that you have successfully booted and ran XINU on your backend router, you might want to try to [[HOWTO:Build_Backend_Pool|build a pool of backends]] to allow multiple users to each run their own version of XINU on a different backend.
+Update       0 Package(s)
+Remove       0 Package(s)
-<hr/>
+Installed: tftp-server.i386 0:0.48-6.fc9
-''This work is supported in part by NSF grant DUE-CCLI-0737476.''
+Complete!
 === Configuring the TFTP Server ===
@@ Line 183: / Line 193: @@
 Now that you have successfully booted and ran XINU on your backend router, you might want to try to [[HOWTO:Build_Backend_Pool|build a pool of backends]] to allow multiple users to each run their own version of XINU on a different backend.
-For more information on the XINU operating system check out the [[Main Page|Embedded XINU wiki]].
+For more information on the XINU operating system check out the Embedded XINU wiki [http://mulug.mscs.mu.edu/xinu/].
 <hr/>
 ''This work is supported in part by NSF grant DUE-CCLI-0737476.''