<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hello,<br>
<br>
Sorry to post again for the same subject, but I guess I haven't been
very clear in my last question to the list, so I'm trying to ask it
differently.<br>
<br>
I've done some drawing that illustrate the settings I've tried and also
provide the whole log, that could be seen here<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.brozs.net/wimax/wimax-freeradius.png">http://www.brozs.net/wimax/wimax-freeradius.png</a><br>
<br>
In Setup 1 (one radius with local authentication) everything is fine<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.brozs.net/wimax/wimax.log">http://www.brozs.net/wimax/wimax.log</a><br>
<br>
In setup 2 (inner request proxy to ISP radius that will answer with
Wimax Attribute)<br>
<br>
-> In that case Wholesale Radius will discard Wimax attributes
contains in the access accept from the ISP radius during the
proxification, so that the access accept does not have all the wanted
access acccept.<br>
I'm trying to understand why.<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.brozs.net/wimax/wimax-proxy1.log">http://www.brozs.net/wimax/wimax-proxy1.log</a><br>
<br>
In setup 3 (which is the solution I would like to use, ie inner request
proxy to ISP radius, and Wimax attributes are being added after
receiving the access accept from ISP Radius)<br>
-> In that case Wholesale Radius will add some of the wanted
attribute but not all the one that are in attrs<br>
I'm also trying to know why.<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.brozs.net/wimax/wimax-proxy2.log">http://www.brozs.net/wimax/wimax-proxy2.log</a><br>
<br>
Regards<br>
<br>
Thomas<br>
<br>
<br>
<br>
</body>
</html>