Forum Replies Created

@janice,
the boot screen shows the various boot kernels and you choose to boot from the one you prefer.
Once running, you may tell Zeroshell the default kernel to use (menu SETUP, button BOOT, dropdown list BOOTIMAGE)

I believe this is not implemented, as stated on the manual.
Probably a forgotten part of this project.
Would be nice to have it done. Would allow me to use the integrated captive portal of ZS. Mobile devices nowadays hunt so much for bandwidth that this is a very important feature to enable.

Connection Limits
For each class of accounting is possible to define an upper limit in Megabytes for the traffic generated and the maximum number of hours or fractions of hours for which the user can remain connected. When the user exceeds at least one of the two limits is automatically disconnected and no longer allowed to connect until the counters are not reset. Note that the bandwidth limit in Megabytes per second has not yet been implemented in the current version of Zeroshell (1.0.beta16).

I just tried with with v3.8.2 and it is not limiting.

Kudos to Fulvio for putting this project together by the way, I keep coming back to ZS after trying other solutions.

Today I need Zeroshell to connect to a VPS PPTP server.
The idea is that other clients dial into the same VPS PPTP server, and reach the Zeroshell LAN network for some remote work needed on a weekly basis.

I do not see this ZS_as_PPTP_Client option integrated into Zeroshelll 3.8.1
I am going to attempt to use the Beta proposed in this thread and I hope it works. I will keep you all posted.

If anyone has a better fix today, I would appreciate some feedback.
Thanks.

Well… since yesterday, it started misbehaving again. I am downgrading.
I have OpenVPN tunnels between 4 sites, maybe the restarts have to do with unstable VPN links, it is the only abnormality I see with this particular Zeroshell vm.

I will downgrade back to v3.7.1 and cross fingers. Maybe in the meantime, I will restore an existing vm backup and continue checking why this is happening.

LOG
02:55:34 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
03:51:03 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
04:27:49 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
04:55:19 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
05:01:27 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
05:25:05 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
05:33:14 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
06:21:04 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
06:38:06 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
07:31:59 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
07:50:42 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
08:07:18 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
09:05:51 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
09:11:56 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
10:02:17 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
10:22:16 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
12:29:08 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
12:32:36 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
13:25:35 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
13:43:59 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
15:04:20 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0

I keep getting random reboots on my ZS, running on Proxmox host.
version 3.8 keeps rebooting randomly.
I have tried clean installs, and also upgrades.
The results are the same.
Everytime I go back to v3.7.1, it works again fine.

Admin logs show the reboots follow no time_related pattern:
00:14:24 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
01:07:01 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
04:27:08 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
06:16:46 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
12:20:54 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
12:48:09 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
12:57:58 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
15:40:36 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
16:41:11 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
17:47:12 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
20:02:51 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
20:32:51 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0

I cannot see a reason for reboot.
Proxmox vm running the zeroshell does not report error either, it shows it’s up all the time.

Do you recommend anywhere else to check?
My workaround is to go back to v3.7.1, but might not be a safe choice.

***EDITED Mar 16th 2017, to help with Dropbox new Public folder changes***
Now images displayed as links, not embedded, till I find out how to do it with the new changes in Dropbox.

>>>>>>>>>>>>>>>>
Not sure if you still need these hints.

The main reason for me to start using Zeroshell was QoS.
It works fantastically well and it is extremely flexible compared to other tools that I did try too. The Zeroshell QoS interface is very user friendly.

I do not prioritize by machine, but by traffic type.
Probably if you do it by machine, you are doing it the right way, each one with its own dedicated bandwidth.
In my case, the only machine prioritized and with reserved bandwidth is my VOIP gateway.
The rest may use all the available bandwidth at a given time.

L7 filters might be outdated yes, but prioritizing works well with other aspects of QoS in Zeroshell. Also, notice that with nDPI on the new Zeroshell kernel 3.6, we may use nDPI classification too.

Then I created my own classification scheme. Notice that not only helps to prioritize traffic but also classify reporting, so that you may know what type of traffic use you have on your network. You may even benefit from DSCP too if you want to use it.

After that, I assign each class to the interface that I want. In my simplified case, I used the same for upload and download, but may be done differently. The link is 608kb download and 320kb upload, so I setup the global bandwidth on each interface to match that of the link. I used 85% of the max bandwidth.

And then, voila! My home QoS is setup and working.
Again, this is a ridiculous bandwidth we are talking about on this part of the World, as Internet is very expensive here (608kbps/308kpbs) but I can listen to the radio, talk on the phone without interruption while my kids are playing network games on the same Internet line.

I cannot believe how I did it all these years without Zeroshell.

**Do not forget to save the configuration profile before and after each modification.

I thank this community for its existence. And congrats Fulvio, this is definitely a very good product.