You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Lalit Patel <lk...@gmail.com> on 2020/06/04 12:37:42 UTC

Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Dear all,
Does anybody have a installation where openmeetings (ver 5.0.x) clients are
behind strict firewall with only TCP ports 80 and 443 allowed ? I know I
can use TCP TURN for signalling. How to switch client to media server
communication from UDP to TCP ? Is it possible with openmeeting with
kurento as media server if so, please advise what are the things I need to
do ?

Regards
Lalit Patel

Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Maxim Solodovnik <so...@gmail.com>.
You need TURN server accessible by all parties
This server should have enough UDP (or TCP if you have followed Peter's
advice and switch to TCP) ports opened to the wild

On Fri, 5 Jun 2020 at 20:24, Peter Dähn <da...@vcrp.de> wrote:

> Hi all,
>
> tcp shloud work, if applicationContext.xml is changed like that:
>
> p:turnUrl="HOST:PORT?transport=tcp"
>
> Greetings Peter
>
> Am 05.06.20 um 10:05 schrieb Lalit Patel:
> > Thanks Maxim for your comment. In my case, the server and clients are
> > located at different locations protected by strict firewall rules.
> > Can you elaborate what are things to be done in order to achieve this?
> >
> > Regards
> > Lalit Patel
> >
> >
> > On Fri, Jun 5, 2020 at 7:29 AM Maxim Solodovnik <so...@gmail.com>
> > wrote:
> >
> >> Hello,
> >>
> >> On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com> wrote:
> >>
> >>> Dear all,
> >>> Does anybody have a installation where openmeetings (ver 5.0.x) clients
> >>> are behind strict firewall with only TCP ports 80 and 443 allowed ?
> >>>
> >> AFAIK this is impossible
> >>
> >>
> >>> I know I can use TCP TURN for signalling. How to switch client to media
> >>> server communication from UDP to TCP ? Is it possible with openmeeting
> with
> >>> kurento as media server if so, please advise what are the things I
> need to
> >>> do ?
> >>>
> >> This _might_ be possible but will require code modification
> >> Why you want to switch to TCP?
> >>
> >>
> >>> Regards
> >>> Lalit Patel
> >>>
> >>
> >> --
> >> Best regards,
> >> Maxim
> >>
>
>

-- 
Best regards,
Maxim

Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Peter Dähn <da...@vcrp.de>.
Hi all,

tcp shloud work, if applicationContext.xml is changed like that:

p:turnUrl="HOST:PORT?transport=tcp"

Greetings Peter

Am 05.06.20 um 10:05 schrieb Lalit Patel:
> Thanks Maxim for your comment. In my case, the server and clients are
> located at different locations protected by strict firewall rules.
> Can you elaborate what are things to be done in order to achieve this?
>
> Regards
> Lalit Patel
>
>
> On Fri, Jun 5, 2020 at 7:29 AM Maxim Solodovnik <so...@gmail.com>
> wrote:
>
>> Hello,
>>
>> On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com> wrote:
>>
>>> Dear all,
>>> Does anybody have a installation where openmeetings (ver 5.0.x) clients
>>> are behind strict firewall with only TCP ports 80 and 443 allowed ?
>>>
>> AFAIK this is impossible
>>
>>
>>> I know I can use TCP TURN for signalling. How to switch client to media
>>> server communication from UDP to TCP ? Is it possible with openmeeting with
>>> kurento as media server if so, please advise what are the things I need to
>>> do ?
>>>
>> This _might_ be possible but will require code modification
>> Why you want to switch to TCP?
>>
>>
>>> Regards
>>> Lalit Patel
>>>
>>
>> --
>> Best regards,
>> Maxim
>>


Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Lalit Patel <lk...@gmail.com>.
Thanks Maxim for your comment. In my case, the server and clients are
located at different locations protected by strict firewall rules.
Can you elaborate what are things to be done in order to achieve this?

Regards
Lalit Patel


On Fri, Jun 5, 2020 at 7:29 AM Maxim Solodovnik <so...@gmail.com>
wrote:

