Reply
Highlighted
Established Member
Posts: 924
Registered: ‎05-28-2012
Kudos: 189
Solutions: 6

Rip Config lost on reboot 1.5

I have the following RIP config on a router at home running 1.5

However on a router Reboot the entire section of config goes AWOL

ubnt@fbdn-home# show protocols rip
 interface pptpc0
 neighbor 10.0.56.1
 redistribute {
     connected {
         route-map ripm
     }
 }

 

This happened in 1.5 Beta as well but I didn't report it then as I wasn't sure if I'd remembered to save after setting the config, however this time I've explictly saved and rebooted and it does indeed disappear
The route map and it's rules remain but the Rip config itself seems to vanish.
 
I guess it's probably something silly like the pptp interface isn't yet created at the time the config tries to apply.
 
The reason I'm running RIP over PPTP is so I can route multiple subnets over an IPSEC connection as the other Peer has a license restriction on the number of IPSEC tunnels it will support and they count each IP pair as a different tunnel

Previous Employee
Posts: 13,551
Registered: ‎06-10-2011
Kudos: 5465
Solutions: 1656
Contributions: 2

Re: Rip Config lost on reboot 1.5

Yeah currently the validation fails the configuration when the specified interface does not exist (yet), and we'll need to look into whether this is necessary. Thanks for reporting!

Established Member
Posts: 924
Registered: ‎05-28-2012
Kudos: 189
Solutions: 6

Re: Rip Config lost on reboot 1.5

Can the CLI be scripted easily?


I was thinking perhaps I could have a startup script that sleeps 30s - 1Min to give the system time to create the PPTP interface then applys and commits this config.

Previous Employee
Posts: 13,551
Registered: ‎06-10-2011
Kudos: 5465
Solutions: 1656
Contributions: 2

Re: Rip Config lost on reboot 1.5

There are some examples on scripting config changes on the forum before, for example here.

Previous Employee
Posts: 10,504
Registered: ‎06-09-2011
Kudos: 3126
Solutions: 945
Contributions: 16

Re: Rip Config lost on reboot 1.5

If you feel like hacking you can edit the template file and make the interface check a warning.

Edit the file /opt/vyatta/share/vyatta-cfg/templates/protocols/rip/interface/node.def
 and look for the line like:

commit:expression: exec "/usr/sbin/ubnt-ifctl valid-intf $VAR(@) all"

 Then add the word warn at the end.

commit:expression: exec "/usr/sbin/ubnt-ifctl valid-intf $VAR(@) all warn"

 Now if the interface hasn't been created you'll still get the error/warning messages, but the commit won't fail.

EdgeMAX Router Software Development
Reply