I know of a few other people that have gotten clustering to work other than Sacha and I. The multicast route is just one of the few possible things that could go wrong. I'll get you going Jon, just give me some time.
Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jon Martin > Solaas > Sent: Wednesday, June 12, 2002 12:59 PM > To: [EMAIL PROTECTED] > Subject: SV: [JBoss-user] adding multicast route on Win2k > > > > >Hope I have understood your question correctly :-) > > Uh, it was an answer, not a question, but anyway, your answer > seems to confirm mine :-) > > Btw, isn't the right term broadcast and not multicast? > > The wole question here is about getting clustering and farming up > on w2k. Clusters are implemented using JavaGroups, and the group > members are supposed to discover the others using broadcasting > (or multicasting). But for some reason it doesn't work (on my > box that is), with or without the famous route mentioned in my post. > > The basic setup/configuration is quite simple, so it'd be cool if > anybody with two or more networked w2k-machines actually managed > to get it up and running. Use the `run -c all` to run and put a > farm-service.xml as described in the QuickStart guide in the > ...server\all\deploy dir. "Anything" in the ...server\all\farm > directory (that appears automagically as soon as the > farm-service.xml is deployed) will get distributed with failover > and loadbalancing clusterwide. > > -- > Best Regards, > [EMAIL PROTECTED] > > -----Opprinnelig melding----- > Fra: Rajesh Acharya [mailto:[EMAIL PROTECTED]] > Sendt: 12. juni 2002 18:26 > Til: [EMAIL PROTECTED] > Emne: Re: [JBoss-user] adding multicast route on Win2k > > > Hope I have understood your question correctly :-) > Multicast is on by default on Windows while we need to do it > explicitly on > Linux. With newer versions of Linux (Mine is RedHat) the > multicast is enabled > by default with increased need of P2P systems trying to publish > and discover > each others' presence. > > Hope this helps. > Rajesh > > On Wednesday 12 June 2002 20:36, you wrote: > > Isn't this present by default in the routing table on w2k? I remember > > having to configure this manually on linux 2.0 in order to get > dhcp-server > > to work, but that is long ago ... > > > > Here is my routing-table (that I have not altered, use `route > print` to see > > yours): > > > > <snip> > > > > > ================================================================== > ========= > > Interface List > > 0x1 ........................... MS TCP Loopback interface > > 0x2 ...00 50 04 29 8d 9c ...... FE575 Ethernet Adapter > > > ================================================================== > ========= > > > ================================================================== > ========= > > Active Routes: > > Network Destination Netmask Gateway > Interface Metric > > 0.0.0.0 0.0.0.0 172.16.2.1 > 172.16.3.30 1 > > 127.0.0.0 255.0.0.0 127.0.0.1 > 127.0.0.1 1 > > 172.16.2.0 255.255.254.0 172.16.3.30 > 172.16.3.30 1 > > 172.16.3.30 255.255.255.255 127.0.0.1 > 127.0.0.1 1 > > 172.16.255.255 255.255.255.255 172.16.3.30 > 172.16.3.30 1 > > 224.0.0.0 224.0.0.0 172.16.3.30 > 172.16.3.30 1 > > 255.255.255.255 255.255.255.255 172.16.3.30 > 172.16.3.30 1 > > Default Gateway: 172.16.2.1 > > > ================================================================== > ========= > > Persistent Routes: > > None > > > > </snip> > > > > I think the entry > > > > 172.16.2.0 255.255.254.0 172.16.3.30 > 172.16.3.30 1 > > > > would be the result after applying a w2k-version of the example > route add > > -net linux-command in your post. My IP is 172.16.3.30 and netmask > > 255.255.254.0, so I could add this route with the command > > > > route add 172.16.2.0 MASK 255.255.254.0 172.16.3.30 metric 1 if 0x2 > > > > but it's already there, so ... > > > > The "173.16.3.30"-part is actually the gateway address for my > network. My > > PC is it's own gateway to the network it's on. The linux-variant of the > > route command uses the -net option and a local device (like eth0) > > as gateway-specification for the route. As the gateway-ip is specified, > > it seems w2k is smart enough that you can skip the device "if 0x2"-part. > > > > Hence > > > > `route add 224.0.0.0 MASK 240.0.0.0 224.50.50.50 metric 1` > > > > should do the trick, if your IP is 224.50.50.50. > > > > Still no clustering, though ... > > _______________________________________________________________ > > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > _______________________________________________________________ > > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________________________ Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
