3 Oct
2016
3 Oct
'16
5:53 a.m.
Hi,
Hmmm, to follow up on this... I've gotten it to route correctly, but on the ultimate destination (i.e. at "realhome.realm"), I now get a message saying that the EAP Identity does not match User-Name, which then subsequently leads to failure. It's not quite unexpected since EAP keeps track of what User-Name *should* be.
expected - as you've messed with the User-Name - you need to keep the user-name the same, and just use unlang to make the proxy decision. the END host needs to receive the packet as is....and have the smarts to deal with it. alan