VLAN no working on WS-12-250B

[sirhc]

There are several differences in the way a ToughSwitch and a WISP Switch will handle VLANs (Packet Filtering).

We toiled around about this for quite awhile when we did our VLAN configurations.

When you define a VLAN on a switch there is a lot going on behind the scenes.

One is the VLAN filter. For instance you can tell the switch to accept any packets on a port (Tagged or UnTagged) regardless of the defined VLAN map.

So if you have a "T" on say Port 5 on VLAN ID 5 you can tell the switch to accept both Tagged and Untagged and if the packet matches the VLAN configuration (Tagged with a VLAN ID of 5) it directs it accordingly and if it does not have a VLAN Tag it just handles it as a normal switch packet and looks for the destination MAC in it's MAC table. That practice cuts down on tech support because there is a higher percentage chance that things might simply work albeit incorrectly.

This is a similar attitude by Wireless AP manufacturers, when a consumer buys an AP from a store and by default it is "OPEN" with no security which means most people will just plug it in and it works....LESS TECH SUPPORT.

We decided against this approach because as a network administrator we "wanted" to know the VLANs were setup correctly or it simply does not work.

So with our switch if a port has a U it expects and Untagged packet and if it has a T is expects a Tagged packet and under most circumstances it will discard the packets that do not match the VLAN Map for that port.

[smaicas]

Then with this configuration must work

I can understand.

ç


Sorry but i think is most complex, TRUNK PORT why ?

[sirhc]

Not sure why you have the Tagged ports on the Default VLAN ID 1 on ports 7 and 8?

The switch UI/CLI resides on the Default VLAN

[smaicas]

I try with not Tagged ports on the Default VLAN ID 1 and not work

Any idea

[sirhc]

Not really, but if it works the other way go with it I suppose, should not hurt anything.

It is hard for me to follow everyone's network layout as everybody does it differently and uses the switches with different gear and in a different way.

I just tell people using our switches for the first time to LAB it up and get it working the way you want it too then roll it out.

From that point on it should be a cookie cutter application.

All of my WISP Towers are identical for the "most" part.

[smaicas]

I have prepared a new test scenario with the following settings
MIkrotik 951 as pppoe Server on VLAN 20 (vlan20 is over ether1)
MIkrotik 951 as pppoe Client on VLAN 20 (vlan20 is over ether1)
When I make a direct connection between both it works perfectly

When the connection is made by passing traffic Netonix not working. I tested the following configurations
PORT 11 (pppoe server)
PORT 12 (pppoe client)
Create VLAN 20 and mark port Tagged à Not work
Create VLAN 20 and mark port UnTagged à Not work

MikroTik vlan configuration




Netonix config tested









In none of the cases I have gotten it to work. I need help


I have seen in the post that there is a beta versión of firmware 1.3 that fixes some problems VLAN.
From where you can download?

[sirhc]

I am not going to be much help on MikroTik or PPPoE as I do not use them.

However I do know a LOT of people are using our switches with MikroTik and PPPoE I am just not sure how many use "both"?

Hopefully someone that does will chime in here.

But we are going to release v1.3.0 FINAL maybe later today, tomorrow at the latest.

TRY SETTING THE SWITCH MTU TO 9600 ON THE WISP SWITCH ON ALL PORTS BUT LEAVE THE OTHER EQUIPMENT AT THE CURRENT MTU

I am thinking this in an MTU related issue.

[Mikea]

In Mikrotik PPPoE Server do you get any errors on Logging for PPPoE !debug?
When you have Netonix in the middle can you ping the PPPoE Server?
What MTU you have along the path and what in Netonix switch?

[smaicas]

in MIKROTIK LOG SERVER anything is show. And over neivor from cliente is not show seem like traffic is filter
When you have Netonix in the middle can you ping the PPPoE Server? NO

[sirhc]

TRY SETTING THE SWITCH MTU TO 9600 ON THE WISP SWITCH ON ALL PORTS BUT LEAVE THE OTHER EQUIPMENT AT THE CURRENT MTU
I am thinking this in an MTU related issue.

Please try this and then run through your VLAN configs