How common are IP Aliases on WAN interfaces?
-
How common are IP Aliases on WAN interfaces?
I am having a problem with my RCN internet connection.
I have a /28 network block with my connection.
On the WAN interface I have 146.x.x.2 assigned and I also have 146.x.x.3, 146.x.x.4, 146.x.x.5 and 146.x.x.6 configured as aliases.
The reason for multiple IPs is exposing several SSL websites on my internal network via port forwarding.
Problem is, only the dot 2 address is accessible from the Internet. I know that dot 3 – dot 6 is working on the WAN side of pfSense by testing with a laptop, but from the Internet they are unreachable.I have been trying to explain to RCN tech support that I have 2 – 6 all assigned to the same interface on the same device, but they seem to think I am crazy for doing so.
Am I?
-
IP Aliases are very common on WANs in that style of deployment on a single unit (clusters would use CARP VIPs). If you are using them purely for NAT, then either IP Alias or Proxy ARP would be the type used normally in that situation.
There are some upstream modems/sources that want each IP to have a unique MAC address, which would happen with CARP but not IP Alias. So you might try seeing if using a CARP VIP will work. Such requirements are infrequent, but it's worth trying.
-
Thanks for the info. Sorry for the REALLY late reply.
I ended up dumping RCN because their support was horrible and went back to Comcast which worked fine with IP Alias config.
If I ever run into this again and want to use the CARP option, would I need to fill in the Virtual IP Password, VHID Group or Advertising frequency when using a single firewall?
-
Talk about late? ;) This thread was from 2014… Almost 4 years late... wow.. hehehe
-
If I ever run into this again and want to use the CARP option, would I need to fill in the Virtual IP Password, VHID Group or Advertising frequency when using a single firewall?
Yes, you still need to fill that in even if it's a single unit since they are all required parameters to configure CARP.