<?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: WESM and dynamic NAT in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/wesm-and-dynamic-nat/m-p/4144397#M13362</link>
    <description>Hi&lt;BR /&gt;&lt;BR /&gt;Usually the configuration of the WESM in the 5400/5300 switch will be encrypted, (we need agent 007's help to decrypt it) :)&lt;BR /&gt;&lt;BR /&gt;Anyway, you can explain what you've done in the Web page of the WESM and write it here.&lt;BR /&gt;&lt;BR /&gt;Good Luck !!!</description>
    <pubDate>Wed, 13 Feb 2008 15:24:54 GMT</pubDate>
    <dc:creator>Mohieddin Kharnoub</dc:creator>
    <dc:date>2008-02-13T15:24:54Z</dc:date>
    <item>
      <title>WESM and dynamic NAT</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/wesm-and-dynamic-nat/m-p/4144396#M13361</link>
      <description>The goal on this configuration is to nat the users in the wireless side (inside) of the wesm in order to browse Internet (outside), reachable trough a routing infrastructure.&lt;BR /&gt;The problem is that this configuration is not working. &lt;BR /&gt;I can't see any entry in the wesm ip nat translation table.&lt;BR /&gt;Any help would be appreciated.&lt;BR /&gt;Thanks in advance&lt;BR /&gt;Enrico</description>
      <pubDate>Wed, 13 Feb 2008 12:10:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/wesm-and-dynamic-nat/m-p/4144396#M13361</guid>
      <dc:creator>ENRICO BASSI_1</dc:creator>
      <dc:date>2008-02-13T12:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: WESM and dynamic NAT</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/wesm-and-dynamic-nat/m-p/4144397#M13362</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Usually the configuration of the WESM in the 5400/5300 switch will be encrypted, (we need agent 007's help to decrypt it) :)&lt;BR /&gt;&lt;BR /&gt;Anyway, you can explain what you've done in the Web page of the WESM and write it here.&lt;BR /&gt;&lt;BR /&gt;Good Luck !!!</description>
      <pubDate>Wed, 13 Feb 2008 15:24:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/wesm-and-dynamic-nat/m-p/4144397#M13362</guid>
      <dc:creator>Mohieddin Kharnoub</dc:creator>
      <dc:date>2008-02-13T15:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: WESM and dynamic NAT</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/wesm-and-dynamic-nat/m-p/4144398#M13363</link>
      <description>Ok&lt;BR /&gt;1) Enabled Ip routing on the WESM&lt;BR /&gt;2) Defined the interface (VLAN 1020) for the wireless users and bound it to the assigned WLan&lt;BR /&gt;3) Assigned ip address to the vlan 1020 (172.31.20.1/24)&lt;BR /&gt;4) Configured a dhcp server for the vlan 1020 (172.31.20.101-200 - dg 172.31.20.1 - dns x.x.x.x)&lt;BR /&gt;5) Defined an extended acl (Ospiti-GP) for the dynamic NAT:&lt;BR /&gt;ip access-list extended Ospiti-GP&lt;BR /&gt; permit ip 172.31.20.0/24 any log rule-precedence 10&lt;BR /&gt;6) Defined the interface vlan 1020 as inside interface&lt;BR /&gt;7) Configured the nat statement:&lt;BR /&gt;ip nat inside source list Ospiti-GP interface vlan1 overload&lt;BR /&gt;&lt;BR /&gt;The clients in the wireless area are able to receive the ip address form the dhcp, but their ip addresses are not source natted.&lt;BR /&gt;&lt;BR /&gt;Anyway in the attached configurations.txt file you can see part of the configuration in clear text.&lt;BR /&gt;Thank you&lt;BR /&gt;Enrico</description>
      <pubDate>Wed, 13 Feb 2008 15:57:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/wesm-and-dynamic-nat/m-p/4144398#M13363</guid>
      <dc:creator>ENRICO BASSI_1</dc:creator>
      <dc:date>2008-02-13T15:57:04Z</dc:date>
    </item>
  </channel>
</rss>

