Community discussions

MikroTik App
 
4GSam
newbie
Topic Author
Posts: 25
Joined: Tue Dec 28, 2010 7:49 am

VLAN Tagging on SwOS

Wed Apr 20, 2011 6:04 am

I don't want to be that guy that comes in flaming about a device, but I am at wit's end with the 250GS and VLAN tagging, and if anyone can help me out here I would thank you to no end. I have looked at the forums for weeks and have spent countless hours trying to get VLANs to work with no avail.

Setup:

RB750G Ether3 (VLAN10) -> 250GS Ether3 (VLAN10) -> Laptop (VLAN 10 ether4)

I have tried countless configs and none of them have worked.

Ingress on port 3 was set to strict and egress was set to Always Strip.
Ingress on port 4 was set to enabled and egress was set to Always Strip.

I feel like my config may be messed up there, but I have tried many different combinations that would seem logical and they have not worked wither. I am running 1.4.

I know for the laptop it should strip off the VLAN header, and I'm assuming this is on the Egress on port 4. For port 3, I'd assume the incoming traffic would be from the laptop on port 4 which is set to strict. In one config I also had egress on port 3 set to Add if Missing and I still had no luck.
 
Jeroen1000
Member Candidate
Member Candidate
Posts: 205
Joined: Fri Feb 18, 2011 2:05 pm

Re: VLAN Tagging on SwOS

Fri Apr 22, 2011 1:14 am

What are you trying to do exactly? Can't figure it out from your post.
 
4GSam
newbie
Topic Author
Posts: 25
Joined: Tue Dec 28, 2010 7:49 am

Re: VLAN Tagging on SwOS

Fri Apr 22, 2011 6:35 am

I will rephrase. I posted that the other night slightly in haste..but I am still having issues.

On my 750G, I created VLAN10 (with DHCP) on ether3. My MacBook supports VLAN tagging so I plugged it into port 3 and configured VLAN10 on the Mac and it worked as I expected (the regular ethernet interface didn't get an IP from the DHCP, but the VLAN interface did). So now I know VLANs are working.

Then, I plugged the 250GS into port 3, then plugged my MacBook into the 250GS. To keep things simple I went from Ether3 on the 750G -> Ether3 on the 250GS. Macbook is plugged into Ether4 on the 250GS.

This is the settings that I'm assuming work, but they do not. As in, my laptop cannot get an IP on port 4 from the DHCP on VLAN10.
want.png
These settings WORK, but it shouldn't have to add the VLAN tag if missing. Also, my MacBook still picks up the IP on it's VLAN10 interface, whereas shouldn't the switch strip it off before it gets to the laptop? That's what I want, and it's not working.
works.png
You do not have the required permissions to view the files attached to this post.
 
reverged
Member Candidate
Member Candidate
Posts: 270
Joined: Thu Nov 12, 2009 8:30 am

Re: VLAN Tagging on SwOS

Sat Apr 23, 2011 9:27 am

In the first example, port 4 is set to always strip on egress (exit) which means no vlan tags leave that port. Therefore, it can never be seen as tagged with vlan 10 when it reaches the Macbook. You might see the 750 dhcp leases showing "offered" for the Macbook. The 750 might be getting a dhcp request from the Macbook but the response is being stripped of the tag on egress and never reaches vlan 10 on the mac.

Uncheck force vlan id in case you want to add more vlans later - an assumption - or you want just 1 vlan? Then why vlans at all?

Set both ports to "add if missing". With the 750 and Mac you only want tagged packets. They are not switches and cannot deal with both tagged and untagged packets. (Some RB's like the 450G have switch chips that can add/remove tags) This is more important if you add non-vlan aware devices on other ports.

Make sure vlan 10 is checked for both ports on the vlans tab and forwarding is enabled between those ports.

All will be well. (Assuming you are using version 1.2 or later. Earlier versions have big problems with vlans.)
 
4GSam
newbie
Topic Author
Posts: 25
Joined: Tue Dec 28, 2010 7:49 am

Re: VLAN Tagging on SwOS

Tue May 03, 2011 6:16 am

I went back to tackle this issue today and it worked like I had it in my first image.

DHCP from 750G -> Switch (tagged to untagged) -> MacBook.

It takes 60 seconds for it to get a DHCP lease! It was working the whole time, I just gave up after ~20-30 seconds. But I let it sit for a minute and boom! The correct addresses came in. I don't know why it takes this long, as it's instant without VLANs in the way.
 
vaidis
just joined
Posts: 1
Joined: Tue Jun 07, 2011 9:16 am

Re: VLAN Tagging on SwOS

Tue Jun 07, 2011 10:00 am

It was very hard to make it working for me, but after one day experiments... In my network switch connected:
1 port: connected to HP ProCurve switch
3003 vlan tagged
3002 vlan untagged ( untagged wlan, by default means vlan 1, but on HP ProCurve switch it is 3002 untagged vlan )

2 port: connected PC
3003 vlan untagged

3 port: connected PC
3002 vlan untagged

Working configurations:
Vlans table empty.
port 1: Vlan mode - disabled, default vlan ID - 1, Vlan header - add if missing.
port 2: Vlan mode - disabled, default vlan ID - 3003, Vlan header - always strip.
port 3: Vlan mode - disabled, default vlan ID - 3002, Vlan header - always strip.

Vlans table empty.
port 1: Vlan mode - optional, default vlan ID - 1, Vlan header - add if missing.
port 2: Vlan mode - optional, default vlan ID - 3003, Vlan header - always strip.
port 3: Vlan mode - optional, default vlan ID - 3002, Vlan header - always strip.

Vlans table: Vlan ID 1, 3002, 3003 ( on all ports, just for fun ).
port 1: Vlan mode - enabled, default vlan ID - 1, Vlan header - add if missing.
port 2: Vlan mode - enabled, default vlan ID - 3003, Vlan header - always strip.
port 3: Vlan mode - enabled, default vlan ID - 3002, Vlan header - always strip.

Make sure: if you have tagged and untagged vlan's, in my situation link from HP ProCurve switch, by default untagged vlan means vlan 1, but not for mikrotik, mikrotik use as untagged vlan 3002, not vlan 1 !!!!!!!!!!