Hi Sven,

There is a dhcp plugin that you can use instead of the host-local ipam plugin.
https://www.cni.dev/plugins/current/ipam/dhcp/

---
Paul

On Wed, May 10, 2023 at 10:17 PM Sven Schwermer via Podman <podman@lists.podman.io> wrote:
Hi,

I have a host running Debian Bullseye (Podman v3.0.1). On that host, I run an OPNsense VM via KVM. The goal is to create a (virtual) network connection between that VM and one or more Podman containers.

So far, I have created a dedicated bridge network for the VM via this network definition:

<network connections='1'>
  <name>services</name>
  <uuid>884d7543-91b0-4752-93b7-7efc6633d733</uuid>
  <bridge name='virbr1' stp='on' delay='0'/>
  <mac address='52:54:00:78:f8:79'/>
  <ip address='192.168.50.1' netmask='255.255.255.0'>
  </ip>
</network>

I then created this network for Podman:

[
  {
    "cniVersion": "0.4.0",
    "name": "services",
    "plugins": [
      {
        "ipam": {
          "gateway": "192.168.50.2",
          "routes": [
            {
              "dst": "0.0.0.0/0"
            }
          ],
          "subnet": "192.168.50.0/24",
          "type": "host-local"
        },
        "master": "virbr1",
        "type": "macvlan"
      }
    ]
  }
]

The container is is started like so:

podman run --network=services --ip=192.168.50.10 [...]

This does work, however, it doesn't seem ideal. Is there a better way to achieve networking between VM and containers? Is there a way to make Podman actually configure networking by making DHCP requests (to the OPNsense VM)? That way, DNS would be configured properly as well.

Any pointers are welcome 😄

Thanks, Sven
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io