Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Can pulse listen in other ports?
6 views
Skip to first unread message
arm...@mozilla.com
Apr 30, 2016, 9:33:49 AM4/30/16
to
It seems that martianwars could not run pulse_actions in his institute:
> My institute only allows outgoing requests for port 80, 443 (HTTP/HTTPs)
> and SSH. Pulse works on port 5761 and it won't be easy to run Pulse
> Actions with this connection.
Any suggestions?
> My institute only allows outgoing requests for port 80, 443 (HTTP/HTTPs)
> and SSH. Pulse works on port 5761 and it won't be easy to run Pulse
> Actions with this connection.
Any suggestions?
Jonas Finnemann Jensen
Apr 30, 2016, 11:59:10 AM4/30/16
to Armen Zambrano G., tools-pulse
Use a cheap VPN provider...
Or a really cheap VPS for development.
I don't really see any other good options.
events.taskcluster.net exposes pulse publicly over a custom websocket
protocol. That's what the pulse inspector uses... You could also use that,
but only for consumption of messages. And you would never use this in
production.
The construct is unreliable by nature, if websocket drops messages may drop.
tc-client for node includes a WebListener that uses events.taskcluster.net.
Note: Consider talking to you IT department. HTTP/HTTPS/SSH seems a bit
strict for a CS department..
Best of luck.
> _______________________________________________
> tools-pulse mailing list
> tools...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/tools-pulse
>
Or a really cheap VPS for development.
I don't really see any other good options.
events.taskcluster.net exposes pulse publicly over a custom websocket
protocol. That's what the pulse inspector uses... You could also use that,
but only for consumption of messages. And you would never use this in
production.
The construct is unreliable by nature, if websocket drops messages may drop.
tc-client for node includes a WebListener that uses events.taskcluster.net.
Note: Consider talking to you IT department. HTTP/HTTPS/SSH seems a bit
strict for a CS department..
Best of luck.
> tools-pulse mailing list
> tools...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/tools-pulse
>
John Ford
Apr 30, 2016, 1:15:35 PM4/30/16
to Zambrano Gasparnian, Armen, tools...@lists.mozilla.org
What about using port 80 or 443 to establish an SSH connection, then
redirect the required port through that tunnel?
redirect the required port through that tunnel?
arm...@mozilla.com
May 2, 2016, 11:29:27 AM5/2/16
to
Thank you! I will ask martianwars to look here and see what would work for him.
0 new messages