<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Airespace AP &amp; switch connection in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570991#M65473</link>
    <description>&lt;P&gt;A cisco 1010 that runs multiple Wlans which are connected to diffrent dynamic interfaces (with version 4.x aireos). Must that AP be connected as a trunk to the switch? And if yes does it then mean that for each wlan there is a different tunnel to the controller tagged with it's propper vlan from the dynamic interface. &lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 19:37:53 GMT</pubDate>
    <dc:creator>diro</dc:creator>
    <dc:date>2021-07-04T19:37:53Z</dc:date>
    <item>
      <title>Airespace AP &amp; switch connection</title>
      <link>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570991#M65473</link>
      <description>&lt;P&gt;A cisco 1010 that runs multiple Wlans which are connected to diffrent dynamic interfaces (with version 4.x aireos). Must that AP be connected as a trunk to the switch? And if yes does it then mean that for each wlan there is a different tunnel to the controller tagged with it's propper vlan from the dynamic interface. &lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 19:37:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570991#M65473</guid>
      <dc:creator>diro</dc:creator>
      <dc:date>2021-07-04T19:37:53Z</dc:date>
    </item>
    <item>
      <title>Re: Airespace AP &amp; switch connection</title>
      <link>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570992#M65474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;no, it does not need to be a trunk.  it will work as an access port with no problem.  The only time you need to have the port configured as a trunk port is when you are in RLDP mode.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jul 2006 16:48:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570992#M65474</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2006-07-17T16:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: Airespace AP &amp; switch connection</title>
      <link>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570993#M65475</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's what i tought also, but if the ap is not on a trunk the clients which are in the same vlan as the ap recieve a dhcp address,all the other clients belonging to other vlan's don't receive a dhcp address. But when i turn on the trunk between ap and switch everybody gets an ip adrress from their associated vlan. Any ideas?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jul 2006 14:51:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570993#M65475</guid>
      <dc:creator>diro</dc:creator>
      <dc:date>2006-07-18T14:51:47Z</dc:date>
    </item>
    <item>
      <title>Re: Airespace AP &amp; switch connection</title>
      <link>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570994#M65476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The LWAP / Airespace sends everything back to the controller encapsulated in IAPP (maybe not IAPP, but it's encaps'd). All of the traffic travels through this tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Back at the controller, the various VLANs are broken out and routed accordingly ... and any services (like DHCP) must be available at the controller. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, the interface on the router for VLAN_X must have an "IP-HELPER" statement that point to VLAN_Y where the DHCP server resides. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The easiest way to look at it (to my possibly limited understanding) is to think of the controller as having the same connection / configuration as an L2 switch - any VLANs will require a router for VLAN-to-VLAN communication. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unless you have a DHCP server on each segment/VLAN, you need to direct the traffic (by way of an IP-HELPER address on the client-side router interface) towards the single DHCP server (which should have multiple scopes defined, one per VLAN).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good Luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jul 2006 15:12:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570994#M65476</guid>
      <dc:creator>scottmac</dc:creator>
      <dc:date>2006-07-18T15:12:12Z</dc:date>
    </item>
    <item>
      <title>Re: Airespace AP &amp; switch connection</title>
      <link>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570995#M65477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That was all done and true that's the theory i know to, but still with trunk the dhcp did work without it, it didn't.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jul 2006 18:21:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/airespace-ap-switch-connection/m-p/570995#M65477</guid>
      <dc:creator>diro</dc:creator>
      <dc:date>2006-07-18T18:21:07Z</dc:date>
    </item>
  </channel>
</rss>

