Is Collanos Server Based?

[Murugan]

I read Herr Helman's notes on Firewalls and proxies and understand that even if one uses 
port 9701  for sync, that CUD still requires port 443? N'est ce pas? At any rate I can have the CUD IP on 443 white listed, 24/7. so that will not be a problem.

Then for sync I would try 9701 as net admin here says that should be open all the time. But, I don't see in the preferences on the Mac OS X version (macbookPro) where to set 9701 as the preferred port?

If  Collanos Workspace successfully reaches CUD on 443 and then tries port 80 to sync with other members, but port 80 is blocked will it automatically try 9701?  And if the other member is on 80... does it matter if I am on 9701 (probably not but I had to ask) ?  Or do we need to do some configuration to get 9701 as the default port?

It's starting to get hot here in Hawaii. I would love to meet you for lunch in Ascona 

[Peter Helfenstein]

There are three types of servers supporting Collanos Workplace's communication.
First the CUD, your workplace communicates with its port 443 using https protocol.
Then there is a rendezvous server. Workplace tries to connect to this server's port 9701 and then if that does not work to its port 80 using either TCP for 9701 or http. And the third server it connects to is a relay server. Same ports are addressed as for rendezvous.

You do not need to do anything regarding the port preferences. This is all handeled by Collanos Workplace. It just tries to connect these servers like that.

This means minimally outgoing communication to port 443 of superedge02.collanos.net and to port 80 of one of the rendezvous and relay servers from the list mentioned before must pass and the system works.

If outgoing traffice to the ports 97xx of the rendezvous and relay servers is enabled even better.

If incoming traffic to port 80 or 97xx is open and a peer is not in a network with Network Adress Translation (NAT) then Collanos Workplace can be directly communicating with other peers in the network.

Users should not need to care about all this. But it is helpful to have this information in case you need to setup firewalls to let pass Collanos traffic.

Regards
Peter

[Murugan]

Aloha Peter

Excellent, thank you. Very clear.

This means I will need the IP's for both the Rendezvous server(s) and the relay server(s)

Cheers

[Peter Helfenstein]

Hello Murugan
Correct. You need at least CUD, 1 Rendezvous and 1 Relay. Since CUD and 1 Rendezvous is on superedge02.collanos.net Collanos will work if that server and 1 relay server is accessible. But it is better to have the communication to the ports of all servers listed as rendezvous and relay opened. Sometimes a relay or rendezvous cannot accept new peers since they are fully loaded.
A nice Sunday afternoon in Hawaii!
Cheers
Peter

[Murugan]

Mon Cher Peter:

Aloha..not sure we are connecting: don't  then need also the IP for 1 relay server? "But it is better to have the communication to the ports of all servers listed as rendezvous and relay opened."  right, but I need the IP's of those machines to do that..., so: do you have a place that lists all the IP's? I need the actual IP's to enter into the firewall rules here.  206.165.150.222  is superedge02.collanos.net   but that can't be the only machine... ?

on the "server-based"  issue: As it turns out we DO have a machine that is running 24/7  (our mail/voip server) which is outside the fire wall, has a public IP... we just forgot about it... I will set up the "mothership/sync" perpetually running instance of collanos on there... I assume we have to invite her to every work space for her to do the sync job....i.e the mother ship instance of collanos cannot do syncing unless it is a member of a work space.

[Peter Helfenstein]

Hi Murugan,
sorry for the misunderstanding. I an earlier reply I sent you the address where you can find all the relay and rendezvous addresses listed:
http://www.collanos.com/files/jxta_seeding/relay.xml for the relays
and
http://www.collanos.com/files/jxta_seeding/rendezvous.xml for the rendezvous.
If you open them you find each address listed twice (for port 9701 and 80).
Regards
Peter

[Murugan]

got it Thanks! Sorry I wasn't paying attention earlier:

<jxta:seeds ordered="false">
<jxta:RA>
<Dst>
<jxta:APA>
<EA>tcp://194.126.200.14:9701</EA> etc.

[snip]

I think we are "ready to roll" now..

Take care.