<?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 IP Address in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ip-address/m-p/5501606#M301608</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a site using the MR 192.168.9.x (via DHCP) ip address but their clients are getting 10.x.x.x range, and they indicate that they are having issues with their network printer. They don't have an external DHCP. Would adding static ip address be an option?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2024 13:23:02 GMT</pubDate>
    <dc:creator>erodriguez@iqteksolutions.com</dc:creator>
    <dc:date>2024-06-27T13:23:02Z</dc:date>
    <item>
      <title>IP Address</title>
      <link>https://community.cisco.com/t5/wireless/ip-address/m-p/5501606#M301608</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a site using the MR 192.168.9.x (via DHCP) ip address but their clients are getting 10.x.x.x range, and they indicate that they are having issues with their network printer. They don't have an external DHCP. Would adding static ip address be an option?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 13:23:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-address/m-p/5501606#M301608</guid>
      <dc:creator>erodriguez@iqteksolutions.com</dc:creator>
      <dc:date>2024-06-27T13:23:02Z</dc:date>
    </item>
    <item>
      <title>Re: IP Address</title>
      <link>https://community.cisco.com/t5/wireless/ip-address/m-p/5501607#M301609</link>
      <description>&lt;P&gt;The SSID is probably configured to use NAT mode.&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/NAT_Mode_with_Meraki_DHCP" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/NAT_Mode_with_Meraki_DHCP&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 13:24:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-address/m-p/5501607#M301609</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2024-06-27T13:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: IP Address</title>
      <link>https://community.cisco.com/t5/wireless/ip-address/m-p/5501608#M301610</link>
      <description>&lt;P&gt;In NAT mode, client isolation is enabled, which explains the behavior. Switch to bridge mode and everything should be fine.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 13:25:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-address/m-p/5501608#M301610</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2024-06-27T13:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: IP Address</title>
      <link>https://community.cisco.com/t5/wireless/ip-address/m-p/5501609#M301611</link>
      <description>&lt;P&gt;Just to add to what Alemabrahao said, you can think of NAT mode as a "Guest" network. It is completely isolated from your local LAN. So any of your clients getting an IP from a Domain Controller or DHCP won't be able to reach those clients. If you switch to Bridge Mode, those clients will receive an IP based off the subnets you personally created and as a result, you'll be able to communicate over the LAN. They may start getting 192.168.9.X addresses depending on how you configured it.&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 13:39:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-address/m-p/5501609#M301611</guid>
      <dc:creator>ntuccillo</dc:creator>
      <dc:date>2024-06-27T13:39:31Z</dc:date>
    </item>
  </channel>
</rss>

