Okay…Thanks... ;)

zabbix2-agent pkg v 0.6_2 has a working config file.  :)

Hiya, Thanks for the reply and I hope you could assist me a bit further. Here is my setup zabbix server                pfsense main firewall                        pfsense another site 192.168.0.31                    192.168.0.251 (Local)                        192.168.20.250(local)                                 192.168.23.251 ( different vlans)            this is linked to 192.168.23.0/24 vlan There are multiple vlans on the main firewall some connection to other remote pfsense firewalls. So my question is on the remote pfsense, I install the zabbix client. In the client  setting, I will put the following : server:192.168.20.251 server Active:192.168.20.251:10050 Hostname:(name of firewall) Listen IP:0.0.0.0 listen port:10050 refresh active checks:120 timeout:3 buffer send:5 buffer size:100 start agents:3 On the main pfsense install the settings for the proxy is : Proxy settings server:192.168.0.31 server port:10051 hostname:(Proxyname) Mode Active: yes config frequency:3600 On the Zabbix server I created a proxy called (Proxyname) and then added the remote pfsense as a client but I do not get any results. On the remote pfsense agent logs is as follows: 6469:20130211:090609.894 Got signal [signal:15(SIGTERM),sender_pid:55456,sender_uid:0,reason:65537]. Exiting …   6054:20130211:090609.894 One child process died (PID:6653,exitcode/signal:65280). Exiting ...   6361:20130211:090609.894 Got signal [signal:15(SIGTERM),sender_pid:55456,sender_uid:0,reason:65537]. Exiting …   6054:20130211:090611.895 Zabbix Agent stopped. Zabbix 2.0.4 (revision 31984).   4277:20130211:090614.908 Starting Zabbix Agent [tfcfire01]. Zabbix 2.0.4 (revision 31984).   4348:20130211:090614.909 agent #0 started [collector]   4679:20130211:090614.910 agent #2 started [listener]   4457:20130211:090614.910 agent #1 started [listener]   5290:20130211:090614.910 agent #4 started [active checks]   4972:20130211:090614.910 agent #3 started [listener]   5290:20130211:092305.201 Got signal [signal:15(SIGTERM),sender_pid:6797,sender_uid:0,reason:65537]. Exiting …   4679:20130211:092305.202 Got signal [signal:15(SIGTERM),sender_pid:6797,sender_uid:0,reason:65537]. Exiting …   4348:20130211:092305.202 Got signal [signal:15(SIGTERM),sender_pid:6797,sender_uid:0,reason:65537]. Exiting …   4972:20130211:092305.202 Got signal [signal:15(SIGTERM),sender_pid:6797,sender_uid:0,reason:65537]. Exiting …   4457:20130211:092305.203 Got signal [signal:15(SIGTERM),sender_pid:6797,sender_uid:0,reason:65537]. Exiting …   4277:20130211:092305.203 One child process died (PID:4679,exitcode/signal:65280). Exiting ...   4277:20130211:092307.204 Zabbix Agent stopped. Zabbix 2.0.4 (revision 31984). 18350:20130211:092310.215 Starting Zabbix Agent [tfcfire01]. Zabbix 2.0.4 (revision 31984). 18681:20130211:092310.216 agent #0 started [collector] 18873:20130211:092310.216 agent #2 started [listener] 19115:20130211:092310.216 agent #4 started [active checks] 18710:20130211:092310.217 agent #1 started [listener] 18972:20130211:092310.217 agent #3 started [listener] 19115:20130211:092310.438 No active checks on server: host [tfcfire01] not found 19115:20130211:202847.418 No active checks on server: host [tfcfire01] not found The proxy logs on the main pfsense is as follows: 44419:20130211:091238.401 Zabbix Proxy stopped. Zabbix 2.0.4 (revision 31984). 10294:20130211:091258.834 Starting Zabbix Proxy (active) [bpsproxy]. Zabbix 2.0.4 (revision 31984). 10294:20130211:091258.834 **** Enabled features **** 10294:20130211:091258.834 SNMP monitoring:      YES 10294:20130211:091258.834 IPMI monitoring:        NO 10294:20130211:091258.834 WEB monitoring:        YES 10294:20130211:091258.835 ODBC:                  NO 10294:20130211:091258.835 SSH2 support:          NO 10294:20130211:091258.835 IPv6 support:          YES 10294:20130211:091258.835 ************************** 10357:20130211:091258.848 proxy #1 started [configuration syncer #1] 10482:20130211:091258.848 proxy #2 started [heartbeat sender #1] 10730:20130211:091258.849 proxy #3 started [data sender #1] 11948:20130211:091258.854 proxy #13 started [trapper #4] 11816:20130211:091258.853 proxy #11 started [trapper #2] 10294:20130211:091258.856 proxy #0 started [main process] 12588:20130211:091258.857 proxy #17 started [http poller #1] 13293:20130211:091258.859 proxy #21 started [history syncer #3] 11923:20130211:091258.863 proxy #12 started [trapper #3] 12007:20130211:091258.865 proxy #14 started [trapper #5] 13238:20130211:091258.911 proxy #20 started [history syncer #2] 12571:20130211:091258.914 proxy #16 started [housekeeper #1] 12571:20130211:091258.914 executing housekeeper 11498:20130211:091258.916 proxy #9 started [unreachable poller #1] 13572:20130211:091258.917 proxy #22 started [history syncer #4] 10756:20130211:091258.945 proxy #4 started [poller #1] 11278:20130211:091258.959 proxy #7 started [poller #4] 10892:20130211:091258.966 proxy #5 started [poller #2] 11374:20130211:091259.004 proxy #8 started [poller #5] 12790:20130211:091259.013 proxy #18 started [discoverer #1] 12225:20130211:091259.013 proxy #15 started [icmp pinger #1] 12959:20130211:091259.014 proxy #19 started [history syncer #1] 11534:20130211:091259.015 proxy #10 started [trapper #1] 10990:20130211:091259.017 proxy #6 started [poller #3] 12571:20130211:091259.190 housekeeper deleted 0 records from history (spent 0.004097 seconds) 10482:20130211:091358.853 Unable to connect to the server [192.168.0.31]:10051 [cannot connect to [[192.168.0.31]:10051]: [4] Interrupted system call] 10357:20130211:091414.095 Unable to connect to the server [192.168.0.31]:10051 [cannot connect to [[192.168.0.31]:10051]: [60] Operation timed out]. Will retry every 120 second(s) 10730:20130211:091414.198 Unable to connect to the server [192.168.0.31]:10051 [cannot connect to [[192.168.0.31]:10051]: [60] Operation timed out]. Will retry every 1 second(s) 10482:20130211:091458.860 Unable to connect to the server [192.168.0.31]:10051 [cannot connect to [[192.168.0.31]:10051]: [4] Interrupted system call] 10357:20130211:091529.103 Still unable to connect… 10730:20130211:091529.205 Still unable to connect... 10482:20130211:091558.868 Unable to connect to the server [192.168.0.31]:10051 [cannot connect to [[192.168.0.31]:10051]: [4] Interrupted system call] 10730:20130211:091645.215 Still unable to connect… 10482:20130211:091658.877 Unable to connect to the server [192.168.0.31]:10051 [cannot connect to [[192.168.0.31]:10051]: [4] Interrupted system call] Do I need any rules on the fiirewall pls. The link between the remote and main firewall is an openvpn site to site link always on.

