<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Network on Marcus Folkesson</title>
    <link>https://www.marcusfolkesson.se/tags/network/</link>
    <description>Recent content in Network on Marcus Folkesson</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 Dec 2023 19:39:34 +0200</lastBuildDate>
    <atom:link href="https://www.marcusfolkesson.se/tags/network/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Expose network namespace created by Docker</title>
      <link>https://www.marcusfolkesson.se/blog/expose-netns-from-docker/</link>
      <pubDate>Wed, 20 Dec 2023 19:39:34 +0200</pubDate>
      <guid>https://www.marcusfolkesson.se/blog/expose-netns-from-docker/</guid>
      <description>Expose network namespace created by Docker Disclaimer: this is probably *not* the best way for doing this, but it&#39;s pretty good for educational purposes.&#xA;During a debug session I wanted to connect an application to a service that ran in a docker container. This was for test-purposes only, so hackish and fast are the keywords.&#xA;First of all, I&#39;m not a Docker expert, but I&#39;ve a pretty good understanding on Linux internals, namespaces and how things works on a Linux system.</description>
    </item>
    <item>
      <title>Loopback with two (physical) ethernet interfaces</title>
      <link>https://www.marcusfolkesson.se/blog/loopback-with-two-ethernet-interfaces/</link>
      <pubDate>Sat, 21 Oct 2023 19:39:34 +0200</pubDate>
      <guid>https://www.marcusfolkesson.se/blog/loopback-with-two-ethernet-interfaces/</guid>
      <description>Loopback with two (physical) ethernet interfaces Imagine that you have an embedded device with two physical ethernet ports. You want to verify the functionality of both these ports in the manufacturing process, so you connect an ethernet cable between the ports, setup IP addresses and now what?&#xA;As Linux (actually the default network namespace) is aware of both adapters and their IP/MAC-addresses, the system sees no reason to send any traffic out.</description>
    </item>
  </channel>
</rss>
