WDS - Wireless Bridge Configuration

[Daggett, John]

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 ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Brian Anderson - ASI]

There is fairly extensive help on the wireless controller about WDS. Here is the link on the controller I'm on. You can search the help for Deploying WDS and you should find it:
https://1.1.1.1:5825/Help/wwhelp/wwhimpl/js/html/wwhelp.htm#href=User_Guide/hwc_wds.11.8.html<https://10.20.0.228:5825/Help/wwhelp/wwhimpl/js/html/wwhelp.htm#href=User_Guide/hwc_wds.11.8.html>


Brian Anderson
***@ArcadiaSecureIT.com<mailto:***@ArcadiaSecureIT.com>
Network Engineer
P.O. Box 30051, Edmond, OK 73003
C [phone]
F [phone]
[Arcadia]



From: Daggett, John [mailto:***@ursinus.edu]
Sent: Thursday, October 31, 2013 8:55 AM
To: Enterasys Customer Mailing List
Subject: [enterasys] WDS - Wireless Bridge Configuration


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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@arcadiasecureit.com<mailto:***@arcadiasecureit.com>

________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2014.0.4158 / Virus Database: 3615/6788 - Release Date: 10/28/13

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Daggett, John]

Thanks, but all they seem to have is the "nothing" that I showed in the attachment. Have you actually done this at your site?

JD

From: Brian Anderson - ASI [mailto:***@arcadiasecureit.com]
Sent: Thursday, October 31, 2013 10:03 AM
To: Enterasys Customer Mailing List
Subject: RE:[enterasys] WDS - Wireless Bridge Configuration

There is fairly extensive help on the wireless controller about WDS. Here is the link on the controller I'm on. You can search the help for Deploying WDS and you should find it:
https://1.1.1.1:5825/Help/wwhelp/wwhimpl/js/html/wwhelp.htm#href=User_Guide/hwc_wds.11.8.html<https://10.20.0.228:5825/Help/wwhelp/wwhimpl/js/html/wwhelp.htm#href=User_Guide/hwc_wds.11.8.html>


Brian Anderson
***@ArcadiaSecureIT.com<mailto:***@ArcadiaSecureIT.com>
Network Engineer
P.O. Box 30051, Edmond, OK 73003
C [phone]
F [phone]
[cid:***@01CED620.E9F92580]



From: Daggett, John [mailto:***@ursinus.edu]
Sent: Thursday, October 31, 2013 8:55 AM
To: Enterasys Customer Mailing List
Subject: [enterasys] WDS - Wireless Bridge Configuration


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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@arcadiasecureit.com<mailto:***@arcadiasecureit.com>

________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2014.0.4158 / Virus Database: 3615/6788 - Release Date: 10/28/13

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Brian Anderson - ASI]

We have deployed it before.

Attached is the help file that I have, perhaps your version of help is different.

From: Daggett, John [mailto:***@ursinus.edu]
Sent: Thursday, October 31, 2013 9:07 AM
To: Enterasys Customer Mailing List
Subject: RE:[enterasys] WDS - Wireless Bridge Configuration

Thanks, but all they seem to have is the "nothing" that I showed in the attachment. Have you actually done this at your site?

JD

From: Brian Anderson - ASI [mailto:***@arcadiasecureit.com]
Sent: Thursday, October 31, 2013 10:03 AM
To: Enterasys Customer Mailing List
Subject: RE:[enterasys] WDS - Wireless Bridge Configuration

There is fairly extensive help on the wireless controller about WDS. Here is the link on the controller I'm on. You can search the help for Deploying WDS and you should find it:
https://1.1.1.1:5825/Help/wwhelp/wwhimpl/js/html/wwhelp.htm#href=User_Guide/hwc_wds.11.8.html<https://10.20.0.228:5825/Help/wwhelp/wwhimpl/js/html/wwhelp.htm#href=User_Guide/hwc_wds.11.8.html>


Brian Anderson
***@ArcadiaSecureIT.com<mailto:***@ArcadiaSecureIT.com>
Network Engineer
P.O. Box 30051, Edmond, OK 73003
C [phone]
F [phone]
[Arcadia]



From: Daggett, John [mailto:***@ursinus.edu]
Sent: Thursday, October 31, 2013 8:55 AM
To: Enterasys Customer Mailing List
Subject: [enterasys] WDS - Wireless Bridge Configuration


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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@arcadiasecureit.com<mailto:***@arcadiasecureit.com>

