#19560: Sysupgrade to newest trunk results in router blocking all local ports
------------------------+------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: packages | Version: Trunk
Resolution: | Keywords:
------------------------+------------------------
Comment (by anonymous):
Same person who opened the ticket. After some troubleshooting, the problem
is caused by a change in behavior how the command "ip" works it seems,
because now it always will use a priority of 0 instead of automatically
downgrading it from 32765. I cant imagine this is intended behavior, but
more of a bug. The problem was triggered by executing OpenVPN which added
a default route to the table "vpn1", but the ip rules were wrong and all
had a priority of 0. I fixed it by adding a priority by hand to my ip
rules like:
#ip rules
ip rule add prio 32765 fwmark 1 table alice
ip rule add prio 32764 fwmark 2 table vpn1
ip rule add prio 32763 fwmark 3 table vpn2
ip rule add prio 32762 fwmark 4 table vpnkue
ip rule add prio 32761 fwmark 5 table main
ip rule add prio 32760 from 10.0.0.11 table alice
ip rule add prio 32759 from 10.0.0.22 table alice
and so on...
Why was this changed? Before, over the last two years, it worked that it
automatically would use the next lower priority starting from 32765
downwards.
--
Ticket URL: <https://dev.openwrt.org/ticket/19560#comment:1>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
