<?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: MSM guest network in M and MSM Series</title>
    <link>https://community.hpe.com/t5/m-and-msm-series/msm-guest-network/m-p/6258821#M2339</link>
    <description>&lt;P&gt;What are your settings regarding "Ingress and Egress" on the Guest SSID? Do you have the right VLANs assigned, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you using HTML Based Authentication or WEP/WPA/RADIUS?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any IP Routes and Gateways configured?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Our Scenario:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Earlier in the year we struggled with connecting clients to the Internet through an Access Controlled SSID with HTML Authentication. We overcame this by configuring a Guest-SSID that egressed into the Guest VLAN (access control was not configured) Clients would connect using an 8 character WPA key changed every now and then as required.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our firewall had an interface dedicated to Guest Traffic (IP: 172.16.91.253/24) Clients would receive an IP Address from our internal DHCP Server ( eg. 172.16.91.1/24 ) this was possible with the use of dhcp ip helpers on the Guest VLAN. Clients then had the ability to connect to the internet on a filtered set of rules by the firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this gives you an idea of another possible solution for Guest Access.&lt;/P&gt;</description>
    <pubDate>Tue, 05 Nov 2013 01:07:13 GMT</pubDate>
    <dc:creator>Tim_Bawden</dc:creator>
    <dc:date>2013-11-05T01:07:13Z</dc:date>
    <item>
      <title>MSM guest network</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm-guest-network/m-p/6244293#M2312</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am facing issue in one POC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Customer Network&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Controller ACCESS port -&lt;STRONG&gt;VLAN 10&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Controller Internet port -VLAN 20&lt;/P&gt;&lt;P&gt;FIrewall LAN port -&lt;STRONG&gt;VLAN 10&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Guest users -VLAN 20&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Requirement : Guest SSID&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Customer requires controller and WAPs should be in VLAN 10 (Management VLAN)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Internet port is connected to firewall port through layer 3 switch&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;Here guest users (access controlled) &amp;nbsp;are able to reach every other vlan connected to layer 3 switch except vlan 10.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So there are not able to get internet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this right behaviour..?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My explanation : when access controlled packets destined to vlan 10 reaches controller it will look to routing table and it will find a connected route in access port.Since its a tunneled user , packet will be dropped (stateful firewall will not allow tunneled user to go to access port network )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this right explanation ...?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2013 15:57:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm-guest-network/m-p/6244293#M2312</guid>
      <dc:creator>Georgeisaac</dc:creator>
      <dc:date>2013-10-22T15:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: MSM guest network</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm-guest-network/m-p/6258821#M2339</link>
      <description>&lt;P&gt;What are your settings regarding "Ingress and Egress" on the Guest SSID? Do you have the right VLANs assigned, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you using HTML Based Authentication or WEP/WPA/RADIUS?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any IP Routes and Gateways configured?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Our Scenario:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Earlier in the year we struggled with connecting clients to the Internet through an Access Controlled SSID with HTML Authentication. We overcame this by configuring a Guest-SSID that egressed into the Guest VLAN (access control was not configured) Clients would connect using an 8 character WPA key changed every now and then as required.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our firewall had an interface dedicated to Guest Traffic (IP: 172.16.91.253/24) Clients would receive an IP Address from our internal DHCP Server ( eg. 172.16.91.1/24 ) this was possible with the use of dhcp ip helpers on the Guest VLAN. Clients then had the ability to connect to the internet on a filtered set of rules by the firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this gives you an idea of another possible solution for Guest Access.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Nov 2013 01:07:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm-guest-network/m-p/6258821#M2339</guid>
      <dc:creator>Tim_Bawden</dc:creator>
      <dc:date>2013-11-05T01:07:13Z</dc:date>
    </item>
  </channel>
</rss>

