@kdmiller45:

That was just an example,  a better one be users going to porn sites

Keith

That might be solved by using Squid and Squidguard, or perhaps also e2guardian which is what Marcelloc is currently working on.

Adding "WebCfg - Diagnostics: Reboot system" did not work.  Still getting "Operation Not Permitted".

@Gertjan:

@remzej:

@satifhussainr:

Hi Guys

I am using Pfsense in Home environment for web filtering and caching.

I checked Transparent proxy for minimum configuration at client side

now I setup my pfsense for SSL Filtering I create a certificate and download it at client

If client is computer then everything is ok but if client is smart phone or tablet then apps for facebook viber
and whatapp is not working, although https site is working fine.

I did not change any thing in rules. Rules are as it is by default.

Please let me know What should I do ?

Thank you

We have the same problem. Everything both HTTP and HTTPS are working for PCs and smartphones web browsers. But facebook application for android and iphone cannot access.

You have the same problem ?
Then why wouldn't you accept the answer already given (== stop the MTM stuff - NSA might pull this one of, 'we' : never) ?

Thanks! I already found other options that still meets our requirements.

Yes just found it thanks for the quick reply!

It was indeed Stephen.
Am in the UK and it was a standard (Huawei) BT modem feeding an FTTC ISP connection via DSL to ethernet to the NIC.

Sorry for the delay I don't appear to have notifications on my posts….

Could be over heating?
Have you checked inside for dust build up?

Solved it myself.  So obvious I overlooked it.

Firewall > NAT > Port Forward

Interface: WAN
Protocol: TCP
Source Address: *
Source Port: *
Dest. Address: WAN Address
Dest. Ports: 80
NAT IP: 10.10.10.144
NAT Ports: 80

@johnpoz:

Sure looks like it supports being a dhcp server to me!

http://h20566.www2.hpe.com/portal/site/hpsc/template.PAGE/action.process/public/psi/manualsDisplay/?sp4ts.oid=3897494&javax.portlet.action=true&spf_p.tpst=psiContentDisplay&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.prp_psiContentDisplay=wsrp-interactionState%3DdocId%253Demr_na-c04490719%257CdocLocale%253Den_US&javax.portlet.endCacheTok=com.vignette.cachetoken

Did you actually go over the management and configuration guide?

Thanks. It turn out hp.com had an older version of the manual. A firmware update allowed DHCP to work. Thanks again to everyone for the help!

You image is waay to big.

The way spanning works is it tracks all the routes between switches and stops dual routes. If you add a second connection between switches and create a dual route which causes a loop this is a storm which can take a switch down trying to resolve the loop. STP, spanning tree blocks this second connection which kills the storm.  But you can use this method with the second link for redundancy and it becomes a hot stand by.  When the first connection goes down STP, spanning stops blocking the second connection and you have redundancy.

You need to buy switches with spanning tree.  I have only ever used Cisco switches but others have it.

pfsense is pretty versatile – depending on how you want it running and what you want it to do, you'll need different things.  At a minimum, you'll need something running pfsense -- that can be a virtual machine, a server, a laptop, or even a little box that just runs pfsense (like this:  https://store.netgate.com/SG-1000.aspx).

From there, it's LIKELY that you'll have some network connections -- pfsense is good at managing what and how things get from one connection to the other.

What would you like pfsense to do for you?

The direction of traffic is from the perspective of the firewall itself. You seem to have that backwards. It's leaving your LAN but that does not make it outbound from the firewall to the LAN, it's inbound from the LAN to the firewall.

For example, traffic leaving local systems going to the Internet comes IN to the firewall on the LAN interface and exits OUT of the firewall on the WAN interface.

Hello,

Thanks for your answer.

Regards,

Found this one and solved the problem.

Changing architecture (32-bit to 64-bit or vice versa) during upgrade

https://doc.pfsense.org/index.php/Upgrade_Guide#Changing_architecture_.2832-bit_to_64-bit_or_vice_versa.29_during_upgrade

Case closed

If anyone comes across this in the future with the same problem…I removed the pci card and installed pfsense using only the onboard NIC, then I added hint.agp.0.disabled=1 to  /boot/loader.conf.local then rebooted the machine and reattached the PCI card.  It was recognized as is now working great.

@jimp:

That said, you can edit that file from Diagnostics > Edit File. It may not exist yet, so put in that path, click load, type in what you need, then save. Then reboot to activate the settings.

Do you know where to access the diagnostics page? I cant get past the inital setup that you do on first boot.