Re: Port selection
Vitezslav Crhonek <[email protected]>
| Newsgroups | gmane.network.open-pegasus.general |
|---|---|
| Message-ID | <[email protected]> |
On 10/20/2011 06:08 PM, Kirk Augustin wrote: > Probably not a good idea. > First of all, ports are reserved and handed out by standards committee, and you should not be using ports arbitrarily. > Second is that all clients and servers possibly connecting have to agree. > It is not one build, but all the builds of all the systems that might be involved. > The whole point is to have a well established common port. > It is not normally desirable to have any port variation. > Nor can I imagine any advantage to it, other than if there is a protocol variation, such as SSL. > So first tell us why you think you would want to use a different port? Well, I'm trying to solve the situation where default ports are already used by another service (I know that's probably not good, but I have to take it as a fact that I can't affect). Another fact is that there are more network interfaces and the second service listens only to one of them (on a different network). But Pegasus listens to all interfaces, that's the reason why I asked PEP #290, which was to add the ability to listen to a specific network interface instead of all of the interfaces. That would really solve the problem, changing Pegasus ports is just a workaround. Vitezslav Crhonek > > > Kirk Augustin > 11821 NW McNamee Rd > Portland, OR 97231 > > > HM: 503-289-4356 > WK: 503-744-8841 > > >> ________________________________ >> From: Vitezslav Crhonek<[email protected]> >> To: "[email protected]"<[email protected]> >> Sent: Thursday, October 20, 2011 7:44 AM >> Subject: Port selection >> >> Hello, >> >> Is there any possibility to set own http/https port values? >> >> I see httpPort and httpsPort options, but it seems that these options are disabled: >> >> $ cimconfig -g httpPort >> Specified property name was not found. >> CIM_ERR_NOT_FOUND: Configuration property "httpPort" >> >> Is there any way how to enable them? (Probably some env. variable during build time?) >> >> I'm also curious what happened with PEP #290: >> http://www.openpegasus.org/pp/upreviews/40/2362/orig/PEP290.html >> >> Because this feature would be useful in some situations. >> >> Best regards, >> Vitezslav Crhonek >> >> >> >>