@juelmk said in No inbound traffic coming into my WAN: When I set my WAN interface to get dhcp address from the modem it get 0.0.0.0 Well then how would it work? You sure your own the pfsense wan interface plugged into your router? You sure the cable is good? When pfsense does get an IP you need to make sure that your wan and lan of pfsense do not overlap - ie they can not be the same network 192.168.0/24 for example

That'll do it!

@m0nji said in Whitelist-Ansatz für Windows- und Programmebene: Allen nicht explizit legitimierten (ausgehenden) Datenverkehr unterbinden: @jegr said in Whitelist-Ansatz für Windows- und Programmebene: Allen nicht explizit legitimierten (ausgehenden) Datenverkehr unterbinden: Snort+OpenAppID Application Filtering on pfSense ist vollkommen an mir vorbei gegangen. Danke für die Richtigstellung. Kein Problem, gerne. Steht leider noch auf meinem ToDo Zettel zum Testen aber leider dank Krankheit und Arbeit noch nicht dazu gekommen ;)

Fiz um novo teste com outro cabo e funcionou, problema resolvido.

poderia relacionar quais foram os hosts que colocou:?

Quem tem mais conhecimento com tcpdump consegue me dizer do que ele esta reclamando. com o cenário de rede acima.

That's great to hear! As far as the YouTube content... Hmmm that's a tricky one! Might be a little bit beyond my pay grade! Ruling out a coincidence, I'd be thinking it's something to do with the port that they use or a connection (firewall state) being kept open, but I'd only be guessing.

There are many how to's on the youtube and interwebs. Here is one I have saved https://www.youtube.com/watch?v=W2gy1bLHm5o Skip the pfsense install part as it goes through the whole process from pfsense setup to squid, to squidguard, and lightsquid. Squidguard itself is not hard to setup once you have setup you squid transparent proxy which is basically enabling squid, checking transparent proxy, settings caches and that's it for squid then switch to squidguard and configure it. I have squid setup as an HAVP sine it is built into the squid package now and not a separate package before 2.3. Overall there is are many video and guides with pictures to assist in setting up or helping troubleshoot pieces of pfsense you need help with when you google for it such as in your case "pfsense squidguard setup". Don't hesitate you use your Googlefu.

I imagine you will fine routing at the firewall between the internal subnets. That hardware is probably far in excess of what you need. Steve

If you just want to do DNS bases blacklisting you could take a look at pfBlockerNG.

I stand corrected! ~Mat

@medikopter said in OpenVPN TLS Fehler: Das klingt ja eigentlich ganz cool und simple, allerdings scheitere ich schon an der Umsetzung eines Failover. Nunja, aber das sind ja auch zwei verschiedene paar Stiefel ;) VPN auf beiden Interfaces zum Laufen zu bringen ist wesentlich leichter, weil du nichts umschalten/routen/sonstwas musst. Daher überhaupt nicht schwer. Also das er das Interface automatisch wechselt wenn eins Down ist. Es genügt doch eine Gateway Gruppe zu machen und die bei den Regeln auf dem LAN einzusetzen?