@sf Use firewall rules on your LAN interface to direct all traffic from specified LAN IPs to the gateway you want. pfSense calls it Policy Routing: Policy Routing Configuration Placement of the rules are important as the order matters so make sure you place your rule so that it matches the traffic before other general rules.

Hmm, Nextcloud adding forwards with UPnP?

@chudak See this thread for a comparison. Right now they are similar. Long term, the FAQ (from a year ago) mentioned in an earlier post in that thread talks about a new GUI and other things.

@proxymoxy thank you, i had the same situation here, restarting php-fpm solved it. Don´t know what happens after next reboot ....

@stephenw10 I just like small steps to understand what I'm doing

@spacey said in Going on day 9 without home internet and what caused it was experimenting around and trying to find the best possible configuration for my 2.5GB NICs intel 11th gen Mini PC that receive recently: I don't know why I'm even paying for sense plus when I get this kind of customer support0 Please give me your support ticket number so I can review this. I still see no tickets from this email address so I assume you used a different one. Which would make sense since I don't see any support subscriptions on it either. @spacey said in Going on day 9 without home internet and what caused it was experimenting around and trying to find the best possible configuration for my 2.5GB NICs intel 11th gen Mini PC that receive recently: What I don't get is why static assign devices like my iPhone for example or my PC can't communicate with another statically assigned device in DHCP or even my switch for example it would refuse the connection If those devices are in the same subnet that traffic doesn't go through pfSense at all. So I would look at something in the same layer 2 like maybe port isolation on the switch. @spacey said in Going on day 9 without home internet and what caused it was experimenting around and trying to find the best possible configuration for my 2.5GB NICs intel 11th gen Mini PC that receive recently: it would show that there's no bootable device found and I went through bios settings Either the install image is not on the USB stick correctly (try using Etcher) or it's a BIOS like you looked for or it's a hardware issue like a bad USB driver or bad port. Steve

Hmm, I assume CPU usage is minimal during this test? Try running at the CLI during the test: top -aSH Can you see the expected throughput between internal interfaces? Steve

@netfly It didnt matter to SAK here in CH. Plugged the converter and the ASUS RTAAX88U and voila.....no need for VLAN on WAN.

I found another thread, same issue with someone who went from 2.5.1 to 2.5.2. They did this so I gave it a shot. So far so good and the ping and traceroute web pages work again.... pkg unlock icu pkg delete -f icu pkg install -yf icu I remember now I had pkg icu locked becuase it had issues with running Ubiquiti Unifi on pfSense. I can still hit the unifi page on port 8443 so it seems that upgrading from icu: 69.1,1 to icu: 70.1_1,1 is still allowing unifi to work alongside pfSense.

PPPoE is quite common, I also doubt that's the issue. It looks at least partly like hardware given the randomness. Perhaps your hardware testing os just not hitting it for some reason? Have you updated to 2.6 or 22.01 to test there?

@pete35 Solved, it is caused by wrong routing.

@stephenw10 said in Migrating to ZFS with 2.6.0 - A Couple Questions: Yes, you could use the config recovery process like that but I prefer to use either of that USB based config import methods listed there. Whatever you do make sure you've backed up the config first. Steve Performed the migration from UFS to ZFS tonight and everything went well! I did choose the "Recover config.xml" option during on the install menu, but it goes by so fast that I couldn't really tell whether it had worked correctly or not. Took the gamble and proceeded with the install anyway since I had made additional backups. In less than 5 minutes everything had completed and pfSense was booting and applying my prior configuration. Package re-installation overall went well also, however I had to manually reinstall both the OpenVPN Client Export and Nut packages (their configurations were kept fully intact though). Overall I'm really impressed with the robustness of the restore process: The last time I performed a fresh install of pfSense on this particular system was in early 2017 and there were no issues whatsoever restoring the configuration almost 5 years later after going through multiple pfSense version upgrade cycles. I also decided to move forward with the migration to pfsense Plus - both systems are now happily humming along on 22.01. Thanks again for all your help.

@gelcom I was just researching Wireguard and had just finished Tom Lawrence's tutorial on it. He's got 3 firewall rules (Firewall > Rules > Wireguard, Firewall > Rules > WAN and Firewall > NAT > Outbound) and you only mention 2 (that I can see). In case it helps, here's where he starts talking about the rules: https://youtu.be/8jQ5UE_7xds?t=365

@stephenw10 I cant recall changing it but at least I understand how this section works now. Ive backed up my config. Next I move onto mounting my hardware property and then vpn .

Well that might be all you can do then if you can't use whatever is coming into their router directly. Clearly other users are doing that since there are numerous instructions floating about like the one I linked to. Might be service dependent though. Steve

@raven20 I guess I should have read the release notes. "RAM disks have been converted to tmpfs." So it is working as it should. Thanks for the screen shot, it led me to investigate further.

@areckethennu said in Noob Question: How to Get to my NAS from the Internet?: Asustor provides a Cloud ID via their EZ-Connect service, but I don't know how trustworthy that is or what it would take to punch through pfSense. Probably nothing required in pfSense as long as the NAS can connect out. By far the safest way to connect to the NAS is using a VPN to pfSense. Probably exactly how you did it before. That way you have complete control over who can connect at all and when. A public cert really gives you nothing additional there and in fact can be argued to be worse since you don't control the CA. Use a remote access OpenVPN. https://docs.netgate.com/pfsense/en/latest/recipes/openvpn-ra.html Steve

You probably don't need SWAP at all. However you're no-where near using the available drive space so I would just keep any eye on the usage for now. Steve