"Alex Chen" <[EMAIL PROTECTED]> wrote: > I think we are getting into the debate of how 'octet' values should > be handled.
No. We are trying to explain it to you, and you are disagreeing with us. > But the fact remains that if something is store in the DB > with the hex values of 41, 42, 43, 44, they will be displayed on > the client side as '0x41424344'. That's fine. > And when this string is resent back, the hex values of the string > "0x41424344" will not be interpreted as 41, 42 ,43, 44. Instead they > become the hex values of ASCII code '0', 'x', '4', '1', '4',' 2', > '4', '3', '4', and '4'. Again, you have not explained WHY this is happening. Just what the heck are you doing to that data, in order to make the server NOT interpret it as a series of octets? > If the 'radclient' does not interpret the octet-string, but just > print out the octets one by one, i.e. hex values '41', '42', '43' > and '44', what will we get? The ASCII codes of 'A' 'B', 'C' and 'D', right? Absolutely not. We've tried explaining this. You refuse to listen. > Similarly if other non-printable octets are printed literally, we will > probably get junk output (to the human eyes, but not to the machine.) Which is why they're printed as octets. Do you really want non-humanly-readable binary data printed out by the server? Why the heck would ANYONE think that makes sense? > It is because the radclient maps the octet values to HEX numbers do we > get the "0x41424344" string output from the four octets. Again, you're intentionally missing the point. radclient doesn't "map" the octets. It prints them out in a form for you to understand, in the same way it prints "User-Name" instead of a binary '01'. Is this so hard for you to understand? > I use the schema defined by FreeRaius and the data type of the 'Value' > field is 'varchar'. That is the only data type that maps better to > the 'octet' type. That's fine. > What am I supposed to do when I get the string "0x41424344" from > radlicent when it prints out such thing? Don't I need to remap this > into the hex values '41', '42', '43', '44'? No. That's the whole point. You don't f*ck with it. Can you PLEASE explain to me what the REAL problem is? You're so stuck on the "octets versus string" crap that I can't for the life of me figure out if there's anything in the server which needs fixing. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
