on

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: What driver to use with VMware #52510

    on
    Member

    The SCSI controller on the virtual machine should be defined as LSI Logic SAS and not as the default LSI Logic Parallel.

    in reply to: Captive Portal survey #51984

    on
    Member

    Hi,

    1) In what context do you use the Captive Portal of Zeroshell?

    To authenticate our users before they access Internet. We are a Computer Science department, Master and Doctoral level. User database is on an external LDAP server.

    2) What are the hardware (CPU, RAM and disk) do you use?

    Dell PowerEdge R200
    CPU: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz 2400MHz
    RAM: 4GB
    Disk: 2×146 GB SAS in RAID 1

    3) What release of Zeroshell do you use?

    1.0.beta14 so far. I am afraid my customizations (patches that are automatically applied at start-up) will break if I upgrade.

    4) Did you enable the protection against DoS (Denial of Service)? if the answer is yes, please specify the protection level (Low, Medium or High).

    I think no, because I cannot find this option 🙂

    5) What is the total number of users that you manage with the captive Portal?

    200 to 250

    6) What was the peak of concurrent users connected?

    60

    7) At the peak of concurrent users connected, did you notice unacceptable delays in the captive portal authentication?

    Never

    Thank you,

    Olivier

    in reply to: Additional comment field on firewall rules #48213

    on
    Member

    @atroposx wrote:

    I agree to add comments-capability. Makes sense when having hundreds to thousands of rules. It’s one thing to be the only admin, but another to have multiples and everyone having their hands on changes and no comments on the rules.

    In fact, the ability to put comments exists in the options:

    -m comment — comment

    But it is tedious to type, and because it cannot have space, you need to be careful.

    So basically, it is only an input string that will be coded as /* comment */ in the rule.

    Best regards,

    Olivier

    in reply to: Dell R210 Devices #51848

    on
    Member

    Carlos,

    See my two posts at http://www.zeroshell.net/eng/forum/viewtopic.php?t=2972&highlight=dell

    There is an issue in Dell with SAS/SATA cdrom (cdrom plugs to a connector labeled SATA, but still shows as SAS…)

    Olivier

    in reply to: Additional comment field on firewall rules #48211

    on
    Member

    @aileron wrote:

    Hi!

    My list of firewall rules is getting more and more complex. After some time I can’t remember why I had added a particular rule. Therefore, it would make sense to be able to add a short description to each rule so that one can keep track of why rules were added.

    Anyway, thx to Fulvio for his work on that great project!

    Hi,

    I totally support that idea, I have nearly 1000 lines in my ipfilter config, I would be dead without comments.

    I also totally agree on the compliment 🙂

    Olivier

    in reply to: ZeroShell and Dell #51781

    on
    Member

    Hi,

    My box for ZeroShell is a Dell R200, with RAID controller SAS6, using MPT driver. Disks are configured in RAID 1 (mirror).

    ZeroShell cannot install out of the box; here are the steps I had to perform before I could get it running. As usual, this comes with no guaranty, all I can say is that it worked for me.

    1) I prepared a USB key as described in http://www.zeroshell.net/eng/forum/viewtopic.php?t=2971

    2) I also got ps_initrd.sh script (http://www.nigilist.ru/nit/ps_initrd.sh/)

    3) I boot ZeroShell from the USB key. At this stage the USB is seen as drive /dev/sda and the hard disk as /dev/sdb

    4) I partitionned my hard disk; size if up to your tastes, my partitions look like:

    root@cs root> fdisk -l

    Disk /dev/sda: 145.9 GB, 145999527936 bytes
    255 heads, 63 sectors/track, 17750 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/sda1 1 1306 10485760 83 Linux
    Partition 1 does not end on cylinder boundary.
    /dev/sda2 1306 7833 52428800 83 Linux
    Partition 2 does not end on cylinder boundary.
    /dev/sda3 7833 17751 79662080 83 Linux
    Partition 3 does not end on cylinder boundary.

    5) I made the file systems on the 3 partitions of the hard disk:

    mkfs.ext2 -I 128 /dev/sdb1
    mkfs.ext2 /dev/sdb2
    mkfs.ext2 /dev/sdb3

    Note the -I for the first partition, this is important for grub in a future step.

    6) I copied the contents of the USB key to the hard disk:

    mount /dev/sdb1 /mnt
    cd /boot
    tar cf - --one-file-system . | (cd /mnt; tar xfBp -)
    umount /mnt
    mount /dev/sdb2 /mnt
    cd /cdrom
    tar cf - --one-file-system . | (cd /mnt; tar xfBp -)
    umount /mnt
    mount /dev/sdb3 /mnt
    cd /DB
    tar cf - --one-file-system . | (cd /mnt; tar xfBp -)
    umount /mnt

    7) I installed grub to run from the hard disk:

    mkdir /mnt/boot
    mount /dev/sdb1 /mnt/boot
    grub-install --recheck --no-floppy --root-directory=/mnt /dev/sdb
    umount /mnt/boot

    8) I copied the kernel modules needed by RAID:

    mount /dev/sdb1 /mnt
    cd /mnt
    ps_initrd.sh initrd.gz open
    cd initrd.gz-image
    cd lib
    mkdir mpt
    cd mpt
    mkdir deps chipsets
    cd deps
    cp /cdrom/modules/2.6.25.20/kernel/drivers/message/fusion/mptbase.ko .
    cp /cdrom/modules/2.6.25.20/kernel/drivers/message/fusion/mptscsih.ko .
    cp /cdrom/modules/2.6.25.20/kernel/drivers/scsi/scsi_transport_sas.ko .
    cd ../chipsets
    cp /cdrom/modules/2.6.25.20/kernel/drivers/message/fusion/mptbase.ko .
    cp /mnt/initrd.gz-image

    9) I edited /mnt/initrd.gz-image/linuxrc to load the modules:

      for M in  /lib/usb/deps/* /lib/sata/deps/* ; do
    /sbin/insmod $M 2>/dev/null
    done

    # load mpt RAID dependencies in right order
    /sbin/insmod /lib/mpt/deps/scsi_transport_sas.ko
    /sbin/insmod /lib/mpt/deps/mptbase.ko
    /sbin/insmod /lib/mpt/deps/mptscsih.ko

    for M in /lib/usb/host/* /lib/sata/chipsets/* /lib/mpt/chipsets/* ; do
    /sbin/insmod $M 2>/dev/null
    done

    Note that there is a modification in the second for loop.
    I also changed so that the first partition is mounted read-write. I change the line:

    echo "/dev/${CDROM}1 /boot ext2 ro 1 2" >> /cdrom/etc/fstab

    to be:

    echo "/dev/${CDROM}1 /boot ext2 defaults 1 2" >> /cdrom/etc/fstab

    11) I closed /mnt/initrd.gz:

    cd /mnt
    ps_initrd.sh initrd.gz close
    cd /
    umount /mnt

    12) From the it should boot from the hard disk.

    in reply to: Captive protal not working #51769

    on
    Member

    @giancagianca wrote:

    You must assign ip to brigde to run captive portal.

    Bye.

    Thanks, I found out the hard way 🙂

    in reply to: Captive protal not working #51768

    on
    Member

    Thanks, in fact I am one step further.

    The bridge DO NEED an IP address to display the authentication page. So I am there now.

    I have to find how to authenticate to my existing Radius.

    Olivier

Viewing 8 posts - 1 through 8 (of 8 total)