Bridging 2 4410ns with VLANs

Greetings,
I have recently purchased 2 4410n APs with the hope of bridging a couple of buildings together.  ive found that the APs do have limited support for connecting an SSID to a VLAN, and the AP even accepts tagged traffic on the wired side (obviously, for multiple vlans).  Howerver, it doesnt seem that bridging 2 of the APs together passes tagged traffic across the bridge...  am i missing something, or do the APs not send the tagged traffic across the wireless?
Thanks
Solved!
Go to Solution.

Despite this is an old topic, I want to add some crucial info which I found out after hours of searching the web and trying suggestions I found there.
My goal was to use a WDS bridge configuration with a single SSID to transport the untagged VLAN 1 and tagged VLANs 2 and 3. The last hint to define the VLANs before switching to bridge mode did not help - I did not find a way to define multiple VLANs for a single SSID in AP mode. Defining one SSID per VLAN and then going back to bridge mode with a single SSID let VLANs 2 and 3 disappear from the configuration again.
Finally, I inspected the saved configuration file of the 4410N which is plain text fortunately, and found the line that needs modification:
WDS_VLAN_List= ;a,b,...,"a" is a VLAN ID. Different IDs divided by ",". 4 VLAN IDs should be set at most
I added my three VLANs to this list on both 4410Ns, resulting in:
WDS_VLAN_List=1,2,3 ;a,b,...,"a" is a VLAN ID. Different IDs divided by ",". 4 VLAN IDs should be set at most
uploaded the configurations and voila! everything worked as desired.
I did not find a way to define this configuration in the WebGUI.
Hope this is still useful for someone else.
Hans.

Similar Messages

  • Bind external device into Hyper-V by bridging adapters and using VLAN?

    Hi,
    i tried several hours and researched the web but no solution.
    I am running a Windows Server 2012 with Hyper-V virtualizing several networks. Each network is in its own vlan (Network 1 = Vlan 100 , Network 2 = Vlan 200,  Network 3 = Vlan 300 etc.). They are all connected to an external network vSwitch TESTNET.
    This vSwitch TESTNET is connected to one NIC on the host. I can send/receive VLAN tagged packets to this NIC from outside and it works. I can reach the corresponding networks.
    NOW I have an external device which I have to physically connect to that server on a new NIC. It has to be placed into Network 1 means be reached directly from there.
    The first idea I got is to bridge this network connection with my vSwitch Testnet. Due to the fact that the virtualized Network 1 is in a vlan I also tag the new NIC with Vlan 100. Several attemps later I still can't get it working.
    1.) Is it possible to bridge a vSwitch with a physical NIC? Will the tagged vlan packets from the physical NIC be sent to the corresponding VMs with the same vlan configuration over the vSwitch Testnet?
    2.) Or Do I need to create another vSwitch for the second NIC for my external device? And afterwards bridge these two vSwitches together?
    3.) Or is the only way to add this network device to a virtual router in a virtual machine?
    Hope somebody can help me.
    Regards DrWho

    I'm not understanding why this device has to directly connect to the physical host. If it's required that it be in network 1, why can't you plug it into a physical switch in a port with a default/PVID VLAN of 1? If you directly connect it to a regular physical
    port on a computer, it won't be in a network at all, at least not as defined anywhere else in your configuration, unless that port has somehow been bound and configured as a router. The end result of all that trouble would not really different from just plugging
    it into the physical switch to begin with.
    No, you can't bind the virtual switch and another physical port together in the way that you describe.
    You can't have a device that only communicates with a particular partner AND participates on a common network beyond those two devices unless that partner is a router.
    Eric Siron Altaro Hyper-V Blog
    I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
    "Every relationship you have is in worse shape than you think."

  • Hi there, I cannot open bridge and I get this warning, "Adobe Bridge Cannot be Opened because of a problem. Check with the developer to make sure Adobe Bridge CC works with this version of Mac OS X. You may need to reinstall any updates for this applicati

    Hi there, I cannot open bridge and I get this warning, "Adobe Bridge Cannot be Opened because of a problem. Check with the developer to make sure Adobe Bridge CC works with this version of Mac OS X. You may need to reinstall any updates for this application and Mac OS X" although bridge has been running on my Mac for over a yera. I have installed all current updates for Mac and reinstalled Bridge again from CC and still get the same issue? Any advice?

    Would you please provide details about your setup?
    BOILERPLATE TEXT:
    Note that this is boilerplate text.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    etc.,
    someone may be able to help you (not necessarily this poster).
    a screen shot of your settings or of the image could be very helpful too.
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

  • Problem using Bridge Photo Downloader with new camera

    I have the new Olympus E5. I can't use the Photo Downloader in Bridge for RAW files. It doesn't convert the ORF ( RAW ) files to dng.

    No, in the last several versions of PSE for mac prior to PSE 9, Adobe Bridge was included for keywording and such. The version of bridge that ships with the big Creative Suite programs includes the full Adobe Raw Converter, the one you get with full Photoshop. Elements has always had a somewhat cut down version of the Adobe raw converter--same basic plug-in, but doesn't have all the features enabled.
    In PSE 8, for some reason the full features were not disabled in the version of bridge that ships with PSE (prior to that opening a file into the bridge converter showed you exactly the same features you got if you just opened a raw file directly into the PSE Editor's version of the converter). However, that was just a one-time thing. (I'm guessing they ran out of time or something).
    But all versions of Elements include their own raw converter, with the smaller feature set, whether or not you use Bridge or Organizer. If you don't use bridge or organizer, you can open a raw file into the Elements editor by using File>Open, and that will bring up the PSE converter window.
    In PSE 9, Adobe has stopped shipping any version of bridge, and now includes a version of the Organizer that windows PSE users have been getting. But you can still use bridge if you have it from PSE 8, only you can't update it anymore. You can still update the raw converter in PSE itself.

  • SG-300 28P switches problem with VLAN Data and Voice, working all the time as Voice VLAN

    Hi Everyone,
    Thank you very much for your help in advance. I’m pulling my hair to fix the problem.
    I  just got the new SG-300 28P switches. My Bios ordered for me. I did not  know how it runs until now... not an IOS based. I really do not know  how to configure it.
    I have 2 VLAN are Data and Voice.
    -          Data VLAN ID is 2 IP 192.168.2.X/255.255.255.0
    -          Voice VLAN ID is 200 IP 192.168.22.X/255.255.255.0
    -          I created two vlans, in switch, Data and Voice.
    -          On the port number 28, it is trunk by default, so I add Data vlan ID 2 tagged.
    -          On the port number 26, it is trunk by default, so I add Voice vlan ID 200 tagged.
    -          On the port number 27, I add Data vlan ID 2 tagged for Data vlan out.
    -          Port settings No.1
    I set it up as Trunk with Data vlan 2 untagged, and  200  Tagged (voice vlan). I plugged in a phone with a pc attached. But the  PC will get to the vlan 200 to get the DHCP address, but no from vlan 2.  The Phone works with correct vlan ip.
    -          Port settings No.2
    Trunk with vlan 1UP, 2T, and 200T. The phone is even worse. Would never pick up any IP from DHCP.
    -          Port settings No.3
    Access  with 200U...of course the phone will work... and the PC could not get  to its own vlan. Instead, the PC got an ip from the voice vlan. Not from  VLAN 2.
    I have Linksys phone I’m not sure if this help.
    For more information I setup in switch,
                - enable voice vlan
    - set the port on auto voice vlan
    - enable LLDP-MED globally
    - create a network policy to assign VLAN 200
    - assign this network policy to the port the phone is connected to.
    I  hope this information help to help me to setup Data and Voice vlans, to  plug the phone to work with vlan Voice 200 (IP rang 192.168.22.X), from  phone to Pc and pc work as Data vlan 2 (IP rang 192.168.2.X).

    I just got done setting up voice VLANs on an SF 300-24P and verified working.  This was working with Cisco 7900 series phones connected to a Cisco UC setup.
    Here's my sample config.
    Note that I edited this by hand before posting, so doing a flat out tftp restore probably won't work.  However, this should give you a clue.  Also, don't take this as 100% accurate or correct.  I've only been working with these things for about a week, though I've worked with the older Linksys SRW switches for a couple of years.  I'm a CCNP/CCDP.
    VLAN 199 is my management VLAN and is the native VLAN on 802.1q trunks.
    VLAN 149 is the data/computer VLAN here.
    VLAN 111 is the voice/phone VLAN here.
    VLAN 107 does nothing.
    interface range ethernet e(1-24)
    port storm-control broadcast enable
    exit
    interface ethernet e1
    port storm-control include-multicast
    exit
    interface ethernet e2
    port storm-control include-multicast
    exit
    interface ethernet e3
    port storm-control include-multicast
    exit
    interface ethernet e4
    port storm-control include-multicast
    exit
    interface ethernet e5
    port storm-control include-multicast
    exit
    interface ethernet e6
    port storm-control include-multicast
    exit
    interface ethernet e7
    port storm-control include-multicast
    exit
    interface ethernet e8
    port storm-control include-multicast
    exit
    interface ethernet e9
    port storm-control include-multicast
    exit
    interface ethernet e10
    port storm-control include-multicast
    exit
    interface ethernet e11
    port storm-control include-multicast
    exit
    interface ethernet e12
    port storm-control include-multicast
    exit
    interface ethernet e13
    port storm-control include-multicast
    exit
    interface ethernet e14
    port storm-control include-multicast
    exit
    interface ethernet e15
    port storm-control include-multicast
    exit
    interface ethernet e16
    port storm-control include-multicast
    exit
    interface ethernet e17
    port storm-control include-multicast
    exit
    interface ethernet e18
    port storm-control include-multicast
    exit
    interface ethernet e19
    port storm-control include-multicast
    exit
    interface ethernet e20
    port storm-control include-multicast
    exit
    interface ethernet e21
    port storm-control include-multicast
    exit
    interface ethernet e22
    port storm-control include-multicast
    exit
    interface ethernet e23
    port storm-control include-multicast
    exit
    interface ethernet e24
    port storm-control include-multicast
    exit
    interface range ethernet g(1-4)
    description "Uplink trunk"
    exit
    interface range ethernet g(1-4)
    switchport default-vlan tagged
    exit
    interface range ethernet e(21-24)
    switchport mode access
    exit
    vlan database
    vlan 107,111,149,199
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 107
    exit
    interface range ethernet e(21-24)
    switchport access vlan 111
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 111
    exit
    interface range ethernet e(1-20)
    switchport trunk native vlan 149
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 149
    exit
    interface range ethernet g(1-4)
    switchport trunk native vlan 199
    exit
    voice vlan aging-timeout 5
    voice vlan oui-table add 0001e3 Siemens_AG_phone________
    voice vlan oui-table add 00036b Cisco_phone_____________
    voice vlan oui-table add 00096e Avaya___________________
    voice vlan oui-table add 000fe2 H3C_Aolynk______________
    voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
    voice vlan oui-table add 00d01e Pingtel_phone___________
    voice vlan oui-table add 00e075 Polycom/Veritel_phone___
    voice vlan oui-table add 00e0bb 3Com_phone______________
    voice vlan oui-table add 108ccf MyCiscoIPPhones1
    voice vlan oui-table add 40f4ec MyCiscoIPPhones2
    voice vlan oui-table add 8cb64f MyCiscoIPPhones3
    voice vlan id 111
    voice vlan cos 6 remark
    interface ethernet e1
    voice vlan enable
    exit
    interface ethernet e1
    voice vlan cos mode all
    exit
    interface ethernet e2
    voice vlan enable
    exit
    interface ethernet e2
    voice vlan cos mode all
    exit
    interface ethernet e3
    voice vlan enable
    exit
    interface ethernet e3
    voice vlan cos mode all
    exit
    interface ethernet e4
    voice vlan enable
    exit
    interface ethernet e4
    voice vlan cos mode all
    exit
    interface ethernet e5
    voice vlan enable
    exit
    interface ethernet e5
    voice vlan cos mode all
    exit
    interface ethernet e6
    voice vlan enable
    exit
    interface ethernet e6
    voice vlan cos mode all
    exit
    interface ethernet e7
    voice vlan enable
    exit
    interface ethernet e7
    voice vlan cos mode all
    exit
    interface ethernet e8
    voice vlan enable
    exit
    interface ethernet e8
    voice vlan cos mode all
    exit
    interface ethernet e9
    voice vlan enable
    exit
    interface ethernet e9
    voice vlan cos mode all
    exit
    interface ethernet e10
    voice vlan enable
    exit
    interface ethernet e10
    voice vlan cos mode all
    exit
    interface ethernet e11
    voice vlan enable
    exit
    interface ethernet e11
    voice vlan cos mode all
    exit
    interface ethernet e12
    voice vlan enable
    exit
    interface ethernet e12
    voice vlan cos mode all
    exit
    interface ethernet e13
    voice vlan enable
    exit
    interface ethernet e13
    voice vlan cos mode all
    exit
    interface ethernet e14
    voice vlan enable
    exit
    interface ethernet e14
    voice vlan cos mode all
    exit
    interface ethernet e15
    voice vlan enable
    exit
    interface ethernet e15
    voice vlan cos mode all
    exit
    interface ethernet e16
    voice vlan enable
    exit
    interface ethernet e16
    voice vlan cos mode all
    exit
    interface ethernet e17
    voice vlan enable
    exit
    interface ethernet e17
    voice vlan cos mode all
    exit
    interface ethernet e18
    voice vlan enable
    exit
    interface ethernet e18
    voice vlan cos mode all
    exit
    interface ethernet e19
    voice vlan enable
    exit
    interface ethernet e19
    voice vlan cos mode all
    exit
    interface ethernet e20
    voice vlan enable
    exit
    interface ethernet e20
    voice vlan cos mode all
    exit
    interface ethernet e1
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e2
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e3
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e4
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e5
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e6
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e7
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e8
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e9
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e10
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e11
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e12
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e13
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e14
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e15
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e16
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e17
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e18
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e19
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e20
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e21
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e22
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e23
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e24
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g1
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g2
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g3
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g4
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e1
    lldp med notifications topology-change enable
    exit
    interface ethernet e2
    lldp med notifications topology-change enable
    exit
    interface ethernet e3
    lldp med notifications topology-change enable
    exit
    interface ethernet e4
    lldp med notifications topology-change enable
    exit
    interface ethernet e5
    lldp med notifications topology-change enable
    exit
    interface ethernet e6
    lldp med notifications topology-change enable
    exit
    interface ethernet e7
    lldp med notifications topology-change enable
    exit
    interface ethernet e8
    lldp med notifications topology-change enable
    exit
    interface ethernet e9
    lldp med notifications topology-change enable
    exit
    interface ethernet e10
    lldp med notifications topology-change enable
    exit
    interface ethernet e11
    lldp med notifications topology-change enable
    exit
    interface ethernet e12
    lldp med notifications topology-change enable
    exit
    interface ethernet e13
    lldp med notifications topology-change enable
    exit
    interface ethernet e14
    lldp med notifications topology-change enable
    exit
    interface ethernet e15
    lldp med notifications topology-change enable
    exit
    interface ethernet e16
    lldp med notifications topology-change enable
    exit
    interface ethernet e17
    lldp med notifications topology-change enable
    exit
    interface ethernet e18
    lldp med notifications topology-change enable
    exit
    interface ethernet e19
    lldp med notifications topology-change enable
    exit
    interface ethernet e20
    lldp med notifications topology-change enable
    exit
    interface ethernet e21
    lldp med notifications topology-change enable
    exit
    interface ethernet e22
    lldp med notifications topology-change enable
    exit
    interface ethernet e1
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e2
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e3
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e4
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e5
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e6
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e7
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e8
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e9
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e10
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e11
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e12
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e13
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e14
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e15
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e16
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e17
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e18
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e19
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e20
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e21
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e22
    lldp med enable network-policy poe-pse
    exit
    lldp med network-policy 1 voice vlan 111 vlan-type tagged
    interface range ethernet e(1-22)
    lldp med network-policy add 1
    exit
    interface vlan 199
    ip address 199.16.30.77 255.255.255.0
    exit
    ip default-gateway 199.16.30.3
    interface vlan 1
    no ip address dhcp
    exit
    no bonjour enable
    bonjour service enable csco-sb
    bonjour service enable http  
    bonjour service enable https 
    bonjour service enable ssh   
    bonjour service enable telnet
    hostname psw1
    line console
    exec-timeout 30
    exit
    line ssh
    exec-timeout 30
    exit
    line telnet
    exec-timeout 30
    exit
    management access-list Management1
    permit ip-source 10.22.5.5 mask 255.255.255.0
    exit
    logging 199.16.31.33 severity debugging description mysysloghost
    aaa authentication enable Console local
    aaa authentication enable SSH tacacs local
    aaa authentication enable Telnet local
    ip http authentication tacacs local
    ip https authentication tacacs local
    aaa authentication login Console local
    aaa authentication login SSH tacacs local
    aaa authentication login Telnet local
    line telnet
    login authentication Telnet
    enable authentication Telnet
    password admin
    exit
    line ssh
    login authentication SSH
    enable authentication SSH
    password admin
    exit
    line console
    login authentication Console
    enable authentication Console
    password admin
    exit
    username admin password admin level 15
    power inline usage-threshold 90
    power inline traps enable
    ip ssh server
    snmp-server location in-the-closet
    snmp-server contact [email protected]
    ip http exec-timeout 30
    ip https server
    ip https exec-timeout 30
    tacacs-server host 1.2.3.4 key spaceballz  timeout 3  priority 10
    clock timezone -7
    clock source sntp
    sntp unicast client enable
    sntp unicast client poll
    sntp server 199.16.30.1
    sntp server 199.16.30.2
    ip domain-name mydomain.com
    ip name-server  199.16.5.12 199.16.5.13
    ip telnet server

  • Encrypting Aironet 1410 bridge link using multiple VLANs

    I've looked at the documentation available for Aironet 1400 series, and still would like to see a single document showing an example of
    the best encryption/authentication available for bridge links using multiple VLANs.
    As I understand it, 1400 series can support WPA-PSK using AES, which would work for me.  I just can't picture how to integrate chapters 9 and 10 for the 'WEP and WEP Features' + 'Configuring Authentication Types' instructions.
    I'm looking either for an example config, or a step-by-step that did all steps consecutively.
    Thanks

    What doc are you refering to?  If you want to encrypt the link from root bridge to non-root bridge, then WPA/TKIP-PSK is what you should use.  Here is a link to how to setup your link ssid to WPA: http://www.cisco.com/en/US/docs/wireless/bridge/1400/12.2_15_JA/configuration/guide/p15auth.html#wp1044935
    Don't worry about the example they show on the WEP, just use the configuration from the above link for your encryption.
    Configuring a VLAN
    Configuring your bridge to support VLANs is a five-step process:
    1. Create subinterfaces on the radio and Ethernet interfaces.
    2. Enable 802.1q encapsulation on the subinterfaces and assign one subinterface as the native VLAN.
    3. Assign a bridge group to each VLAN.
    4. (Optional) Enable WEP on the native VLAN. <-- Use WPA-PSK
    5. Assign the bridge's SSID to the native VLAN.
    http://www.cisco.com/en/US/docs/wireless/bridge/1400/12.2_15_JA/configuration/guide/p15vlan.html
    Here is an example of vlan 1 (native) will be your management and your wireless link.  vlan 10 & 20 will pass through the link.
    BR# configure terminal
    BR(config)# interface dot11radio0.1
    BR(config-subif)# encapsulation dot1q 1 native
    BR(config-subif)# bridge group 1
    BR(config-subif)# exit
    BR(config)# interface fastEthernet0.1
    BR(config-subif)# encapsulation dot1q 1 native
    BR(config-subif)# bridge group 1
    BR(config)# interface fastEthernet0.10
    BR(config-subif)# encapsulation dot1q 10
    BR(config-subif)# bridge group 10
    BR(config)# interface fastEthernet0.20
    BR(config-subif)# encapsulation dot1q 20
    BR(config-subif)# bridge group 20
    BR(config-subif)# exit
    BR(config)# interface dot11radio0
    BR(config-if)# ssid batman
    BR(config-ssid)# vlan 1
    BR(config-ssid)# infrastructure-ssid
    BR(config-ssid)# end

  • 802.1x with VLAN assignment on Catalyst 2950T-48-SI

    I will really appreciate if you can confirm me if the C2950T-48-SI will support the following features.
    - IEEE 802.1x with VLAN assignment
    - SSHv2
    - SNMPv3
    The data sheet for the Cisco Catalyst 2950 Series Switches with Standard Image mentions all the above and more features for the 2950T-48-SI, but at the same time the power point presentation, (Cisco Catalyst 2950 Series Switches, and the tool Sofware advisor say that those features are only supported with the Enhanced Image.
    If your those feature are supported by the Standard Image, would you please also inform the last IOS version supported.
    Thanks a lot.

    SSH isn't available on the SI version of the 2950 as you require the Crypto features and these are not available for the SI (the documentation is a little vague here but trust me I have upgraded one and it doesn't like it...). The documentation says 'Switches that support only the SI cannot run the cryptographic image.'
    802.1x with VLAN assignment is available only in the latest IOS - or at least since 12.1(22).
    SNMPv3 is supported.
    HTH
    Andy

  • 871 802.1x with vlan assignment aka dynamic vlan

    you can do vlan assignment on 871W wireless using the local radius server but unfort only LEAP which is N.G.
    I have been pounding on wired 802.1x PEAP (which works) trying to get vlan re-assignment. Have tried with IAS which I am using to do vlan reassignment with the WLC so I have the idea of how it works with IAS. With 871, no go. Have also tried ACS for radius with same results: can't escape the switchport's vlan. With debug radius local you can see the tunnel attributes for reassignment plainly but with debug radius with IAS or ACS, nada.
    Using 12.4(6)T advanced IP.
    I have just seen that 12.4(4)CX2 has "802.1x with vlan reassignment" but the download is MIA. Wonder what's up with that?
    Has anybody got this to work? Any info much appreciated
    Greg Turner

    SSH isn't available on the SI version of the 2950 as you require the Crypto features and these are not available for the SI (the documentation is a little vague here but trust me I have upgraded one and it doesn't like it...). The documentation says 'Switches that support only the SI cannot run the cryptographic image.'
    802.1x with VLAN assignment is available only in the latest IOS - or at least since 12.1(22).
    SNMPv3 is supported.
    HTH
    Andy

  • How to resolve A VMWare portgroup with VLAN ID 0 cannot be founf on virtual switch vSwitch0.

    Hi All,
    I have deployed Microsoft private cloud using SCVMM, SCOM, SCCM, SCSM, SCO and SCSM Portal...
    Also, i am using cloud service process pack runbooks and offerings for my vm provisioning in VM Ware platform...
    After submitted the request vm got created but it is throwing an error in SCVMM jobs:
    A VMWare portgroup with VLAN ID 0 cannot be found on virtual switch vSwitch0...
    VLAN ID of the existing virtual switch vSwitch is 48 and that we cannot change...also we cannot create a new vswitch in DC...
    How can i resolve this error...
    Thanks in advance for your help...
    Regards,
    Sudheesh M A

    Hi Alexander,
    Thank for answering. I asked custumer to send some config file from the switch. I don´t how complete is this, but, regarding "mls cos" entries, we have:
    no aaa new-model
    switch 1 provision ws-c2960x-48ts-l
    ip domain-name ecs.local
    login on-failure trap
    login on-success log
    vtp mode transparent
    mls qos
    crypto pki trustpoint TP-self-signed-1837850112
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-1837850112
     revocation-check none
     rsakeypair TP-self-signed-1837850112
    interface GigabitEthernet1/0/1
     switchport access vlan 235
     switchport mode access
     srr-queue bandwidth share 1 70 25 5
     priority-queue out
     mls qos trust dscp
     service-policy input ACCESS_INGRESS
    interface GigabitEthernet1/0/2
     switchport access vlan 235
     switchport mode access
     srr-queue bandwidth share 1 70 25 5
     priority-queue out
     mls qos trust dscp
     service-policy input ACCESS_INGRESS
    interface GigabitEthernet1/0/48
     switchport access vlan 235
     srr-queue bandwidth share 1 70 25 5
     priority-queue out
     mls qos trust dscp
     service-policy input ACCESS_INGRESS
    Is these entries make any sense for the behavior we are facing?
    Thanks

  • Most recent update to Photoshop CC and Bridge breaks use with snow leopard. need previous vsn

    The most recent version of Bridge CC installed with adobe's updater killed my systems year long use of Bridge CC so it won't load.  I need the previous version.  I can't update to 10.7 for technical and other software workflow reasons.  How can I get back to the previous vsn that did work yesterday?

    I would guess you need to uninstall bridge cc and then reinstall without applying the 6.1 update
    (use the uninstaller in /Applications/Adobe Bridge CC)
    You can download Bridge CC direct from here
    Download New Adobe CC Trials: Direct Links (no Assistant/Manager) | ProDesignTools
    And the Bridge cc 6.0.1 update from here any others you might need
    (don't install the 6.1 bridge cc update, because that is the update that breaks bridge on 10.6.8)
    All the Adobe CC Updates: The Direct Download Links for Mac OS | ProDesignTools
    Be sure you follow the directions where it says Note: Very Important Instructions or the links won't work.

  • How do i bridge my extreme with a Verizon FIOS router?

    how do i bridge my extreme with a Verizon FIOS router?

    Unfortunately, the AirPort Extreme Base Station (AEBS) cannot be configured as a wireless Ethernet bridge. Although it can "join" the Verizon's wireless network, doing so its Ethernet ports will NOT be enabled for wired clients.

  • Connecting Half Bridge I Config with SCXI 1520 and 1314

    Hi! I'm using Half Bridge -I Configuration with SCXI 1520 and 1314, but the diagrams in the SCXI-1520 manual are not very comprehensible to me. Three questions:
    1) Is it "necessary" to connect SCx terminals?
    2) If yes, why is there no lead resistance "RL" shown?
    3) Are one end each of two strain gauges to be shorted externally, or wired all the way upto SCXI-1340?
    If u can also post a drawing with actual leads and gauges shown, it will be great.
    These questions may seem trivial, but I'm just starting with strain measurement so...
    Thanks
    Rajat

    Rajat,
    If you are wanting to perform a shunt calibration on your strain gauges then the SCA terminals will need to be connected. The reason that no lead resistance (RL) is shown is that the resistance of those leads will not be affecting the reading you are taking. Lead resistances only need to be considered when they are part of the wheatstone bridge.
    The strain gauges are R3 and R4 in figure 2-3 on page 2-7 of the SCXI-1520 User Manual (linked below). One side of the strain gauges should be connected to each other, then the other side of the strain gauges need to be connected to P+ and P-. Only connections to the right of the 1314 terminal block (in figure 2-3) are connections you will need to make. I hope this helps.
    SCXI-1520 User Manual
    http://digital.
    ni.com/manuals.nsf/webAdvsearch/ED087ED0FDB34CF586​2569DC0068992B?OpenDocument
    Regards,
    Todd D.
    Applications Engineer
    National Instruments

  • How to set all new vm with VLAN ID as a default settings and alose set the avaiablity high .

    How to set all new vm with VLAN ID as a default settings and alose set the avaiablity high .

    Hi Ramy,
    As a work around , you can create a VM without installing OS and  configure the Vlan of VNic , then export it .
    The new VM will be with Vlan ID when you import the "export file".(note : you need to select "copy the virtual machine " in the tab "choose import type" during importing ) .
    Hope this helps
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • ISP with vlan id , cannot dialup

    I use cisco 1921 k9 , made a pppoe setting, here the problem , my ISP come with a vlan ID :620, where should i input this vaule?

    HI,
    Create Sub-interface  with VLAN tag where the IPS modem/Device is connected  and then configure the Dialer interface with PPPOE setting.
    Example:
    Interface Gig 0/0 or 0/1
    no ip address
     duplex auto
     speed auto
    interface Gig0/0.620
     encapsulation dot1Q 620
     pppoe enable group global
     pppoe-client dial-pool-number 1
    end
    interface Dialer0
    ip address  xxxxxxxxxxxx
     ip mtu 1492
     ip nat enable
     encapsulation ppp
     ip tcp adjust-mss 1452
     dialer pool 1
     dialer-group 1
     ppp authentication pap chap callin
     ppp chap hostname  ( Username)
     ppp chap password ( password)
     ppp pap sent-username ( Username) password 7 (Password)
    end

  • Need basic Help - SG300 with vlan and routing

    Hi,
    i need some basic help with configuring vlan/routing.
    Situation:
    DSL Router - Cisco 300 - XenServer
    192.168.1.253 - 192.168.1.19 - 192.168.1.10 (mgmt ip)
    goal is, to reach from inside xenserver vms the internet.
    vms = 192.168.2.x
    gateway ip = 192.168.2.1
    what i did:
    - configured vlan 102, tagged, with the xenserver port
    - configured on xenserver a network with vlan id 102, attached to the vm
    - this network is conntected to an external bond
    - configured ipva4 interface: vlan102 - Static - IP 192.168.2.1 (this is the gateway ip of the vms)
    - automatic configured IPv4 Route: 192.168.2.0/24 next hop 0.0.0.0, Directly connected
    So at the moment i cant ping from inside a vm to the DSL Router (192.168.2.2 to 192.168.1.253)
    any ideas what i misconfigured or whats wrong?
    cheers,
    -Marco

    Hi Tom,
    ok, that make sense. I can ping the router now inside vms from 192.168.2.x network.
    But i cant ping external adresses, error: Destination net unreachable.
    My other problem i have, i cant reach any server from outside over router portforwarding.
    How do i have to configure the upload port to the dsl router? Is it a access port or a trunk
    port with all vlans (tagged or untagged?) At the moment ive a tagged Trunkport with all vlans.
    IPv4 Interface Table
    Interface
    IP Address Type
    IP Address
    Mask
    Status
    VLAN 1
    Static
    192.168.1.19
    255.255.255.0
    Valid
    Should the VLAN1 ip adress not the router ip adress ? Do i need an additional vlan for
    the router ? At the end i like to change the switch ip from dhcp to static (change automaticly
    when switching to layer 3 mode), but ive to look for the ios commands first.
    What else do i missing ?
    Thanks a lot,
    Marcus

Maybe you are looking for