Hi this post is really related to a post earlier this year from
someone called Serg, with subject line "About Field "Network Address" in
the OES_SP2".

I'm not sure what the etiquette is here but I wanted to get some answers
to Serg's question which nobody has answered as yet. I don't know if
replying to an old post would get a response which is which I am posting a
new one. I also wanted to correct some typos in my original response to
Serg's post.

Hi I'm wondering if anyone has any idea about Serg's enquiry.

I have just stumbled on this behaviour and it is very undesirable. I use
a perl script to authenticate users to squid based on their Network
Address attribute in eDirectory. This will stop working if I migrate to
OES Linux everywhere.

The issue can best be explained by looking at an example of the LDAP
search filter I use to find the user with a particular IP.

At the moment (for NetWare) I use filter ...
(networkAddress = \49\35\0A\14\04\0F)
.... for instance to check for user with IP address (stored as
1#ascii(10)ascii(20)ascii(4)ascii(15)). Here 1# (or Hex \49\35) signifies
IP, the hash is "just there" as a separator or something and the four
octets of the IP are stored as RAW unsigned chars).

However with OES Linux the networkAddress attribute of a connected
client workstation is not listed in the same way: the connection type
is not IP but TCP and is represented by 9# (or Hex \57\35), the four
octets are represented as before but there is a bit of stuff in between
which seems to be unpredictable - possibly the TCP/IP port number? So the
filter becomes ...
(networkAddress = \57\35\??\??\0A\14\04\0F)
.... where I cannot predict the two unsigned chars \??\??. I cannot replace
that segment of the search filter with a wildcard as - not sure if this is
an eDirectory or LDAP lmitation - it throws errors (viewable in ndstrace
as "substring match used on unsupported syntax").

Unless I can somehow predict what value to use for \?\? then my perl
script and hence my squid authentication will be broken when I move to OES
Linux. I can code around this but this will start to get fairly elaborate
and I'd prefer not to.

Please help me someone!