OpenVPN (or better, wireguard) for remote client access.Dynamic DNS support, ideally with namecheap, but DNS-O-Matic could probably work too.Route-based and policy-based IPSec VPN support, including DNS-based endpoint support (some systems only allow you to setup a tunnel using IPs and that doesn't work if you have DHCP endpoints using dynamic-DNS) - for P2P stuff between work and home or between myself and family members homes or whatever.UPnP (because Xboxes), ideally with the ability to restrict which ports can be opened by which hosts/IPs (pfSense allows this with some basic filter statements, it uses miniupnpd in the background).I generally use DHCP reservations for most "servers" but I like to be able to give them CNAMEs, sometimes even "override" my own public domain since I use a fake/internal domain at home.
#Upnp port forward utility ver 1.00 registration
#Upnp port forward utility ver 1.00 software
I'm not married to a "software-based" setup running on commodity hardware, but I don't think there's a pre-built box out there that will really give me the flexibility I want, hence the focus on software stuff. BSD's routing and multi-wan, combined with some of the choices that pfSense developers made in how the rule ordering works, leaves a bit to be desired. I recently started down the path of multi-WAN (two different cable ISPs, Spectrum & WOW). I am fully aware of the ramifications of UPnP and don't need a lecture on it this is my home, not a business. I "require" UPnP because I have two Xboxes in the same house, and XBox Live doesn't play well with more than one if you don't have a decent UPnP daemon involved. I was actually partially responsible for the paid bounty that brought UPnP support to that system. I'm a very longtime pfSense user at home.
0 kommentar(er)
