<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div>Jose,</div><div><br></div><div>This is pretty easy on the MLX. This is also referred to as “Super Netting”.</div><div><br></div><div>The trick is to create two separate VE interfaces, one for each subnet’s default gateway, then assign both VE interfaces to the same VLAN. You will need to create the VE first before adding it to the MLX’s VLAN. </div><div><br></div><div>Config would look something like:</div><div><br></div><div>Interface ve 100 </div><div>Ip address 10.0.1.100</div><div><br></div><div>Interface ve 101</div><div>Ip address 10.0.1.101</div><div><br></div><div>Vlan 100</div><div>Router-interface</div><div>Ve 100</div><div>Ve 101</div><div><br></div><div>Apologies for not being able to confirm the exact syntax; don’t have access to a router right now. </div><div><br></div><div>Wilbur</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Charles Monson <<a href="mailto:monson@wins.net">monson@wins.net</a>><br><span style="font-weight:bold">Date: </span> Wednesday, November 12, 2014 at 6:15 AM<br><span style="font-weight:bold">To: </span> "<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>" <<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>><br><span style="font-weight:bold">Subject: </span> Re: [f-nsp] Multiple subnets on same VLAN<br></div><div><br></div><div 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"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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]--><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Do you have “no route-only” on the physical interface(s)? I’ve had trouble with routing between multiple subnets on a router-interface once and things started
behaving normally after changing that.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">- Charles
<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p><p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> foundry-nsp [<a href="mailto:foundry-nsp-bounces@puck.nether.net">mailto:foundry-nsp-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>José Santos<br><b>Sent:</b> Tuesday, November 11, 2014 6:53 PM<br><b>To:</b> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br><b>Subject:</b> [f-nsp] Multiple subnets on same VLAN<o:p></o:p></span></p><p class="MsoNormal"><o:p> </o:p></p><div><div><div><p class="MsoNormal" style="margin-bottom:12.0pt">Hi,<o:p></o:p></p></div><p class="MsoNormal" style="margin-bottom:12.0pt">I'm needing to merge two subnets that were before in two diferent VLANs in the same VLAN (attached to one untagged ethernet port) in a MLX router.<br><br>
I configured multiple IP subnets in the same router-interface and I'm experiencing a lot of network issues. I am now trying to configure the subnets, let's say
<a href="http://192.168.50.1/24">192.168.50.1/24</a>, <a href="http://192.168.51.1/24">
192.168.51.1/24</a> and <a href="http://192.168.52.1/24">192.168.52.1/24</a> in distinct virtual interfaces belonging to the same VLAN, however I am not being able to accomplish this since only one router-interface is allowed.<br><br>
I thought configuring them in different loopback ports and then configure multiple unnumered interfaces or trunk various VLANs but none of this ideas seem possible as well.
<o:p></o:p></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">Anyone knows how can I accomplish this and can provide a brief config example?
<o:p></o:p></p></div><div><p class="MsoNormal">Thank you in advance!<br><br>
-- <br>
Best Regards,<br>
José<o:p></o:p></p></div></div></div></div></div></span></body></html>