Re: [AFMUG] reusing vlan IDs

2015-07-07 Thread That One Guy /sarcasm
I decided to use the last octet of the connecting subnet ID, it adds
another layer of complexity, but probably avoids some future disaster. Ill
probably regret doing this down the road when we his 723 million customers

On Mon, Jul 6, 2015 at 11:50 AM, Shayne Lebrun  wrote:

> On Mikrotik, if you put vlan 40, say, on interface 1, 2, 3, 4 and 5, but
> don’t actually bridge any of them together, or trunk them on layer 2,
> they’ll never see each other.
>
>
>
> *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Bill Prince
> *Sent:* Monday, July 6, 2015 12:20 PM
> *To:* af@afmug.com
> *Subject:* Re: [AFMUG] reusing vlan IDs
>
>
>
> On a MT?
>
> AFAIK, the VLANs on one port are not connected to the VLANs on another
> port. In other words, each VLAN is like a new port.
>
> You could then bridge ether1-VLANxyz to ether2-VLANxyz if you were so
> inclined.
>
>
> bp
>
> 
>
>
>
> On 7/6/2015 9:12 AM, That One Guy /sarcasm wrote:
>
> Will I break the internet of things of I reuse the same vlan ID on
> multiple ports
>
>
>
> This is solely for simplified deployment of site routers since it turns
> out I need my OSPF subnets on vlans so I dont have to keep track of a
> billion vlan IDs as well as a billion /30s
>
>
>
> The ports would not be bridged, just share a VLAN ID
>
>
>
> I assume this is a big No No, more curious on the impact of doing so
>
>
>
> --
>
> If you only see yourself as part of the team but you don't see your team
> as part of yourself you have already failed as part of the team.
>
>
>



-- 
If you only see yourself as part of the team but you don't see your team as
part of yourself you have already failed as part of the team.


Re: [AFMUG] reusing vlan IDs

2015-07-06 Thread Shayne Lebrun
On Mikrotik, if you put vlan 40, say, on interface 1, 2, 3, 4 and 5, but don’t 
actually bridge any of them together, or trunk them on layer 2, they’ll never 
see each other.

 

From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince
Sent: Monday, July 6, 2015 12:20 PM
To: af@afmug.com
Subject: Re: [AFMUG] reusing vlan IDs

 

On a MT? 

AFAIK, the VLANs on one port are not connected to the VLANs on another port. In 
other words, each VLAN is like a new port.

You could then bridge ether1-VLANxyz to ether2-VLANxyz if you were so inclined.




bp

 

On 7/6/2015 9:12 AM, That One Guy /sarcasm wrote:

Will I break the internet of things of I reuse the same vlan ID on multiple 
ports 

 

This is solely for simplified deployment of site routers since it turns out I 
need my OSPF subnets on vlans so I dont have to keep track of a billion vlan 
IDs as well as a billion /30s

 

The ports would not be bridged, just share a VLAN ID

 

I assume this is a big No No, more curious on the impact of doing so


 

-- 

If you only see yourself as part of the team but you don't see your team as 
part of yourself you have already failed as part of the team.

 



Re: [AFMUG] reusing vlan IDs

2015-07-06 Thread Faisal Imtiaz
Technically, you can get away with this... 

However in terms of best practices, it is not advisable 
(in many cases, these vlans are going to get connected to other non-mikrotik 
devices, and as such they may or may not be able to distinguish between them..) 

If you are going to do this, at the very least document the vlan id's to 
include the port #. 

Faisal Imtiaz 
Snappy Internet & Telecom 
7266 SW 48 Street 
Miami, FL 33155 
Tel: 305 663 5518 x 232 

Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net 

- Original Message -

> From: "That One Guy /sarcasm" 
> To: af@afmug.com
> Sent: Monday, July 6, 2015 12:28:24 PM
> Subject: Re: [AFMUG] reusing vlan IDs

> yes MT

> For the most part I couldnt see a time I would want to bridge the ports.

