<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;"><div>Hey list,<br></div><div><u></u><br></div><div>Following up on André Grüneberg's thread from August 19/2023 titled "No IRRDB shown for IPv6 only peer" (<a target="_blank" data-zeanchor="true" href="https://www.inex.ie/pipermail/ixpmanager/2023-August/003709.html">https://www.inex.ie/pipermail/ixpmanager/2023-August/003709.html</a>), I noticed that the same situation is occurring for us in our IXPmanager instance. This unfortunately prevents us from filtering an IPv6-only member on our route servers, meaning that we have to allocate and "waste" an IPv4 address for that member.<br></div><div><br></div><div>I created an issue on the GitHub repository (<a target="_blank" data-zeanchor="true" href="https://github.com/inex/IXP-Manager/issues/873">https://github.com/inex/IXP-Manager/issues/873</a>) in case anyone is able to pick that up and recommend a fix.</div><div><br></div><div class="zmail_signature_below"><div id="" data-zbluepencil-ignore="true" data-sigid="723925633"><div>Kind Regards,<br></div><div>Peter Potvin | AccurIX Management<br></div><div>Email: peter@accurix.net<br></div><div>Website: <a target="_blank" href="https://accurix.net/">https://accurix.net/</a> <br></div></div></div><div><br></div></div><br></body></html>