Hi guys,   I'm deploying a CUBE SBC hanging off our Meraki MX What I've found so far is that we can do a 1:1 NAT with the MX, but it has not ALG to handle swapping out the external/internal SIP messages. CUBE is a beast, and we can write SIP profiles to do this, but I don't really want to manually intervene like that.   I'm thinking at the moment, I may just give the CUBE a public IP (same network as outside MX interface) on an outside interface, and then give it an inside interface back into the MX on a DMZ.   That solution would work, but I would still rather have the CUBE behind the MX.I don't think I can route inbound traffic through the MX onto a DMZ without using NAT though? I don't think I can route inbound traffic through the MX onto a DMZ without using NAT though? (I would still want to limit traffic with firewall rules from internet to CUBE)   This also just raises the question - can I have a DMZ running public IP's without NAT?   Has anyone else tackled this? Am I missing anything?   Cheers,   Tim.   * EDIT * Just checking to see if I can do a 1:1 NAT with the same Public and LAN IP - i.e. 1.1.1.1 to 1.1.1.1 to achieve the inbound routing? ... View more