> Just something simple like saying VLAN ID 255 is reserved on the network for
> the router to router OSPF communications. the third octet of the VLAN IDs is
> always 255 so it would keep it uniform for remembering. The 4th octet is our
> site ID, I could use a combination of site IDs to each link, but then you
> run into a monkey trying to figure out which id is first and which is
> second, then they get confused and start clicking things, then it becomes a
> click orgy. next thing you know theyre at the command line with a browser
> window open googling things to type, then I end up with router herpes.

> On Mon, Jul 6, 2015 at 11:20 AM, Bill Prince < part15...@gmail.com > wrote:

> > On a MT?
> 

> > AFAIK, the VLANs on one port are not connected to the VLANs on another
> > port.
> > In other words, each VLAN is like a new port.
> 

> > You could then bridge ether1-VLANxyz to ether2-VLANxyz if you were so
> > inclined.
> 

> > bp
> 
> > 
> 
> > On 7/6/2015 9:12 AM, That One Guy /sarcasm wrote:
> 

> > > Will I break the internet of things of I reuse the same vlan ID on
> > > multiple
> > > ports
> > 
> 

> > > This is solely for simplified deployment of site routers since it turns
> > > out
> > > I
> > > need my OSPF subnets on vlans so I dont have to keep track of a billion
> > > vlan
> > > IDs as well as a billion /30s
> > 
> 

> > > The ports would not be bridged, just share a VLAN ID
> > 
> 

> > > I assume this is a big No No, more curious on the impact of doing so
> > 
> 

> > > --
> > 
> 
> > > If you only see yourself as part of the team but you don't see your team
> > > as
> > > part of yourself you have already failed as part of the team.
> > 
> 

> --
> If you only see yourself as part of the team but you don't see your team as
> part of yourself you have already failed as part of the team.


Re: [AFMUG] reusing vlan IDs

2015-07-06 Thread That One Guy /sarcasm
yes MT

For the most part I couldnt see a time I would want to bridge the ports.

Just something simple like saying VLAN ID 255 is reserved on the network
for the router to router OSPF communications. the third octet of the VLAN
IDs is always 255 so it would keep it uniform for remembering. The 4th
octet is our site ID, I could use a combination of site IDs to each link,
but then you run into a monkey trying to figure out which id is first and
which is second, then they get confused and start clicking things, then it
becomes a click orgy. next thing you know theyre at the command line with a
browser window open googling things to type, then I end up with router
herpes.

On Mon, Jul 6, 2015 at 11:20 AM, Bill Prince  wrote:

>  On a MT?
>
> AFAIK, the VLANs on one port are not connected to the VLANs on another
> port. In other words, each VLAN is like a new port.
>
> You could then bridge ether1-VLANxyz to ether2-VLANxyz if you were so
> inclined.
>
> bp
> 
>
>
> On 7/6/2015 9:12 AM, That One Guy /sarcasm wrote:
>
> Will I break the internet of things of I reuse the same vlan ID on
> multiple ports
>
>  This is solely for simplified deployment of site routers since it turns
> out I need my OSPF subnets on vlans so I dont have to keep track of a
> billion vlan IDs as well as a billion /30s
>
>  The ports would not be bridged, just share a VLAN ID
>
>  I assume this is a big No No, more curious on the impact of doing so
>
>  --
>   If you only see yourself as part of the team but you don't see your
> team as part of yourself you have already failed as part of the team.
>
>
>


-- 
If you only see yourself as part of the team but you don't see your team as
part of yourself you have already failed as part of the team.


Re: [AFMUG] reusing vlan IDs

2015-07-06 Thread Bill Prince

On a MT?

AFAIK, the VLANs on one port are not connected to the VLANs on another 
port. In other words, each VLAN is like a new port.


You could then bridge ether1-VLANxyz to ether2-VLANxyz if you were so 
inclined.


bp


On 7/6/2015 9:12 AM, That One Guy /sarcasm wrote:
Will I break the internet of things of I reuse the same vlan ID on 
multiple ports


This is solely for simplified deployment of site routers since it 
turns out I need my OSPF subnets on vlans so I dont have to keep track 
of a billion vlan IDs as well as a billion /30s


The ports would not be bridged, just share a VLAN ID

I assume this is a big No No, more curious on the impact of doing so

--
If you only see yourself as part of the team but you don't see your 
team as part of yourself you have already failed as part of the team.