I’m having problems understanding the steps needed to forward RADIUS traffic from 2 x RB450G to an external server connected via an OpenVPN connection.
The VPN bridge between routerA(10.0.254.2) and the external RADIUS server(10.0.254.1) works fine; I can ping both ways.
Both routers, routerA and routerB need to pass RADIUS authentication and accounting traffic to the external radius server via the VPN.
routerA(eth5 10.0.1.1) is connected to routerB(eth1 10.0.1.100). routerB’s default route is to routerA.
RADIUS traffic originating on routerA (eth3 10.1.3.0/24) & eth4 (10.1.4.0/24) needs to be forwarded to the RADIUS server via routerA(10.0.1.1)
RADIUS traffic originating on routerB (eth3 10.2.3.0/24) & eth4 (10.2.4.0/24) needs to be forwarded to the RADIUS server via routerA(10.0.1.1)
I’m lost in a world of forwarding/mangle/nat and need some advice on the ‘correct’ methods I need to implement so that the RADIUS server knows from what NAS the traffic is being sent.
Will try, but my very confusing. What you need to be sure of is that you could ping the radius from any of the ip’s. Use tracert to see where problem happens. Would probably only be a routing problem, and most probably your radius that does not have the right routing info. As a test, add a rule in nat with masquerade on the interface connected to the radius. Not the right way to do it, but should fix problem.
Was indeed a routing problem on the RADIUS server. I setup the correct routes and am able to pass AAA traffic backwards and forwards. Thanks for sending me in the right direction. Now if only FreeRADIUS would authenticate my users I’d be even more happy
I am trying the same you already realized but I get stocked before…
One local RB750 (10.0.0.1 f.ex. should be the NAS-Client - hotspot with radius server activ) should connect over pptp to another rb450g.
This rb450G is connected to the radius server.
Only all radius traffic should pass so for the radius server the NAS-IP-Address would be the 10.0.0.1 (for authentification reasons a fixed ip).
I think this you have already managed.
Can you post please your settings - I get stocked in something at the very beginning…
It is very strange also that my tunnel colapse very often - every minute - so there ist something realy wrong in my setting and the radius client has no connection to the radius server at all!
in a world of forwarding/mangle/nat and need some advice on the ‘correct’ methods I need to implement so that the RADIUS server knows from what NAS the traffic is being sent.