What ports does cgate try to use?

Hi,

We have been trying to get cgate working through my firewall (smoothwall).

So far we have cgate running as a service on a wintel box. Various computers around the house can connect via toolkit happily as they are in the access file.

All good so far.

Now I want my installer to be able to access cgate from outside the firewall.

I assumed adding his ip to the access file and alllowing access on 20022 would be enough in the firewall config but I see from the firewall logs that he never gets as far as cgate - the firewall is rejecting him because he is coming in on a different port everytime. So far we have seen toolkit try to connect to the following ports even though it is set as 20022 in the remote connect properties of toolkit

20021 20022 20023 20025 20026 20028 20126

Any ideas what is going on ?


Thanks
Chris

 

The config options that matter to Toolkit are:


#### secure.port-base:
# Base port number for SSL secured ports
# Default Value: 20123
# Scope: global
# Effective on: restart
###
secure.port-base=20123

#### load-change-port:
# TCPIP port to use for load change port
# Default Value: 20025
# Scope: global
# Effective on: restart
###
load-change-port=20025

#### event-port:
# TCP port number for the event interface
# Default Value: 20024
# Scope: global
# Effective on: restart
###
event-port=20024

#### config-change-port:
# Port number to use for the config change port
# Default Value: 20026
# Scope: global
# Effective on: restart
###
config-change-port=20026

Tica, Circa, Piced etc... need this port as well:

#### command-port:
# TCP port number for the command interface
# Default Value: 20023
# Scope: global
# Effective on: restart
###
command-port=20023

Toolkit will only accept using the default values, this is deliberate as we plan on changing this to simplify things in the future (reduce it down to one port).

 

Should 20022 be in there also?

Ta Chris

 

Not that I'm aware of

 

Oh its just that when you connect to a remote cgate in toolkit you give an ip and it lists that port next to it.

Chris

 

Just checked the source code...

C-Bus Toolkit uses the following ports 20123, 20025, 20024 & 20026.

All other apps use port 20023 and optionally 20025, 20024 & 20026.

My copy of C-Bus Toolkit 1.1.8 reports using port 20021 for remote connections .... which it doesn't. I haven't ever seen any references to port 20022.

 

BTW , this is entered in our change management system.

 

Quite possibly it was 21 - I was at work when I wrote the comment not in front of toolkit to check. Hopefully you are just going to remove that box.

Thanks for your help

Chris

 

The plan is (no timeframe) to reduce the number of ports required down to one (makes configuration easier) and allow it to be editable in Toolkit. Since the port can be changed in C-Gate it makes sense to be able to change it in Toolkit. This would only be a benefit to a minority, but may prove essential for configraing access through firewalls or to prevent conflicts with other software packages. No promises on when or if any of this happens ofcourse.

 

Thanks for all the help - cgate is now accessable from anywhere through my firewall once the ports you listed had been forwarded to the appropriate server.

I have of course implemented access control



Chris