Skip to content

bridge: unmanaged mode should properly support aardvark-dns #1177

@Luap99

Description

@Luap99

Currently if one does try to create network with a gateway that is not on a ip on the host it aardvark-dns will fail because we always assume the gateway is the correct aardvark-dns bind ip. That however is often not the case in umanaged mode where one might expose the existing bridge on their LAN and use the real gateway which can be on another system.

It should be quite simple for us to check the existing bridge for ip addresses and then use them instead of the gateway from the config. If there is no ip address on the bridge then we just fail with a clear error that the user must disable dns (--disable-dns) when creating the network.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions