No, but there is a public Slack and IRC ( #pfSense on freenode )

Yes sir john. Different subscribers i have this: everything is fiber which is speed of light what speed transmit the receive is they same speed right? I have FTTH (fiber to the home) in every household and different areas. so the upload is  all of  theme is open for the corporate only because more on sending email, posting photos, uploading files etc. while the download you have to limit specially saving bandwidth. which is  download is for opening web page, receiving email, watching online videos. etc. and also  the residential subscribers you have to limit of theme. single user (1pc): upload –---->512 KB | Download-----> 1024 offices (maximum 6cpc): upload ------>open bandwidth | Download-----> up to MB upgrade Internet cafe (maximum 20 pc): upload ---------->Mb | Download------------->Mb Corporate (maximum 50 pc): upload ------>open bandwidth | Download-----> 4 MB sir john this is right to limiting bandwidth? what is your suggestion? "all of that Disturbing IDM"  :'(

Hi Robin, im using splice all, always taking much ram time to time. do you have same issue with me? SOLVED im try all selected option on ssl proxy for your problem Robin, try disable your refresh pattern.

Cache/Proxy Forum: https://forum.pfsense.org/index.php?board=60.0

Turned out to be our UPS being misconfigured, and shutting down the server while we blamed the update… sorry and thank you for helping!

@SammyWoo: …so I can tell right on top, aha, somebody is running an at&t DSL... Probably better than using your family name or number.street as SSID. Knowing an ISP doesn't give you much of an attack vector.

Change the port the webGUI is listen to in System > Advanced > Admin Access. Also check "WebGUI redirect" to disable the redirection of port 80. Allow access to the new webGUI port only on internal interfaces.

For systems behind a firewall, this add a sensitive lag when logiing in or going to the dashboard. It would be nice to make that call not as often as the page is loaded.

Umm, wrong post? The OP was not talking about Squid taking up too much memory. And Squid is a cache, it's supposed to cache data. If it's using too much memory, you're caching too much. https://wiki.squid-cache.org/SquidFaq/SquidMemory Start a new thread, probably over here https://forum.pfsense.org/index.php?board=60.0

0.0.0.0 is the source address used before a device knows it's IP address.  It's often used for DHCP requests.  You can use packet capture or Wireshark, to see where those packets are coming from and what they're doing.

Don't be so lazy and try different searches, for example: @roncbk: Cannot allocate memory - The line in question reads Also a different sign of being lazy, update your pfSense install your way behind.

OK, just saw a Tweet from Deutsche Telekom that they had issues with "some" connections with static IP  ::) … Seems the problem was an external one.

@querichelli: I need to keep WAN1 working, but test WAN2 with ping test for 1hour+, is it possible? Whats the purpose of the Test? If your wanting to test WAN2 specifically for devices behind pfSense than the policy route via firewall rule as suggested would be the way to go. If you just wanting to see the quality of your WAN2 from ping results than I would suggest changing the monitoring IP for that gateway to 8.8.8.8 and let pfSense monitor this for you. This way you can see the current quality of your WAN2 when you login and also check the history of that link by going to Status –> Monitoring. If you haven't done so already, I would suggest doing this for WAN1 as well. In order for failover to work properly this should have already been done but maybe this isn't the purpose for your test.

Is your modem routing, if it was bridging you's see a non RFC1918 address on the pfSense WAN NIC ? BTW my blacklist is to block shodan.io & other IP addresses.

@aagaag: The only remaining issue is that I think that I may need to do the same for IPv6. However configuring IPv4+6 disallows the gateway options. Naturally, IPv6 requires an IPv6 gateway. So you cannot set the IPv4 VPN gateway for IPv6 traffic anyway. @aagaag: I stand corrected. I do have a DNS leak. Might you be so kind and explain to me how I can ensure that traffic moving through the VPN uses a specific DNS server, and only that one? The simplest way would be to use an external DNS server on the concerned devices. Assuming you use the DHCP server on pfSense to configure the network on your devices, add a static mapping for all devices you're directing over that vpn. In the static mapping you can define an external DNS like Googles 8.8.8.8 or what ever you want. Since any traffic of that devices is directed over the vpn by the firewall rule, the DNS requests also have to go over the vpn.

No, that is not possible.