+1 also:
https://github.com/zeromq/zyre/blob/055219523325cef4e87941e07abc39718d7350e4/src/zyre_node.c#L948 moving to a pattern where you’re actively tracking peers as part of “the loop” and forcefully expiring them when they’re un-responsive (active management) is probably more the way to go. > On Aug 2, 2016, at 7:52 AM, Kevin Sapper <kevinsappe...@gmail.com> wrote: > > Hi Dharani, > > have a look how zyre handles peers: > https://github.com/zeromq/zyre/blob/055219523325cef4e87941e07abc39718d7350e4/src/zyre_node.c#L555 > > //Kevin > > > > 2016-08-02 11:37 GMT+00:00 dharani kumar <dharanikumars...@gmail.com>: > Hi, > I have a vpn network where the zmq router is installed on node with static ip > and all peers are installed on nodes with dynamic ip which means the ip will > change every time the vpn connection is made. If a peer node unfortunately > disconnects from the vpn network, the router wont be aware of this > disconnected peer. If the same peer reconnect to vpn but unfortunately gets a > different ip, it won't able to connect to router with same identity but > different ip. > > I can write a ping-pong code to detect dead peer but how to delete the dead > peer from router socket registry so that it allows new connection for the > same identity but from a different ip? > > Regards, > Dharani kumar > > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev -- wes wesyoung.me
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
