Just catching this... To clarify, what you are doing is a double hop?
Thanks, Reese From: Daggett, John [mailto:[email protected]] Sent: Thursday, October 31, 2013 9:27 AM To: Enterasys Customer Mailing List Subject: RE: [enterasys] WDS - Wireless Bridge Configuration The Enterasys documentation is not useful because although it goes on for many pages about several different complex bridging configurations (which I have read through several times) there is no decent description of this very simplistic connection, other than the quarter-page that I included as an attachment. What I am looking for is a "trick" from someone who has actually done this. The issue that I am having seems to be in the remote-AP, not the remote switch. Once the AP Ethernet port is activated the remote switch seems perfectly happy and its port is up and active and not STP-blocked. It is the remote AP, including its wireless bridge link, that gets confused and goes down. Thanks anyway JD From: Kaiser, Markus [mailto:[email protected]] Sent: Thursday, October 31, 2013 10:16 AM To: Enterasys Customer Mailing List Subject: Re: [enterasys] WDS - Wireless Bridge Configuration Hi, there is a lot of documentation on our support site http://www.enterasys.com/support , which describes the features WDS (and also MESH, might be a option) and how they are configured. It's well described. Sorry, can't provide the direct links, only on my mobile phone at the moment. Is there a chance that you create a Layer 2 Loop (in the test environment) and Spanning-Tree is disabling a port and forwarding is interrupted? This is what mostly happens if WDS is setup to test it. Maybe this helps. Kind regards, Markus On Thu, Oct 31, 2013 at 2:54 PM, Daggett, John <[email protected]<mailto:[email protected]>> wrote: I think that I am trying to do something too basic to be officially documented by Enterasys, but I seem to be missing something and I am having a terrible time with it. Perhaps someone out there can help me out. I want to set up a simple point-to-point wireless "tunnel" to drive a remote Ethernet switch and wired LAN segment over a pair of 37xx AP. The documentation says that I can do this (they call it the "Wireless Bridge Configuration" of WDS) and they even have a nice little picture of exactly what I want to do. The sum-total of the documentation that I can find is in the attached JPEG however. "...you must specify on the user interface that a Satellite AP is connected to the wired LAN". Great - what do they mean by that? I have found a place on the VNS Configuration/WLAN Services screen of the controller, where I configure the WDS Service, to check a box stating that the remote satellite-AP is participating in WDS and acting as a "WDS Bridge", but things are still not working right. As long as I have the remote satellite-AP connected to a PoE switch with the Ethernet port disabled (i.e. delivering power but no Ethernet), everything works great. This is the configuration that Enterasys calls "Simple WDS" and it is wireless-only. I have the Wifi Bridge up, the remote AP is visible to the controller over the wifi bridge and I can even connect a wifi client to the remote satellite-AP over an enabled WLAN and it all works, but that isn't good enough. I also need the remote satellite-AP wired port to pass traffic into the switch on the remote side, just as it shows in the diagram for LAN Segment-2. The problem is that as soon as I "enable" the switch-port that the remote satellite-AP is attached to, it drops the wifi bridge link and seems to go off searching for a controller on the LAN Segment-2 side, and there isn't one of course. When I disable the Ethernet port again, the wifi bridge connection comes back. How do I tell the remote satellite-AP that it is attached to an independent LAN and not a segment that has a controller on it? How do I configure it to pass tunneled traffic from LAN segment-1 to LAN segment-2 over that remote wired port? Thanks JD * --To unsubscribe from enterasys, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe enterasys [email protected]<mailto:[email protected]> * --To unsubscribe from enterasys, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe enterasys [email protected]<mailto:[email protected]> * --To unsubscribe from enterasys, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe enterasys [email protected]<mailto:[email protected]> The information transmitted, including any attachments, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you received this in error, please contact the sender and delete the material from any computer. Axiall Corporation (formerly known as Georgia Gulf corporation) is a Delaware corporation. This communication may come from Axiall Corporation or one of its subsidiaries. --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
