Show static routes in Luci

The static routes shown through cli are not shown through Luci. It would be a nice touch to have this ability in Luci.


Routes configured via luci are shown here and in status/routing.

1 Like

i know. all i am saying is not a bug. it is a feature request to show the routes in both places.

Implicit routes to directly connected networks? You kind of derive those from ip addr

2 Likes
  • Why would a route not yet created appear in active routes?
  • Why would a Kernel or other route appear where you created static routes (@brada4 alluded to this already)?
  • Why would you show configs on an [active] status page?
    • Are you asking for the ability to edit them in both places too?

I think that it was also noted that this statement is inaccurate, or perhaps you meant to word it differently?

1 Like

i am not creating a cult here :grimacing:
i am looking to add something that IMHO would look nice to see in the webUI the same info as in the CLI.

?

Basic question:

I ask because this would be the only item that has an edit ability (and IMO would change the aesthetic and pattern the developers used for the status page). We can't guess what you desire - you have to explain (in detail).

Answering the other inquiries would likewise be helpful.

It's already there. You're just looking in the wrong place.

1 Like

Example:

I have a rouing engine (for Amateur Radio) that makes ~600 [dynamic] routes.

  • I'm trying to understand why myself (or others likewise running other routing engines) would wanna see those listed as "static routes"
  • This made me realize and wonder - why do you want the non-static routes you pictured to be listed there as "static routes"

could you share where is the place in Luci that has the routes?

1 Like

Status > Routing

2 Likes

Example 2:

I'm using bird2 at home for OSPF and BGP to connect to DN42.
I have like you ~ 1000 routes.

I also know of some commercial router or firewall OS with a (web) gui, and yes, they do fail miserably on showing routes.

@atux_null there are over a couple dozen ways to manage routes. Yes in the end they all end up in one or another routing table. But lets take "static routes" as an good example:

The kernel will insert routes for directly connected networks.
The user can add routes manually with ip route add, too.
If a user now uses a dynamic routing daemon like bird or frr, most of the time the user wants to import these kernel routes (into the routing daemons routing table) too.
And most often users add additional static routes not via the kernel directly, but with the routing daemon, which then exports these routes to the kernel routing table.
One such route would be a blackhole route like for rfc1918 network, to ensure that even if a default route is present, packets with an rfc1918 destination will not leave the router.

What I want to say:

  • It's not enough the show static configured routes from luci
  • It is may not even enough or useful the show the full routing table
  • Just showing the output of ip -4 route show and ip -6 route show on the web gui gives no benefit at all IMHO.
2 Likes

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.