http://wiki.docking.org/index.php?action=history&feed=atom&title=Cluster_Networking_Quirks 2026-04-07T17:30:21Z Revision history for this page on the wiki MediaWiki 1.39.1 http://wiki.docking.org/index.php?title=Cluster_Networking_Quirks&diff=16701&oldid=prev 2025-05-05T22:58:58Z

<p>Created page with &quot;== Introduction == This is a wiki page detailing weird network quirks the lab has encountered over the years. == List of events == *May 5, 2025 *: &lt;source&gt; Vav and Gimel (both are in the 169.230.26.0 subnet) had a problem contacting the 169.230.75.0 subnet. Both of these machines had similar ip route rules, displayed below. #vav 169.230.0.0/16 dev enp4s0 proto kernel scope link src 169.230.26.169 metric 100 #gimel 169.230.0.0/16 dev eth4 proto kernel scope link src...&quot;</p> <p><b>New page</b></p><div>== Introduction ==<br /> This is a wiki page detailing weird network quirks the lab has encountered over the years.<br /> <br /> == List of events ==<br /> *May 5, 2025<br /> *: &lt;source&gt;<br /> Vav and Gimel (both are in the 169.230.26.0 subnet) had a problem contacting the 169.230.75.0 subnet.<br /> Both of these machines had similar ip route rules, displayed below.<br /> <br /> #vav<br /> 169.230.0.0/16 dev enp4s0 proto kernel scope link src 169.230.26.169 metric 100<br /> #gimel<br /> 169.230.0.0/16 dev eth4 proto kernel scope link src 169.230.26.166<br /> <br /> The rules above tell us that any IP addresses in this range 169.230.1.0 ~ 169.230.255.254 should be visible but they weren&#039;t.<br /> <br /> But for some reason, if I narrow down the subnet to 255.255.255.0 then we&#039;re able to ping the 169.230.75.0 subnet. So here are the new rules that allow connection to happen.<br /> <br /> #vav<br /> 169.230.26.0/24 dev enp4s0 proto kernel scope link src 169.230.26.169 metric 100<br /> #gimel<br /> 169.230.26.0/24 dev eth4 proto kernel scope link src 169.230.26.166<br /> &lt;/source&gt;</div>

Jgutierrez6