The service is disabled during uninstall/reinstall.

File manager.  Great.

yesss, for next refers,it was a simple mistake by me,just select lightsquid>setting>Report Scheme (something other than Text) :D

222.PNG
222.PNG_thumb

No worries, upgrading to 2.1.3 has fixed the issue. Must have been something that got changed in the package or the package system.

Thanks!

Edit: Not sure if it matters, but the error message said something pertaining to a missing nmap.inc, install failed, then the install would gracefully back out and perform the nmap uninstall, removing all nmap components. If I can get the exact error message from an un-updated install I will before I update it.

@BBcan17:

Great stuff… This will make testing that much easier!!

EDIT:

On another note, also having the functionality to create a fresh NEW interface would also be beneficial instead of trying to re-enable all of the previously disabled rules.

That functionality is there today with the current (+) icon.  I'm not changing that one.  I will be adding new (+) icons beside each configured interface.  Clicking the (+) beside an already configured interface will perform the DUP function.  The layout will be pretty much just like the firewall rules page.  So the (+) icon at the top right of the tab will create a new fresh interface (just like it does today).  The (+) icon beside an existing configured interface will DUP it.

In terms of the rules, on the RULES tab today is an icon that will remove all forced enable/disable changes for all rules on the interface.  This essentially resets the rules to their default state.  There is a similar icon that will do this for only the currently selected category.

Bill

@priller:

Not "alerts.log" …... "suricata.log".  It uses a different date format from all the other logs.

suricata.log

3/5/2014 -- 14:37:21

To match the other logs that should be 5/3/2014, or more specifically 05/03/2014 .  Today being 5/5, it's a bad day to compare the different formats!  ;D

alerts.log

05/01/2014-02:38:47.669925

http.log

05/03/2014-17:40:37.873931

tls.log

05/02/2014-07:39:35.069581

Oh…sorry, I understand now.  I will look again in the config docs, but I don't think there is any way to change that outside of editing the actual binary source code.  I can see how much of an issue that would be and perhaps sneak it into the next release when I upgrade to 2.0.

Bill

Then I am baffled as to why one firewall has the issue while another (supposedly configured the same way) does not.  There would be only two logical explanations:  (1) either they are, in fact, not actually configured the same although they are supposed to be, or (2) you said one was VMware-based, and it is conceivable that VMware's virtual networking could play into the mix with that HTTP_INSPECT alert.

Maybe setting up a standalone pfSense install to see if VMWare is the culprit is the best solution to rule out the Virtual machine idiosyncrasys. or a VM machine for the Main Site.

A simple reboot of the laptop resolved it.  Why would this be the case?

Tx.
I noticed another issue this WE.

I took a fresh Asterisk backup and did some config tests.
After that I wanted to go back to my backup (as I usually do after testing)…:

it restored the backup and initiated a reboot after reboot....it re-installed the Asterisk package again !!!! then I had to restore (again) and it works...

Strange behaviour no ?

Seems you have found the wrong forum? pfSense which is based on FreeBSD has nothing to do with CentOS ?
You should probably try the haproxy mailing-list for this question, maybe one of the core developers present on that list can help you further: haproxy@formilux.org

@simby:

Hi!

i have install Suricata 1.4.6 pkg v1.0.1 with snort. Snort is disabled, suricata is On with AC + blocking.

In log i don see any alerts, no blocking.

I have tested with grc.com  :((

I have pfsense 2.1.3 x64

Not a good idea at all to run these two packages together on the same firewall.  I would remove the Snort package if you want to use Suricata.  Also, did you select some rules for Suricata to enforce?  You did not mention that in your post.  Oh, and one other point– Suricata really works best only with the Emerging Threats rules.  There are many of the Snort rules that have Snort-specific keywords in them, and these rules will fail to compile on Suricata.  Suricata will start, but it will not use any rules that fail to compile.  This is different from Snort.  If Snort chokes on any rule during compilation, it will not start up.  Go to the Logs Browser tab and examine the suricata.log file for the interface and look for any errors.

Bill

@tomtomtom6600:

hi bmeeks,

thanks for explaining my second problem. This is clear now.
Back to my first problem. I will do what you have mentionend, but is it possible that my problem has something to do with squid running in transparend mode. Is it possible that those downloads are cached

thanks

Ah!  Yes, caching is a possibility.  If you mentioned it before, I missed you saying anything about squid running.

Bill

Hrmm yeah only unbound-1.4.21_1.tbz is available. 1.4.22 for 2.0.X was not built for some reason automatically.
You on 2.1.3 now so I am not going to worry too much :)

Can you manually connect to http://interfaceaddress:8000/  ??

It seems many times I post here, a bit of knowledge is forced back to me through the web, my keyboard and into my head.  It seems I figure it out immediately after posting (whether or not a get good advice).

In this case it was the interface assignment which was set to the physical interface, not the VLAN on that interface.

Miles Deep out

@bmeeks:

While not a bad idea, if the IP address changed, then it would become a false "fix" and folks would assume it was working when it in fact might not be.

If pfSense could fix the code to allow domain names it would be really beneficial.

Couldn't an alias be setup as packages.pfsense.org and at each interface restart, it would perform a

dig packages.pfsense.org +short as the ip address?

I assume that the repo is coded in the update page and could be extracted.

Just a thought.