________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2014.0.4158 / Virus Database: 3615/6788 - Release Date: 10/28/13

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@arcadiasecureit.com<mailto:***@arcadiasecureit.com>

________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2014.0.4158 / Virus Database: 3615/6788 - Release Date: 10/28/13

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Kaiser, Markus]

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

Post by Daggett, John
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 ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Daggett, John]

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:***@enterasys.com]
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 <***@ursinus.edu<mailto:***@ursinus.edu>> 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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>


* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Reese Borel]

Just catching this... To clarify, what you are doing is a double hop?


Thanks,
Reese

From: Daggett, John [mailto:***@ursinus.edu]
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:***@enterasys.com]
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 <***@ursinus.edu<mailto:***@ursinus.edu>> 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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>


* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@axiall.com<mailto:***@axiall.com>





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 ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Matthew Hunter]

I went through something similar when I was setting up my point to point bridge. I was just missing a checkbox. Your first post you mentioned a checkbox but I figured I would share this with you anyways. I've attached a screenshot of the checkbox. Once I set this the WDS bridge worked perfect.



From: Daggett, John [mailto:***@ursinus.edu]
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:***@enterasys.com]
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 <***@ursinus.edu<mailto:***@ursinus.edu>> 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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>


* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@wctc.edu<mailto:***@wctc.edu>

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Daggett, John]

Thanks. One thing that I have found while experimenting;

The WDS Service configuration has a check-box to specify "WDS Bridging" on the remote AP (not the parent). One would logically assume (though it is not documented) that this is what we need in order to do "bridging" over the remote-AP RJ45 port. In a desperate and very counter-intuitive stab, I actually clicked this check-box OFF, and then I found that at least the remote AP stayed up-and-running when the switch Ethernet port was active - although it was still not passing traffic into the attached switch.

I hate to declare that things are "broken", but I am starting to wonder.

JD



From: Matthew Hunter [mailto:***@wctc.edu]
Sent: Thursday, October 31, 2013 10:35 AM
To: Enterasys Customer Mailing List
Subject: RE: [enterasys] WDS - Wireless Bridge Configuration

I went through something similar when I was setting up my point to point bridge. I was just missing a checkbox. Your first post you mentioned a checkbox but I figured I would share this with you anyways. I've attached a screenshot of the checkbox. Once I set this the WDS bridge worked perfect.



From: Daggett, John [mailto:***@ursinus.edu]
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:***@enterasys.com]
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 <***@ursinus.edu<mailto:***@ursinus.edu>> 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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>


* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@wctc.edu<mailto:***@wctc.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Daggett, John]

Thanks;
What I am doing looks like the original attached Enterasys diagram, but without the repeater-device in the middle (which the documentation presents as optional anyway). So - there are only 2 AP at the moment, a parent and a child that is attached to the LAN segment-2.

JD

From: Reese Borel [mailto:***@axiall.com]
Sent: Thursday, October 31, 2013 10:34 AM
To: Enterasys Customer Mailing List
Subject: RE: [enterasys] WDS - Wireless Bridge Configuration

Just catching this... To clarify, what you are doing is a double hop?


Thanks,
Reese

From: Daggett, John [mailto:***@ursinus.edu]
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:***@enterasys.com]
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 <***@ursinus.edu<mailto:***@ursinus.edu>> 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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>


* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@axiall.com<mailto:***@axiall.com>




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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Reese Borel]

You are correct. In looking at ours. We had the same situation.. The Parents WDS bridge checkbox is NOT checked. We have, however, set the Radio 1 as a parent. Only the children are checked as WDS bridge. We also ran into a problem (with earlier code releases) where the children would not connect if the "Preferred Parent" or "Backup Parent" were set to "Any Parent".

To be honest we have gotten away from using WDS bridge... We switched to another lower cost P2P solution easier to configure.


Thanks,
Reese

From: Daggett, John [mailto:***@ursinus.edu]
Sent: Thursday, October 31, 2013 9:43 AM
To: Enterasys Customer Mailing List
Subject: RE: [enterasys] WDS - Wireless Bridge Configuration

Thanks. One thing that I have found while experimenting;

