Perhaps I'm the wrong person to answer, since I have a similar problem (multiple VLANs over a wireless bridge -- and it doesn't work yet...) but as far as I understood your problem, I would reccomend the following: Take care that on both sides of the bridge your VLANs have the same VLAN-ID. Do you have the same configuration of your up-/downlink ports on both swiches? (i.e. VLAN-1 untagged, VLAN-2 tagged). Take care that one port of each switch (the one through which you want to access the traffic from VLAN-2) transfers the data untagged (in case the attached network card does not know what to do with the VLAN tags). Perhaps, you even should consider to forbid traffic for VLAN-1 on those ports.
As I just said -- I'm just a layman, have never worked with VoIP, but that would be my approach.
thanks for the help, but I found out it was my wireless bridge configuration. I originally configured it via command prompt, I reconfigured to from the web interface and everything works now. I must of missed something on the original config....
HolgerM.
5 Posts
0
January 23rd, 2006 21:00
Hi there,
Perhaps I'm the wrong person to answer, since I have a similar problem (multiple VLANs over a wireless bridge -- and it doesn't work yet...) but as far as I understood your problem, I would reccomend the following: Take care that on both sides of the bridge your VLANs have the same VLAN-ID. Do you have the same configuration of your up-/downlink ports on both swiches? (i.e. VLAN-1 untagged, VLAN-2 tagged). Take care that one port of each switch (the one through which you want to access the traffic from VLAN-2) transfers the data untagged (in case the attached network card does not know what to do with the VLAN tags). Perhaps, you even should consider to forbid traffic for VLAN-1 on those ports.
As I just said -- I'm just a layman, have never worked with VoIP, but that would be my approach.
// Holger.
Message Edited by HolgerM. on 01-24-2006 12:45 AM
n8than1
10 Posts
0
January 24th, 2006 00:00