LRP2 FAQ - Frequently asked questions Linux Router Project 2 - Materhorn by DREAMWVR.COM dreamwvr@dreamwvr.com This document is a list of Frequently Asked Questions (with the hopefully correct answers) about the Materhorn. 1. Meta-questions 1.1 Where do I get this document? 1.2 Where do I send questions, corrections etc. about this document? 2. MATERHORN Basics 2.1 What is the Linux Router Project Materhorn? 2.2 Why should I use the Materhorn? 2.3 What do i need to do to prepare myself for using Materhorn? 2.4 Can you explain the basic unix commands that i should know? 2.5 How does the Materhorn work? 2.6 Where do i need prior to beginning in order to do the Materhorn? 2.7 What packages do i need next for the Materhorn? 2.8 How do i access the console at bootup? 2.9 What do i enter as my password on my first login to Materhorn? 2.10 How do i check to make certain that my network interfaces have been recognized? 2.11 How do i check to make certain my routing is correct as i understand 'route' not 'ip'? 2.12 What are the *.lrp files that i will need to use for a basic static ip install? 2.13 Which *.lrp files are required for dynamic ip usage? 2.14 How do i alert myself to the fact that my ports are being scanned and block this activity selectively? 2.15 What file do i edit to determine what *.lrp files are loaded at bootup? 2.16 What else do i need to do to prepare for Materhorn with vi? 3. Obtaining and installing Materhorn 3.1 What is the latest version of Materhorn? 3.2 May I legally use Materhorn? 3.3 What about commercial use of Materhorn? 3.4 Where can I obtain Materhorn? 3.5 How do I install the Materhorn? 3.6 Where do I get help? 3.7 Are there any versions for other operating systems than Linux? 4. Materhorn advanced Usage 4.1 How does one add Materhorn to Disk-On-Chip Devices? 4.2 What is the proceedure to add Materhorn so it does traffic equalization? 4.3 How does one add a LS120 for Materhorn? 4.4 How does one add ssh and sshd and generate the keys on Materhorn? 4.5 How does one setup wavlan devices on Materhorn? 4.6 How do i create my own *.lrp files for use on the Materhorn? 5. Problems 5.1 Are there any known problems with the Materhorn? 5.2 Does using ip masquerading cause problems and if so with what services? 6. Miscellaneous 6.1 What known versions are there of the LRP? 6.2 How widespread is use of the LRP and Materhorn? 6.4 Credits 1. Linux Router Project 2 - Materhorn Meta-questions Contents of this section 1.1 Where do I get this document? The latest version of this document is available from http://www.dreamwvr.com/lrp2-info/lrp2-faq.html . It can also be posted, on a regular basis, to the Usenet newsgroups comp.editors, comp.unix.admin, comp.answers, comp.unix.questions, comp.unix, and news.answers. This version can be, and will be available from http://www.dreamwvr.com/lrp2-info/lrp2-faq and from http://www.dreamwvr.com/lrp2-info/lrp2-faq.faq . Also of interest is the DREAMWVR.COM home plate which contains several other FAQs, at http://www.dreamwvr.com/webframe.htm . 1.2 Where do I send questions, corrections etc. about this document? Please send them to the maintainer, dreamwvr@dreamwvr.com 2. Linux Router Project 2 - Materhorn basics Contents of this section 2.1 What is the Linux Router Project Materhorn? The Linux Router Project - Materhorn is a small signature (floppy based) distribution of linux suitable for creating a firewall or router. It's origin can be traced to the original LRP that is based on the 2.036 kernel whereas Materhorn is based on the 2.2.13 kernel. It has proven itself to be very reliable, robust, and extremely fast since it runs exclusively in ramdisk. It has been known to put many so called 'Commercial' products to shame in both areas of versatility as well as security. Ever noticed how the commercial routers as well as firewall vendors often add secure access management as a afterthought. Then they tend to use proprietary, obfuscated methodologies designed it seems more to confuse? Materhorn leverages recognized secure access methods that have been 'publically' and widely scrutinized. It requires little in the way of hardware since it is know to run reasonable well from the author's experience in less that 7.5 Meg of ram. Whereas for serious use any x86 computer with 16 Meg is more than adequate. So breath new life into your old 486, Pentium I or II and work more securely on the big I. 2.2 Why should I use the Materhorn? If you are looking for a cost effective solution to interfacing quite securely to the Internet then Materhorn is the way to go. It provides thru masquerading the ability to merge many to one. What does that mean? Say you have a network with a single ip either statically assigned or dynamically assigned Internet routable address then you now have with the LRP2 the ability to have many computers access the internet simultaneously if desired. You might also have the need for a straight router to separate your networks in your organization routing packets as required from source to destination. Well then LRP2 is a good choice that won't break your budget and allows for firewalling as well between networks if you so choose. The logic being the LRP2 provides a very flexible means of routing and/or firewalling your internal systems. Since the contents are saved to a floppy and the system runs entirely solid state in ram it is very secure. (Simply once you have configured exactly as you intend LRP2 to operate you need only set the floppy's read only tab and your set.) Even if the system fails or is altered you would simply reboot to restore Materhorn to your customized state of consciousness although if altered you definately need to research much further. ;-)) From DS1 WAN Router, RAS, to Wireless T1 bridge it can be done with the Materhorn.(Although most will leverage as a ethernet router of the 10/100 variety.) One of the more exotic uses are as superfast mini-webservers using thttp so it really depends on your specific needs. 2.3 What do i need to do to prepare myself for using Materhorn? Materhorn requires that one get up to speed on: Understanding of the basics of ip networking and hardware integration... Reasonable understanding of the linux boot process and interpreting device messages to console. Some baseline understanding of how unix shells work and how they can be manipulated via scripts. knowledge on routing basics as well as basic tools such as `ping` which will be your friend. Willingness to learn some basic key unix commands the benefits to be learned at a later `date`;-)) Remember that every adventure begins with a first step and you will be fine as i plan to take you there with this FAQ or cry trying.. 2.4 Can you explain the basic unix commands that i should know? Here are the basic commands you should know for this FAQ: cd <- This command changes your directory ls <- This command lists the contents of your working directory exit <- This will exit you from your current terminal back to the login prompt insmod <- This install a module for you if required lsmod <- This will list the currently installed modules on the Materhorn more <- This is often used to print to standard out a files contents The above illustrates just how few commands are required to get up and running. any other commands you might need will be addressed as the need arises. 2.5 How does the Materhorn work? You ask all the good questions.. Well in a attempt to encapsulate better explanations here goes.. 1a - First the boot sector program "LDLINUX.SYS" in the root directory of your floppy is executed 1b - This is indicated by the echo to your console of "SYSLINUX 1.48 2004-09-26 by Peter Alvin" It is important to note that the syslinux program produces the above boot loader (LDLINUX.SYS) that makes your floppy bootable. ldlinux.sys also provides the intelligence to initialize the boot time ramdisk that follows. 2a- The boot manager reads the syslinux.cfg file and determines that you have indicated you wish it to create a ramdisk for the file called 'root.lrp' by the statement 'initrd=root.lrp'. 2b - root.lrp is searched for in the root directory of the floppy and if there is inserted into the newly created ramdisk on your Materhorn system. This lrp file contains the base of your linux filesystem that the rest of the lrp files will depend upon. It includes /, /bin, /lib, /opt, /root, /sbin, /usr, /var and all they contain which now is deposited onto the ramdisk initiated by ldlinux.sys 3 - Then ldlinux.sys again goes to work this time determining whether it should display a boot message before it sends you a prompt. It does this by reading the 'syslinux.cfg' file and scanning the statement 'display=syslinux.dpy' which is then displayed. This banner besides being good reading also tells you how far exactly you have traveled in the boot process. 4- At this stage in the game you will be signaled by the console that it is now "Loading linux...". Then the kernel as indicated is uncompressed into ram and the kernel is booted. As the stream of text flies by this is a good sign as it means that your devices are being searched for and recognized or not. Here Materhorn tells you as clearly as it can step by step what it is doing. As you scan what the 'linux' kernel is telling you you will see a line that reads "RAMDISK" you want to pay close attention from this time on. Here we see that root.lrp is located and then expanded into ramdisk. Then at the root filesystem is then mounted as per line "VFS:" this is all good news. Then upon completion of the root.lrp extraction we move onto.. "LINUXRC:" here the 'syslinux.cfg' is leveraged again this time for the additional .lrp files that you wish loaded. For instance it might read 'LRP=etc,log,modules,sshd,dhclient'. This is indicated at your console as "LINUXRC: Installing - etc log modules sshd dhclient - Finished" meaning that these have been recognized and will be installed to use further down in the bootup proceedure. Next we see "INIT:" which is real important as it tells us that the parent process of all processes to follow is running or not at this point we are still booting. Next swap space is activated and our modules that we had configured are installed onto our system. Here we want to pay particular attention to the fact that we see our network card modules are loaded as well as the other masquerading modules we might want to have. Continuing the kernel brings up our network cards ready for business as well as activates our firewalling rules. Note that we setup our firewall rules before we actually allow any real transmission to occur in any direction from our network cards. At this point we establish all our system specific values, start our system daemons, and master daemon (inetd). Then we proceed to start our dhclient if we are using dhcp for our external interface. This establishes as well our default route for packets that the system does not know where to send locally. Then our firewall turns on forwarding so that we can transmit and receive hopefully selectively packets from the big I. 5- Having completed a successful boot we now ask the kernel to have mgetty provides us with a login prompt via way of the 'login' program which it does. At this point our happy owner of the Materhorn would simply enter 'root' as the username prompt and their password at the 'password:' prompt. 2.6 Where do i need prior to beginning in order to do the Materhorn? First you need to obtain the various bundled packages and tools that will take you there. To begin the adventure first obtain NASM which is the Netwide Assembler that Syslinux has a dependency on during the build process. Get the latest version and build it. It is very portable and modular which assists on the why for how come. Next you need to grab the source for Syslinux which can be located at Syslinux-1.48 There are lots more locations for Peter's versatile program which has been released GPL. So if you don't like to build tars there are also .deb kicking around on many sites out here. Now onto the fun stuff we need to decide whether we are going to be doing this for a dynamic Internet routable ip or a static ip assigned by ARIN or whatever. Think about that last sentence and lets move on. 2.7 What packages do i need next for the Materhorn? 2.8 How do i access from the console at bootup? Just type at the login: prompt 'root' this will get you to the lrp config manager. 2.9 What do i enter as my password on my first login to Materhorn? Simply hit enter but not too hard as you might damage your 'Enter' key. Note that the default password is blank so you will need to change this immediately to something much harder to guess;-)) 2.10 How do i check to make certain that my network interfaces have been recognized? Since Materhorn uses new 'ip' command rather than 'ifconfig' and 'route' you need to first get to the command prompt for root. you do this by entering 'q' for quit till you drop down to the '#' prompt this the the command shell prompt for entering any commands directly to the operating system. do a: #ip addr show You will see the following for example: 1: lo: mtu 3924 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope global lo 2: brg0: mtu 1500 qdisk noop link/ether aa:bb:cc:dd:ee:ff brd ff:ff:ff:ff:ff:ff 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 link/ether bb:cc:dd:ee:ff:gg brd ff:ff:ff:ff:ff:ff inet aaa.bbb.ccc.ddd/24 brd 255.255.255.255 scope global eth0 3: eth1: mtu 1500 qdisc pfifo_fast qlen 100 link/ether cc:dd:ee:ff:gg:hh brd ff:ff:ff:ff:ff:ff inet aaa.bbb.ccc.ddd/8 brd aaa.255.255.255 scope global eth1 You should see a reply from your system pretty much like the above with the exception that 'eth0' and 'eth1' will contain specifically your MAC address information as well as you current unedited ip address information. You will not really need to change 'eth1' to have a working router but most definately will need to change 'eth0' to reflect either your static ip address or the dynamic ip address. The important thing is that your system has assigned some sort of ip addresses for you for 'lo', 'eth0', and 'eth1'. Notice in the above example that all your interfaces are 'UP' this is the same as you would see with 'ifconfig' if your hardware is recognized and the network cards are up ready to do business. Later in the HOWTO i will describe howto configure for both dynamic and static address assignments but in the meantime lets move forward. 2.11 How do i check to make certain my routing is correct as i understand 'route' not 'ip'? This is again a new technology transition from the traditional 'route' to 'ip' equivalent. in order to check for your routes to your various networks and 'really important' default route your need to do a: #ip route show This indicates what your network interfaces know to be true. For instance: aaa.bbb.ccc.0/24 dev eth0 proto kernel scope link src aaa.bbb.ccc.ddd aax.bbx.ccx.0/24 dev eth2 proto kernel scope link src aax.bbx.ccx.ddx default via aaa.bbb.ccc.ddd dev eth0 The above example would indicate that aaa.bbb.ccc.ddd is your default route where all packets that are unsure where else to go and you have not told where to go;-)) go to this network address to be routed further down the line. To test that they are responding simply do for example a ping 10.123.123.123 or what ever numbers are actually indicated above. If your get a reply you know that all is fine so far. Else don't worry too much about it as yet as remember we are still setting up and most likely you have yet to even boot your Materhorn. This information is important to remember though for our later diagnostics. 2.12 What are the *.lrp files that i will need to use for a basic static install? Here they are in a semi-organized fashion. linux <- this is the linux operating system and is required. let me know if you can get the LRP to bootup without it:-)) syslinux.cfg <- this file is what determines all your specific configuration info that Materhorn will use to decide what *.lrp files it should install for you and how they will be configured. Syslinux reads this info as the it manages the bootup process. etc.lrp <- this is the specific configuration files for your system. ie. pretty much everything that configures your devices and your specific connection with the network as well as services provided. log.lrp <- this contains the directory structure and files where your system logs will live. root.lrp <- this is your base filesystem directory structure and specific binaries that are available to you by default. This is where your actual command programs originate. syslinux.dpy <- although optional this is the nice LRP banner that comes up to you on bootup keep as it also works as a measurement to tell you how far specifically you have gotten in the boot process. ldlinux.sys <- this is where the Syslinux boot manager lives and must exist in order to boot conventionally the Materhorn or the original LRP. modules.lrp <- this contains the modules that you will be having the operating system leverage for your specific needs. For instance ip_masq_ftp.o is required in order to do standard ftp as otherwise the data channel never gets established. Since i am writing this section when my eyes feel like their bleeding please inform me of any typos etc. 2.13 Which *.lrp files are required for dynamic ip usage? The one you want to locate is the dclient.lrp as this provides your system with the tools required to make this happen. 2.14 How do i alert myself to the fact that my ports are being scanned and block this activity selectively? Grab psentry.lrp as this is psionics portsentry security program that does this on the fly. It used to called by a different name but i simply can't remember the name anymore:-() 2.15 What file do i edit to determine what *.lrp files are loaded at bootup? The file that 'requires' editing is the file named 'syslinux.cfg' this contains the defaults which you will note is enough for booting up a static LRP. This needs changes for a dyamincally assigned ip. Here is what you do. First you most likely need a text editor so for instance using 'vi' do the following: 1 - change directory to the directory that the file called 'syslinux.cfg' is living. This will be one of the files you pulled off the Internet. The reason i am suggesting your 'cd' there is that this is more straight forward for first time users. 2- Next you want to issue a command of 'vi syslinux.cfg' at the command prompt. 3- The above will take you into the file for editing using 'vi'. Then simply move your cursor to the part that says "LRP=etc,log,modules" this is where you will append the optional *.lrp files. Let do that for dhclient. (Note: that in 2.036 the original one the above variable is "LRP=etc.lrp,log.lrp,modules.lrp" other than that the concept the same) Move the cursor to the end of the 'modules' text and press your 'i' key. This puts you into insert mode so what you want to do here is insert ",dhclient". Save your changes now with a 'w!' (w bang) this command will write your changes to the 'syslinux.cfg' file. Last to exit the vi editor do a 'q' which quits you from your present editing session. That is all there is to it! 2.16 What else do i need to do to prepare for Materhorn with vi? You need to change the settings in 'syslinux.cfg' to reflect the needs of Materhorn which is different than the original LRP. Set it to "ramdisk_size=6184" on the appropiate line. Notice that i did not mention howto use 'vi' this time since i leave this up the second time around to the installer of the Materhorn. 3. Obtaining and installing Materhorn Contents of this section 3.1 What is the latest version of Materhorn? The latest version of kernel used for Materhorn at the time that this howto was written is 2.2.13. 3.2 May I legally run Materhorn? The Materhorn may be used and distributed freely under GNU GPL but for details of any issues related please consult the many authors of the various components who should be considered more definative than this faq if any conflict arises. The main website for Materhorn's email address is: Matthew Grant 3.3 What about commercial use of Materhorn? The Materhorn is freely distributed under GNU General Public License so please give credit where due to its authors, and almost certainly will remain to be so in future. Read 'COPYING' for a copy of GNU GPL. 3.4 Where can I obtain Materhorn? The central site for the distribution of the Materhorn is: http://lrp.plain.co.nz/linux-router/dists/ Some other mirrors may be available please email the author of this document should you become aware of it to append to this list. :')) 3.5 How do I install the Materhorn? First you need to determine what *.lrp packages that you are planning to use for the Materhorn. Note that in this case as in most cases of optimization less is more. This is also required since the number of packages that you can install on Materhorn is dependent on floppy space. I have taken the liberty of providing hyperlinks to the 'required' LRP files that you will need to build a base system from there you can always expand;-}) 1- You need to create a new device in /dev/fd* directly related to the size of floppy you wish to make. This is a recommended size and i can't really comment when you will hit the wall if you go larger. There are limitations that you should be aware of however. Please see Booting Linux with higher density floppy disksThis document describes the why 4 how how very precisely. Anyways lets make a 1.722 Meg floppy device right now with the following command. It is important to mention that the b indicates block device. The 2 indicates the major number in common for all fd* devices in /dev . The 60 reflects a unique number to identify the device with the kernel. #mknod -m660 /dev/fd0u1722 b 2 60 The above command makes a device called fd0u1722 with a major block number of 2 and a minor block number of 60. 2- We now need to use the superformat command that we obtained from the programs described as pre-install of Materhorn requirements. proceed at the command prompt with a: #superformat -s /dev/fd0u1722 This will superformat the floppy disk to a size od 1.722 Meg for your use. You just completed the hardest part of the Materhorn install the rest comes much more quickly. 3- Now grab the lrp packages immediately below. Place them somewhere safe on your hard drive where ever that is;-)) My suggestions is use these as a template and remember.."MAKE COPIES". 3a- We need the linux operating system the brains of this operation. Get linux kernel here and place it in the safe place i mentioned on your hard drive. *REMEMBER: When downloading these files with Netscape you need to hold the key while clicking the hyperlinks to properly download the packages without corruption. With Internet Exploder i can't comment as i never use anything that i can't remove if i want to.. 3b- Next we grab the 'root.lrp' this is a essential package. We grab the root.lrp here . 3c- Followed by the 'modules.lrp' which contains the modules we want and need to run some services and in order to have support for some of the network cards. We grab the modules.lrp here . I feel that is important to mention that i use exclusively 3c509s and 3c905s so i can't comment on other cards. so YMMV 3d- Now grab the 'etc.lrp' package this contains your file structure for the /etc as you would normally expect in linux or other *Nix based systems. You will not actually edit these files manually but will use the "Linux Router Project -- configuration menu"" 3e- It is a nice feature to be able to produce logs and troubleshoot problems with help from the system. This is done with 'log.lrp' so lets grab log.lrp here At this time we have all the lrp packages we need for a base lrp using all static ip addresses. With the exception of the syslinux.cfg and syslinux.dpy which are supplied below.. 3f- If we are going to need to deal with dynamic ip address assignments from our provider we need 'dhclient.lrp' so lets grab dhclient.lrp here as we need this package to deal with this issue. 3g- Now we need to edit 'syslinux.cfg' but first we need to grab syslinux.cfg here as well as syslinux.dpy for our bootup display. The one we need to alter is syslinux.cfg file so we will do this in vi. 3h- Proceed as follows with vi: $cd my-materhorn-file-directory $vi syslinux.cfg # <- the pound sign is how i will indicate my comments while you are in vi # move your cursor to line four which starts with 'append=' goto "ramdisk_size=" and change the numbers to.. # "ramdisk_size=6184" This is done by moving your cursor to the number immediately after the equal sign in # "ramdisk_size=" and enter 'dw' on your keyboard. This removed the number there. Then enter 'i' on your # keyboard and insert the numbers '6184' this is what is required there. Then using arrow key move over to # where the words "LRP=" are and change the string after the "LRP=" to "LRP=etc,log,modules" for a static # Materhorn or "LRP=etc,log,modules,dhclient" for a dynamically assigned based Materhorn. Remember in order # to remove words use a 'dw'. To insert words use a 'i' and to remove characters one at a time use a 'x' # changes are written to file using a key and then the letters 'w!' whereas to quit the vi editor you # need to do a 'q!' which is enough to get you through the day. 3i- Now lets mount the floppy drive so we can pour the packages over to it. do a: $su -l root #mount -tmsdos /dev/fd0u1722 /mnt/floppy #cp $my-materhorn-file-directory/* /mnt/floppy #umount /mnt/floppy 3j- Your now ready to bootup your Materhorn! celebrate watch reruns of 'Matrix' and enjoy a cool one;-)) 3k- boot your LRP floppy and watch the screen as the diagnostic messages swirl by..When you get the 'login:' prompt you need to enter 'root' as your username. Then hit the enter key for your password. Note: Always change this password immediately especially if on a network else you might be in for some surprises. 3l- Before you is a pleasing sight the "Linux Router Project -- configuration menu" you need to enter '1' for 'Network settings' and then '1' again for Network Configuration. This is the key area you should learn to love. Scroll down to the area called 'General Settings' this is where we begin the custom configuration stuff for you. Note that unlike 'vi' this script is edited much like a standard editor the only commands you need know is to write changes and in order to quit this file. Now i will show you how the variables that you need to change by example otherwise you should be able to leave everything else alone. Below is from a working Materhorn so it should work for you as well. # Under General Settings heading VERBOSE=YES MAX_LOOP=10 IPFWDING_KERNEL=FILTER_ON IPALWAYSDEFRAG_KERNEL=YES CONFIG_HOSTNAME=YES CONFIG_HOSTSFILE=YES CONFIG_DNS=YES # Under Interfaces heading - Pay attention here.. IF_AUTO="eth0 eth1" IF_LIST="$IF_AUTO" ALLIF_ACCEPT_REDIRECTS=NO DEF_IP_SPOOF=YES DEF_IP_KRNL_LOGMARTIANS=YES BRG_SWITCH=NO BRG_EXEMPT_PROTOS="" #eth0_IPADDR=aaa.bbb.ccc.ddd #eth0_MASKLEN=24 #eth0_BROADCAST=aaa.bbb.ccc.255 # Note that the last 3 lines if using static need to contain a valid ip address with the pound sign removed #eth0_DEFAULT_GW=aaa.bbb.ccc.ddd # Note the above line is the default gateway that you isp has assigned please check with them..or if dynamically assigned comment out as shown. eth0_IP_SPOOF=YES eth0_IP_KRNL_LOGMARTIANS=YES eth0_IP_SHARED_MEDIA=NO eth0_BRIDGE=NO eth0_PROXY_ARP=NO eth0_FAIRQ=NO eth1_IPADDR=aaa.bbb.ccc.ddd eth1_MASKLEN=24 eth1_BROADCAST=aaa.bbb.ccc.255 eth1_IP_SPOOF=YES eth1_IP_KRNL_LOGMARTIANS=YES eth1_IP_SHARED_MEDIA=NO eth1_PROXY_ARP=NO eth1_FAIRQ=NO # under IP Filter setup heading IPFILTER_SWITCH=firewall SNMP_BLOCK=YES SNMP_MANAGER_IPS="aaa.bbb.ccc.ddd" EXTERN_IF="eth0" # Note Under start of changes by Charles Steinkuehler for DHCP # if you are using static your 'nearly' done if not use settings below.. EXTERN_DHCP=YES IF_DHCP=$EXTERN_IF EXTERN_DYNADDR=NO # Under This is easy...use if you have a static IP EXTERN_IP=0.0.0.0 # above line would for static have a real ip address EXTERN_TCP_PORTS="0/0_ssh" # Under Internal interface INTERN_IF="eth1" INTERN_NET=aaa.bbb.ccc.0/24 INTERN_IP=aaa.bbb.ccc.ddd MASQ_SWITCH=YES # Under Hostname HOSTNAME=myhostname # Under Hosts file HOSTS0="$eth1_IPADDR $HOSTNAME.private.network $HOSTNAME mr rtr" # Under Domain Search Order ... DOMAINS="private.network" DNS0="your-1st-dns-ip-addr" DNS1="your-2nd-dns-ip-addr" # REMEMBER YMMV 3m- now you need to 'save' your settings so do a to write your custom settings to file saying 'y' to writing changes to the file Then do a to quit from editing /etc/network.conf file. 3n-Type a 'q' to quit this screen. You will arrive back at a screen that under the 'b)' you see what is called 'Back-up ramdisk' "do that now!" saving changes to the floppy disk. answer all the prompts and when completed you will have your changes saved. 3o- now reboot your system however you prefer.. with a 'init 6' or a 'reboot' or whatever you decide. 3p- When you have successfully rebooted the Materhorn obtain the '#' prompt and do a 'ip addr show' this command will display exactly what interfaces have been recognized. You should see all your interfaces with the exact ip addresses that are mapped to the actual physical network device. To test that they are up and listening ready to work for you do a 'ping aaa.bbb.ccc.ddd' where the aaa.bbb.ccc.ddd is the actual ip address that you have assigned. This should do it! If you can ping your interfaces then first ping the gateway you provided in the /etc/network.conf and if that works as well try a real address by name out on the Big I. If you get a reply you are ready for action so surf to your hearts content from then on! 3q- REMEMBER TO CHANGE AND SAVE THE CHANGES TO YOUR PASSWORD TO THE FLOPPY AS THE DEFAULT IS BLANK.. you do this with a 'passwd' then follow the prompts. 3.6 Where do I get help? First of all, read the READMEs included and not included but available at the download sites which should answer any questions you have regarding the building of the Materhorn. Then and only then either contact the author of this document (which is probably not the best idea due to this author is receiving 300 - 500 emails daily) or you might try they most likely have heard of the animal ;-) or the author of the Materhorn. It is suggested that if you request assistance please have details of the specific problem. Note exhaust as many possibilities as possible before asking for help and consult the search engines/archives to see if the answer is blowing in the cyberwind... :-) 3.8 Are there any versions for other operating systems than Linux? AFAIK other than linux the only other confirmed version that Materhorn has been ported to is linux :-)) There is really no need now for any others ;-)) 4. Materhorn advanced Usage Contents of this section 4.1 How does one add Materhorn to Disk-On-Chip Devices? 4.2 What is the proceedure to add Materhorn so it does traffic equalization? 4.3 How does one add a LS120 for Materhorn? 4.4 How does one add ssh and sshd and generate the keys on Materhorn? 4.5 How does one setup wavlan devices on Materhorn? 4.6 How do i create my own *.lrp files for use on the Materhorn? 5. Materhorn - Problems Contents of this section 5.1 Are there any known problems with the Materhorn? The most common problem is getting initially setup after that your sailing. Remember to read all the areas of this HOWTO before proceeding full steam ahead. 5.2 Does using ip masquerading cause problems and if so with what services? It can be a issue with some ip based technologies for instance IPSEC can get hooped in some instances. 6. LRP Materhorn - Miscellaneous Contents of this section 6.1 What know versions are there of LRP? There are two versions available with each in my opinion having advantages. The original LRP was based on the 2.0.36 kernel whereas Materhorn is based on the 2.2.13 kernel. 6.2 How widespread is the use of LRP? Hmmm... difficult question to answer. Suffice it to say that since it is open source and therefore distributed very widely it would be safe to say many thousands of happy administrators. 6.3 Credits This one is pretty difficult to answer fully. But some that do come to mind are Dave, Charles, Koon, and Rick. The others will remain anonymous for now ;-) If i have missed someone please let me know! Here is 'some of the sites' that have proved invaluable.. LRP Linux 2.2 Support Project This the the website that started my interest in moving up to the Materhorn. Simple Materhorn LRP Firewall If you are going to be getting your Internet address dynamically then this one is a must see. As well Charles is very helpful on getting one over the humps in the transition from LRP1 to LRP2. Linux Router Project This one is the new mainsite it appears for LRP related issues. Well that should get you started ok .. good luck:-))