<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ipv6 on Under the Model</title><link>https://oguzpastirmaci.com/tags/ipv6/</link><description>Recent content in Ipv6 on Under the Model</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 01 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://oguzpastirmaci.com/tags/ipv6/index.xml" rel="self" type="application/rss+xml"/><item><title>ARP, rp_filter and accept_ra for RDMA Pods on Kubernetes</title><link>https://oguzpastirmaci.com/posts/arp-rp-filter-and-accept-ra-for-rdma-pods-on-kubernetes/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://oguzpastirmaci.com/posts/arp-rp-filter-and-accept-ra-for-rdma-pods-on-kubernetes/</guid><description>&lt;p&gt;A GPU node with 16 RoCE rails has 16 network interfaces, often in one subnet. Linux treats an IP address as owned by the host, not by an interface. That default is fine for one NIC. With 16 rails, it breaks RDMA in ways that look like RDMA bugs.&lt;/p&gt;&#10;&lt;p&gt;These are some of the failures I saw:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;code&gt;ib_write_bw&lt;/code&gt; failed on 6 of 16 rails, and the failing rails changed between runs.&lt;/li&gt;&#10;&lt;li&gt;Two peer addresses resolved to the same MAC address. One of them got the MAC of a VF on another rail.&lt;/li&gt;&#10;&lt;li&gt;NCCL stopped with &lt;code&gt;ibv_modify_qp failed with 61 No data available&lt;/code&gt;, because most rails had no IPv6 address.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The fix is always a few sysctls. The hard part on Kubernetes is where they live. A pod can get its RDMA interface in several ways. Each way decides which network namespace the interface ends up in, and who owns its settings.&lt;/p&gt;</description></item></channel></rss>