Actions
Feature #15641
open
Allow a route next-hop to a different address family than the route .
Status:
New
Priority:
Normal
Assignee:
-
Category:
Routing
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Description
See also #15601
Against my better judgement this is a feature request instead of a bug report.
Since a route next hop in a different address family is a valid configuration it should be allowed. It is currently denied by form validation:
It can be manually added and accepted by FreeBSD and operate normally like this:
route add -4 10.202.255.1/32 -6 2001:470:e01a:ff::1
Files
No data to display
Actions