| Version Changes Administrator's Manual Links & Resources Product Announcements Howto Guides |
Technical difficulties
or feedback:
webmaster@cequrux.com
SECTION A - HARDWARE & INSTALLATION
You'll need a 386 or better PC, with at least 16 Mb of RAM and at least
500 MB of hard disk space, two network cards (or one network card, a
serial port, and a modem for SLIP/PPP, or one network card, and a sync
comms card) and a VGA card and monitor.
More specific details about what hardware is supported can be found below.
The missing operating system message is usually a case of CEQURUX Firewall/VPN
and DOS or some other OS conflicting over their ideas of disk geometry.
If your controller or BIOS supports cylinder translation (often marked
as `>1GB drive support' or `LBA mode'), try toggling its setting and
reinstalling CEQURUX Firewall/VPN.
CEQURUX Firewall/VPN does not scan for bad blocks on the hard drive before
installing. IDE drives are supposed to come with built-in bad-block
remapping; if you have documentation for your drive, you may want to see
if this feature has been disabled on your drive.
This is usually caused by an interrupt conflict (e.g., two boards
using the same IRQ), or by having the wrong interrupt specified in
the hardware setup.
CEQURUX Firewall/VPN works with both IDE and SCSI hard drives.
CEQURUX Firewall/VPN can also be used with MFM, RLL and ESDI drives,
but this is not recommended.
CEQURUX Firewall/VPN supports the following SCSI controllers:
CEQURUX Firewall/VPN supports SCSI, QIC-02 and QIC-40/80 (Floppy based) tape
drives, including 8-mm (aka Exabyte) and DAT drives.
There is support for the following cards:
There is also support for the Arnet (Digi) Sync/570i ISA, RISCom N2,
WANic 400/405, and Cronyx/Sigma sync cards using synchronous PPP.
If you want a specific recommendation, try getting Genius GE2500III cards -
these are cheap, fast and reliable (NE2000 compatible).
This can be caused by bad hardware (memory, motherboard, etc.). Try
running a memory-testing program on your PC. Note that, even though
every memory testing program you try will report your memory as being
fine, it's possible for slightly marginal memory to pass all memory
tests, yet fail under operating conditions (such as during busmastering
DMA from a disk controller).
As the CEQURUX Firewall/VPN kernel boots, it will probe for the serial ports in
your system for which the kernel was configured. Once it has started up,
log in and run the command:
There are two possibilities. The first is that this IDE drive is one of
extremely few drives that actually doesn't work with CEQURUX Firewall/VPN.
Far more likely is that the drive is the only IDE device on that IDE
interface, and that it is jumpered as a slave. To fix, just rejumper the
drive to be a master. One also shouldn't put a CDROM on the second IDE
interface if there are no devices on the first IDE interface (rather just
use the first).
The gateway program on the firewall performs a 'ping' once at startup to obtain the MAC address of the default router and then caches the result forever. Therefore, if the default router's MAC address changes, you have to run 'zap cdsgw' on the firewall console (as root user) to cure the problem.
Log in to the firewall as root user and edit the file: /usr/local/custom/rc.local
ifconfig fxp0 media 100basetx mediaopt full-duplex
Yes, this is possible.
Possible problems:
This answer applies to version 4.1.x of CEQURUX firewall.
Install the harddrive. If the BIOS doesn't detect the drive, then you shouldn't boot the firewall.
In the BIOS, set the LBA for IDE drives. When the firewall boots, it will assign the new drive a name.
This could be something like 'wd3' or 'sd2'. Once booted and logged in, you can deduce the drive(s) name by running 'dmesg | less'
from the command line. If you are using IDE then look for wd0, wd1, wd2 or something similar. If you are using SCSI then look for sd0, sd1, sd2 or soemthing similar. The following is just an excerpt from the dmesg output.
Proceed with:
[dd if=/dev/zero of=/dev/wd2 bs=512 count=1000] This is to completely erase the partion table and any disklabel that may have existed on the drive prior to the installation.
[fdisk -i wd2] Here you should hit enter for every question, until it asks: "Should we write the new partition table" and to this you should you should answer 'y' and hit enter.
[fdisk wd2] From this command, you should take notes. Record the following data that fdisk returns: 'cylinders', 'heads', 'sectors/track', and 'blks/cyl'.
[disklabel -r -w wd2 minimum] This creates a default disklabel (with entirely wrong data), which we will modify to our needs.
[disklabel -e wd2] You will find yourself inside a vi session. Change the following values in the file:
[newfs wd2e] Nothing to get wrong here, except be sure to append an 'e' to the drive in question.
[mkdir /extra1] If you have more than one drive that you are trying to add, then call them /extra[n] where [n] represents a decimal digit.
IMPORTANT: Be sure to use the designation extra to ensure the preservation of any links that you may have create before such operations as upgrading.
[mount /dev/wd2e /extra1] This should succeed. Type 'df' after that, to confirm that it is mounted, and is the correct size.
Now, to make sure that it mounts after every reboot, append the following line to the file /usr/local/custom/rc.local (if the file doesn't exist, then create it afresh):
During this procedure, ignore error messages on the system console. Do, however, consider them important after you've finished, and have mounted the drive - there should be none.
All non-SCSI interfaces are known to be extremely slow compared to SCSI
drives.
dmesg | grep sio
Here's some example output from the above command:
sio0 at 0x3f8-0x3ff irq 4 on isa
This shows two serial ports. The first is on irq 4, is using port
address 0x3f8, and has a 16550A-type UART chip. The second uses the
same kind of chip but is on irq 3 and is at port address 0x2f8.
Internal modem cards are treated just like serial ports - except that
they always have a modem `attached' to the port.
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
Insert the following lines:
ifconfig fxp1 media 100basetx mediaopt full-duplex
NOTE:
The answer for version 4.3 of the firewall will be added at a later stage.
Example
We can thus see that there are two drives, a Fujitsu 6G and a Seagate 20G. Then run the mount command from the command line to see which of the 'wd' devices are mounted.
Example
From the mount command we can see that wd0(Fujitsu) is mounted. We can therefore deduce that wd2(Seagate) is unmounted
and is the new added drive. For the rest of the answer, we shall use 'wd2'.
Everything in square brackets are the commands that you need to type into the root shell on the firewall.
Note that if you get a single character wrong, you could destroy all your data, so tread gently!
Also make a note of the 'size' value, specified in the third last line.
mount /dev/wd2e /extra1
The easiest way is to upgrade to the latest release of CEQURUX, which will come with the latest kernels.
If you need to manually upgrade a kernel for some reason:
- fetch the appropriate file from ftp://ftp.cequrux.com/pub/kernels/. kernel.256 for example, is for a machine with 256MB of RAM.
- create a temporary directory (say 'jnk') (ie. mkdir /tmp/jnk)
- move the kernel file into your new directory, and call it 'kernel'. (ie. mv kernel.256 /tmp/jnk/kernel)
- run the upgrade_kernel command, supplying it with the temporary directory as a parameter (ie. upgrade_kernel /tmp/jnk)
- lastly, remove your temporary files. (ie. rm -rf /tmp/jnk)
The End.