Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support to specify dedicated ports for xmlrpc/binrpc, etc. interconnections. #192

Open
jens-maus opened this issue Jan 31, 2025 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@jens-maus
Copy link
Contributor

When viewing recent lighttpd-access.log logs in a CCU connection one can note the following connection track:

127.0.0.1 127.0.0.1:1999 - [31/Jan/2025:12:05:37 +0100] "POST / HTTP/1.1" 200 132 "-" "Go-http-client/1.1"
127.0.0.1 127.0.0.1:9292 - [31/Jan/2025:12:05:37 +0100] "POST /bidcos HTTP/1.1" 200 123 "-" "Go-http-client/1.1"

These connections originate from CCU-Jack. However, when CCU-Jack is running on the CCU/RaspberryMatic itself it would be more appropriate/good to perform the interconnection between CCU-Jack and all the other interface processes (HMIPServer, rfd, etc.) using direct non-proxied connections. So for HMIPServer (HmIP) connection CCU-Jack should connect to 39292 and for rfd (BidCos) to 31999, etc. However, there does not seem to be a possibility to specify/override these ports in the ccu-jack.cfg file or somewhere from the CCU-Jack configuration page. Even better would be if CCU-Jack would automatically prefer to perform direct connections without involvement of the lighttpd proxy.

@mdzio
Copy link
Owner

mdzio commented Jan 31, 2025

Is it necessary to differentiate between a CCU3 and RaspberryMatic in this respect? Or can the "high" ports also be used on a CCU3?

@jens-maus
Copy link
Contributor Author

Is it necessary to differentiate between a CCU3 and RaspberryMatic in this respect? Or can the "high" ports also be used on a CCU3?

They also exist on a CCU3. There is actually no difference in this regard...

@mdzio mdzio added the enhancement New feature or request label Feb 1, 2025
@mdzio mdzio added this to the v2.10.1 milestone Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants