<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext">Sorry my understanding is you don’t get a broadcast domain but you can easily route it as such and have a routed /24 in place.<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-AU" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#AD2A43;mso-fareast-language:EN-AU"><br>
</span><span lang="EN-AU" style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#ED7D31;mso-fareast-language:EN-AU">CONFIDENTIALITY & PRIVILEGE NOTICE</span><span lang="EN-AU" style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#AD2A43;mso-fareast-language:EN-AU"><br>
</span><span lang="EN-AU" style="font-size:8.0pt;font-family:"Arial",sans-serif;color:gray"><br>
</span><span lang="EN-AU" style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#A6A6A6">The information contained in this email and any attached files is strictly private and confidential. The intended recipient of this email may only use, reproduce,
disclose or distribute the information contained in this email and any attached files with Simtronic Technologies Pty Ltd’s permission. If you are not the intended recipient, you are strictly prohibited from using, reproducing, adapting, disclosing or distributing
the information contained in this email and any attached files or taking any action in reliance on it. If you have received this email in error, please email the sender by replying to this message, promptly delete and destroy any copies of this email and any
attachments.<br>
<br>
It is your responsibility to scan this communication and any files attached for computer viruses and other defects and recommend that you subject these to your virus checking procedures prior to use. Simtronic Technologies Pty Ltd does NOT accept liability
for any loss or damage (whether direct, indirect, consequential, economic or other) however caused, whether by negligence or otherwise, which may result directly or indirectly from this communication or any files attached.</span><span lang="EN-AU" style="font-size:8.0pt;font-family:"Times New Roman",serif;color:windowtext"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> AusNOG <ausnog-bounces@lists.ausnog.net>
<b>On Behalf Of </b>Matthew VK3EVL<br>
<b>Sent:</b> Tuesday, February 12, 2019 1:05 PM<br>
<b>To:</b> ausnog@lists.ausnog.net<br>
<b>Subject:</b> Re: [AusNOG] AWS With Megaport<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Are you sure?<o:p></o:p></p>
<p><a href="https://aws.amazon.com/directconnect/faqs/">https://aws.amazon.com/directconnect/faqs/</a><o:p></o:p></p>
<p><b>Q. Can I extend one of my VLANs to the AWS Cloud using AWS Direct Connect?</b>
<o:p></o:p></p>
<p>No, VLANs are utilized in AWS Direct Connect only to separate traffic between virtual interfaces.<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>There may be creative ways to kind of achieve it but not out of the box... megaport itself can span a broadcast domain but AWS is the limiting factor here.<o:p></o:p></p>
<p>If you know of a way around this i'd be extremely interested to know.<o:p></o:p></p>
<p>Cheers<br>
Matthew<o:p></o:p></p>
<p>On 12/02/2019 12:52, Nathan Brookfield wrote:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>100% possible :)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Nathan Brookfield<o:p></o:p></pre>
<pre>Chief Executive Officer<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Simtronic Technologies Pty Ltd<o:p></o:p></pre>
<pre><a href="http://www.simtronic.com.au">http://www.simtronic.com.au</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On 12 Feb 2019, at 12:40, Joseph Goldman <a href="mailto:joe@apcs.com.au"><joe@apcs.com.au></a> wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Hi *<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> Just wondering if the following scenario is supported for EC2 instances with AWS.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> Over megaport, I'd like to use a VXC (Or Direct Connect) - On that interface on my router, I put x.x.x.1/24, then on my EC2 instances I'd want to put x.x.x.2-254/24 directly on my compute instances, so those EC2 instances basically become a part of my broadcast domain over the VLAN on Megaport, and I can control data in/out of those instances.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> I'm fairly fresh to AWS so not entirely sure the correct way to go about it through the route tables, VPCs etc - is what I'm asking for relatively easy and possible?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks,<o:p></o:p></pre>
<pre>Joe<o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>AusNOG mailing list<o:p></o:p></pre>
<pre><a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><o:p></o:p></pre>
<pre><a href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a><o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>AusNOG mailing list<o:p></o:p></pre>
<pre><a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><o:p></o:p></pre>
<pre><a href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a><o:p></o:p></pre>
</blockquote>
</div>
</body>
</html>