You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ip-rule1 utility supports the ipproto keyword, allowing us to route UDP traffic differently using the following command:
ip ru add from all ipproto udp table udp_table prior 10
The ip utility in Openwrt also supports this keyword. Howerver, In Luci, there is no option to configure the ipproto keyword. The network configuration file /etc/configure/network also does not support it either. 2
As a result, to implement routing according to L4 protocol, we can only use command line or route using fwmark with the help of nftables. It would be more convenient if support for the ipproto keyword were added.
Steps to reproduce:
go to: Network → Routing→ IPv4 rules
no method to set ipproto
Additional Information:
OpenWrt version information from system /etc/openwrt_release
This is not complex to add within luci, but luci depends on what exists in the openwrt base system. I sent a patch for netifd to the mailing list and opened a PR which will probably take about 17 years to get acknowledged.
The
ip-rule
1 utility supports theipproto
keyword, allowing us to route UDP traffic differently using the following command:The
ip
utility in Openwrt also supports this keyword. Howerver, In Luci, there is no option to configure theipproto
keyword. The network configuration file/etc/configure/network
also does not support it either. 2As a result, to implement routing according to L4 protocol, we can only use command line or route using
fwmark
with the help of nftables. It would be more convenient if support for theipproto
keyword were added.Steps to reproduce:
ipproto
Additional Information:
OpenWrt version information from system
/etc/openwrt_release
I have also installed
ip-full
Footnotes
https://man7.org/linux/man-pages/man8/ip-rule.8.html ↩
https://openwrt.org/docs/guide-user/network/routing/ip_rules ↩
The text was updated successfully, but these errors were encountered: