These are builds of Raqcop 2.0. This will run on Raq3, Raq4, Qube3 and Raq550 as well as XTR the latter will take some work. Important!! You must be running the cobalt-2.10.3-ext3 rom in order to run Raqcop. If you are used to using Raqcop 1.4.x the difference is that the partition to set is hda1 NOT hda4 for both root and boot. If running raid, set both root and boot to md0 in the rom menu via serial console. A total rom reset on all but the 550 defaults to hda1 as the root and boot partitions. The 550 defaults to md0 so a serial console cable (null modem) is needed to change the boot partition but you will need a null modem cable anyway, read below, the lcd menu in the rom only changes the root partition not /boot. ================================================================================ Important Instructions: You will need a serial console (null modem) cable following boot to setup networking since it's pointless to set up networking on a VM or Donor machine and then try to set up again on the running Cobalt because the mac addresses are stored in both udev and ethernet settings now which is actually a good thing, I have set up the install to skip networking but allow you to set up hostnames, passwords and so forth. This will at least allow you the ability to log in via serial console. Run depmod and then setup to configure your network any way you want. Use this time to change your passwords and hostname and then reboot. You WILL see errors on first boot through the console before depmod and setup, this is normal as you have not configured your network yet. If using the provided images, you may also want to edit /var/ipcop/main/hostname.conf and /var/ipcop/main/settings to reflect your actual host name if they don't already reflect any changes you made in setup, this affects the proxy visible hostname. Reboot after everything is set up, it's the easiest way to start all the services that did not start without a network and your http certs will be generated upon first boot with the network configured. All 2.0.0 images including the cdrom iso image have the upgrade mechanism set up to look to the Raqcop site server for upgrades that are signed by me with a Raqcop unique gpg key. It is also named differently from the standard IPCop in that i486 is replaced with cobalt. These steps will make it very difficult to apply the wrong update in Raqcop and also trying to install a Raqcop update in a standard IPCop PC installation. This means that you will be able to dynamically upgrade to subsequent versions in the web gui itself. ================================================================================ The diff patches between pure IPCop and the corresponding Raqcop builds are in the Raqcop-to-IPcop-diffs folder. The diff does not include the raqcop.gpg public key which is unique to Raqcop. It is available for anyone that for whatever reason wants to build Raqcop themselves, http://raqcop.com/pub/lfs-repo/raqcop.gpg, and goes in the /config/cfgroot/ folder in the build folder. Nothing top secret about the gpg key, the web gui requires it to do updates to ensure they are signed properly and from the right source (here for Raqcop). Anyone can apply an unsigned update by simply extracting the update and running ./install via serial console or ssh but with the ability to download and apply updates via the web gui, it's not worth doing it manually anymore. No, I will not give you my private key and password. Same default passwords and address apply: root: raqcop admin: password backup: backup to log into the web gui: https://x.x.x.x:8443 (192.168.1.1 default) ssh: 8022 proxy: 8080 Dave Studeman Special XTR Notes: This does indeed have the Highpoint driver needed to make an XTR boot, but the first drive bay is /dev/hde NOT hda. Some Symantec Velociraptors models 1300 and so on were XTR units with only one drive bay stuffed. Most owners of the Symantec XTR based units simply add three more drives and install server software like most XTR owners do and NOT use them as a firewall/gateway appliance. They are over two feet deep, have several fans, have four hot swap bays in the front under a hinged cover and came with either an 850mhz or 1ghz PIII processor. If you're going to run a firewall on a 5000 series Cobalt, get a Raq550. The Raq550, is only two inches deeper than a Raq3/4 and comes with either a 1GHZ or 1.266ghz PIII processor and can be quieted down a LOT by replacing the high rpm Delta fans with 5400 rpm models in the same series, the stock ones are LOUD! Both have 64 bit pci-x slots and will run Intel multi port gigabit nics here with no problem. The 550 also has a tool-less lid with spring loaded captive thumbscrews and has the same LCD setup as a 3000 series. The XTR has a tiny lcd which you can barely read even close up and it uses the i2c bus, not parallel like the rest do. Special VMWare Notes: With the newer OS and kernel, the device nodes are not hard coded as they were with 1.4.x and it's 2.4 kernel, with a few exceptions, device nodes only show up as they exist. The file fstab no longer specifies which device nodes / root and /var/log or with a flash install, /var/log_compressed are linked to. This greatly simplifies installing via usb in VMWare as the system will not care what device nodes the installation process used. You can simply plug a usb CF reader in the host machine and boot VMWare from the iso image given here, you do have to make the VM connect the usb though, once you have booted up the iso in VMWare and have begun the install, upon selecting which drive to install to, just choose the CF one and choose Flash install, yes it will show up as /dev/sdx but this will not matter after installation. Once the CF card with the installed os is plugged into your Raq, the device nodes will show up as /dev/hda1 and so forth and will boot normally with no problems at all. You can also do this with a usb to ide bridge and a normal hard drive but 20GB or so will take a while to format and install to with even usb2. Once you have it running on a Raq and have run setup to get the nics right for THAT machine, your mac addresses for THAT machine are now in the network config and udev net rules, make a backup and save to usb stick, be sure to export the key and put it in the usb stick. On the next VMWare install you can plug that in and connect it via usb in VMWare along with your usb to CF or IDE setup and install, use the usb restore after that and it will be exactly right for THAT Raq on first boot and have network access since you have the same mac addresses in the backup and restore process for THAT exact machine, any new machine you move the CF or HD to will have to have setup run again much like you did after a virgin VMWare install to get the nics working. Unlike 1.4.x, you CAN change the green device anytime you want and with a serial console connection you are not at risk of being disconnected while doing so.