On Tue, Dec 15, 2009 at 01:10:20PM -0500, David Peterson wrote:
What I am not understanding at this point is how the authentication works with the username "hashed" or using "hex stuff" but the accounting doesn't. You can see on this debug that the username looks the same when its authenticated as it does when it's used for accounting yet the username in the database is clear text.
rad_recv: Access-Request packet from host 172.16.4.2 port 1812, id=152, length=192 User-Name = "{am=1}1F48C19B43C8C33846FAA9CFC58990F4@test.com" Tue Dec 15 12:03:56 2009 : Info: [sql] sql_set_user escaped user --> '{am=1}1F48C19B43C8C33846FAA9CFC58990F4@test.com' Tue Dec 15 12:03:56 2009 : Info: [wimax] WARNING: Not calculating MN-HA keys Tue Dec 15 12:03:56 2009 : Info: ++[wimax] returns updated Sending Access-Accept of id 152 to 172.16.4.2 port 1812 User-Name = "test@test.com" Tue Dec 15 12:03:56 2009 : Info: Finished request 7.
Looks like you get the clear User-Name only after you run the 'wimax' module. Run it earlier?
rad_recv: Accounting-Request packet from host 172.16.4.2 port 1813, id=13, length=239 User-Name = "{am=1}1F48C19B43C8C33846FAA9CFC58990F4@test.com"
It doesn't look like you run the 'wimax' module during the processing of accounting packets. Run it? :) -- 2. That which causes joy or happiness.