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

TBrookServer needs to be "isolatable" to a single IP on a physical server #15

Open
KevinLeeMorris opened this issue Apr 18, 2022 · 0 comments

Comments

@KevinLeeMorris
Copy link

In an attempt to cut out any "layer" higher than my Microsoft Windows .exe BrookServer app, (such as Apache, Nginx, or anything else), I need the ability to configure the TBrookServer component to listen ONLY on one single IP address. My server has 2 different Network Interface Cards, each with it's own IP address (x.11 and x.13). I want one of my BrookServer app exes to listen on port 443 on the x.11 IP address card and a DIFFERENT BrookServer app exe to listen on port 443 on the x.13 IP address card. (More virtual IP address can be configured on my router, so I basically have a huge number of IP + port 443 combinations, all available in software, each accessing their own domain + IP + 443 combination). At the moment, every BrookServer app listens on ALL port 443s on BOTH x.11 and x.13 IP addresses. (cports displays this as a 0.0.0.0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant