[zeromq-dev] zyre

[Andrew Hume]

i don’t mean to be dense here, but exactly how do you “forward” the broadcast packets between them?
i am hoping for a zeromq mechanism, or you talking about some C
thing where we do forwarding in “raw” C/TCP crap?

	andrew

> On Mar 19, 2015, at 4:47 PM, Utsav Drolia <utsavdrolia at gmail.com> wrote:
> 
> I guess you can have few nodes that are connected to both subnets forward the broadcast packets between them.
> However, for the rest of the communication, there should be routes between nodes on the 2 subnets.
> 
> On Mar 19, 2015 7:41 PM, "Andrew Hume" <andrew at humeweb.com <mailto:andrew at humeweb.com>> wrote:
> pieter,
> 
>         can you be more explicit here?
> exactly how do you “point” a node at another (persistent) node?
> 
>         andrew
> 
> > On Mar 19, 2015, at 4:29 PM, Pieter Hintjens <ph at imatix.com <mailto:ph at imatix.com>> wrote:
> >
> > You can cross subnets with Zyre (the C version) if you use gossip
> > discovery. It's not really gossip, more like federation. You put up
> > one or a few persistent nodes and point everyone to those, and they
> > distribute the knowledge of the whole network.
> >
> > On Fri, Mar 20, 2015 at 12:18 AM, Joss Gray <joss at jossgray.net <mailto:joss at jossgray.net>> wrote:
> >> zbeacon broadcasts udp packets broadcast for discovery so they won't be able
> >> to cross subnets.
> >>
> >> You will have to change the broadcast domain like you mentioned.
> >>
> >> On Thu, Mar 19, 2015 at 11:08 PM, Andrew Hume <andrew at humeweb.com <mailto:andrew at humeweb.com>> wrote:
> >>>
> >>> we’re trying to run tyre (actually, the gyre implementation) across
> >>> different subnets
> >>> (that is, one node is in 10.20.59.xx and the other in 10.120.45.xx). they
> >>> don’t see each other.
> >>> what would be the best way to have them see each other?
> >>>
> >>> we could change the broadcast domain to 255.255.0.0 but that seems vaguely
> >>> dodgy.
> >>> any other hints?
> >>>
> >>>        andrew
> >>>
> >>> _______________________________________________
> >>> zeromq-dev mailing list
> >>> zeromq-dev at lists.zeromq.org <mailto:zeromq-dev at lists.zeromq.org>
> >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev <http://lists.zeromq.org/mailman/listinfo/zeromq-dev>
> >>
> >>
> >>
> >> _______________________________________________
> >> zeromq-dev mailing list
> >> zeromq-dev at lists.zeromq.org <mailto:zeromq-dev at lists.zeromq.org>
> >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev <http://lists.zeromq.org/mailman/listinfo/zeromq-dev>
> >>
> > _______________________________________________
> > zeromq-dev mailing list
> > zeromq-dev at lists.zeromq.org <mailto:zeromq-dev at lists.zeromq.org>
> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev <http://lists.zeromq.org/mailman/listinfo/zeromq-dev>
> 
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org <mailto:zeromq-dev at lists.zeromq.org>
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev <http://lists.zeromq.org/mailman/listinfo/zeromq-dev>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150319/0d10eb87/attachment.htm>