@billsecond
It should, assuming the router has enough horsepower to do all the packet processing at a 3Gbps rate.

Here's a somewhat recent discussion about wifi calling behind pfsense:

https://forum.netgate.com/topic/143639/at-times-wifi-calling-and-sending-sms-doesn-t-work

Jeff

When you try to log in to Skype you are not logged in It does not show any error message.
In the Squid log when I try to log in it does not show any errors.

I have configured two aliases, in which I have introduced the skype domains and the skype networks found in this post

https://forum.netgate.com/topic/107516/solucionado-pfsense-version-2-3-2_1-liberar-skype-y-whatsapp-de-toda-la-red-lan/5

followed the steps of this post and failed to solve it

What can I do to solve the problem?

uhm I should have warnings coming from my server if it was that, r710 poweredge with centos, dell manager say it's all ok on my raid.
i will try qemu/kvm

yes i am aware and it is f'n tragic. people dont have any privacy anymore. its done. or maybe internet privacy was a joke to begin with. like the internet was invented for this purpose. to track everyone. not worldwide communication and sharing of knowledge and ideas like we've been led to believe. makes me wonder where neo is. ha

So I just ended up using one of my extra ports to reconfigure the vlan on it. I deleted all the other instances and redid the firewall rules. It now works. I don't know what the issue was. It's probably cleaner to keep the vlan on it's own port and not shared with my lan port. Thanks for your replies.

Ok thanks.

its not dns broadcasting... It would be the client doing a netbios broadcast for the hostname... Hey who is called somehost..

So your clearly not doing dns redirection.

So you want to set it up correctly.. Point your clients to pfsense, or some other local NS that will resolve all your local resources, and will then forward or resolve all your public dns needs.

Pointing clients to outside NS is not going to allow you to actually resolve any local resources, nor will it give you the ability to block bad stuff.. You have no control over the dns at all when you tell client to use 8.8.8.8 for their dns..

But if you have them point to something local for dns, say pfsense - you then can control stuff by blocking stuff you don't want them to get to.. You can resolve say www.whatever.com to the local IP its hosted off of, vs getting the public IP for this fqdn and having to use nat reflection.

Also pointing clients locally allow you save some bandwidth, because if client A looks up www.something.com, and then client B asks for it its already cached at your local dns, and doesn't have to be looked up again, etc.

So fix it already - not really sure why we are stilling having this discussion ;)

Yeah it would be hard to do. Most things like that involve edits to multiple sections.

You could maybe diff the configs against default and then apply it as a patch. But you would likely only be able to apply one patch as subsequent patches would not apply cleanly.

Steve

@PhlMike said in Looking for syslogs to update my cyberattackmaps website:

That is interesting, I have over 100 pfSense firewalls and I use pfmonitor as well, I could probably aggregate something if I can figure out how to automate it and remove anything sensitive.

That could be interesting indeed. If you like to give it a try, maybe for just 1 one them, please let me know. If you want to I can also try make a TCP (ssl) port available instead of UDP. But then you will need some customization (syslog-ng forwarding?) in pfsense in order to send to that I believe.