Using Jami in LAN without Internet

changed title from Using Jami in LAN without Interent to Using Jami in LAN without Internet

changed the description

Sure. Depending the client, there is more or less option available.

The thing is, Jami needs a bootstrap server to enter the network. So you can modify it in the settings to set your own bootstrap node. The other way is the option "Auto connect on local network" (available on Linux only for now) where the client will detect other clients on the network and auto bootstrap on it.

Other options exists, but the clients don't show it for now:

In the account's config, you can see:

Account.peerDiscovery: false
Account.accountDiscovery: false
Account.accountPublish: false

where the first option is the auto bootstrap option. Account discovery/publish is the options to detect other jami accounts on a network, but it's not shown in the client (on GNU/Linux, this options are in: ~/.local/share/jami/YOUR_ACCOUNT_ID/config.yml)

To summarize, 3 options:

Change the bootstrap to your own (on your local network) in the settings
Manually change the config in ~/.local/share/jami/
Wait till clients add these options.

I'm sorry but I'm little confused.

I have 3 nodes A(Debian 192.168.1.5), B(Ubuntu 192.168.1.10) and C(Windows 192.168.1.15). Now, let's first start with A and B, both Linux boxes.

I have this in config.yml of both the nodes:

Account.peerDiscovery: true
Account.accountDiscovery: true
Account.accountPublish: true

Is this enough? Since I have "Auto connect on local network" enabled (Account.peerDiscovery: true) on both the nodes, I don't need to set up the bootstrap server, right?

But still I am not able to send messages from these nodes to each other. Both the nodes show the 3 dots in wave-like motion beside the messages. (I think that means sending/in process)

@sblin should Auto connect on local network be enabled by default?

When the option will be tested enough.

assigned to @vivanov

added 1 deleted label

hello,

I investigated this feature and almost everything works, here are the scenario of what I tried in a LAN without internet (behind a switch with ethernet and with a wifi router withouut internet):

ipv4 to ipv4 (works)
ipv4 to ipv6 (works)
ipv6 to ipv6 (works)

Make sure to enable these lines as discussed previously:

n0t build $ grep -rni -A 2 peerDiscovery ~/.local/share/jami/
/home/n0t/.local/share/jami/7c7dc97b2d7758a6/config.yml:38:Account.peerDiscovery: true
/home/n0t/.local/share/jami/7c7dc97b2d7758a6/config.yml-39-Account.accountDiscovery: true
/home/n0t/.local/share/jami/7c7dc97b2d7758a6/config.yml-40-Account.accountPublish: true

Moreover, make sure that your router, switch is not filtering mutlicasting, some routers disable it to avoid impacting the network from the search that all devices launch with the mutlicasting.

I'm joining a flow of two devices finding eachother with peer discovery.

What doesn't work is when there are multiple devices the messages are sent and received with a delay and the green (online) icon is not switching properly. It seems to happen on a host with multiple network card thus, it must be a connectivity change issue. Otherwise, all of the above works just fine.

host2.log

host1.log

@vivanov do intercom calls work, i.e.

video calls
audio only calls

Thank you

@ovari normally, yes like I can send & receive messages but I think there is a small issue with calls that our team is suppose to check asap.

@vivanov can you please advise when asap has arrived so we can also check. Thank you

@ovari we just confirmed the presence of this issue with @sblin in case of multiple accounts it seems a connectivity change triggers this issue, I will update you as soon as there is a hot fix to allow you to test it on your side. Thank you for the patience! :)

unassigned @vivanov

assigned to @sblin

In fact @mzhang did some tests. The auto connect is working (if your network accepts broadcast).

The only issues is with calls where the DNS resolution can take time (17 seconds * 3 on my computer) for the TURN.

Quick solution: If you are in a LAN, deactivate TURN. Daemon solution, improve the ICE init and avoid to connect to TURN after the first ERESOLV error (until next connectivity change).

closed

added typefeature request label and removed typebug label

Using Jami in LAN without Internet

Designs

Child items ...

Activity