Cisco LNS realm redirection
aland at deployingradius.com
Wed Mar 15 22:25:51 CET 2017
On Mar 13, 2017, at 12:49 PM, Richard Savage <rich at quavey.co.uk> wrote:
> Im just looking to see if someone can point me in the right direction. I have a slight issue in that im trying to repoint a PPP session that is terminating on a cisco LNS(220.127.116.11) from a DSL carrier (TT/BTW) to another LNS (18.104.22.168) (but the carrier (TT/BTW) dont get to see the customer LNS direct). We get the initial request from the carrier and send back an access accept to the carrier to land this on the LNS which is all fine, then we get the access request from our LNS which we then need to reply back with a different LNS IP (22.214.171.124) instead of itself (126.96.36.199) to tell the cisco LNS to forward the PPP session onto the other LNS. Would be good if we can do this based on realm. Is this possible and whats the best way of achieving this as there seems little info on how to achieve this.
> Im running freeradius 2.1.12
Honestly... upgrade. 2.1.12 is many years old. The newer versions are better, simpler, and have better documentation.
> *NEEDS TO SAY:*
> Tunnel-Server-Endpoint:0 = "188.8.131.52"
> Tunnel-Type:0 = L2TP
> Tunnel-Client-Auth-Id:0 = "XXXXXXX-TT"
> Attr-69 = 0x00c5f560efa721d0f0cd39b73e64ca1145004a
> Tunnel-Preference:0 = 1
So... edit raddb/sites-enabled/default to do that.
We don't know where these values come from, so we can't really offer any detailed suggestion.
i.e. the only reason the server answers A instead of B is because you told it to answer A. If you want it to answer B, well... tell it to answer B.
More information about the Freeradius-Users