@ahcarak yeah whenever possible I would use the built in net and address aliases.. Because those will change if you change the IP or network on an interface.
Only time I would think makes sense to use a specific cidr, if wanting to do a subset of your actual network for something. Or if placing rules on transit or connector network interface and allowing for the downstream networks.
@phil80 we can hope - the ability to do that was available in isc dhcp as well. But never implemented.. As they start adding features for the kea integration it would be nice if they add that ability. I have no current use for it.. But it a common asked about feature for dhcp..
I am hoping they do something with the logging, the logging in kea currently is not as friendly to read as isc logging.
@provels yeah the best way to access pfsense gui while remote would be via a vpn. But it openvpn, ipsec, wireguard, tailscale - or sure a ssh tunnel via say public key auth would be what ya call it a poor mans vpn ;)
I set VLANs on my switch so that I only use the built-in NIC of the ThinkPad as LAN and the WAN connected to VLAN
👍
I forgot about that one.
Look here : pfsense on 1 network/ethernet port PC using VLANS
Way back, I actually bought that switch, so I could try the 'One NIC device' router setup. It never took the time to do it.
Hmm, that might be a little too quick. I often retest projects after a week or more. Still, you've made two helpful suggestions. I'm a little surprised others haven't experienced similar issues and frustrations. But since everything does work, a little extra scrolling is really just a first world problem.