<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
We’d like our Openstack configuration to provide 2 ways to obtain an address on our campus network.
<div><br>
</div>
<div>First, I’ve defined an EXTERNAL network and attached a subnet from which floating IP addresses can be allocated. Then, in normal fashion, instance boot into a private tenant network and can be associated with a public IP address or not, as needed. In
this case, the proper NAT entries get created allowing instances to reach the metadata service.</div>
<div><br>
</div>
<div>I’ve also configured a FLAT shared network and associated additional subnets from our campus network. When booting instances and selecting this network for their NIC attachment, the instance comes up directly on a routable address within our campus. However
the proper NAT rule is not being added to the iptables which would allow the instances to talk to the metadata service.</div>
<div><br>
</div>
<div>Assuming a subnet attached to the FLAT network is a /24 subnet with the default router at x.x.x.1 - what’s the iptable rule that needs to be manually added to iptables to allow instances to reach the metadata service.</div>
<div><br>
</div>
<div>Hopefully this is clear. Additional info can be provided if necessary.</div>
<div><br>
</div>
<div>Thanks in advance,</div>
<div>Ross</div>
<div><br>
</div>
<div apple-content-edited="true">--<br>
Ross Lillie<br>
Distinguished Member of Technical Staff<br>
Motorola Solutions, Inc.<br>
<br>
<a href="http://motorolasolutions.com">motorolasolutions.com</a><br>
O: +1.847.576.0012<br>
M: +1.847.980.2241<br>
E: ross.lillie@motorolasolutions.com<br>
<br>
<br>
<span><img height="33" width="277" apple-inline="yes" id="7510683A-39E3-4AC8-8266-670CF2DD7DC9" apple-width="yes" apple-height="yes" src="cid:75FF7557-F6FD-4406-A0BB-5CBD9BE3780A@comm.mot.com"></span></div>
<br>
</body>
</html>