Re: [pfSense] [SOT] apu1c4/apu1d4 stability

2014-09-22 Thread Odette Nsaka
Not 20 but just 1 (at the moment), working as espected 24/7 since when 
installed (a couple of months). The environmet temperature is between 
20°C and 27°C.

Odette 


*/In data lunedì 22 settembre 2014 18:10:55, mayak ha scritto:/*
*/> hi all,/*
*/> /*
*/> in an earlier thread, i recounted issues that i had with the apu1c4 
unit/*
*/> silently dying -- this was the only thread that i saw here, so i assume/*
*/> that i just got a bad unit./*
*/> /*
*/> can anyone confirm a small deployment of 20 of these without issue? i 
am/*
*/> currently getting ready to do a proposal and i need to reassured./*
*/> /*
*/> thanks/*
*/> /*
*/> m/*
*/> ___/*
*/> List mailing list/*
*/> List@lists.pfsense.org/*
*/> https://lists.pfsense.org/mailman/listinfo/list/*
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] [SOT] apu1c4/apu1d4 stability

2014-09-22 Thread mayak


On 09/22/2014 07:05 PM, Chris Bagnall wrote:

On 22/9/14 5:10 pm, mayak wrote:

in an earlier thread, i recounted issues that i had with the apu1c4 unit
silently dying -- this was the only thread that i saw here, so i assume
that i just got a bad unit.


I cannot give you a sample of 20 - they're too new for that - but I can say of 
the dozen or so we've used thusfar we've had no failures reported.

They do run noticeably warmer to the touch than the previous ALIX boards, and 
as others have posted here, it's important to attach the heat spreader 
correctly and ensure it has good contact with the chassis.

So if your install environment is particularly warm, or particularly poorly 
ventilated, then you might want to consider an alternative. All of ours are 
installed in reasonably well-ventilated 19" cabs.

hi chris,

what would you consider for a `warmer` environment?

thanks

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


Re: [pfSense] [Bulk] Re: Https proxy squid3 squidguard squid3 not working

2014-09-22 Thread PiBa

Hi Mohan,

I think it needs SNI forwarding from client-request to squid-request 
which seems that is not yet implemented in squid.

see: http://wiki.squid-cache.org/Features/SslPeekAndSplice

I think currently something like this is happening:
openssl s_client -connect gmail.com:443 | grep subject
subject=/C=US/ST=California/L=Mountain View/O=Google Inc/CN=mail.google.com

While when the proper SNI value would have been send a different 
certificate would be returned:

openssl s_client -connect gmail.com:443 -servername gmail.com | grep subject
subject=/C=US/ST=California/L=Mountain View/O=Google Inc/CN=gmail.com

That means google is using SNI to determine what certificate to send 
back, and squid is probably sending the wrong or no SNI extension in the 
request for a server-certificate.


Short of implementing those changes, getting them merged into a main 
branche and getting it released, there is no workaround.. There seems to 
be some work going on for that though.. If you can compile squid 
yourself on FreeBSD 8.3 you might be able to use that specific 
development branch.


My two cents,
PiBa-NL

