<?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 Client gets IP address before authentication in Wireless Questions and Best Practices</title>
    <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Client-gets-IP-address-before-authentication/m-p/42976#M2101</link>
    <description>We are using web authentication and the problem is that clients are getting the IP address before entering the credentials, and they can ping, telnet on to other IP's on the same subnet etc. &lt;BR /&gt;&lt;BR /&gt;Any ideas how solve this issue?</description>
    <pubDate>Fri, 26 Aug 2016 14:39:20 GMT</pubDate>
    <dc:creator>augustas_margys</dc:creator>
    <dc:date>2016-08-26T14:39:20Z</dc:date>
    <item>
      <title>Client gets IP address before authentication</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Client-gets-IP-address-before-authentication/m-p/42976#M2101</link>
      <description>We are using web authentication and the problem is that clients are getting the IP address before entering the credentials, and they can ping, telnet on to other IP's on the same subnet etc. &lt;BR /&gt;&lt;BR /&gt;Any ideas how solve this issue?</description>
      <pubDate>Fri, 26 Aug 2016 14:39:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Client-gets-IP-address-before-authentication/m-p/42976#M2101</guid>
      <dc:creator>augustas_margys</dc:creator>
      <dc:date>2016-08-26T14:39:20Z</dc:date>
    </item>
    <item>
      <title>Re: Client gets IP address before authentication</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Client-gets-IP-address-before-authentication/m-p/42977#M2102</link>
      <description>WebAuth clients are allowed to ARP, DHCP, DNS only before authentication, when they are allowed full network access.&lt;BR /&gt;&lt;BR /&gt;Add Client Isolation to the WLAN, to prevent same AP client communications that you describe beforehand.</description>
      <pubDate>Fri, 26 Aug 2016 18:16:48 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Client-gets-IP-address-before-authentication/m-p/42977#M2102</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2016-08-26T18:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: Client gets IP address before authentication</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Client-gets-IP-address-before-authentication/m-p/42978#M2103</link>
      <description>Hi Michael,&lt;BR /&gt;&lt;BR /&gt;Thank you for quick reply. So from your comment it looks like I shouldn't be able to ping or telnet on to other devices before authentication? &lt;BR /&gt;Also let me know if I am correct thinking that client isolation will prevent communication between clients after authentication?&lt;BR /&gt;&lt;BR /&gt;What I want to achieve is that users should not be able to ping, telnet or do a packet capture before authentication but could do everything once authenticated?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Augustas</description>
      <pubDate>Tue, 30 Aug 2016 08:58:12 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Client-gets-IP-address-before-authentication/m-p/42978#M2103</guid>
      <dc:creator>augustas_margys</dc:creator>
      <dc:date>2016-08-30T08:58:12Z</dc:date>
    </item>
  </channel>
</rss>

