<?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: No-NAT via API in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418428#M3082</link>
    <description>&lt;P&gt;I used to use the NO-NAT feature, but haven't done so in years now.  Instead, I tend to create 1:1 NATs where the source and destination IP addresses are the same.  The interface you specify (such as WAN1) is ignored.  The NATed address can also be used on internal VLANs.&lt;/P&gt;</description>
    <pubDate>Mon, 29 Sep 2025 18:31:08 GMT</pubDate>
    <dc:creator>Philip D'Ath</dc:creator>
    <dc:date>2025-09-29T18:31:08Z</dc:date>
    <item>
      <title>No-NAT via API</title>
      <link>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418426#M3080</link>
      <description>&lt;P&gt;Try to find information regarding the No Nat feature on the MX&lt;BR /&gt;The function is stil in beta according to the dashboard, but guess this is more of an UI clean-up miss since nonat is a prereq for using BGP&lt;/P&gt;&lt;P&gt;How can we alter the configuration for this via an API instead of using he dashboard?&lt;/P&gt;&lt;P&gt;Any ideas are welcome&lt;/P&gt;&lt;P&gt;//Mikael&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 11:37:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418426#M3080</guid>
      <dc:creator>mikefredrik</dc:creator>
      <dc:date>2025-09-29T11:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: No-NAT via API</title>
      <link>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418427#M3081</link>
      <description>&lt;P&gt;Hi, unfortunately, No NAT configuration is not currently exposed via the Meraki Dashboard API.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 14:17:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418427#M3081</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2025-09-29T14:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: No-NAT via API</title>
      <link>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418428#M3082</link>
      <description>&lt;P&gt;I used to use the NO-NAT feature, but haven't done so in years now.  Instead, I tend to create 1:1 NATs where the source and destination IP addresses are the same.  The interface you specify (such as WAN1) is ignored.  The NATed address can also be used on internal VLANs.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 18:31:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418428#M3082</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2025-09-29T18:31:08Z</dc:date>
    </item>
    <item>
      <title>Re: No-NAT via API</title>
      <link>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418429#M3083</link>
      <description>&lt;P&gt;interesting solution, will test this for sure.&lt;BR /&gt;unfortunately  the BGP feature require no nat to what I understand to be able to advertise the local vlans or maybe this is just for reachability from the outside and if that is the case nat1:1 might work&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 18:52:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/no-nat-via-api/m-p/5418429#M3083</guid>
      <dc:creator>mikefredrik</dc:creator>
      <dc:date>2025-09-29T18:52:37Z</dc:date>
    </item>
  </channel>
</rss>

