How to use rewrite.called_station_id IN dynamic clients authorize section

[Ben Humpert]

I just saw that your customers have install a customized Purple WiFi
firmware on their router. The easiest solution would be to implement a
DynDNS like client. Then you could move away from dynamic-clients and
use FQDN names for the clients instead and the problems are solved.
You also could implement VPN (PPTP would be enough) so you could
assign IPs of an internal network to your clients. You could move away
from dynamic-clients too since each client has it's static internal
IP. You even could sync that with Radius & LDAP. However, VPN would
require you to keep a VPN server running on your side and it may cause
troubles with routing of internet traffic so I would go with the
DynDNS solution.


2015-03-26 15:32 GMT+01:00 James Wood <james.wood at purplewifi.com>:
> You are describing about a perfect scenario where customers will do as you
> ask.
>
> When you are not supplying the kit to customers, and they are big enterprise
> level customers, they will not install anything 3rd party in their existing
> network. You try getting them to install an extra piece of kit they don't
> know anything about ;) They won't do it.
>
> So we have two options, work with what they have, or drop them as a
> customer.
>
> As I said, there is no choice when we do not control/own their network, we
> have to (sadly) work with what they have. No two systems are the same and we
> try to cater for them all.
>
> Thanks
>
> James
>
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html