<html>
    <head>
      <base href="https://bugzilla.netfilter.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Conntrack marks ICMPv6 multicast and anycast ping responces as invalid."
   href="https://bugzilla.netfilter.org/show_bug.cgi?id=1447">1447</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Conntrack marks ICMPv6 multicast and anycast ping responces as invalid.
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>netfilter/iptables
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86_64
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P5
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>nf_conntrack
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>netfilter-buglog@lists.netfilter.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>igo9586@yandex.ru
          </td>
        </tr></table>
      <p>
        <div>
        <pre>For example:


ping ff02::1%interface # ping all nodes on the link

ping ff02::2%interface # ping all routers on the link

ping ff05::2 # ping all nodes in ULA

ping fd00:: # anycast ping the ULA


In all these cases the conntrack expects the responces to be from the same
address as ping request, however, the responces will come from a different
addresses.


For example, the link local multicasts will receive reply from fe80::/10 range
(example fe80::aaaa:bbbb:cccc:dddd).


This causes an issue if you have conntrack setup to drop invalid packets. (`ct
state invalid drop` in nftables)</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are watching all bug changes.</li>
      </ul>
    </body>
</html>