[FROG] FRR getting started
sharpd at cumulusnetworks.com
Thu Oct 4 07:58:45 EDT 2018
On Thu, Oct 4, 2018 at 3:49 AM Heikki Lavaste
<heikki.lavaste at hotmail.com> wrote:
> I'm just getting started with FRR in EVE-NG. I have a couple of questions:
> If I use vtysh to connect, I have access to all routing protocols I have enabled in the daemons file. If I do the same with telnet to localhost 2601, I don't have the protocols. If I understand correctly, I each protocol runs with a different port number and I can connect to OSPF with 2604, etc. Is there a way to "telnet in" and have access to all protocols?
vtysh? I personally would not recommend using telnet. vtysh ensures
that commands entered are passed to all relevant daemons. This is
especially important if you have route-maps, access-lists or
prefix-lists that you want to modify in real time and have them used
across multiple daemons.
> Is there a way to get rid of the APIPA kernel routes?
remove them from the kernel? FRRouting needs to have the correct
state of the FIB in order to properly handle the rib and to properly
program the fib. Since FRRouting did not originate the routes we must
respect them. If you want to override them ensure that they are
installed with a max metric value and FRRouting will do the right
thing from there based upon the admin distance.
> frr(config)# do show ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP,
> O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
> T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
> F - PBR,
> > - selected route, * - FIB route
> B>* 184.108.40.206/32 [20/0] via 220.127.116.11, eth0.108, 00:21:59
> E 18.104.22.168/24 [90/0] is directly connected, eth0.58, 00:27:09
> C>* 22.214.171.124/24 is directly connected, eth0.58, 00:27:09
> E 126.96.36.199/24 [90/0] is directly connected, eth0.108, 00:26:51
> C>* 188.8.131.52/24 is directly connected, eth0.108, 00:26:51
> K * 169.254.0.0/16 [0/1007] is directly connected, eth0.58, 00:27:48
> K * 169.254.0.0/16 [0/1006] is directly connected, eth0.108, 00:27:48
> K>* 169.254.0.0/16 [0/1002] is directly connected, eth0, 00:27:48
> They are just cosmetic, as long as I don't use the range for any hosts in the lab, but I would like to clean up the routing table.
> Knd Regards
> Heikki Lavaste
> frog mailing list
> frog at lists.frrouting.org
More information about the frog