Re: [pfSense] Squidgaurd seems not be working.

[Alberth David Perez Marfil]

Does the Squid is working?El 23/01/2014, a las 01:51, ivan  escribió:hi all, I am running pfsense 2.1 and squidguard. I want to filter adult content and i have added the filters but looks like the web filter is not working. M/U/G/U/Y/A I/V/A/N W/A/N/D/I/R/A+256712253430KAMPALA (U)___List mailing listList@lists.pfsense.orghttp://lists.pfsense.org/mailman/listinfo/list
Alberth  David Pérez MarfilM.C.C. M.A.D.N.I.  Calle 57 x 44  #247 Col. CordemexMérida Yucatán C.P. 97110Ofi. 999 287 3597  Cel. 999 576 0362Nextel ID: 92*10*17917Nextel      999 31 34 198“Tecnología para tu empresa”www.facebook.com/NegDeHoy

___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] psSense stops working

[Brian Caouette]

Thank you!

On 1/23/2014 10:26 AM, compdoc wrote:


>How would I pull that off?

Computers have several common points of failure. They are  the power 
supply, the motherboard, RAM, cooling fans, and the hard drive.


Fans are easy - just make sure they are spinning at the proper speed. 
This includes the fan inside the PSU.


If the motherboard is a few years old, it can develop bad capacitors. 
(caps) They are easy to spot when you open the case. Any caps that are 
rounded on top, are bad.  Some even leak. If so, replace the 
motherboard. Here are some sample pictures:


http://en.wikipedia.org/wiki/Capacitor_plague

Cheap power supplies often develop bad caps inside too, but it's 
dangerous to open the PSU so just swap it out to test. Sometimes you 
can see the caps inside if you just look through the openings.


Bad Ram is more rare, but you can test it for free by booting 
memtest86 or memtest86+. At least 3 or 4 passes is best. I've had bad 
ram that didn't show up until 5 test passes. I like to let the tests 
run overnight when possible.


The hard drive is easy. There's no need to run any tests - you just 
read the drive's SMART info. It records when sectors are failing, and 
when other bad things happen. PfSense has a SMART Status menu under 
Diagnostics.




___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] psSense stops working

[compdoc]

>How would I pull that off?



Computers have several common points of failure. They are  the power supply,
the motherboard, RAM, cooling fans, and the hard drive. 

 

Fans are easy - just make sure they are spinning at the proper speed. This
includes the fan inside the PSU.

 

If the motherboard is a few years old, it can develop bad capacitors. (caps)
They are easy to spot when you open the case. Any caps that are rounded on
top, are bad.  Some even leak. If so, replace the motherboard. Here are some
sample pictures:

 

http://en.wikipedia.org/wiki/Capacitor_plague

 

Cheap power supplies often develop bad caps inside too, but it's dangerous
to open the PSU so just swap it out to test. Sometimes you can see the caps
inside if you just look through the openings.

 

Bad Ram is more rare, but you can test it for free by booting memtest86 or
memtest86+. At least 3 or 4 passes is best. I've had bad ram that didn't
show up until 5 test passes. I like to let the tests run overnight when
possible.

 

The hard drive is easy. There's no need to run any tests - you just read the
drive's SMART info. It records when sectors are failing, and when other bad
things happen. PfSense has a SMART Status menu under Diagnostics.

 

 

___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] MultiWAN vs unbound

[Brian Caouette]

I played with unbound. Worked real good for the afternoon. Everything 
was really speedy then it just died. Switch back for forwarder and 
traffic began to flow again. I'm finding pfSense to be really temperamental.


Brian

On 1/23/2014 4:50 AM, Dave Warren wrote:
Can anyone point me in the right direction to set up unbound to work 
across multiple WANs (specifically, to failover to the second WAN if 
the primary WAN becomes unavailable)


We flipped back to the built-in DNS forwarder this evening, it seems 
to be doing the job, but this requires a manual switch (and of course 
puts us back to forwarding, rather than resolving locally, which is 
less than ideal)




___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] Processes

[Brian Caouette]

Thank you! Will take a look when I get home tonight.

On 1/22/2014 9:47 PM, David Burgess wrote:



On Jan 22, 2014 6:59 PM, "Brian Caouette" > wrote:

