That message is part of a stop operation from systemctl stop|0) # Stop all daemons at level '0' or 'stop' stop_watchfrr if [ "$dmn" != "watchfrr" ]; then [ -n "${dmn}" ] && eval "${dmn/-/_}=0" stop_prio 0 $dmn fi if [ -z "$dmn" -o "$dmn" = "zebra" ]; then echo "Removing all routes made by FRR." The default route should come right back upon restart. If you do not want routes removed by FRR on shutdown feel free to remove this section from the tool donald On Thu, Aug 9, 2018 at 4:37 PM, Brandon Applegate <brandon@burn.net> wrote:
I’m having quite the day today :/
This is Ubuntu 18.04. I have a static IP and default route configured. I’m using Ansible to provision these machines.
I logged into the console on the box and ran ‘watch “ip route show”’ - to keep an eye on the routing table. As soon as ansible installed FRR - my default route was gone.
I see this in the logs on the box:
Aug 9 16:24:41 ubuntu frr[2186]: Removing all routes made by FRR.
Technically the default route was there before FRR. So if that is what is removing it - color me confused. Once this happens - ansible gets stuck (my ansible is running from a box on a different subnet and therefore needs the default route to stay stable).
Can someone explain this behavior to me ? Is there something I can do ? Put a temp static route in for my ansible host ? Add a route in a manner that FRR won’t touch it yet ? Would it help to have FRR config in place beforehand (I can do this in ansible easy enough) ?
Many thanks in advance on this. I’m so so close on this project I’m working on. Just need to get over this bump.
-- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 0641 D285 A36F 533A 73E5 2541 4920 533C C616 703A "For thousands of years men dreamed of pacts with demons. Only now are such things possible."
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog