Matteo <[email protected]> writes:
Hi, alright, if on my server I run $netcat -l 0.0.0.0 myport
and then from a remote machine I do a: $netcat -v serverIP
myport
I get a successful TCP connection.
Still my node won't bind to it.
One doubt remains: I am binding a node to an address that is not
of
the machine where the node is located.
A few of cloud providers that I have used give you something they
call
an Elastic IP. This IP is basically public and they NAT it 1:1 to
a
local IP you get in your VPC. It's possible that this public IP
isn't
assigned to any network interface on the OS.
Looking at the documentation for the TCP transport, it seems to me
that
the IP needs to be assigned to one of the interfaces on the
machine[1]. Can you check if you have the IP assigned to an
interface
with `ifconfig` or `ip addr`?
On Mon, Apr 20, 2020 at 9:46 AM Arnaud Loonstra
<[email protected]>
wrote:
What you're describing should be perfectly possible. Perhaps
check
your network setup first. You could just test with netcat
whether
you're network setup is correct.
Rg,
Arnaud
On 20-04-2020 17:10, Matteo wrote:
> Hi Kevin, I opened port forwarding on my router and still the
> node
> cannot bind to my server ip address:port. I tried having my
> node
> inside my DMZ and still nothing. I am starting to wonder if
> the
> cloud provider (where my server resides) blocks some ports or
> if
> there is a config I need to work on, on the server side. I
> opened
> that port on my ubuntu server via iptables, but maybe I need
> to
> use ufw? I'll dig more.
> Is it confirmed that Zyre can connect to a remote tcp address
> right? I mean an address that is outside of the node LAN
> Thank you
> On Mon, Apr 20, 2020 at 2:20 AM Kevin Sapper
> <[email protected] <mailto:[email protected]>>
> wrote:
> Hi Matteo, maybe you need Port forwarding from your router to
> the
> peer?
> Matteo <[email protected]
> <mailto:[email protected]>> schrieb am Mo.,
> 20. Apr. 2020,
> 03:55:
> Hi all, I am using Zyre and I am trying to bind to a server
> (that
> I have control over), server has a public address and I tried
> binding to a "9999" port that where I accept all incoming tcp
> connections (as a test) but so far I had no luck. The node
> cannot
> bind to it.
> I know I am probably missing something silly.
> Any input?
> -- Matteo _______________________________________________
> zeromq-dev mailing list [email protected]
> <mailto:[email protected]>
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev> >
> _______________________________________________ zeromq-dev
> mailing
> list [email protected]
> <mailto:[email protected]>
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev> >
>
> -- Matteo
> _______________________________________________ zeromq-dev
> mailing
> list [email protected]
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev> >
_______________________________________________ zeromq-dev
mailing
list [email protected]
https://lists.zeromq.org/mailman/listinfo/zeromq-dev>
Footnotes:
[1] Assigning a local address to a socket
(http://api.zeromq.org/2-1:zmq-tcp)
Best,
--
Narendra Joshi
_______________________________________________
zeromq-dev mailing list
[email protected]
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
