<?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 Port-based policy to block outbound traffic except for specific IP addresses and service in ExtremeControl</title>
    <link>https://community.extremenetworks.com/t5/extremecontrol/port-based-policy-to-block-outbound-traffic-except-for-specific/m-p/120457#M2131</link>
    <description>&lt;P&gt;I am looking at creating a really basic NAC policy where all devices in a switch can communicate freely within their subnet (192.168.0.0/24 for example), nothing else, except for a single device (192.168.0.10).&lt;BR /&gt;&lt;BR /&gt;192.168.0.10 (on a separate physical switchport) needs to be able to talk to not only everything in 192.168.0.0/24, but also needs to be able to send HTTPS requests via TCP/443 out to a device with 10.0.0.10 IP address. I've been able to easily get policy applied to ports to allow or block services completely, but would appreciate assistance in figuring out the simplest approach to also specify IP addresses allowed to communicate.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In short:&lt;BR /&gt;1) 192.168.0.0/24 can talk to everything within that subnet unrestricted. Can't talk to anything else with the exception of a single device (192.168.0.10).&lt;/P&gt;&lt;P&gt;2) 192.168.0.10 needs to talk to everything on 192.168.0.0/24&lt;/P&gt;&lt;P&gt;3) 192.168.0.10 needs to also talk to 10.0.0.10 via TCP/443. Communication initiates from 192.168.0.10 outbound to 10.0.0.10&lt;BR /&gt;&lt;BR /&gt;I apologize if this is easily found on documentation. I've been going through the documentation and training. Figured I'd ask for assistance to make sure I am going down the right path. Thank you!&lt;/P&gt;</description>
    <pubDate>Tue, 07 Oct 2025 15:07:14 GMT</pubDate>
    <dc:creator>jc0299</dc:creator>
    <dc:date>2025-10-07T15:07:14Z</dc:date>
    <item>
      <title>Port-based policy to block outbound traffic except for specific IP addresses and service</title>
      <link>https://community.extremenetworks.com/t5/extremecontrol/port-based-policy-to-block-outbound-traffic-except-for-specific/m-p/120457#M2131</link>
      <description>&lt;P&gt;I am looking at creating a really basic NAC policy where all devices in a switch can communicate freely within their subnet (192.168.0.0/24 for example), nothing else, except for a single device (192.168.0.10).&lt;BR /&gt;&lt;BR /&gt;192.168.0.10 (on a separate physical switchport) needs to be able to talk to not only everything in 192.168.0.0/24, but also needs to be able to send HTTPS requests via TCP/443 out to a device with 10.0.0.10 IP address. I've been able to easily get policy applied to ports to allow or block services completely, but would appreciate assistance in figuring out the simplest approach to also specify IP addresses allowed to communicate.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In short:&lt;BR /&gt;1) 192.168.0.0/24 can talk to everything within that subnet unrestricted. Can't talk to anything else with the exception of a single device (192.168.0.10).&lt;/P&gt;&lt;P&gt;2) 192.168.0.10 needs to talk to everything on 192.168.0.0/24&lt;/P&gt;&lt;P&gt;3) 192.168.0.10 needs to also talk to 10.0.0.10 via TCP/443. Communication initiates from 192.168.0.10 outbound to 10.0.0.10&lt;BR /&gt;&lt;BR /&gt;I apologize if this is easily found on documentation. I've been going through the documentation and training. Figured I'd ask for assistance to make sure I am going down the right path. Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 15:07:14 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecontrol/port-based-policy-to-block-outbound-traffic-except-for-specific/m-p/120457#M2131</guid>
      <dc:creator>jc0299</dc:creator>
      <dc:date>2025-10-07T15:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: Port-based policy to block outbound traffic except for specific IP addresses and service</title>
      <link>https://community.extremenetworks.com/t5/extremecontrol/port-based-policy-to-block-outbound-traffic-except-for-specific/m-p/120505#M2135</link>
      <description>&lt;P&gt;I think you can achieve this with the following approach:&lt;/P&gt;&lt;P&gt;Role A:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Permit destination IP 192.168.0.0/24&lt;/LI&gt;&lt;LI&gt;Permit DHCP&lt;/LI&gt;&lt;LI&gt;Permit ARP&lt;/LI&gt;&lt;LI&gt;Permit DNS (if not on 192.168.0.0/24)&lt;/LI&gt;&lt;LI&gt;Deny the rest&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Apply this role to all access ports except the one where 192.168.0.10 is present&lt;/P&gt;&lt;P&gt;Role B:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Permit destination IP 192.168.0.0/24&lt;/LI&gt;&lt;LI&gt;Permit destination socket 10.0.0.10 with TCP port 443&lt;/LI&gt;&lt;LI&gt;Permit DHCP&lt;/LI&gt;&lt;LI&gt;Permit ARP&lt;/LI&gt;&lt;LI&gt;Permit DNS (if not on 192.168.0.0/24)&lt;/LI&gt;&lt;LI&gt;Deny the rest&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Apply this role to the port where the 192.168.0.10 is located.&lt;BR /&gt;&lt;BR /&gt;Do not apply any role to the uplink port.&lt;/P&gt;&lt;P&gt;Notes:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;in the policy manager we use Role, in the CLI it is called profile.&lt;/LI&gt;&lt;LI&gt;you can use NAC (Extreme Control) to assign those roles dynamically, instead of static assignment to the port&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Oct 2025 07:34:23 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecontrol/port-based-policy-to-block-outbound-traffic-except-for-specific/m-p/120505#M2135</guid>
      <dc:creator>Zdeněk_Pala</dc:creator>
      <dc:date>2025-10-14T07:34:23Z</dc:date>
    </item>
  </channel>
</rss>

