audio issue if user dont have ipv6

[naziur604]

We have encountered an issue with audio when IPv6 is disabled on the server. In such cases, users are unable to join the room. However, if IPv6 is enabled on the server and a user does not have IPv6 support, they can join the room but are unable to access audio. It's important to note that most users do not have IPv6 support since their ISPs primarily use IPv4.

please address this problem and ensure IPv4 support for all users to join and use smoothly,

How to Reproduce
you can follow these steps:

Disable IPv6 on the server:
    Open the /etc/sysctl.conf file using a text editor.

Add the following two lines to the sysctl.conf file:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

Save and close the sysctl.conf file.

Apply the changes by running the following command:

sysctl -p

Alternatively, you can reboot the server to ensure that IPv6 is completely disabled.

Currently, we are running the latest version of Livekit on Docker, and clients side using the latest version of the Android SDK.

[davidzhao]

@naziur604 are you able to reproduce this only with the Android SDK? If so please file it in the Android repo along with detailed logs from the client itself.

Your repro steps indicate IPv6 support should be disabled on the server in order to reproduce. That sounds quite opposite to what the title of the issue is indicating: i.e. IPv6 support unavailable on the client.. instead of the server.

[naziur604]

Your repro steps indicate IPv6 support should be disabled on the server in order to reproduce. That sounds quite opposite to what the title of the issue is indicating: i.e. IPv6 support unavailable on the client.. instead of the server.

The issue arises when IPv6 is not disabled on the server, preventing the LiveKit server from starting. Consequently, the client SDK is unable to establish a connection to the server. During our research and development (R&D) phase, we utilized the Android SDK. It's important to note that this problem is associated with the LiveKit server rather than the client SDK.

[davidzhao]

Please provide the information requested in order for us to reproduce the issue. It's insufficient to state a specific problem with your own app.

If you suspect it's an issue with livekit, you would need to provide repro steps using our example app.

[naziur604]

Please provide the information requested in order for us to reproduce the issue. It's insufficient to state a specific problem with your own app.

If you suspect it's an issue with livekit, you would need to provide repro steps using our example app.

How to reproduce

1. disable IPV6 on server side
2. start livekit server (if ipv6 disable livekit will not start)

Disable IPv6 on the server:
Open the /etc/sysctl.conf file using a text editor.

Add the following two lines to the sysctl.conf file:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

To properly configure and troubleshoot LiveKit server, follow these steps:

1.    Install the latest version of the LiveKit server on any chosen server.
4.    Disable IPv6 on the server. After doing so, you may encounter an issue where the LiveKit server fails to start.

Additionally, it's important to note that even if IPv6 is not disabled and the LiveKit server is running, clients without IPv6 support may face connectivity issues with the server. In such cases, while a connection might be established, audio transmission problems could occur, indicating a potential issue with the LiveKit server's handling of IPv6 connections.