>
> What would cause CPU to run high on pfSense? I'm not running any 
extra packages. I am back to the base install. I doubled my memory 
thinking it would help with performance. It didn't. Is there a way to 
see everything running and what its using? I'm a windows man so 
anything compare to ctrl-alt-del processes?


'top'

Run in the shell.

db



___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] psSense stops working

[Brian Caouette]

How would I pull that off?

On 1/22/2014 9:31 PM, Jason Pyeron wrote:



*From:* list-boun...@lists.pfsense.org
[mailto:list-boun...@lists.pfsense.org] *On Behalf Of *Brian Caouette
*Sent:* Wednesday, January 22, 2014 21:03
*To:* pfSense support and discussion
*Subject:* Re: [pfSense] psSense stops working

100% default of package install. I will check those things out
when I reinstall the package. Dam box stopped working completely
so I did a factory reset from the drop down. This thing sure is
temperamental!

I had a similar issue, but it turns out to be an under powered power 
supply. Have you tested/load tested your hardware?



Brian

On 1/22/2014 8:17 PM, Michael Schuh wrote:

i suppose squid is caching all sites?
using LRU algorithm?
this sounds like squid could not update the cache or acl deny the
access.
enough diskspace? cache size big enough?
another caching algorithm tried? or caching algorithm changed
after the installation and first runs
and not cleared the cache dirs?

i would try to clear the entire cache and start over
http://wiki.squid-cache.org/SquidFaq/ClearingTheCache

= = = http://michael-schuh.net/ = = =
Projektmanagement - IT-Consulting - Professional Services IT
Postfach 10 21 52
66021 Saarbrücken
phone: 0681/8319664
@: m i c h a e l . s c h u h @ g m a i l . c o m

= = =  Ust-ID:  DE251072318  = = =


2014/1/22 Brian Caouette mailto:bri...@dlois.com>>

DNS should be handled by the ISP as the wan is using DHCP to
get that info. I also see the DNS is passed thru to my laptop
when I look at TCP/IP properties but you right it does sound
like DNS. Any thoughts on were I should be looking? What
puzzles me the most is it works fine on reboot but stops
after a short time with the exception of recently visited
sites which appear to still work. Last night for example I
was watching YouTube hours after all other sites stopped
working. It's like if they stay active there is no issue.
Fairly confident it is caching / TTL related. But from my
limited knowledge it all looks good. Pretty much defaults on
everything.

Brian


On 1/22/2014 9:59 AM, Maine Techie wrote:

Sounds like a classic case of cache (squid) or possibly a
DNS config issue. Just a couple ideas where to start the TS
process.  Plenty of resources on both on the pfSense forum.


On Wed, Jan 22, 2014 at 9:52 AM, Brian Caouette
mailto:bri...@dlois.com>> wrote:

Having some trouble that I can' figure out. Upon fresh
reboot my system works good. Shortly after it starts
failing to serve webpages to the lan port. Via the web
interface I can do ping and tracert and it all looks
good but from my pc it all fails after 15 minutes to a
few hours. Some web pages work others don't. I suspect
recently visited sites are the ones that continue to
work for a little bit longer. I have a base install with
captive portal and squid as extras.

Thoughts?


___
List mailing list
List@lists.pfsense.org 
http://lists.pfsense.org/mailman/listinfo/list




___
List mailing list
List@lists.pfsense.org  
http://lists.pfsense.org/mailman/listinfo/list



___
List mailing list
List@lists.pfsense.org 
http://lists.pfsense.org/mailman/listinfo/list




___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list


--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron  PD Inc. http://www.pdinc.us 
 -

- Principal Consultant  10 West 24th Street #100-
- +1 (443) 269-1555 x333Baltimore, Maryland 21218   -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.


___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list

[pfSense] MultiWAN vs unbound

[Dave Warren]

Can anyone point me in the right direction to set up unbound to work 
across multiple WANs (specifically, to failover to the second WAN if the 
primary WAN becomes unavailable)


We flipped back to the built-in DNS forwarder this evening, it seems to 
be doing the job, but this requires a manual switch (and of course puts 
us back to forwarding, rather than resolving locally, which is less than 
ideal)


--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren

1832-Curling is introduced to the U.S., giving Americans
a sport combining the surface of hockey with the thrill
of watching paint dry.


___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list