> Hello,
>
> On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com> wrote:
>
>> Dear all,
>> Does anybody have a installation where openmeetings (ver 5.0.x) clients
>> are behind strict firewall with only TCP ports 80 and 443 allowed ?
>>
>
> AFAIK this is impossible
>
>
>> I know I can use TCP TURN for signalling. How to switch client to media
>> server communication from UDP to TCP ? Is it possible with openmeeting with
>> kurento as media server if so, please advise what are the things I need to
>> do ?
>>
>
> This _might_ be possible but will require code modification
> Why you want to switch to TCP?
>
>
>>
>> Regards
>> Lalit Patel
>>
>
>
> --
> Best regards,
> Maxim
>

Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Maxim Solodovnik <so...@gmail.com>.
both protocols require multiple ports opened

On Fri, 12 Jun 2020 at 14:39, Lalit Patel <lk...@gmail.com> wrote:

> Switching to TCP is not going to solve my problem because TCP will require
> many ports to be open in firewall. Am I correct ?
>
> Regards
> Lalit Patel
>
> On Fri, Jun 12, 2020 at 6:52 AM Maxim Solodovnik <so...@gmail.com>
> wrote:
>
>> You can use TCP mode :)
>> (not sure why do you need this, UDP is faster ....)
>>
>> On Thu, 11 Jun 2020 at 12:23, Peter-Otto Weber <cy...@hotmail.de>
>> wrote:
>>
>>> So using turn  i do not need udp?
>>>
>>>
>>>
>>> Really complicated stuff…
>>>
>>>
>>>
>>> But if this would be true, OM should not Need UDP Ports if i am using
>>> TURN?
>>>
>>>
>>>
>>> POW
>>>
>>>
>>>
>>> *Von: *Maxim Solodovnik <so...@gmail.com>
>>> *Gesendet: *Mittwoch, 10. Juni 2020 09:07
>>> *An: *Openmeetings user-list <us...@openmeetings.apache.org>
>>> *Betreff: *Re: Openmeetings clients behind strict firewall with only
>>> TCP ports 80 & 443 allowed
>>>
>>>
>>>
>>> Hello POW,
>>>
>>>
>>>
>>> TURN server should be such proxy ....
>>>
>>>
>>>
>>> On Tue, 9 Jun 2020 at 13:04, Peter-Otto Weber <cy...@hotmail.de>
>>> wrote:
>>>
>>> Hello,
>>>
>>>
>>>
>>> i have it running on 80/443 but also needed to open TCP/UDP ports in
>>> Firewall.
>>>
>>>
>>>
>>> As the server is hosted by „myself“ i guess i can trust this kind of
>>> configuration.
>>>
>>>
>>>
>>> The alternative would be „installing an app“.
>>>
>>>
>>>
>>> Of course having only tcp and 443 would allow the use of a proxy and no
>>> need for firewall changes. But i guess this will be not easy.
>>>
>>>
>>>
>>> But it would be a real good thing as esp. In large companies every
>>> special configuration should be avoided.
>>>
>>>
>>>
>>> Maybe setting up any kind of gateway computer could solve this problem?
>>>
>>>
>>>
>>> POW
>>>
>>>
>>>
>>> *Von:* Maxim Solodovnik <so...@gmail.com>
>>> *Gesendet:* Freitag, 5. Juni 2020 03:59
>>> *An:* Openmeetings user-list <us...@openmeetings.apache.org>
>>> *Betreff:* Re: Openmeetings clients behind strict firewall with only
>>> TCP ports 80 & 443 allowed
>>>
>>>
>>>
>>> Hello,
>>>
>>>
>>>
>>> On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com> wrote:
>>>
>>> Dear all,
>>>
>>> Does anybody have a installation where openmeetings (ver 5.0.x) clients
>>> are behind strict firewall with only TCP ports 80 and 443 allowed ?
>>>
>>>
>>>
>>> AFAIK this is impossible
>>>
>>>
>>>
>>> I know I can use TCP TURN for signalling. How to switch client to media
>>> server communication from UDP to TCP ? Is it possible with openmeeting with
>>> kurento as media server if so, please advise what are the things I need to
>>> do ?
>>>
>>>
>>>
>>> This _might_ be possible but will require code modification
>>>
>>> Why you want to switch to TCP?
>>>
>>>
>>>
>>>
>>>
>>> Regards
>>>
>>> Lalit Patel
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best regards,
>>> Maxim
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best regards,
>>> Maxim
>>>
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Maxim
>>
>

