Opened 7 years ago

Closed 5 years ago

Last modified 4 years ago

#8493 closed enhancement (no_response)

qos-stop deletes all mangle chains, not just the ones created by qos-start

Reported by: ddxx0n Owned by: developers
Priority: response-needed Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: qos-scripts qos iptables firewall Cc:


Using custom mangle chains in firewall.user is not compatible with qos-scripts: When qos is reloaded via LuCI (Save & Apply) or /etc/init.d/qos *all* -t mangle rules are deleted in /usr/bin/qos-stop and /usr/lib/qos/ by running iptables -t mangle -F; iptables -t mangle -X

A much nicer approach would be just to delete the (insert name here) and (insert name here)_ct chains generated from /etc/config/qos, in the stock configuration it's just Default and Default_ct

Attachments (0)

Change History (5)

comment:1 Changed 7 years ago by ddxx0n

... I forgot, there are of course the references to the (insert name here) chains and the IMQ Reference, too, see iptables -t mangle -vnL

comment:2 Changed 6 years ago by kevin@…

Is the problem you are describing the same as the one in bug #4544? Looks like it was fixed in trunk by r28622 and in backfire by r28670. It should be fixed in the latest snapshot and the next 10.03.1 release candidate (RC7 or release).

comment:3 Changed 6 years ago by swalker

  • Priority changed from low to response-needed

comment:4 Changed 5 years ago by nbd

  • Resolution set to no_response
  • Status changed from new to closed

comment:5 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.