At the very least you will need to allow it to route VPN traffic on that port, otherwise your VPN connection won't work and/or won't be re-established.
I want it to drop all connections if it is not on the vpn.
It can never be on the VPN if the outer, encrypted VPN packets are not allowed on the connection. I mention it because it is one of the more complex bits to handle about your requirement, depending on if you always connect to the same IP via VPN or need to connect to a dynamic peer, possibly one you need to look up via DNS first.
The router will need to look up the IP address of the vpn server using DNS. None of the other clients on the LAN should be doing that. Point is I only want the other client devices to have access to the outside world if the VPN is connected. If it is somehow disconnected, I don’t want those other LAN client devices to access the internet.
Ah, so you don't care about software running locally on the router being able to access things without the VPN but do care if routed traffic does? You might also want to consider if the router offers services like a caching DNS server, a HTTP or SOCKS proxy,... that might look like local traffic to the network layer because a local process initiates connections at the instruction of some other system.
I accomplished this by setting a firewall rule to block all outbound traffic on that interface except to the VPN and the LAN.
Thanks! That makes sense. I’ll give this a try.
To answer my own question, in the hope that maybe it helps someone else...
So I tried
- openwrt
- dd-wrt
- tomato
- merlin
Finally I found Merlin. Merlin let me configure OpenVPN with a .ovpn file.
There is an option "Redirect Internet Traffic" you can set to "Policy Rules"
You can use CIDR notation to specify all client IPs on the subnet, e.g. 192.168.1.0/24, destination 0.0.0.0
And you can select "Block routed clients if tunnel goes down"
See also: https://www.snbforums.com/threads/vpn-what-does-redirect-internet-traffic-all-do.56145/
Also search for: killswitch
networking
Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.