porkradish

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: [SOLVED] zeroshell 1 beta 14 USB 1GB ISO problem. #51834
    porkradish
    Member

    Glad I could help!

    in reply to: [SOLVED] zeroshell 1 beta 14 USB 1GB ISO problem. #51832
    porkradish
    Member

    I don’t run captive portal so I’ll give it one more shot then maybe someone else who has done this can jump in.

    If you copy your version of cp_showauth to /Database.
    In the web interface Setup -> Startup/Cron
    Add the following to the post boot script:


    rm -f /root/kerbynet.cgi/template/cp_showauth
    cp /Database/cp_showauth /root/kerbynet.cgi/template/cp_showauth

    make sure the “Enabled” check is set and save it. (check your permissions on the file so they match)

    As long as you have a profile saved and activated it the file should persist and the startup script should replace the built-in with your copy.

    Hope this helps – if not let me know if you answer it – be nice to know if I enable this in the future.

    in reply to: [SOLVED] zeroshell 1 beta 14 USB 1GB ISO problem. #51830
    porkradish
    Member

    I see what you are saying – I think rc.local has executed by the time you are copying over it. Check out the Setup under Startup/Cron tab – you may need to enter your script in the preboot section (although I don’t think /Database is mounted yet) or post boot and see if you can re-cycle the service if necessary.

    The file you look to be after is:
    /root/kerbynet.cgi/template/cp_showauth

    Hope this helps.

    in reply to: [SOLVED] zeroshell 1 beta 14 USB 1GB ISO problem. #51828
    porkradish
    Member

    Zeroshell remembers it’s settings through a “Profile”.

    Use the Setup menu and Profile tab. What you need to do is select a partition and create a new profile. Once it is activated it will keep settings between reboots. You can even save files to /Database and they will persist.

    in reply to: ZeroShell VPN Lan to Lan malfunction #51823
    porkradish
    Member

    As for the NAT – just make sure no interfaces are listed under “NAT Enabled Interfaces” to disable it.

    what does a trace route command look like on the clients that cannot connect to the the 192.168.0.0/24 network.

    so if you are running windows on a computer with an ip address like:

    192.168.2.10 that cannot reach 192.168.0.10 then

    open the run box
    type cmd
    tracert 192.168.0.10

    and see where the traffic stops. Are you sure the client is using 192.168.2.223 as its default gateway?

    in reply to: ZeroShell VPN Lan to Lan malfunction #51820
    porkradish
    Member

    Looks correct as long as you other box reverses it – are you using NAT? If so try disabling it on both boxes and see if it fixes the issue.

    in reply to: ZeroShell VPN Lan to Lan malfunction #51818
    porkradish
    Member

    ZSHLL site 1 eth0 192.168.0.223/24
    eth1 XXX.XXX.XXX.XXX
    VPN 20.20.20.1 Server

    ZSHLL site 2 eth0 192.168.2.223/24
    eth1 YYY.YYY.YYY.YYY
    VPN 20.20.20.2 Client

    The VPN goes up and the routing rules are the following:

    ZSHLL site 1 192.168.2.0/20 20.20.20.2
    ZSHLL site 2 192.168.0.0/20 20.20.20.1

    It might be a typo but 192.168.2.0/20 is using a different subnet then 192.168.2.223/24

    check your routing and see if it is set to /24 not /20.

    the output of your route command would be helpful from both boxes – like:


    root@zs-noc-1 sbin> route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    10.0.0.0 * 255.255.255.0 U 0 0 0 ETH01
    10.0.1.0 * 255.255.255.0 U 0 0 0 BRIDGE00
    192.168.1.0 * 255.255.255.0 U 0 0 0 ETH00
    192.168.44.0 10.0.1.44 255.255.255.0 UG 0 0 0 BRIDGE00
    192.168.250.0 * 255.255.255.0 U 0 0 0 VPN99
    10.10.10.0 10.0.1.4 255.255.255.0 UG 0 0 0 BRIDGE00
    192.168.40.0 10.0.1.4 255.255.255.0 UG 0 0 0 BRIDGE00
    10.1.0.0 10.0.1.12 255.255.0.0 UG 0 0 0 BRIDGE00
    default 192.168.1.1 0.0.0.0 UG 0 0 0 ETH00
    in reply to: How to Use ZeroShell-1.0.beta13-VMWARE in ESXi and vSphere #51482
    porkradish
    Member

    This is helpful but I found another way which may be preferred for some people. Instead of converting the image I downloaded the iso image and uploaded it to the datastore on my ESXi4 server. Then I created a blank VM with a small HDD. In the machine config I pointed the CDROM to the datastore ISO and put a check mark in the “Connect at Power on.” option.

    Boots to the cd everytime and is a quick and dirty way to get running. This does leave the Zeroshell core readonly though so you may have problems if you want to make changes to the installed packages.

    Since I am testing VPN throughput and QoS functions it has been a fast easy way to test drive the distro.

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