The WDS Service configuration has a check-box to specify "WDS Bridging" on the remote AP (not the parent). One would logically assume (though it is not documented) that this is what we need in order to do "bridging" over the remote-AP RJ45 port. In a desperate and very counter-intuitive stab, I actually clicked this check-box OFF, and then I found that at least the remote AP stayed up-and-running when the switch Ethernet port was active - although it was still not passing traffic into the attached switch.

I hate to declare that things are "broken", but I am starting to wonder.

JD



From: Matthew Hunter [mailto:***@wctc.edu]
Sent: Thursday, October 31, 2013 10:35 AM
To: Enterasys Customer Mailing List
Subject: RE: [enterasys] WDS - Wireless Bridge Configuration

I went through something similar when I was setting up my point to point bridge. I was just missing a checkbox. Your first post you mentioned a checkbox but I figured I would share this with you anyways. I've attached a screenshot of the checkbox. Once I set this the WDS bridge worked perfect.



From: Daggett, John [mailto:***@ursinus.edu]
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:***@enterasys.com]
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 <***@ursinus.edu<mailto:***@ursinus.edu>> 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 ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>


* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@wctc.edu<mailto:***@wctc.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ursinus.edu<mailto:***@ursinus.edu>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@ppg.com<mailto:***@ppg.com>





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 ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org

[Noni, Jason]

Hi John,

If you are unchecking the "Bridge" box and it starts working, it sounds
like there may be a connection between your LAN 1 and LAN 2 segments, and
when "Bridging" is enabled, there is a loop. In this case, the radio will
shut off. If you are able to successfully "disable" bridging and push that
configuration to the child AP, then it sounds like it has a network
connection somewhere.

When the WDS is deployed, the child AP should be removed from any local
network and rebooted to connect to the Parent AP. If Bridging, that LAN
segment should be isolated and will bridge back through the AP's.

We will get a GTAC case opened up and work through this with you.

Thanks,
Jason

Jason Noni | Escalation Support Engineer
Enterasys Networks
Office: 603.952.5636 | Toll Free: 800.872.8440
Email: ***@enterasys.com
Twitter ID: jason_noni

Thanks. One thing that I have found while experimenting; ****
** **
The WDS Service configuration has a check-box to specify “WDS Bridging” on
the remote AP (not the parent). One would logically assume (though it is
not documented) that this is what we need in order to do “bridging” over
the remote-AP RJ45 port. In a desperate and very counter-intuitive stab, I
actually clicked this check-box *OFF*, and then I found that at least the
remote AP stayed up-and-running when the switch Ethernet port was active –
although it was still not passing traffic into the attached switch. ****
** **
I hate to declare that things are “broken”, but I am starting to wonder. *
***
** **
JD****
** **
** **
** **
*Sent:* Thursday, October 31, 2013 10:35 AM
*To:* Enterasys Customer Mailing List
*Subject:* RE: [enterasys] WDS - Wireless Bridge Configuration****
** **
I went through something similar when I was setting up my point to point
bridge. I was just missing a checkbox. Your first post you mentioned a
checkbox but I figured I would share this with you anyways. I’ve attached
a screenshot of the checkbox. Once I set this the WDS bridge worked
perfect. ****
** **
** **
** **
*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****
** **
*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****
** **
** **
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****
** **

[Daggett, John]

I just wanted to update the community about this - because I hate it when you are left hanging and don't hear about the resolution of things.



After messing around for a long time, I came to think that my problems might be switch-based rather than AP based, especially since I was already doing what everyone here was suggesting. In my test environment I was using an Enterasys B3G-124-24P switch on the remote (LAN segment-2) end. This was a refurbished unit straight out of the box with a clean factory-default config on it - not even a password. Although others had suggested that there might be L2 looping involved, I knew that there wasn't because in this test-bed there were exactly two wires connected to the remote switch - a power-cord and the Ethernet cable of the remote satellite-AP. Furthermore, the switch port never went into blocking mode or had any other complaints.



HOWEVER;



When I did a global "disable" on spanning tree (activated by default on these switches, thank you very much) then the AP was able to remain up in bridging mode. Although I still don't understand the mechanism, it seems empirically clear that Bridged AP's don't like being attached to a STP-enabled port - whether or not there is an actual loop. God, I hate spanning tree; the most evil and ineffectual technology ever to afflict the networking world.

Thanks all

JD

From: Daggett, John
Sent: Thursday, October 31, 2013 9:55 AM
To: '***@listserv.unc.edu'
Subject: WDS - Wireless Bridge Configuration


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 ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org