-
I have asked this once before, but didn't get anywhere with the answers - so, here it is again!!
I have a situation where a bonded 3 line ADSL (with about 10 usable IP addresses, because I can't use the first and last ones as their are broadcast & network IPs. There is also a virtual default gateway address that I'm told to point the WAN access to).
On the LAN side, it is a vLan situation whuch I've set up about correctly. The only bit I need to do now is sort of where/how I enter the WAN details (I've then got to give most of the vLans a dedicated WAN IP address - only a couple will share).I'm now lost and would like any help I can get!
-
Interfaces > WAN for the WAN IP details, Firewall > NAT > Outbound for the outgoing IP addresses for each network.
-
I have a situation where a bonded 3 line ADSL (with about 10 usable IP addresses, because I can't use the first and last ones as their are broadcast & network IPs. There is also a virtual default gateway address that I'm told to point the WAN access to).
On the LAN side, it is a vLan situation whuch I've set up about correctly. The only bit I need to do now is sort of where/how I enter the WAN details (I've then got to give most of the vLans a dedicated WAN IP address - only a couple will share).So MLPPP using pppoe?
Set yourself up VIP's, one for each of the addresses you want to use. You can use port forwarding for your (assuming) servers or 1:1 nat after that. You should be able to search the forum for many posts on this.
-
Just saw your other posts…
Create a VIP for one of your IP's.
If you have multiple servers to point this address to then use port forwarding rules (along with corresponding firewall rules) to accomplish your goals.
If you have one server per IP then use 1:1 NAT. Add firewall rules to allow the traffic.
Rinse and repeat for each IP.
-
Most of the vLans are serverless networks - the couple with a server have just one server.
Do I need VIPs with 1:1? Or just 1:1?
-
Most of the vLans are serverless networks - the couple with a server have just one server.
But your original post said @Sensi:
(I've then got to give most of the vLans a dedicated WAN IP address - only a couple will share).
which implies a couple of VLANs will share an IP address which means you will need port forwarding to send (for example) the web requests to the server on "VLAN A" and ssh requests to the server on "VLAN B".
You need the Virtual IPs because you are using IPs not assigned to an interface.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.