Discovery Server (Ubuntu) PULL from source?

[chuckycastle]

Hey folks!

Is it possible to PULL from a source in Discovery Server?

Scenario:
vMix running on Windows (192.168.1.101), with Access Manager configured to use Discovery Server (192.168.1.100)
vMix running on Windows (192.168.1.102), with Access Manager configured to use Discovery Server (192.168.1.100)

With the current scenario, both Windows machines can see all NDI outputs from vMix from both machines - this is working as expected.

New Scenario:
FFMPEG encoder running on Linux (192.168.1.103), with no Access Manager (coming soon, it seems) and no option to use a Discovery Server

With the new scenario, is it possible to have the Discover Server (192.168.1.100) PULL from an NDI source (192.168.1.103) so that the two Windows machines can see the NDI sources from the one Linux machine via the Discovery Server?

I stumbled upon the config file:

{
    "ndi": {
        "groups": {
            "recv": "\"public\"",
            "send": "\"public\""
        },
        "multicast": {
            "recv": {
                "enable": false,
                "subnets": ""
            },
            "send": {
                "enable": false,
                "netmask": "255.255.255.0",
                "netprefix": "239.192.136.100"
            }
        },
        "networks": {
            "discovery": "127.0.0.1",
            "ips": ""
        },
        "tcp": {
            "recv": {
                "enable": false
            },
            "send": {
                "enable": false
            }
        },
        "unicast": {
            "recv": {
                "enable": false
            },
            "send": {
                "enable": false
            }
        }
    }
}

I'm curious if that config can be modified to allow what I'm looking for?

[kanep]

Products that are configured for Discovery Server will continue to 'see' non-Discovery Server sources. So if the Linux system is creating the source and the two Windows machines are the destination, they will see it even if the Linux system isn't on Discovery Server.

The opposite isn't true. The outputs on applications that are connected to Discovery Server, will only be visible to other Discovery Server connected systems.

[chuckycastle]

I see. I would imagine this is true for sources being generated within the same subnet.

I'll update the OP, but will note here that the Linux system is actually on a different subnet (192.168.2.201).

Does that change things?

[kanep]

If the source isn't on the same subnet and doesn't have Discovery Server support, then you will need to setup Remote Sources on the destination systems so they can find the sources. You can use Remote Sources and Discovery Server together.

[chuckycastle]

Thanks!

We've got it mostly working on an AWS instance with multiple network interfaces. Is there a way to "force" Access Manager to use a specific interface?

[nickda]

Thanks!

We've got it mostly working on an AWS instance with multiple network interfaces. Is there a way to "force" Access Manager to use a specific interface?

chuckycastle, were you able to figure out the linux sources in the discovery server without using Remote Sources?