tiger, that's correct. store it in the calling-station-id attr pair. while waiting for the ras setup, you can still test your piece of code by inserting it into a radius client software which will act like a RAS sending authentication and accounting packets. then just point it to your radius server in debug mode which is supposed to print out all of the attr pairs it receives. so you'll know you that at least you encoded the caller-id properly (which is more time consuming than parsing the caller-id string from the modem output right?). i think most good radius server packages come with that radius client test suite.
pong > i saw a website (lost URL, sorry) that indicated that different modems > report the CID in different ways. in this case, i think he said that > the particular model of US Robotics he was working with reported it in > the same line as the line speed/protocols, etc. it was just an extra > field delimited with forward slash. so you could get radius to store > that information, but you'd have to hack the RADIUS code (or get some > radius that had support for that feature). since there's more than one > way (apparently) to receive the CID, i'd just edit the RADIUS code to > store the CID in the Calling-Station-ID attribute pair, or wherever. > > i was going to go ahead and do that here, but the guy configuring the > dialup server gave up on linux/cyclom-y/portslave and installed W2K > advanced server instead. if i can get him to go with linux then i may > get around to trying that yet. (i have influence here, but i don't > make the final decision on linux since it's his department, his box, > oh well). > > tiger > _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