-- 
Best regards,
Maxim

Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Lalit Patel <lk...@gmail.com>.
Switching to TCP is not going to solve my problem because TCP will require
many ports to be open in firewall. Am I correct ?

Regards
Lalit Patel

On Fri, Jun 12, 2020 at 6:52 AM Maxim Solodovnik <so...@gmail.com>
wrote:

> You can use TCP mode :)
> (not sure why do you need this, UDP is faster ....)
>
> On Thu, 11 Jun 2020 at 12:23, Peter-Otto Weber <cy...@hotmail.de>
> wrote:
>
>> So using turn  i do not need udp?
>>
>>
>>
>> Really complicated stuff…
>>
>>
>>
>> But if this would be true, OM should not Need UDP Ports if i am using
>> TURN?
>>
>>
>>
>> POW
>>
>>
>>
>> *Von: *Maxim Solodovnik <so...@gmail.com>
>> *Gesendet: *Mittwoch, 10. Juni 2020 09:07
>> *An: *Openmeetings user-list <us...@openmeetings.apache.org>
>> *Betreff: *Re: Openmeetings clients behind strict firewall with only TCP
>> ports 80 & 443 allowed
>>
>>
>>
>> Hello POW,
>>
>>
>>
>> TURN server should be such proxy ....
>>
>>
>>
>> On Tue, 9 Jun 2020 at 13:04, Peter-Otto Weber <cy...@hotmail.de>
>> wrote:
>>
>> Hello,
>>
>>
>>
>> i have it running on 80/443 but also needed to open TCP/UDP ports in
>> Firewall.
>>
>>
>>
>> As the server is hosted by „myself“ i guess i can trust this kind of
>> configuration.
>>
>>
>>
>> The alternative would be „installing an app“.
>>
>>
>>
>> Of course having only tcp and 443 would allow the use of a proxy and no
>> need for firewall changes. But i guess this will be not easy.
>>
>>
>>
>> But it would be a real good thing as esp. In large companies every
>> special configuration should be avoided.
>>
>>
>>
>> Maybe setting up any kind of gateway computer could solve this problem?
>>
>>
>>
>> POW
>>
>>
>>
>> *Von:* Maxim Solodovnik <so...@gmail.com>
>> *Gesendet:* Freitag, 5. Juni 2020 03:59
>> *An:* Openmeetings user-list <us...@openmeetings.apache.org>
>> *Betreff:* Re: Openmeetings clients behind strict firewall with only TCP
>> ports 80 & 443 allowed
>>
>>
>>
>> Hello,
>>
>>
>>
>> On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com> wrote:
>>
>> Dear all,
>>
>> Does anybody have a installation where openmeetings (ver 5.0.x) clients
>> are behind strict firewall with only TCP ports 80 and 443 allowed ?
>>
>>
>>
>> AFAIK this is impossible
>>
>>
>>
>> I know I can use TCP TURN for signalling. How to switch client to media
>> server communication from UDP to TCP ? Is it possible with openmeeting with
>> kurento as media server if so, please advise what are the things I need to
>> do ?
>>
>>
>>
>> This _might_ be possible but will require code modification
>>
>> Why you want to switch to TCP?
>>
>>
>>
>>
>>
>> Regards
>>
>> Lalit Patel
>>
>>
>>
>>
>> --
>>
>> Best regards,
>> Maxim
>>
>>
>>
>>
>> --
>>
>> Best regards,
>> Maxim
>>
>>
>>
>
>
> --
> Best regards,
> Maxim
>

Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Maxim Solodovnik <so...@gmail.com>.
You can use TCP mode :)
(not sure why do you need this, UDP is faster ....)

On Thu, 11 Jun 2020 at 12:23, Peter-Otto Weber <cy...@hotmail.de> wrote:

