1
24.7 Production Series / Re: Setting up a new leased connection - New to networking!
« on: August 20, 2024, 09:03:26 pm »
Alright.
I understand both the points.
@dseven. That is how I had configured it. Ignoring the /29 subnet. But now I realize that I need the routable public IPs to let some servers have an public IP of their own.
@doktornotor.
I have attached an image of the network that I plan to have eventually.
FYI: I need the nethserver right now as it has old insecure VPN encryption algorithms and the clients/partners aren't budging on setting up a new VPN.
To keep it short. I need to give some servers the public IPs that the new ISP has provided. I will look into disabling NAT for those specific IPs (and how that's done, if I don't get it I might reach out again).
For now, I have 2 subnets (192.168.0.0/24 and 192.168.1.0/24) running on the Nethserver. One for DHCP and direct connections and the other via openvpn resp.
I plan to put another subnet 192.168.2.0/24 on OpnSense LAN interface for clients which will go through the new ISP.
This is where I'm confused. How do I achieve both of my requirements? I'm confused in regard to the LAN configuration particularly!
On a side note, I'm unable to access the opnsense portal from the OpenVPN subnet (As of now I assigned 192.168.0.40/24 as the LAN IP to be able to access from the existing private network). I'm able to access the portal from within the office network of 192.168.0.0/24 subnet but not via VPN from the 192.168.1.0/24.
I know this is a separate discussion but if you're ok to answer it here I won't be creating a thread for this separately
I understand both the points.
@dseven. That is how I had configured it. Ignoring the /29 subnet. But now I realize that I need the routable public IPs to let some servers have an public IP of their own.
@doktornotor.
I have attached an image of the network that I plan to have eventually.
FYI: I need the nethserver right now as it has old insecure VPN encryption algorithms and the clients/partners aren't budging on setting up a new VPN.
To keep it short. I need to give some servers the public IPs that the new ISP has provided. I will look into disabling NAT for those specific IPs (and how that's done, if I don't get it I might reach out again).
For now, I have 2 subnets (192.168.0.0/24 and 192.168.1.0/24) running on the Nethserver. One for DHCP and direct connections and the other via openvpn resp.
I plan to put another subnet 192.168.2.0/24 on OpnSense LAN interface for clients which will go through the new ISP.
This is where I'm confused. How do I achieve both of my requirements? I'm confused in regard to the LAN configuration particularly!
On a side note, I'm unable to access the opnsense portal from the OpenVPN subnet (As of now I assigned 192.168.0.40/24 as the LAN IP to be able to access from the existing private network). I'm able to access the portal from within the office network of 192.168.0.0/24 subnet but not via VPN from the 192.168.1.0/24.
I know this is a separate discussion but if you're ok to answer it here I won't be creating a thread for this separately