Nicola Ferrari (#554252) schreef op 22-9-2014 8:24:
That's the correct behaviour: you're gettings cert warning because you 
are doing https filtering, so your pfsense needs to "inspect" https 
traffic: this is a sort of "man in the middle", so the browser detect 
that the source cert is varied in his CommonName field.


Usually I don't use https filtering. If I need to filter HTTPS for 
some reason, I simply work in a whitelisting configuration: https 
traffic is denied exept for allowed domains.


N


Il 19/09/2014 17:49, A Mohan Rao ha scritto:

Hello experts,

I m struggling with https filtering anybody have idea how to i
configured it all other sites r working good but google and some other
reputed sites r given certificate errors a already check with ie Firefox
and chrome etc.
Same error.

Pls give idea how i resolve this prob.

Thanks
Mohan



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






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


Re: [pfSense] [SOT] apu1c4/apu1d4 stability

2014-09-22 Thread Chris Bagnall

On 22/9/14 5:10 pm, mayak wrote:

in an earlier thread, i recounted issues that i had with the apu1c4 unit
silently dying -- this was the only thread that i saw here, so i assume
that i just got a bad unit.


I cannot give you a sample of 20 - they're too new for that - but I can 
say of the dozen or so we've used thusfar we've had no failures reported.


They do run noticeably warmer to the touch than the previous ALIX 
boards, and as others have posted here, it's important to attach the 
heat spreader correctly and ensure it has good contact with the chassis.


So if your install environment is particularly warm, or particularly 
poorly ventilated, then you might want to consider an alternative. All 
of ours are installed in reasonably well-ventilated 19" cabs.


Kind regards,

Chris
--
This email is made from 100% recycled electrons
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


[pfSense] [SOT] apu1c4/apu1d4 stability

2014-09-22 Thread mayak

hi all,

in an earlier thread, i recounted issues that i had with the apu1c4 unit 
silently dying -- this was the only thread that i saw here, so i assume that i 
just got a bad unit.

can anyone confirm a small deployment of 20 of these without issue? i am 
currently getting ready to do a proposal and i need to reassured.

thanks

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


Re: [pfSense] Adding Ethernetports

2014-09-22 Thread dragonator
If you are running VMware then I assume you're running pfsense as a vm. In that 
case you'll need to add the NIC to VMware the create a new virtual network 
which can then add to the vm. You'll have to add a second nic and point it to 
the virtual network.

 Original message From: Brian Caouette 
 Date:09/19/2014  10:31  (GMT-05:00) 
To: pfSense support and discussion  
Subject: [pfSense] Adding Ethernetports 
>I added a dual port nic to my pfsense box and it doesn't show the 
>additional ports. 
> 
>The new nic doesn't show anywhere. I am using a PowerEdge 2850 and an 
>Intel Card. I am also using vmware on the machine. 
> 
>Any ideas what may be going on? 
>___ 
>List mailing list 
>List@lists.pfsense.org 
>https://lists.pfsense.org/mailman/listinfo/list 
>___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] No logout in 2.1.5 i386

2014-09-22 Thread Vick Khera
your images are no longer available, but i'll assume it is that the
right end menu wrapped around and covers the left end menu.

the fix to that is to clear your browser cache.


On Fri, Sep 19, 2014 at 11:39 AM, Przemysław Pawełczyk  wrote:
> Hi,
>
> New 2.1.5 i386 has bad menu layout.
>
> * Stacked 2 submenus: System, Help
> http://pp.blast.pl/pfs/ssw_127.png
>
> * Rolled-down System with cursor:
> http://pp.blast.pl/pfs/sss_060-1.png
>
> * Rolled-down Help with cursor:
> http://pp.blast.pl/pfs/sss_061-1.png
>
> I can't move cursor on "logout" submenu (and other items).
>
> --
> Przemysław Pawełczyk - p...@blast.pl
>
> ___
> List mailing list
> List@lists.pfsense.org
> https://lists.pfsense.org/mailman/listinfo/list
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

[pfSense] After upgrading 2.1.3->2.1.5 the SNMP.pm can't be found for Nagios anymore

2014-09-22 Thread Rens
Dear all,

 

after upgrading to 2.1.5, coming from 2.1.3 PFSense all of a sudden lost
it's Net/SNMP.pm from it's path.

 

This results in issues with some plugins of Nagios. e.g.

 

/usr/pbi/nrpe-amd64/libexec/nagios/check_ifoperstatus

 

Which gives these errors:

 

Can't locate Net/SNMP.pm in @INC (@INC contains:

/usr/pbi/nrpe-amd64/libexec/nagios

/usr/pbi/nrpe-amd64/lib/perl5/5.14.2/BSDPAN

/usr/pbi/nrpe-amd64/lib/perl5/site_perl/5.14.2/mach

/usr/pbi/nrpe-amd64/lib/perl5/site_perl/5.14.2

/usr/pbi/nrpe-amd64/lib/perl5/5.14.2/mach

/usr/pbi/nrpe-amd64/lib/perl5/5.14.2 .) at

/usr/pbi/nrpe-amd64/libexec/nagios/check_ifoperstatus line 40.

BEGIN failed--compilation aborted at

/usr/pbi/nrpe-amd64/libexec/nagios/check_ifoperstatus line 40.

 

I guess something went wrong in the Perl dependencies.

 

What is advised to get out of this situation?

 

Regards,

 

Rens

 

 

 

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