Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Acting as RDS for the local network #5

Open
billt-hlit opened this issue Aug 23, 2018 · 2 comments
Open

Acting as RDS for the local network #5

billt-hlit opened this issue Aug 23, 2018 · 2 comments

Comments

@billt-hlit
Copy link

Are there any instructions you can share with us that explain how we can use the Vagrant images to manage nodes on the Ethernet, rather that just nodes running on the Vagrant host? Or is some other software require to do that?

Thanks!

@simonrankine
Copy link
Contributor

Hi there,

I'm afraid the joint-ri doesn't really support running in this way at present. I'm aware that it's something people would like to see, but I haven't got round to making the required changes.

Some users have experimented with adapting the vagrant file to use a bridged network adapter, as per https://www.vagrantup.com/docs/networking/public_network.html, although it can cause the joint-ri to use the wrong IP address in IS-04 advertisements sometimes. That's probably your best bet if you want to try using the RI in this way.

Kind regards,

Simon

@andrewbonney
Copy link
Contributor

andrewbonney commented Feb 22, 2019

Just to add some more notes on this, as we suspect the main issue is that the mDNS announcements either won't be visible or will be incorrect. Assuming the host running vagrant is Ubuntu Linux or similar, the following instructions may help:

  • Install 'avahi-daemon'
  • Create two files as shown below in /etc/avahi/services/. The first should be called bbcregistry.service and the second bbcquery.service
  • Add an entry to the file /etc/avahi/hosts which defines the machine’s hostname. Note that you must change the IP address to the IP of the host you are running avahi-daemon on, and which NMOS Nodes will attempt to contact the registry via: ‘10.0.0.1 bbcserver.local’. If this doesn't work out, you can change the machine's main hostname to be 'bbcserver' in /etc/avahi/avahi-daemon.conf.
  • Once these files are in place, run ‘sudo service avahi-daemon restart’
  • You should then be able to run ‘avahi-browse _nmos-registration._tcp -r’ which should reveal a service running on your machine’s IP address with a name ‘bbcserver.local’. Similarly if you browse for _nmos-query._tcp it will show the query service.
  • Provided these entries are in place and the vagrant boxes are running successfully, Nodes should be able to register with the registry.

File 1 contents:

<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">

<service-group>

  <name replace-wildcards="no">BBC-Registry-MDNS</name>

  <service>
    <type>_nmos-registration._tcp</type>
    <domain-name>local</domain-name>
    <host-name>bbcserver.local</host-name>
    <port>8882</port>
    <txt-record>pri=0</txt-record>
    <txt-record>api_proto=http</txt-record>
    <txt-record>api_ver=v1.0,v1.1,v1.2</txt-record>
  </service>

</service-group>

File 2 contents:

<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">

<service-group>

  <name replace-wildcards="no">BBC-Query-MDNS</name>

  <service>
    <type>_nmos-query._tcp</type>
    <domain-name>local</domain-name>
    <host-name>bbcserver.local</host-name>
    <port>8882</port>
    <txt-record>pri=0</txt-record>
    <txt-record>api_proto=http</txt-record>
    <txt-record>api_ver=v1.0,v1.1,v1.2</txt-record>
  </service>

</service-group>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants