WebRTC Fail from Local Lan

[sivak...@gmail.com]

Hi,

We are trying to setup a bigbluebutton server in our company. The server located at the HO to be accessed from HO and branch offices and we are using a FTTH internet connection. The server is setup with 192.168.1.142 and the internet router is configured to forward the required ports to the server. As per the documentation, i already created the loopback interface with the public ip address. The BBB works fine with WebRTC when accesssed though Internet (from branch office), but WebRTC fails when we access the server from local LAN (from HO). The internal clients can resolve the bigbluebutton server FQDN to its external ipaddress but they are not able to access the BBBserver using  FQDN.

The work around that we found was to add the Local IP address of BBBserver to the hosts file of each client. But even with this, WebTRC still fails and are forced to use the Flash method.  I am suspecting that the FTTH router does not have the ability to make a hairpin NAT. Is there a way to make WebRTC work from internal client? 

FTTH  provides only very few options to make changes and uses port 80 to manage the FTTH router. Hence I am thinking what if we change the port of BBB from 80 to something else? Is that possible?

Regards,

Siva.

[Fred Dixon]

Hi Siva,

> The BBB works fine with WebRTC when accesssed though Internet (from branch office), but WebRTC fails when we access the server from local LAN (from HO). The internal clients can resolve the bigbluebutton server FQDN to its external ipaddress but they are not able to access the BBBserver using  FQDN.

Use FireFox to try accessing the WebRTC audio from an internal client.  After it fails, open a new tab and enter the URL 

   about:webrtc

This will give you some stats, but most importantly it will help you see what the local and remote IP addresses the browser was using to create an UDP connection.  Click the triangle next to the text 'show details' and check out the IP address for 'Local Candidate' and 'Remote Candidate'.  They should be the local IP address for the computer running the browser and the external IP address for the BigBlueButton server.

> BBB works fine with WebRTC when accesssed though Internet (from branch office),

Try the above for this scenario and see if the IP address for Remote Candidate are consistent.

Regards,... Fred

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.

--

BigBlueButton Developer

http://bigbluebutton.org/

@bigbluebutton

[Chad Pilkey]

Also, what error is WebRTC failing with. The number will go a long way to determining a cause.

On Monday, May 7, 2018 at 7:48:42 AM UTC-4, Fred Dixon wrote:

Hi Siva,

> The BBB works fine with WebRTC when accesssed though Internet (from branch office), but WebRTC fails when we access the server from local LAN (from HO). The internal clients can resolve the bigbluebutton server FQDN to its external ipaddress but they are not able to access the BBBserver using  FQDN.

Use FireFox to try accessing the WebRTC audio from an internal client.  After it fails, open a new tab and enter the URL 

   about:webrtc

This will give you some stats, but most importantly it will help you see what the local and remote IP addresses the browser was using to create an UDP connection.  Click the triangle next to the text 'show details' and check out the IP address for 'Local Candidate' and 'Remote Candidate'.  They should be the local IP address for the computer running the browser and the external IP address for the BigBlueButton server.

> BBB works fine with WebRTC when accesssed though Internet (from branch office),

Try the above for this scenario and see if the IP address for Remote Candidate are consistent.

Regards,... Fred

On Sun, May 6, 2018 at 11:47 AM <sivak...@gmail.com> wrote:

Hi,

We are trying to setup a bigbluebutton server in our company. The server located at the HO to be accessed from HO and branch offices and we are using a FTTH internet connection. The server is setup with 192.168.1.142 and the internet router is configured to forward the required ports to the server. As per the documentation, i already created the loopback interface with the public ip address. The BBB works fine with WebRTC when accesssed though Internet (from branch office), but WebRTC fails when we access the server from local LAN (from HO). The internal clients can resolve the bigbluebutton server FQDN to its external ipaddress but they are not able to access the BBBserver using  FQDN.

The work around that we found was to add the Local IP address of BBBserver to the hosts file of each client. But even with this, WebTRC still fails and are forced to use the Flash method.  I am suspecting that the FTTH router does not have the ability to make a hairpin NAT. Is there a way to make WebRTC work from internal client? 

FTTH  provides only very few options to make changes and uses port 80 to manage the FTTH router. Hence I am thinking what if we change the port of BBB from 80 to something else? Is that possible?

Regards,

Siva.

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-setup+unsub...@googlegroups.com.

To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.

[sivak...@gmail.com]

Hi Fred,

Thanks for the response and sorry for the delayed reply.

As per your direction i check the about:webrtc and when i connect from branch office it shows the ip for remote candidate and local candidate properly. but when accessing from internal network, the ice stats list is empty. i mean there is no nominated candidates available.

Mean time i just installed bigbluebutton in another computer without https. This time when i am accessing the BBBserver from internal network, webrtc works fine and i can see in the  about:webrtc page nominated candidates also. so the problem is while using ssl certificate. i used the certificate from letsencrypt by following the documentation.  

i dont know how to move further, pls let me know how can i resolve this issue

Thanks & Regards 

Siva

On Monday, May 7, 2018 at 2:48:42 PM UTC+3, Fred Dixon wrote:

Hi Siva,

> The BBB works fine with WebRTC when accesssed though Internet (from branch office), but WebRTC fails when we access the server from local LAN (from HO). The internal clients can resolve the bigbluebutton server FQDN to its external ipaddress but they are not able to access the BBBserver using  FQDN.

Use FireFox to try accessing the WebRTC audio from an internal client.  After it fails, open a new tab and enter the URL 

   about:webrtc

This will give you some stats, but most importantly it will help you see what the local and remote IP addresses the browser was using to create an UDP connection.  Click the triangle next to the text 'show details' and check out the IP address for 'Local Candidate' and 'Remote Candidate'.  They should be the local IP address for the computer running the browser and the external IP address for the BigBlueButton server.

> BBB works fine with WebRTC when accesssed though Internet (from branch office),

Try the above for this scenario and see if the IP address for Remote Candidate are consistent.

Regards,... Fred

On Sun, May 6, 2018 at 11:47 AM <sivak...@gmail.com> wrote:

Hi,

We are trying to setup a bigbluebutton server in our company. The server located at the HO to be accessed from HO and branch offices and we are using a FTTH internet connection. The server is setup with 192.168.1.142 and the internet router is configured to forward the required ports to the server. As per the documentation, i already created the loopback interface with the public ip address. The BBB works fine with WebRTC when accesssed though Internet (from branch office), but WebRTC fails when we access the server from local LAN (from HO). The internal clients can resolve the bigbluebutton server FQDN to its external ipaddress but they are not able to access the BBBserver using  FQDN.

The work around that we found was to add the Local IP address of BBBserver to the hosts file of each client. But even with this, WebTRC still fails and are forced to use the Flash method.  I am suspecting that the FTTH router does not have the ability to make a hairpin NAT. Is there a way to make WebRTC work from internal client? 

FTTH  provides only very few options to make changes and uses port 80 to manage the FTTH router. Hence I am thinking what if we change the port of BBB from 80 to something else? Is that possible?

Regards,

Siva.

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-setup+unsub...@googlegroups.com.

To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.

[sivak...@gmail.com]

Hi Chad,

Thanks for the response

it shows "Detected the following WebRTC issue: Error 1007: ICE negotiation failed. Do you want to try Flash instead?" error message. As per the troubleshooting section in the documentation, i make sure that all ports are opened in my firewall and the client computer.

Thanks & Regards

Siva

[Allan Bateman]

Hi,

I have the exact same problem running bigbluebutton v2.0.0. When I check about:wrtc as Fred suggests i see that the Internal Ip is incorrect. It shows as 192.168.88.252:58085/udp(host) . My server internal ip is 192.168.88.150. 

How or where do I fix this?

Regards

[Allan Bateman]

Hi Fred

Apologies, I seem to have posted my reply in the wrong place. Here it is again

I have the exact same problem running bigbluebutton v2.0.0. When I check about:wrtc as Fred suggests i see that the Internal Ip is incorrect. It shows as 192.168.88.252:58085/udp(host) . My server internal ip is 192.168.88.150. 

How or where do I fix this?

Regards

On Monday, 7 May 2018 13:48:42 UTC+2, Fred Dixon wrote:

Hi Siva,

> The BBB works fine with WebRTC when accesssed though Internet (from branch office), but WebRTC fails when we access the server from local LAN (from HO). The internal clients can resolve the bigbluebutton server FQDN to its external ipaddress but they are not able to access the BBBserver using  FQDN.

Use FireFox to try accessing the WebRTC audio from an internal client.  After it fails, open a new tab and enter the URL 

   about:webrtc

This will give you some stats, but most importantly it will help you see what the local and remote IP addresses the browser was using to create an UDP connection.  Click the triangle next to the text 'show details' and check out the IP address for 'Local Candidate' and 'Remote Candidate'.  They should be the local IP address for the computer running the browser and the external IP address for the BigBlueButton server.

> BBB works fine with WebRTC when accesssed though Internet (from branch office),

Try the above for this scenario and see if the IP address for Remote Candidate are consistent.

Regards,... Fred

On Sun, May 6, 2018 at 11:47 AM <sivak...@gmail.com> wrote:

Hi,

We are trying to setup a bigbluebutton server in our company. The server located at the HO to be accessed from HO and branch offices and we are using a FTTH internet connection. The server is setup with 192.168.1.142 and the internet router is configured to forward the required ports to the server. As per the documentation, i already created the loopback interface with the public ip address. The BBB works fine with WebRTC when accesssed though Internet (from branch office), but WebRTC fails when we access the server from local LAN (from HO). The internal clients can resolve the bigbluebutton server FQDN to its external ipaddress but they are not able to access the BBBserver using  FQDN.

The work around that we found was to add the Local IP address of BBBserver to the hosts file of each client. But even with this, WebTRC still fails and are forced to use the Flash method.  I am suspecting that the FTTH router does not have the ability to make a hairpin NAT. Is there a way to make WebRTC work from internal client? 

FTTH  provides only very few options to make changes and uses port 80 to manage the FTTH router. Hence I am thinking what if we change the port of BBB from 80 to something else? Is that possible?

Regards,

Siva.

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-setup+unsub...@googlegroups.com.

To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.