<?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 Re: Case study - wireless and wired network in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/case-study-wireless-and-wired-network/m-p/712279#M29492</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Most of what you want to do can be done by associating an SSDI to a given VLAN. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can prevent one wireless client from talking to anther by enabling "Public Secure Packet Forwarding" (PSPF) on the APs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use RADIUS (or TACACS+, I believe) you can do authentication / filtering by MAC address at the AP (or you can still do it later in the network, if you want).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco ACS would be a good choice for authentication and authorization. It can do the MAC auth, it can access credentials from external databases (i.e., Microsoft AD, Novell Directory, LDAP, SQL ...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also want to use some flavor of "captive portal" (Cisco's is "BBSM") which will force guest users to acknowledge the company's "guest usage policy" before proceeding. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you looking to use standalone (Aironet) or LWAP (Airespace)? &lt;/P&gt;&lt;P&gt;You could use either, but depending on which you choose may change the back-end setup / infrastructure. &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>Sun, 26 Nov 2006 15:52:22 GMT</pubDate>
    <dc:creator>scottmac</dc:creator>
    <dc:date>2006-11-26T15:52:22Z</dc:date>
    <item>
      <title>Case study - wireless and wired network</title>
      <link>https://community.cisco.com/t5/wireless/case-study-wireless-and-wired-network/m-p/712278#M29491</link>
      <description>&lt;P&gt;Good night,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My company need to do a network project. The topology is the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Around two hundred units each one at a distinct subnet. One unit may not to communicate with other, only with router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- It's have wireless signal at any local. For this will be used access points.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Three user types will exist: 1 - The no registred ones; 2 - The registered ones but with only internet access; 3 - The registered ones with full network access. It's have 3 buildings and one CPD (building 2).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The security is the most concern (at layer 2). One idea that I have was use VLAN, one per unit. Each unit access only switch port and router port (multi-vlan port). With 3560 series switches it's possible? One cluster where one switch see others VLAN?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The idea is all unit or access point arrive at router first and there the MAC address will be denied or will not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I only have experience at to divide networks using layer 3 (per IP address). VLAN I did only in the same switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry my english, it's not my native language.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for help.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 20:17:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/case-study-wireless-and-wired-network/m-p/712278#M29491</guid>
      <dc:creator>faustopaiva27</dc:creator>
      <dc:date>2021-07-03T20:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: Case study - wireless and wired network</title>
      <link>https://community.cisco.com/t5/wireless/case-study-wireless-and-wired-network/m-p/712279#M29492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Most of what you want to do can be done by associating an SSDI to a given VLAN. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can prevent one wireless client from talking to anther by enabling "Public Secure Packet Forwarding" (PSPF) on the APs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use RADIUS (or TACACS+, I believe) you can do authentication / filtering by MAC address at the AP (or you can still do it later in the network, if you want).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco ACS would be a good choice for authentication and authorization. It can do the MAC auth, it can access credentials from external databases (i.e., Microsoft AD, Novell Directory, LDAP, SQL ...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also want to use some flavor of "captive portal" (Cisco's is "BBSM") which will force guest users to acknowledge the company's "guest usage policy" before proceeding. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you looking to use standalone (Aironet) or LWAP (Airespace)? &lt;/P&gt;&lt;P&gt;You could use either, but depending on which you choose may change the back-end setup / infrastructure. &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>Sun, 26 Nov 2006 15:52:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/case-study-wireless-and-wired-network/m-p/712279#M29492</guid>
      <dc:creator>scottmac</dc:creator>
      <dc:date>2006-11-26T15:52:22Z</dc:date>
    </item>
  </channel>
</rss>

