Outside of that space, it doesn't.Ģ07.xx.xx.101/24 assigned on public side (207.xx.xx.0/24 handed off to us from our upstream > ip firewall /ip firewall nat> printįlags: X - disabled, I - invalid, D - dynamicĠ General use NATed Ips mapped to 207.xx.xx.0/24Ĭhain=dstnat action=netmap to-addresses=172.20.103.0-172.20.103.255 dst-address=207.xx.xx.0/24ġ General use NATed Ips mapped to 207.xx.xx.0/24Ĭhain=srcnat action=netmap to-addresses=207.xx.xx.0-207.xx.xx.255 /ip address> printġ0 207.xx.xx.102/24 207.xx.xx.0 207.xx.xx.255 /ip route> printįlags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,ī - blackhole, U - unreachable, P - prohibit As long as that is set to the corresponding public IP mapped to the private netmapped IP you are trying to use, it works. The important factor in the route is the preferred source. So, for example, for 207.xx.xx.102/24 assigned to the public interface netmapped to 172.20.103.102/24 works great. I'm fine as long as I assign a corresponding public IP from the /24 space that I'm using in the /24 netmapped private space. Sounds good, but I can't seem to make this routing work.
0 Comments
Leave a Reply. |