<p dir="ltr">Hi,</p>
<p dir="ltr"> Ok you got me. I read the first paragraph. Usually when we say 'dev' it means "working into production" lol</p>
<p dir="ltr"> VPC is a beast on its own. Sorry i gave up on it a while back. You'd thinknthey would just 'work' but i couldn't get it done. Thay was to reach a paying client even, many hours wasted for nothing.</p>
<p dir="ltr"> --Skyler</p>
<div class="gmail_extra"><br><div class="gmail_quote">On Sep 16, 2016 5:14 AM, "Barry Flanagan" <<a href="mailto:barry@flanagan.ie">barry@flanagan.ie</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div data-smartmail="gmail_signature">On 16 September 2016 at 11:41, Skyler <span dir="ltr"><<a href="mailto:skchopperguy@gmail.com" target="_blank">skchopperguy@gmail.com</a>></span> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">You lost me at AWS.</p></blockquote><div><br></div><div>Haha, yeah. I did say it is only a dev box.</div><div><br></div><div>-Barry</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">--Skyler</p>
<div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Sep 16, 2016 3:47 AM, "Barry Flanagan" <<a href="mailto:barry@flanagan.ie" target="_blank">barry@flanagan.ie</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi,<div><br></div><div>We are trying to move our SPCE dev platform to AWS. It works fine for external endpoints out of the box, using the advertised_address for the main interface.</div><div><br></div><div>However, we also have some other endpoints in the same VPC and I can't get SPCE to not used the advertised_ip when it is communicating with the VPC-internal endpoints - it always advertises its elastic IP.</div><div><br></div><div>I have created a second, eth1 interface for use with the VPC hosts, and my network.yml is as follows:</div><div><br></div><div><div> eth0:</div><div> advertised_ip:</div><div> - <My Elastic IP></div><div> ip: 172.31.24.242</div><div> netmask: 255.255.240.0</div><div> type:</div><div> - web_ext</div><div> - sip_ext</div><div> - rtp_ext</div><div> - web_int</div><div> - ssh_ext</div><div> eth1:</div><div> ip: 172.31.58.136</div><div> netmask: 255.255.240.0</div><div> type:</div><div> - web_ext</div><div> - sip_ext</div><div> - rtp_ext</div><div> - web_int</div><div> - ssh_ext</div><div> interfaces:</div><div> - lo</div><div> - eth0</div><div> - eth1</div><div><br></div><div><br></div><div>SPCE is communicating with the VPC hosts over eth1 as expected, but it is advertising the Elastic IP instead of 172.31.58.136. I tried adding an advertised_ip of 172.31.58.136 to eth1 as well to force it, but no go.</div><div><br></div><div>If I were able to specify a hostname in advertised_ip I could make it work by manipulating DNS, but this does not seem to work as rtpengine complains "Invalid interface specification: ext"</div><div><br></div><div>Any ideas?</div><div><br></div><div>Thanks</div><div><br></div><div><br></div><div><div>-Barry Flanagan<br><br><br><br><br><br></div></div>
</div></div>
<br></div></div>______________________________<wbr>_________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/list<wbr>info/spce-user</a><br>
<br></blockquote></div></div>
</blockquote></div><br></div></div>
</blockquote></div></div>