Alias WAN IP not functioning

[BrianD]

Our R81.10 appears to not allow us to add an public ALIAS IP address, that is on a different block from the primary WAN IP.

We have several additional public IPs successfully attached to our ETH1 (external) interface via the ARP feature. However, we have some public IPs that are on a different block which requires those to be added as ALIAS's to the ETH1 interface.

The following is what I did, maybe I missed something?

1. logged into the Gaia web interface and added an ALIAS with member of ETH1 and provided the IP and subnet.

2. Went in SMARTCONSOLE and synchronized the topology which DID NOT see the ALIAS object we created in step 1.

3. Insite the SMARTCONSOLE object explorer, I created a HOST object with the public IP from step #1.

4. Created a NAT rule to forward traffic on a specific port from ANY, TO the ALIAS IP, translated to our test server on the original port.

5. Created a firewall policy to allow traffic to the ALIAS IP with any any.

[PhoneBoy]

Gateway objects only care about the physical interfaces and will ignore any aliases.
That is expected behavior.

If you use Automatic NAT rules, you don't need to create ARPs for anything (or shouldn't).
For the IPs that are aliased on your external interface, if the upstream router simply forwards those IPs to your gateway, you won't need the alias IPs either.

[BrianD]

Unfortanetly, we have to specify gateways on our other routers within the colo.

I have a new block of 32 IPs (/27) that I need to attach to the CP but can't get it to work. I've added an alias interface, attached to our ETH1 (internet), create the HOST object for that new public IP, then created the NAT and access control rules and get traffic to flow.

Since I normally need to specify a gateway on my other routers, how can I accomplish this on the CP? Adding an ALIAS with the right subnet mask, on our ETH1 interface is not doing the trick.

Thank you very much! Any information I can provide to help us please let me know.

[BrianD]

Here's what the ALIAS Interface looks like.

[Chris_Atkinson]

Typically an alias interface shouldn't be required here. 

The adjacent device simply routes the subnet to your existing external interface and you configure NAT.

What is the configuration of the adjacent device that mandates the alias interface?