SysEngBD

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: ‘Modern’ hardware recommendations #52091

    SysEngBD
    Member

    You could take a look at the new Soekris 6501-70 [http://soekris.com/products/net6501.html]. It should be able to handle 100Mbit and be an integrated solution that prevents you from needing to use consumer PC parts. We’ve used Soekris for years and they’re reliable and stable. You could also add in a gigabit dual-Port Intel server adapter for the expansion slot and you’d end up with 6 gigabit ports, dual core CPU, and 2 GB RAM. Which is a lot of power and options for bonding and interconnection.

    You could also look at Soekris’s 5501-70, since they can push around in the range of 50-75Mbits depending on how you’ve got it set up. This will decrease the more packet manipulation you use. (We currently get around 30Mbps sustained out of it but there’s a lot of manipulation happening)

    As a last note, look into hacom.net [http://www.hacom.net/]. They primarily try to bundle with pfSense with it but I’ve seen Zeroshell [and Vyatta] run quite well on the gear. They give you quite a few different options, the VIAs are great and so are the Atom platforms. I tend to stay away from the ones with Realtek NICs because I’ve rarely seen where those NICs didn’t act like garbage…

    in reply to: CF card failures – WARNING. #51678

    SysEngBD
    Member

    @sysengbd wrote:

    @sysengbd wrote:

    mount -t tmpfs -o size=64m,mode=1777,nosuid,nodev,exec tmpfs /tmp
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /var/run
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /var/lock
    mount -t tmpfs -o size=64m,mode=755,nosuid,nodev tmpfs /Database/LOG
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/counters
    mount -t tmpfs -o size=32m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/html

    Should be:

    mount -t tmpfs -o size=64m,mode=1777,nosuid,nodev,exec tmpfs /tmp
    mount -t tmpfs -o size=64m,mode=755,nosuid,nodev tmpfs /Database/LOG
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/counters
    mount -t tmpfs -o size=32m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/html

    /var/lock and /var/run as tmpfs is still untested on my part, the others were, but I haven’t had time to test how those two perform between reboots.

    Cheers,

    mount -t tmpfs -o size=64m,mode=1777,nosuid,nodev,exec tmpfs /tmp
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /var/run
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /var/lock
    mount -t tmpfs -o size=64m,mode=755,nosuid,nodev tmpfs /Database/LOG
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/counters
    mount -t tmpfs -o size=32m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/html

    All these seem to work well between reboots and function as expected. I would think having /var/run /var/lock/ and /tmp as tmpfs would have been a good idea as a matter of course, having logs and MRTG stats on tmpfs is just for serious write cycle saving…

    Thanks again for the warning KLGIT. I had assumed CF saving features had been included in Zeroshell since it is a distro aimed at embedded machines.

    Cheers,

    in reply to: CF card failures – WARNING. #51677

    SysEngBD
    Member

    @sysengbd wrote:

    mount -t tmpfs -o size=64m,mode=1777,nosuid,nodev,exec tmpfs /tmp
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /var/run
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /var/lock
    mount -t tmpfs -o size=64m,mode=755,nosuid,nodev tmpfs /Database/LOG
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/counters
    mount -t tmpfs -o size=32m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/html

    Should be:

    mount -t tmpfs -o size=64m,mode=1777,nosuid,nodev,exec tmpfs /tmp
    mount -t tmpfs -o size=64m,mode=755,nosuid,nodev tmpfs /Database/LOG
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/counters
    mount -t tmpfs -o size=32m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/html

    /var/lock and /var/run as tmpfs is still untested on my part, the others were, but I haven’t had time to test how those two perform between reboots.

    Cheers,

    in reply to: CF card failures – WARNING. #51676

    SysEngBD
    Member

    Thanks for the replies. I have backups of the profiles and images of the CFs on our files servers. The routers are both at remote locations that I won’t be able to access for a few months so I’ve dropped these lines in my PreBoot scripts trying to minimize CF writes, the tradeoff being that I’ll also lose logs and MRTG stats between power cycles.

    mount -t tmpfs -o size=64m,mode=1777,nosuid,nodev,exec tmpfs /tmp
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /var/run
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /var/lock
    mount -t tmpfs -o size=64m,mode=755,nosuid,nodev tmpfs /Database/LOG
    mount -t tmpfs -o size=16m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/counters
    mount -t tmpfs -o size=32m,mode=755,nosuid,nodev tmpfs /Database/var/register/system/mrtg/html

    I’m fairly certain this should buy me some time until I can access the units.

    Cheers,

    in reply to: CF card failures – WARNING. #51673

    SysEngBD
    Member

    Did you happen to have a SanDisk Ultra CF fail?

    When I bought our Soekris boxes I opted to get everything from them (Soekris) and the CF they sell is SanDisk Ultra. Both of the routers have been in production for 10 months so I’m wandering if I should get worried…

    (I’ve got an ALIX running ZS as well but it has a Transcend Industrial CF)

    Cheers,

    in reply to: dns problem #51531

    SysEngBD
    Member

    My guess is that you may have a connectivity issue with that DNS server (or in general).

    If the client is set up as such:
    IP: 192.168.2.2
    DNS: 1.2.3.4
    Default Gateway: 192.168.2.1 (Zeroshell internal)

    The Zeroshell box should have a route to 1.2.3.4 (if say the DNS server is internal) or a default gateway of its own set up (if the DNS server is external plus this is beneficial if you’re intending on internet access).

    Some examples:

    If the DNS Server – 1.2.3.4 is an external DNS server the process would go something like this:

    1) Client sees that it needs to resolve an address, checks the DNS server address in its settings, notices the DNS server isn’t on its subnet (not local to it), and sends the request to its default gateway (the Zeroshell box).

    2)The Zeroshell box would then look up the route to 1.2.3.4, seeing as that is not a local address to the Zeroshell box it’ll send it out through it’s default gateway.

    3) Beyond this a similar process (route lookup and forwarding) occurs until the DNS server is contacted and the reply comes back to the client

    If the DNS server is internal you’d want to make sure Zeroshell knows how to get there i.e.:

    1) If the DNS server is attached to Zeroshell then Zeroshell should have and interface in the same subnet that is attached to the DNS server (like 1.2.3.50 in your example although you refer to this as the external interface). In that case a route is automatically added since it is connected and local to Zeroshell.

    2) If the DNS server is attached elsewhere, Zeroshell will need a route to that network in its routing table (found under “Router” to the left of the GUI)

    Hope this is helpful. If the DNS server is external (on the internet) make sure you’ve set up a Default Gateway for Zeroshell and that is connected to a live internet connection. Also, I’d ensure the internet connection interface has NAT on it (Also under “Router” on the left menu).

    Cheers

    in reply to: dns problem #51529

    SysEngBD
    Member

    You can set up the DNS forwarder:

    Click “DNS” on the Left the “Forwarders” at the top.

    Plug in domain and server pairs.

    I use the domain ANY and OpenDNS servers at 208.67.222.222 and 208.67.220.220 but you can use whatever you want. This will tell Zeroshell which DNS servers to use. And if you set up DHCP and your clients are pointing to your Zeroshell box then they’ll use Zeroshell for DNS which will in turn use what you specify here.

    Cheers

    in reply to: Upgrade from ZS 0.1b13 to 0.1b14 #51507

    SysEngBD
    Member

    Thanks for this!

    I upgraded a VM, an ALIX and two Soekris machines using this script with no issues.

    Cheers

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