An example scenario for RIP over L2TP
Routing Considerations
A routing issue to consider in this set up is the fact that RIP is relatively slow to react to route changes as it only updates, by default, every 30 seconds.
To improve the responsiveness of RIP you can alter the default timers for updating, flushing and so on. You do need to keep in mind that if you lose some packets (quite possible across a lossy Internet connection) some of your routes may flap too much. So the RIP timers need to be adjusted to provide an optimal compromise between responsiveness and robustness.
In this particular example, the various RIP timers are set at half default value.
set ip riptimer update=15 invalid=90 holddown=60 flush=150
Consideration would need to be given to each specific set up to get an optimal balance when adjusting these timers.
Page 4 AlliedWare™ OS How To Note: Dynamic Routing over L2TP
