<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bridges on Linux Café</title>
    <link>https://mrtomlinux.org/tags/bridges/</link>
    <description>Recent content in Bridges on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 26 Oct 2026 09:30:59 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/bridges/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When `ip link` shows no IP but you can ping: diagnosing an absent IPv4 on a bridge interface</title>
      <link>https://mrtomlinux.org/post/2026-10-26-when-ip-link-shows-no-ip-but-you-can-ping-dia/</link>
      <pubDate>Mon, 26 Oct 2026 09:30:59 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-10-26-when-ip-link-shows-no-ip-but-you-can-ping-dia/</guid>
      <description>&lt;p&gt;I was in the middle of setting up a tiny homelab VM that bridges straight to the host. The guest could ping the gateway just fine, but &lt;code&gt;ip addr show br0&lt;/code&gt; was staring back at me with no &lt;code&gt;inet&lt;/code&gt; line. The bridge was up, &lt;code&gt;state UP&lt;/code&gt;, yet no IPv4. What’s going on?&lt;/p&gt;&#xA;&lt;h3 id=&#34;1-distinguish-linkstate-from-ipstate&#34;&gt;1. Distinguish &lt;em&gt;link‑state&lt;/em&gt; from &lt;em&gt;IP‑state&lt;/em&gt;&lt;/h3&gt;&#xA;&lt;p&gt;&lt;code&gt;ip link&lt;/code&gt; only tells you about the link layer. An interface can be physically up and still have no IP if the DHCP client never got a lease or a static config never ran.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
