Thanks for the pointer to the settings tab. Dunno how I missed something so obvious!

That is multicast noise most likely from your router it self, ie that 192.168.1.1, which seems odd that is being block by the ULA rule fc00::/7 ? If you do not want the noise, and your behind a nat.. Then either turn off logging of those rules.. Or create rules that specifically block the noise but don't log it.

@elvisripley Thank you for that invaluable insight. I was able to make a few tweaks based on your guidance (caused lightbulbs to go off in my head!) and I am now able to see the queries!

pf only filters at layer 3, it still works the same way on a bridge. I've setup filtering bridges like that in the past a number of times and it has worked fine. There's no way to debug at the command line I'm aware of. You can pcap on the various interfaces to see what's happening there. Steve

@Konstanti I attach a network diagram of my setup to make it clearer. This is what is weird, when I connect to the VPN from my phone on 4G (option 1 in the attached diagram), I don't get errors any errors just timeouts. I can access everything on the internal LAN and internet, except, I cannot login into certain webservices. When I enter my password and press login, it just stalls - the browser says it is "thinking / loading" and then nothing happens. After a long time I get a "Server not found" error in the browser. However, when I am on my phone on the internal wifi over the VPN (option 2), then I click login and get redirected instantly to the dashboard of the webapp. I can also reach the webapp from outside my network as I have a reverse proxy (option 3), and this works fine. The reason I want to set up the Mobile IPSec VPN is that I want to close down the reverse proxy I have set up so that I can only access my webservices over the VPN and not anymore expose them directly to the internet.

Tried killing the firewall states ?

@eddiemcdiarmid said in Firewall Advice: Hmm interesting. I don’t have any rules but the managed of the network I’ve named ‘external network’ can see my router. Is there a rule I can add to block them being able to access my network? Seeing your network and accessing your network are two very different things. You say both in your reply post above. The default block/deny rules on every pfsense install for the WAN interface, like @johnpoz talks about above, keeps people/hosts from accessing your network. You don't need to do it, but if you're really paranoid about that external network, you could set a specific block rule in your WAN interface to block/deny it's IP addresses. Again, you really don't need to do it, however. This is an example of the default settings and wording from an old version of pfsense, but I think the current versions still look like this on the WAN interface: Jeff

@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?