Whilst BYOD or cooperate device are outside the network they still need filtering to be active

I would like the HTTPS Inspection Warning removed (Guardian > HTTPS Inspection > Settings), because I don't want students to be aware that the traffic is being monitored.

Please consider having the option to Increase the max proxy global cache size beyond 1500 MB

The option is at
Web proxy > Settings > Advanced > Web filter options > Cache options > Global cache size

I installed Smoothwall on my own hardware.

df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 19G 1.7G 17G 10% /
none 12G 4.0K 12G 1% /var/state/login
none 12G 296K 12G 1% /var/tmp
/dev/sda4 894G 291M 849G 1% /var/log

Also consider storing the squid cache in the /var/log directory so it will have sufficient size. A slink could also be used.

If possible I would like to set HTTPS interception for transparent authentication on more than per interface. It would be ideal If i cuold set 'HTTPS' for a transparent authentication policy based on the 'Where'

More filter options like:

1. Start date/time and end date/time - so you can search the logs and specify 11.00-12.00 only

2. Computer Hostname

3. MAC Address

We use Exchange as our mail server and it shortens the Subject line to 256 characters, consequently URL are often cut off and invaldi when received.. If URL were included in the body of the message as well as the Subject line, that issue would be resolved

Would smoothwall consider a proxy timeout or Login Timeout for different groups of users. At the moment it is a global setting. Just thinking it might be nice to have for groups of users.

When viewing the realtime log to troubleshoot what may be happening with a user a freeze button to temporarily freeze the information display so that you can copy & paste urls or other relevant information for further analysis.

Create network redundancy. If you have two network ports on the smoothwall server, both connected to different switches.

Create active-passive teaming on the system, to be safe, if one switch should die.

When viewing the realtime traffic graphics i would like to see an option to be able see the max through put in the last 5mins / 10 mins / 30mins / hour / etc so admins can judge what the max through put on the internet line is at busy times.

The biggest thing I can't stand is trying to track down a network hog on a specific interface - it would be great if the realtime traffic graphs filtered the list of IPs sucking bandwidth to be filtered properly by clicking the interface on the left. Eg. We have an interface which is very busy with IP camera traffic but these cameras do not access the internet - despite clicking on the adsl link on the left, the IP list still shows all of the busy cameras even though they are not communicating with the selected interface.

The IDS / IPS reporting needs an overhaul too - how is it useful to see the outgoing port on the external interfaces instead of the internal IP generating the bad traffic?

At the moment to monitor where a port is blocked I have to ssh into the smoothwall and run a tcpdump to monitor traffic. Previously I've used the Microsoft ISA GUI for this and it told me quite nicely what was being allowed in green, what was being denied in red and what rules were allowing/denying. Could something similar be added to Smoothwall so I can easily see what is denied?

For example, an SMTP/SmoothZap Administrator, rather than just Quarantine. A Guardian 3 Administrator, rather than just an 'unblock' permission for an account...and so forth. Perhaps these users can't shut the system down or change NIC bindings, but they can administer portions of the Smoothwall fully, in addition to the permission set we have now.

Also, this granular permissions functionality will be needed eventually, for enterprise-level customers.

it would be ideal to have an option which allows specific host to use specific external interface while passing through proxy. It works while direct connection not using through proxy.

Have a packet trace tool to see where a firewall rule fails/drops packets when testing or creating port forwards. Similar to that of a cisco firewall where it would telling us at which point it fails.

Add Avahi for mdns / bonjour reflection between lans and vlans (eg wireless vlan and domain lan) to enable airplay services to run.

It would be nice if we could brand the squid error pages such as No Valid DNS or, 404 etc