> So using turn  i do not need udp?
>
>
>
> Really complicated stuff…
>
>
>
> But if this would be true, OM should not Need UDP Ports if i am using TURN?
>
>
>
> POW
>
>
>
> *Von: *Maxim Solodovnik <so...@gmail.com>
> *Gesendet: *Mittwoch, 10. Juni 2020 09:07
> *An: *Openmeetings user-list <us...@openmeetings.apache.org>
> *Betreff: *Re: Openmeetings clients behind strict firewall with only TCP
> ports 80 & 443 allowed
>
>
>
> Hello POW,
>
>
>
> TURN server should be such proxy ....
>
>
>
> On Tue, 9 Jun 2020 at 13:04, Peter-Otto Weber <cy...@hotmail.de> wrote:
>
> Hello,
>
>
>
> i have it running on 80/443 but also needed to open TCP/UDP ports in
> Firewall.
>
>
>
> As the server is hosted by „myself“ i guess i can trust this kind of
> configuration.
>
>
>
> The alternative would be „installing an app“.
>
>
>
> Of course having only tcp and 443 would allow the use of a proxy and no
> need for firewall changes. But i guess this will be not easy.
>
>
>
> But it would be a real good thing as esp. In large companies every special
> configuration should be avoided.
>
>
>
> Maybe setting up any kind of gateway computer could solve this problem?
>
>
>
> POW
>
>
>
> *Von:* Maxim Solodovnik <so...@gmail.com>
> *Gesendet:* Freitag, 5. Juni 2020 03:59
> *An:* Openmeetings user-list <us...@openmeetings.apache.org>
> *Betreff:* Re: Openmeetings clients behind strict firewall with only TCP
> ports 80 & 443 allowed
>
>
>
> Hello,
>
>
>
> On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com> wrote:
>
> Dear all,
>
> Does anybody have a installation where openmeetings (ver 5.0.x) clients
> are behind strict firewall with only TCP ports 80 and 443 allowed ?
>
>
>
> AFAIK this is impossible
>
>
>
> I know I can use TCP TURN for signalling. How to switch client to media
> server communication from UDP to TCP ? Is it possible with openmeeting with
> kurento as media server if so, please advise what are the things I need to
> do ?
>
>
>
> This _might_ be possible but will require code modification
>
> Why you want to switch to TCP?
>
>
>
>
>
> Regards
>
> Lalit Patel
>
>
>
>
> --
>
> Best regards,
> Maxim
>
>
>
>
> --
>
> Best regards,
> Maxim
>
>
>


-- 
Best regards,
Maxim

AW: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Peter-Otto Weber <cy...@hotmail.de>.
So using turn  i do not need udp?

Really complicated stuff…

But if this would be true, OM should not Need UDP Ports if i am using TURN?

POW

Von: Maxim Solodovnik<ma...@gmail.com>
Gesendet: Mittwoch, 10. Juni 2020 09:07
An: Openmeetings user-list<ma...@openmeetings.apache.org>
Betreff: Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Hello POW,

TURN server should be such proxy ....

On Tue, 9 Jun 2020 at 13:04, Peter-Otto Weber <cy...@hotmail.de>> wrote:
Hello,

i have it running on 80/443 but also needed to open TCP/UDP ports in Firewall.

As the server is hosted by „myself“ i guess i can trust this kind of configuration.

The alternative would be „installing an app“.

Of course having only tcp and 443 would allow the use of a proxy and no need for firewall changes. But i guess this will be not easy.

But it would be a real good thing as esp. In large companies every special configuration should be avoided.

Maybe setting up any kind of gateway computer could solve this problem?

POW

Von: Maxim Solodovnik <so...@gmail.com>>
Gesendet: Freitag, 5. Juni 2020 03:59
An: Openmeetings user-list <us...@openmeetings.apache.org>>
Betreff: Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Hello,

On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com>> wrote:
Dear all,
Does anybody have a installation where openmeetings (ver 5.0.x) clients are behind strict firewall with only TCP ports 80 and 443 allowed ?

AFAIK this is impossible

I know I can use TCP TURN for signalling. How to switch client to media server communication from UDP to TCP ? Is it possible with openmeeting with kurento as media server if so, please advise what are the things I need to do ?

This _might_ be possible but will require code modification
Why you want to switch to TCP?


Regards
Lalit Patel


--
Best regards,
Maxim


--
Best regards,
Maxim


Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Maxim Solodovnik <so...@gmail.com>.
Hello POW,

TURN server should be such proxy ....

On Tue, 9 Jun 2020 at 13:04, Peter-Otto Weber <cy...@hotmail.de> wrote:

> Hello,
>
>
>
> i have it running on 80/443 but also needed to open TCP/UDP ports in
> Firewall.
>
>
>
> As the server is hosted by „myself“ i guess i can trust this kind of
> configuration.
>
>
>
> The alternative would be „installing an app“.
>
>
>
> Of course having only tcp and 443 would allow the use of a proxy and no
> need for firewall changes. But i guess this will be not easy.
>
>
>
> But it would be a real good thing as esp. In large companies every special
> configuration should be avoided.
>
>
>
> Maybe setting up any kind of gateway computer could solve this problem?
>
>
>
> POW
>
>
>
> *Von:* Maxim Solodovnik <so...@gmail.com>
> *Gesendet:* Freitag, 5. Juni 2020 03:59
> *An:* Openmeetings user-list <us...@openmeetings.apache.org>
> *Betreff:* Re: Openmeetings clients behind strict firewall with only TCP
> ports 80 & 443 allowed
>
>
>
> Hello,
>
>
>
> On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com> wrote:
>
> Dear all,
>
> Does anybody have a installation where openmeetings (ver 5.0.x) clients
> are behind strict firewall with only TCP ports 80 and 443 allowed ?
>
>
>
> AFAIK this is impossible
>
>
>
> I know I can use TCP TURN for signalling. How to switch client to media
> server communication from UDP to TCP ? Is it possible with openmeeting with
> kurento as media server if so, please advise what are the things I need to
> do ?
>
>
>
> This _might_ be possible but will require code modification
>
> Why you want to switch to TCP?
>
>
>
>
>
> Regards
>
> Lalit Patel
>
>
>
>
> --
>
> Best regards,
> Maxim
>


-- 
Best regards,
Maxim

AW: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Peter-Otto Weber <cy...@hotmail.de>.
Hello,

i have it running on 80/443 but also needed to open TCP/UDP ports in Firewall.

As the server is hosted by „myself“ i guess i can trust this kind of configuration.

The alternative would be „installing an app“.

Of course having only tcp and 443 would allow the use of a proxy and no need for firewall changes. But i guess this will be not easy.

But it would be a real good thing as esp. In large companies every special configuration should be avoided.

Maybe setting up any kind of gateway computer could solve this problem?

POW

Von: Maxim Solodovnik <so...@gmail.com>
Gesendet: Freitag, 5. Juni 2020 03:59
An: Openmeetings user-list <us...@openmeetings.apache.org>
Betreff: Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Hello,

On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com>> wrote:
Dear all,
Does anybody have a installation where openmeetings (ver 5.0.x) clients are behind strict firewall with only TCP ports 80 and 443 allowed ?

AFAIK this is impossible

I know I can use TCP TURN for signalling. How to switch client to media server communication from UDP to TCP ? Is it possible with openmeeting with kurento as media server if so, please advise what are the things I need to do ?

This _might_ be possible but will require code modification
Why you want to switch to TCP?


Regards
Lalit Patel


--
Best regards,
Maxim

Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Maxim Solodovnik <so...@gmail.com>.
Hello,

On Thu, 4 Jun 2020 at 19:38, Lalit Patel <lk...@gmail.com> wrote:

> Dear all,
> Does anybody have a installation where openmeetings (ver 5.0.x) clients
> are behind strict firewall with only TCP ports 80 and 443 allowed ?
>

AFAIK this is impossible


> I know I can use TCP TURN for signalling. How to switch client to media
> server communication from UDP to TCP ? Is it possible with openmeeting with
> kurento as media server if so, please advise what are the things I need to
> do ?
>

This _might_ be possible but will require code modification
Why you want to switch to TCP?


>
> Regards
> Lalit Patel
>


-- 
Best regards,
Maxim

Re: Openmeetings clients behind strict firewall with only TCP ports 80 & 443 allowed

Posted by Rohit Dhamal <ro...@yahoo.com>.
Hello, I am also facing the same problem, upon searching the web, I can see that there are udp to tcp converters. I hope the experts here could shed some light. This is infact needed. Thank you.
Regards, Rohit Dhamal.

Sent from Yahoo Mail on Android 
 
  On Thu, 4 Jun 2020 at 18:08, Lalit Patel<lk...@gmail.com> wrote:   Dear all, Does anybody have a installation where openmeetings (ver 5.0.x) clients are behind strict firewall with only TCP ports 80 and 443 allowed ? I know I can use TCP TURN for signalling. How to switch client to media server communication from UDP to TCP ? Is it possible with openmeeting with kurento as media server if so, please advise what are the things I need to do ?
RegardsLalit Patel