Network list for Outbound NAT for VPN

Started by pasha-19, September 30, 2023, 12:36:36 PM

Previous topic - Next topic
September 30, 2023, 12:36:36 PM Last Edit: September 30, 2023, 01:14:51 PM by pasha-19
I am a relative newbie  I have successfully created a multi vlan router where some communication passes through an OpenVPN client for a purchased VPN connection.  I also port forward requests for all vlans like DNS and NTP over the vpn eventually.  One of the steps in the creation process for the VPN seems to require creating an alias network list for the internal (lan like) vlans to access the VPN Client that becomes the source network for Manual Hybrid Outbound LAN entries I create for the VPN Client.  I have found I can use the generated network references like __lo0_network, __lan_network, __opt?_network to build an Alias list that matches the common Source Network lists in the Automated Outbound NAT entries avoiding hardcoding network references.  Would it be reasonable for you to create a new automatic network list named something like __nat_networks (reflective of your convention) as I am and using a different name; instead of what appear to be pseudo lists in the automated rules eliminating a step in the creation of the Outbound NAT rules for the VPN Client?  It is possibly I do not fully understand the process fully; but if what I ask makes sense please consider it.