News for hackers. Stuff that matters.
Re:IP addresses and routing by corndoge on Thursday July 26, 2018 @12:34PM (#17618744)
metric 600

if two routes to the same destination exist the kernel will (in general) use the one with the lower metric

proto kernel

this is where the route came from, for most end user hosts this will be kernel but if your box is running a dynamic routing protocol this might be something like "ospf", "bgp", etc; those protocols learn routes from neighbors and install them into the kernel routing table

scope link

this is information about the distance to the nexthop, in this case link means the nexthop is on the local network

Re:IP addresses and routing by SteveNuts on Thursday July 26, 2018 @01:59PM (#17619421)
I've got a bunch of static routes on my linux boxen using iproute2 tables to send traffic down the correct interfaces, do you think there's a better way using dynamic routing? If so what should I start googling?
Re:IP addresses and routing by corndoge on Thursday July 26, 2018 @02:22PM (#17619631)
If the topology is simple then managing static routes can be way easier than doing dynamic routing correctly, otherwise I'd start looking at BGP. Your best option right now in terms of software is FRR or bird.

But first you should understand dynamic routing and decide if it's right for your use case.

https://en.wikipedia.org/wiki/Dynamic_routing

Re:IP addresses and routing by zokier on Thursday July 26, 2018 @02:58PM (#17619951)
Is there particular reason you'd go directly to BGP and not e.g. OSPF?
Re:IP addresses and routing by corndoge on Thursday July 26, 2018 @04:43PM (#17620896)
Familiarity and personal preference
Re:IP addresses and routing by SteveNuts on Thursday July 26, 2018 @02:30PM (#17619696)
Thanks!