[nanomsg] Re: is there a nanomsg socket type unaffected by nat/firewall?
- From: Achille Roussel <achille.roussel@xxxxxxxxx>
- To: nanomsg@xxxxxxxxxxxxx
- Date: Fri, 30 May 2014 15:55:21 -0700
There should be no issue once the TCP connection is established. If one side
can reach the other by establishing a TCP connection then they’ll use this pipe
for bi-directional communication and firewalls shouldn’t get in the way… have
you tried reversing the side that connects and the side that binds ? Your
firewall may be configured to let connections go out but not let them get in…
there are no enforcement of which side of the PULL/PUSH is doing the bind or
connect (this is a nice feature of nanomsg), maybe that could solve your issue.
On May 30, 2014, at 3:29 PM, Jason E. Aten <j.e.aten@xxxxxxxxx> wrote:
> I'm wondering if NN_PAIR or another nanomsg socket type can traverse a
> firewall, i.e. because it uses both directions of a socket started from the
> "inside".
>
> I'm using Push/Pull nanomsg sockets right now, and the pulls on one side are
> (as would be expected) blocked by firewall since they are listening on a port
> totally unrelated to the push.
>
> Thanks for your advice and suggestions.
>
> Jason
Other related posts:
