View Full Version : VLAN Issues
clearlink
12-22-2008, 06:45 PM
Greetings --
We have two bullet5's in a test environment working out bugs before we go live with these....
here's our issue.... i spent 4 hrs on the phone with Cisco TAC today trying to resolve trunking issues between switches over a wireless bridge using the bullet 5's.... everything is set in bridge mode and there is no routing and/or firewalls enabled on the bullets....
Here's our setup:
<cisco 6509><bullet5-a> <-- wireless --> <bullet5-b><cisco 2924xl>
If you're familiar with Cisco, you'll scratch your head at this...
the 6509 sees bullet-a and bullet-b with no issues on layer-3 using the native vlan-301....
the 6509 cannot see the 2924 on layer-3 because the dot1q trunk isn't working over the bullets and the mgt vlan is on vlan-600.. however.....
the 6509 CAN see the 2924 on layer-2 using the cisco CDP protocol
-- but --
the 2424 CANNOT see the 6509 on layer-2 using the cisco CDP protocol....
i'm pretty stumped by this and really need some opinions on what to look at.... Cisco seems to think it's something in the radios that's not being sent both-ways - which would make sense, but I have no clue where to look to find this out...
here's some more information:
the link works just fine using cisco's ISL trunking protocol, but I can't use this with ubnt stuff, because ISL is cisco-proprietary and when I establish the link using ISL - I loose all l3 connectivity with the radios :-(
here's my goal:
I want to be able to link sites together and be able to connect all of the VLANs back to our core and edge routers to respect the IP routing and ACL lists in place.... it is *SUPER* important to make this work for us!
is there something I'm missing with the configs to support VLAN tags and trunks being passed to either side????????????
please help!
clearlink
12-23-2008, 09:02 AM
I have worked again with Cisco systems this morning and have the following information to add:
When I take the bullets out of the picture and directly connect the 6509 to the 2924xl all trunks and tagging works fine. This does appear to be a problem with the radios and/or configurations of them.
clearlink
12-23-2008, 09:13 AM
Remote site config:
aaa.1.status=disabled
aaa.status=disabled
bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.1.status=enabled
bridge.1.port.2.devname=ath0
bridge.1.port.2.status=enabled
bridge.1.stp.status=enabled
bridge.status=enabled
dhcpc.1.devname=br0
dhcpc.1.status=disabled
dhcpc.status=disabled
dhcpd.1.status=disabled
dhcpd.status=disabled
dnsmasq.1.devname=eth0
dnsmasq.1.status=enabled
dnsmasq.status=disabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.1.status=enabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=enabled
ebtables.3.cmd=-t broute -A BROUTING --protocol 0x888e --in-interface ath0 -j DROP
ebtables.3.status=disabled
ebtables.50.status=disabled
ebtables.51.status=disabled
ebtables.52.status=disabled
ebtables.status=enabled
httpd.port=80
httpd.status=enabled
igmpproxy.status=disabled
iptables.3.status=disabled
iptables.status=disabled
netconf.1.alias.1.status=disabled
netconf.1.alias.2.status=disabled
netconf.1.alias.3.status=disabled
netconf.1.alias.4.status=disabled
netconf.1.alias.5.status=disabled
netconf.1.alias.6.status=disabled
netconf.1.alias.7.status=disabled
netconf.1.alias.8.status=disabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.promisc=enabled
netconf.1.status=enabled
netconf.1.up=enabled
netconf.2.alias.1.status=disabled
netconf.2.alias.2.status=disabled
netconf.2.alias.3.status=disabled
netconf.2.alias.4.status=disabled
netconf.2.alias.5.status=disabled
netconf.2.alias.6.status=disabled
netconf.2.alias.7.status=disabled
netconf.2.alias.8.status=disabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=enabled
netconf.3.devname=br0
netconf.3.ip=70.46.182.214
netconf.3.netmask=255.255.255.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
ppp.1.password=
ppp.1.status=disabled
ppp.status=disabled
radio.1.ack.auto=enabled
radio.1.acktimeout=25
radio.1.chanshift=5
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.ieee_mode=a
radio.1.mcastrate=6M
radio.1.mode=managed
radio.1.rate.auto=enabled
radio.1.rate.max=54M
radio.1.rx_antenna=1
radio.1.rx_antenna_diversity=disabled
radio.1.status=enabled
radio.1.tx_antenna=1
radio.1.tx_antenna_diversity=disabled
radio.1.txpower=19
radio.countrycode=840
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.nameserver.1.ip=70.46.182.5
resolv.nameserver.1.status=enabled
resolv.nameserver.2.ip=70.46.182.6
resolv.nameserver.2.status=enabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=70.46.182.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
users.1.name=ubnt
users.1.password=VvpvCwhccFv6Q
users.1.status=enabled
users.status=enabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.devname=ath0
wireless.1.hide_ssid=disabled
wireless.1.macclone=disabled
wireless.1.scan_list.status=disabled
wireless.1.security=none
wireless.1.ssid=CLEARLINK
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled
clearlink
12-23-2008, 09:13 AM
Local Site Config:
aaa.1.status=disabled
aaa.status=disabled
bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.1.status=enabled
bridge.1.port.2.devname=ath0
bridge.1.port.2.status=enabled
bridge.1.stp.status=enabled
bridge.status=enabled
dhcpc.1.devname=br0
dhcpc.1.status=disabled
dhcpc.status=disabled
dhcpd.1.status=disabled
dhcpd.status=disabled
dnsmasq.1.devname=eth0
dnsmasq.1.status=enabled
dnsmasq.status=disabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.1.status=disabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=disabled
ebtables.3.cmd=-t broute -A BROUTING --protocol 0x888e --in-interface ath0 -j DROP
ebtables.3.status=disabled
ebtables.50.status=disabled
ebtables.51.status=disabled
ebtables.52.status=disabled
ebtables.status=enabled
httpd.port=80
httpd.status=enabled
igmpproxy.status=disabled
iptables.3.status=disabled
iptables.status=disabled
netconf.1.alias.1.status=disabled
netconf.1.alias.2.status=disabled
netconf.1.alias.3.status=disabled
netconf.1.alias.4.status=disabled
netconf.1.alias.5.status=disabled
netconf.1.alias.6.status=disabled
netconf.1.alias.7.status=disabled
netconf.1.alias.8.status=disabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.promisc=enabled
netconf.1.status=enabled
netconf.1.up=enabled
netconf.2.alias.1.status=disabled
netconf.2.alias.2.status=disabled
netconf.2.alias.3.status=disabled
netconf.2.alias.4.status=disabled
netconf.2.alias.5.status=disabled
netconf.2.alias.6.status=disabled
netconf.2.alias.7.status=disabled
netconf.2.alias.8.status=disabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=enabled
netconf.3.devname=br0
netconf.3.ip=70.46.182.213
netconf.3.netmask=255.255.255.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
ppp.1.password=
ppp.1.status=disabled
ppp.status=disabled
radio.1.ack.auto=enabled
radio.1.acktimeout=25
radio.1.channel=161
radio.1.chanshift=5
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.ieee_mode=a
radio.1.mcastrate=6M
radio.1.mode=master
radio.1.rate.auto=enabled
radio.1.rate.max=54M
radio.1.rx_antenna=1
radio.1.rx_antenna_diversity=disabled
radio.1.status=enabled
radio.1.tx_antenna=1
radio.1.tx_antenna_diversity=disabled
radio.1.txpower=19
radio.countrycode=840
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.nameserver.1.ip=70.46.182.5
resolv.nameserver.1.status=enabled
resolv.nameserver.2.ip=70.46.182.6
resolv.nameserver.2.status=enabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=70.46.182.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
users.1.name=ubnt
users.1.password=VvpvCwhccFv6Q
users.1.status=enabled
users.status=enabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.devname=ath0
wireless.1.hide_ssid=disabled
wireless.1.mac_acl.1.mac=
wireless.1.mac_acl.1.status=disabled
wireless.1.mac_acl.10.mac=
wireless.1.mac_acl.10.status=disabled
wireless.1.mac_acl.11.mac=
wireless.1.mac_acl.11.status=disabled
wireless.1.mac_acl.12.mac=
wireless.1.mac_acl.12.status=disabled
wireless.1.mac_acl.13.mac=
wireless.1.mac_acl.13.status=disabled
wireless.1.mac_acl.14.mac=
wireless.1.mac_acl.14.status=disabled
wireless.1.mac_acl.15.mac=
wireless.1.mac_acl.15.status=disabled
wireless.1.mac_acl.16.mac=
wireless.1.mac_acl.16.status=disabled
wireless.1.mac_acl.2.mac=
wireless.1.mac_acl.2.status=disabled
wireless.1.mac_acl.3.mac=
wireless.1.mac_acl.3.status=disabled
wireless.1.mac_acl.4.mac=
wireless.1.mac_acl.4.status=disabled
wireless.1.mac_acl.5.mac=
wireless.1.mac_acl.5.status=disabled
wireless.1.mac_acl.6.mac=
wireless.1.mac_acl.6.status=disabled
wireless.1.mac_acl.7.mac=
wireless.1.mac_acl.7.status=disabled
wireless.1.mac_acl.8.mac=
wireless.1.mac_acl.8.status=disabled
wireless.1.mac_acl.9.mac=
wireless.1.mac_acl.9.status=disabled
wireless.1.mac_acl.policy=allow
wireless.1.mac_acl.status=disabled
wireless.1.macclone=disabled
wireless.1.security=none
wireless.1.ssid=CLEARLINK
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled
UBNT-Mike.Ford
12-23-2008, 09:18 AM
Hello,
Please set one bullet to AP/WDS mode, and set the second unit into STA/WDS mode. This will act as a true transparent bridge.
Please let me know how this works.
Thanks,
Mike
flea4fly
02-01-2010, 10:46 PM
Hello,
Please set one bullet to AP/WDS mode, and set the second unit into STA/WDS mode. This will act as a true transparent bridge.
Please let me know how this works.
Thanks,
Mike
i have set my bullet as WDS..
after i do that setup i can't manage my bullet from its management IP..
i set to switchport trunk (vlan tag)