@gertjan said in Pfsense with Microsof Teams: @yacud : By any chance, you're not running a cloud based bitcoin cracker in the background ? More serious : pfSense could be used on a POTS modem based 33.6 kbits land line. Video wouldn't work then - sound would be bad. The very same pfSense can be used to connect an entire "1000 employees" company over a 10 Gig line. Some factors : The hardware you use. This includes your own device, and wifi AP if you use them. The settings you use (the default settings doesn't limit you at all). The interconnections you use - your LAN's and WAN's. So, make up the complete list - and you won't be needing us to find your answer. Hi. I was just wondering if you were able to implement your idea? A very interesting version of implementing an ordinary project.

@thetevfik said in Random Reboot with Exiting on signal 15: What can I check? Stop using snort (and any other 'big' packages) and recheck. syslog received a sigterm 15, that's probably part of a process restart, which can happen and is not extraordinary. The system goes down without any special log lines6 minutes later. Check other log files for events during the couple of minutes before Apr 25 07:24:16.

@mtarbox said in sshguard and oddities in the daily system log email: Nothing is hammering on the logs Most probably because it isn't the 'ssh' server that hammers itself. Some other process still keeps on going on port 22, but doesn't know that the ones living there has moved. So sshguard won't see the warning messages from the ssh server in the logs and doesn't add its own. Nothing in the logs doesn't mean nothing is happening. If there is a rogue ssh client running somewhere, it should be detected and be accounted for. wireshark on interface LAN host adresses "192.168.2.1" TCP port 22" and see what pops up. Try all the interfaces.

SOLVED I since upgraded to 2.6.0-DEVELOPMENT and the GUI as well as environment has been stable for about 6 hours now with no packet loss.

@fireix Possibly a sort of state timeout. Basically, connections which are in use (while transmitting packets) don't timeout. The timeout counter starts after the last packet is transmitted. However, I'm not familiar with your tool. Maybe it opens multiple connections to the other host which are partly idle while syncing. You may look up the docs for details on state timeouts in pfSense: https://docs.netgate.com/pfsense/en/latest/config/advanced-firewall-nat.html. For troubleshooting you can add a pass rule to the top of the rule set allowing the access to the remote host and set a high timeout in the advanced options.

Anyone who can help or familiar with this?

@ofloo Read http://nginx.org/en/docs/http/configuring_https_servers.html Go here : https://github.com/pfsense/pfsense/blob/de9ba32bd3531ccf74e143391deaacb77e085097/src/etc/inc/system.inc#L1364 and https://github.com/pfsense/pfsense/blob/de9ba32bd3531ccf74e143391deaacb77e085097/src/etc/inc/system.inc#L1396 and make the listen (and IPv6 listen) more restrictive. Be careful : there is no such thing as a default LAN interface. You could hard code the IP of the interface t to listen to. Or extract it from $g['interfaces'['lan']['ipaddr']

@squirrelly the end of an era https://www.netgate.com/blog/announcing-pfsense-plus.html

It seems to be a common issue: https://forum.netgate.com/topic/161324/openvpn-is-not-working-if-client-is-reconnected-immediately/14 It works by adding "nobind" or "lport 0" to client cfg file.

Thanks a lot guys - amazing great help always here

@jimbo-1 Please look at this to restore your default firewall: https://docs.netgate.com/pfsense/en/latest/config/factory-defaults.html Then read these: https://docs.netgate.com/pfsense/en/latest/firewall/best-practices.html https://docs.netgate.com/pfsense/en/latest/recipes/example-basic-configuration.html You need to be able to talk to LAN net.

Compile your own image for that specific system complete with all the required hardware details and customisations. Then flash it. In reality, unless you're an experienced developer with both ARM and FreeBSD, you don't. Each of the ARM devices we have built images for required significant development effort. Steve

@viragomann said in Port forwarding: @ulflaursen said in Port forwarding: Should I first forward the port from the mobile broadband router to pfSense, and the forward it further on to the Synology? Exactly this. You have to put the Synology into the LAN behind pfSense and reconfigure its IP. Then forward the traffic to pfSense WAN and again on pfSense to the Synology. Consider that pfSense does not allow access from private networks on WAN by default. So if your broadband router does masquerading on incoming forwarded traffic it might be blocked. You can enable access from private addresses in the WAN interface settings by removing the check at "Block private networks". Thanks a lot man :-) /Ulf

Do you have some sort of problem with my personal opinion of the lack of info given in this thread @papdee Yes I am a global moderator.. That has little to do with my personal opinion on specifics, just like you can post your opinion on something, so can I ;) Where did the OP give any details worth anything? Love for you to point them out to me.. Do you actually feel this thread has use to the next guy having a problem? I am not seeing it.

@cool_corona I'll try it, thanks!

@johnpoz I deleted all the Outbound NAT rules and added one as you suggested. I also disabled 'pull routes' in client config. Everything working well so far and NTP status is still showing 377's for the five individual servers. I presently have 1.1.1.1 and 9.9.9.9 in System > general > DNS servers. Leak tests showing VPN public IP (good) and DNS servers as cloudflare and quad9 (should I care? Is it cloudflare trust vs VPN provider trust?). Here are my DNS Resolver settings in case I'm wrong/confused on something. [image: 1619191128573-pfsense-dns-resolver-settings.png]

@kom said in First time user / install problems: @ulflaursen said in First time user / install problems: but should the "pfSense box" not have DHCP enabled as default? When you installed it, part of the step of configuring LAN is it asks you if you want to enable DHCP and if yes then it asks for the IP range to manage. Perhaps you missed that. Give yourself a 192.168.1.2 address, login to pfSense gui and check your Services - DHCP Server settings. That, or reconfigure LAN and do the DHCP part again (option 2 in the console menu). Thanks a lot @KOM it works!! /U

Well no issue since my last update. It was the driver ;-)