Normally yes the fix is https://github.com/bsdperimeter/pfsense-packages/commit/c81902f92799a1f566667f8fae07ecb92069372f

Mostly "If it isn't broke, don't fix it" but if you encounter a problem, first thing to try is a firmware update to a recent snapshot. Or an update once a month or every couple weeks is OK too. Difficult to generalize it really since it depends on the features you use and what work has been done on those since the last update that was done.

Firebug plugin on Firefox can help too.

If you are trying to do this with automatic outbound nat howto's on the forum, it can be frustrating getting it to work, but I managed to get it going out both WAN's last night. First off make sure you dont have "Sticky connections" enabled, this was the prime reason why I noticed all my http traffic was only going out my primary wan, secondary wan was not utilised at all. Also when I created the floating rule, I chose [action:pass | quick:ticked | interface:wan1:wan2 | direction:out | protocol:tcp | destination port range:HTTP | gateway:MultiWan] In my firewall rule for the proxied interface, i.e LAN I created a default rule that passed all traffic to 'Gateway':MultiWan. Maybe the above LAN rule does'nt need to be set as your multiwan and can be just default gateway, as the floating 'quick' rule catches it before hand, also make sure you reset states and restart squid. If you have setup up squid correctly then it should work with the above notes/tips. Hope this helps anyone who had a frustrating time trying to get this to work :0)

@AbdulCebbar: Well, thank you very much :) Be the first to post a bounty  :)

Thanks for posting this; I'd noticed the same bug and hadn't gotten around to posting about it but either you or someone else reported it and it got fixed and hasn't been an issue in recent versions. So thanks for mentioning it!

You might be best off looking into something like freenas or commercial solutions such as those offered by synology. pfSense is a firewall with some options for IDS and UTM, but it probably will never be a download station.

It was updated.

What squid version are you using?

Thanks Wupsje. Assuming it didn't work we uninstalled it and have gone for a different system. The biggest problem I found was the lack of documentation.

click on the rules tab.. you should see all the rules under each category

I went through the backup and restore process, but there was nothing to clean up in the XML file. Everything had a matching opening/closing tag. Any new reverse proxy entries that I add, through the GUI, show up in the XML file, but the GUI stop and restart commands don't work. To restart the proxy service, I still have to reboot the server, so I go back to my original question (until I can investigate a different reverse-proxy pkg). From the command line, how can I stop and then start the Mod_Security+Apache+Proxy package, so that I don't have to reboot the firewall? Anyboday know where the scripts are for this pkg? TIA Paul