[Paul Tiffany]

Thanks, Robert.  Actually the named ports work just fine outside of Cloverleaf…  For example, I can use “telnet 10.200.1.1 testport” and it will connect to the correct port that “testport” refrences.

Thanks for the thought, I will revist the Red Hat forums again just in case.

[Paul Tiffany]

bump

[Paul Tiffany]

Thanks for your input.  I’ll gladly let you know what the final resolution is.

There isn’t a “range” that will work.  For example, even port 1 which is 0001h (hexadecimal) becomes 0100h when you flip the endianness.  🙁

The only ports that we have found that work are when the individual bytes are the same.  For example port 4626 (decimal) would still be 4626 — because 1212h flipped is still 1212h.

So ultimately there are only 255 ports that we could use that are the same regardless of endianness.  Ports that work: 257, 514, 771, 1028, etc…

Clear as mud, right?

Ultimately I am still looking for a setting in Linux or confirmation of a Cloverleaf bug.

Thanks all!!!

[Paul Tiffany]

Thanks for all the replies.  I have discovered why we are having trouble, but I can’t tell at this point if it is due to a Cloverleaf bug, or an OS setting.

My /etc/services file (snippet):

---

testport1 10000/tcp

testport2 20000/tcp

When I cranked-up the EO I discovered that named port “testport1” (10000) was getting converted to 4135.  I thought this was an odd conversion.  So I tried using “testport2” (20000).  It was converted to 8270.  I did a little bit of math and noticed that 8270 is double 4135.  Hmm.  That discovery (plus a co-worker saying the word “hexadecimal” at that moment) led me to try 10000 and 20000 as hex.  Results were 2710h and 4E20h respectively.  Now if you change the “endianness” from big-endian to little-endian you get 1027h (4135) and 204Eh (8270).  See the pattern?  (Hint: flip the bytes.)  I tried this with several ports to the same result.

dec port -> hex port -> flip bytes -> dec port

10000 -> 2710h -> 1027h -> 4135

20000 -> 4E20h -> 204Eh -> 8270

Fun, eh?

So, bottom-line.  Do I have a Cloverleaf bug with named ports, or an OS setting to fix?

My hardware is little-endian.  By default “network byte-order” is big-endian.  I’m running Cloverleaf 5.5 on RedHat 4 on Xeon (little-endian) processors.

Any thoughts?  Do I need to clarify this jumbled mess of an explanation?

[Paul Tiffany]

Thanks, Jim.  It’s good to know that it works under AIX.  Does anyone have it working under Linux?  Is there such a thing as “port permissions” per an application (Cloverleaf)?  Hmm…

[Paul Tiffany]

Thanks, Russ.

[Paul Tiffany]

Look in your Alert Configurator for an alert looking at “e:quovadxqdx5.3” and change it to “e:\quovadx\qdx5.3\”.

[Author]

Replies