<?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: SLX 9140 bgp port 179 open despite rACL in Data Center (SLX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-slx/slx-9140-bgp-port-179-open-despite-racl/m-p/90882#M383</link>
    <description>Happy to help! You need to install an access list for IP and IP6 traffic directed to the CPU and only allow your member links or BGP peering network to have access, e.g.&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;ip access-list extended PROTECT_RE&lt;BR /&gt; seq 10 permit tcp host $JUMP_HOST any eq 22&lt;BR /&gt; seq 70 permit udp host $SNMP_HOST any eq snmp&lt;BR /&gt; seq 80 permit tcp $BGP_NETWORK 0.0.0.255 any eq bgp&lt;BR /&gt; seq 100 hard-drop tcp any any eq 22&lt;BR /&gt; seq 101 hard-drop tcp any any eq 161&lt;BR /&gt; seq 102 hard-drop tcp any any eq bgp&lt;BR /&gt; seq 250 permit ip any any&lt;BR /&gt;ip access-list extended PROTECT_RE&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
Same for IPv6, but here the access list is called with ipv6-prefix:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;ipv6 access-list extended PROTECT_RE6&lt;BR /&gt; seq 10 permit tcp host $JUMP_HOST any eq 22&lt;BR /&gt; seq 70 permit udp host $SNMP_HOST any eq snmp&lt;BR /&gt; seq 80 permit tcp $BGP_NETWORK::/64 any eq bgp&lt;BR /&gt; seq 100 hard-drop tcp any any eq 22&lt;BR /&gt; seq 101 hard-drop tcp any any eq 161&lt;BR /&gt; seq 102 hard-drop tcp any any eq bgp&lt;BR /&gt; seq 250 permit ip any any&lt;BR /&gt; ipv6 access-list extended PROTECT_RE6&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
Please change the variables name to reflect your configuration. &lt;BR /&gt;
&lt;BR /&gt;
Jörg</description>
    <pubDate>Thu, 06 Dec 2018 20:18:20 GMT</pubDate>
    <dc:creator>joergkost</dc:creator>
    <dc:date>2018-12-06T20:18:20Z</dc:date>
    <item>
      <title>SLX 9140 bgp port 179 open despite rACL</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/slx-9140-bgp-port-179-open-despite-racl/m-p/90881#M382</link>
      <description>Hi&lt;BR /&gt;
SLX 9140 NOS v17s.1.02, active BGP sessions with 2 peers, everything works fine, except port 179 is open on all   IP addresses configured on any Layer 3 interface including loopback. Despite a general rACL that specifically allows only connections to port 179 only from the two BGP peers/neighbours.&lt;BR /&gt;
Is the BGP 179 port not covered by the rACL ? Becouse all other CPU traffic, ssh, telnet, snmp etc is being handled by that rACL without a problem.&lt;BR /&gt;
I've run a scan with nmap and the only visible and open port is the 179 bgp.&lt;BR /&gt;
Will be gratefull for any help</description>
      <pubDate>Mon, 05 Nov 2018 21:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/slx-9140-bgp-port-179-open-despite-racl/m-p/90881#M382</guid>
      <dc:creator>Bostjan</dc:creator>
      <dc:date>2018-11-05T21:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: SLX 9140 bgp port 179 open despite rACL</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/slx-9140-bgp-port-179-open-despite-racl/m-p/90882#M383</link>
      <description>Happy to help! You need to install an access list for IP and IP6 traffic directed to the CPU and only allow your member links or BGP peering network to have access, e.g.&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;ip access-list extended PROTECT_RE&lt;BR /&gt; seq 10 permit tcp host $JUMP_HOST any eq 22&lt;BR /&gt; seq 70 permit udp host $SNMP_HOST any eq snmp&lt;BR /&gt; seq 80 permit tcp $BGP_NETWORK 0.0.0.255 any eq bgp&lt;BR /&gt; seq 100 hard-drop tcp any any eq 22&lt;BR /&gt; seq 101 hard-drop tcp any any eq 161&lt;BR /&gt; seq 102 hard-drop tcp any any eq bgp&lt;BR /&gt; seq 250 permit ip any any&lt;BR /&gt;ip access-list extended PROTECT_RE&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
Same for IPv6, but here the access list is called with ipv6-prefix:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;ipv6 access-list extended PROTECT_RE6&lt;BR /&gt; seq 10 permit tcp host $JUMP_HOST any eq 22&lt;BR /&gt; seq 70 permit udp host $SNMP_HOST any eq snmp&lt;BR /&gt; seq 80 permit tcp $BGP_NETWORK::/64 any eq bgp&lt;BR /&gt; seq 100 hard-drop tcp any any eq 22&lt;BR /&gt; seq 101 hard-drop tcp any any eq 161&lt;BR /&gt; seq 102 hard-drop tcp any any eq bgp&lt;BR /&gt; seq 250 permit ip any any&lt;BR /&gt; ipv6 access-list extended PROTECT_RE6&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
Please change the variables name to reflect your configuration. &lt;BR /&gt;
&lt;BR /&gt;
Jörg</description>
      <pubDate>Thu, 06 Dec 2018 20:18:20 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/slx-9140-bgp-port-179-open-despite-racl/m-p/90882#M383</guid>
      <dc:creator>joergkost</dc:creator>
      <dc:date>2018-12-06T20:18:20Z</dc:date>
    </item>
  </channel>
</rss>

