- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Wired clients on RAP's uplink port
Wired clients on RAP's uplink port
06-24-2013 04:34 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: Wired clients on RAP's uplink port
Re: Wired clients on RAP's uplink port
06-24-2013 05:20 AM
- Make sure that the VLAN exist on your controller and trunked if it doesn't live there
- Enable the wired AP and make it trusted if you are not planning to do any authentication on that port
- Add this config to the port you are planning to use
Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: Wired clients on RAP's uplink port
Re: Wired clients on RAP's uplink port
06-24-2013 09:07 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: Wired clients on RAP's uplink port
Re: Wired clients on RAP's uplink port
06-24-2013 09:24 AM
Sorry I am still a little bit confuse on what you are trying to accomplish
If you have e0 serving as the uplink (Internet) builds ipsec tunnel back to the controller , where is the wired user connected ?
Do you have a switch connected to one of the RAP ports or do you have the user connected directly into the RAP ?
RAP0-------->>>>uplink (you can only use that port you reach the controller)
RAP1-------->>>>You can configure it to handle other traffic like the one you describe
If you are using a switch make sure that you are also setting up VLAN1 as native VLAN on that trunk
Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: Wired clients on RAP's uplink port
Re: Wired clients on RAP's uplink port
06-24-2013 11:44 PM
Dear Victor,
Currently I have it working with an additional switch, maybe this way it is more clear:
========= =========
| Vlan1| ---- | Rap e0|
------------| | | |
Uplink | Vlan5| ---- | Rap e1|
(Trunk) ========= =========
My problem is I have only one cable to the ceiling where the RAP stays. So I have to use the same cable for the 'external' side of the RAP (ipsec tunnel) and for the internal side (where the clients connect).
I can use the same vlan id on the controller and on the client side, so it won't be an issue to configure the port as trunk. My initial idea was to configure the E0 port as 'trunk' and have the rap to use untagged/vlan1 as 'external' side and have the 'internal' network as tagged vlan on the same cable. But it didn't work, it seems that the RAP doesn't send me out any tagged traffic on the uplink port.
So I'm currently using the additional switch to consolidate both networks into one wire again. It's not beautiful because I have an additional ugly box hanging on the ceiling next to the Aruba AP but this solution currently works. It would be much smarter if we find a way to use the same port as uplink and for the wired clients on the AP. This would even allow me to use an AP105 as RAP and power it via PoE, so I can also remove the power cords ;)
Thanks & Bye,
Chris
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: Wired clients on RAP's uplink port
Re: Wired clients on RAP's uplink port
06-25-2013 05:35 PM
This was the key info "AP105 as RAP and power it via PoE" since you don't have any additional ports available on the IAP105, unfortunately you cant use the uplink port e0 in that way as you already found out.
Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator