<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[IP V6 support]]></title><description><![CDATA[<p dir="auto">It does not seems that IP V6 is supported: only IP V4 address is displayed on server.<br />
With IP V4 shortage and native support of IP V6, it could be nice to support both stacks and use the preferred one to discuss with the server.</p>
]]></description><link>https://vulndetect.org/topic/142/ip-v6-support</link><generator>RSS for Node</generator><lastBuildDate>Mon, 15 Jun 2026 23:57:37 GMT</lastBuildDate><atom:link href="https://vulndetect.org/topic/142.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 02 Jun 2018 15:28:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to IP V6 support on Sun, 30 Sep 2018 19:06:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/tom" aria-label="Profile: tom">@<bdi>tom</bdi></a> No issue with IPV6 as far as I can see.<br />
IP adresses of systems on my personal LAN are reported using IPV6.<br />
Glad to see a product which does not prefer reporting IPV4 when both stacks are active.</p>
<p dir="auto">Regards.</p>
]]></description><link>https://vulndetect.org/post/1597</link><guid isPermaLink="true">https://vulndetect.org/post/1597</guid><dc:creator><![CDATA[GregAlexandre]]></dc:creator><pubDate>Sun, 30 Sep 2018 19:06:18 GMT</pubDate></item><item><title><![CDATA[Reply to IP V6 support on Thu, 27 Sep 2018 16:59:33 GMT]]></title><description><![CDATA[<p dir="auto">The VulnDetect servers are dualstack, so they support both IPv6 and IPv4.</p>
<p dir="auto">Unfortunately, I can't test this myself at the moment.</p>
<p dir="auto">Please report if there is any issues with IPv6 support.</p>
]]></description><link>https://vulndetect.org/post/1533</link><guid isPermaLink="true">https://vulndetect.org/post/1533</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Thu, 27 Sep 2018 16:59:33 GMT</pubDate></item><item><title><![CDATA[Reply to IP V6 support on Fri, 28 Sep 2018 15:38:38 GMT]]></title><description><![CDATA[<p dir="auto">You may also want to look at this topic:<br />
<a href="https://vulndetect.org/topic/10/ipv6-added-for-vulndetect-com-testing">https://vulndetect.org/topic/10/ipv6-added-for-vulndetect-com-testing</a></p>
]]></description><link>https://vulndetect.org/post/367</link><guid isPermaLink="true">https://vulndetect.org/post/367</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Fri, 28 Sep 2018 15:38:38 GMT</pubDate></item><item><title><![CDATA[Reply to IP V6 support on Fri, 28 Sep 2018 15:36:21 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/gregalexandre" aria-label="Profile: gregalexandre">@<bdi>gregalexandre</bdi></a> I absolutely agree. We did deploy IPv6 for <a href="https://vulndetect.org">https://vulndetect.org</a> and for <a href="https://secteer.com" rel="nofollow ugc">https://secteer.com</a>, but that is still awaiting for ~~<a href="https://carma.secteer.com~~" rel="nofollow ugc">https://carma.secteer.com~~</a> <a href="https://vulndetect.com/?1" rel="nofollow ugc">https://vulndetect.com/?1</a>. However, this is planned for the upcoming production environment and we do expect full IPv6 support for the agent / server and UI of the CARMA. You should be able to access <a href="https://ipv6.vulndetect.org/" rel="nofollow ugc">https://ipv6.vulndetect.org/</a> and <a href="https://ipv6.secteer.com/" rel="nofollow ugc">https://ipv6.secteer.com/</a><br />
However, for the CARMA there will only be dual stack support (unless there is issues and we need to support both dual stack and pure ipv4 and ipv6 stacks.</p>
]]></description><link>https://vulndetect.org/post/366</link><guid isPermaLink="true">https://vulndetect.org/post/366</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Fri, 28 Sep 2018 15:36:21 GMT</pubDate></item></channel></rss>