<?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: Added port to VLAN, existing access-group wasn't applied to port in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/131#M11</link>
    <description>&lt;P&gt;I added another rule to that access-list today, and again it was not applied to the port I was using to test. It appears that this is a more pervasive problem than what I originally thought. I had to remove and re-apply the access-group to get traffic flowing via the new rule I had added.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Feb 2022 01:15:58 GMT</pubDate>
    <dc:creator>kpfleming</dc:creator>
    <dc:date>2022-02-16T01:15:58Z</dc:date>
    <item>
      <title>Added port to VLAN, existing access-group wasn't applied to port</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/127#M9</link>
      <description>&lt;P&gt;ver 09.0.10T213&lt;/P&gt;&lt;P&gt;Existing configuration (snippets):&lt;/P&gt;&lt;LI-CODE lang="python"&gt;vlan 81 name untrusted-no-outbound by port
 tagged ethe 3/1/6 
 untagged ethe 1/1/6 
 ip access-group untrusted-no-outbound in

interface ve 81
 ip address 192.168.81.2/24
 ip helper-address 1 192.168.120.2
 ip helper-address 2 192.168.120.3

ip access-list extended untrusted-no-outbound
 sequence 10 permit tcp any 192.168.88.0/24 established 
 sequence 20 permit icmp any any 
 sequence 50 permit udp any host 192.168.255.1 eq ntp 
 sequence 70 deny tcp any 192.168.0.0/16 
 sequence 80 deny udp any 192.168.0.0/16&lt;/LI-CODE&gt;&lt;P&gt;With this configuration in place, the devices attached to 1/1/6 and 3/1/6 were able to send DHCP requests (and obtain addresses) via VLAN 81.&lt;/P&gt;&lt;P&gt;I added port 4/1/1 (also tagged) to VLAN 81, but the device attached that port was unable to get an address via DHCP. Setting up a monitor on port 4/1/1 showed the DHCP 'discover' arriving (with VLAN id 81) from the device, but it was not forwarded to the ip-helper addresses attached to 'interface ve 81'.&lt;BR /&gt;&lt;BR /&gt;Removing the 'ip access-group' from 'vlan 81' and then re-adding it cured the problem; traffic from port 4/1/1 on vlan 81 began flowing. It appears that adding the port to the VLAN, with an existing access-group, did not result in the access-group's rules being applied to that port.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 12:11:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/127#M9</guid>
      <dc:creator>kpfleming</dc:creator>
      <dc:date>2022-02-15T12:11:20Z</dc:date>
    </item>
    <item>
      <title>Re: Added port to VLAN, existing access-group wasn't applied to port</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/128#M10</link>
      <description>&lt;P&gt;Sorry, forgot to include device information: this is a 4-unit stack of ICX7150-C12Ps.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 12:13:04 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/128#M10</guid>
      <dc:creator>kpfleming</dc:creator>
      <dc:date>2022-02-15T12:13:04Z</dc:date>
    </item>
    <item>
      <title>Re: Added port to VLAN, existing access-group wasn't applied to port</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/131#M11</link>
      <description>&lt;P&gt;I added another rule to that access-list today, and again it was not applied to the port I was using to test. It appears that this is a more pervasive problem than what I originally thought. I had to remove and re-apply the access-group to get traffic flowing via the new rule I had added.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 01:15:58 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/131#M11</guid>
      <dc:creator>kpfleming</dc:creator>
      <dc:date>2022-02-16T01:15:58Z</dc:date>
    </item>
    <item>
      <title>Re: Added port to VLAN, existing access-group wasn't applied to port</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/140#M12</link>
      <description>&lt;P&gt;Hey Kevin,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would recommend opening a support case for this type of item. It likely needs a proper investigation. One of our TAC engineers would be best-suited to assist you.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 18:25:42 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/140#M12</guid>
      <dc:creator>BenBeck</dc:creator>
      <dc:date>2022-02-16T18:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: Added port to VLAN, existing access-group wasn't applied to port</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/154#M14</link>
      <description>&lt;P&gt;I would be happy if I could do that, but I can't purchase a support contract because I bought my ICX devices 'used'. Too bad.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 21:27:17 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/Added-port-to-VLAN-existing-access-group-wasn-t-applied-to-port/m-p/154#M14</guid>
      <dc:creator>kpfleming</dc:creator>
      <dc:date>2022-02-16T21:27:17Z</dc:date>
    </item>
  </channel>
</rss>

