strongswan-mod-updown requires legacy iptables
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Describe the bug
Hello,
currently strongswan-mod-updown requires iptables legacy. Removing the package is not so easy either, since packages like strongswan-default depend on it. Maybe strongswan-mod-updown could be removed from strongswan-default and strongswan-full?
# opkg remove strongswan-mod-updown
No packages removed.
Collected errors:
* print_dependents_warning: Package strongswan-mod-updown is depended upon by packages:
* print_dependents_warning: strongswan-default
* print_dependents_warning: These might cease to work if package strongswan-mod-updown is removed.
* print_dependents_warning: Force removal of this package with --force-depends.
* print_dependents_warning: Force removal of this package and its dependents
* print_dependents_warning: with --force-removal-of-dependent-packages.
Terms
- I am reporting an issue for OpenWrt, not an unsupported fork.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the package definitions for strongswan-mod-updown, strongswan-default, and strongswan-full, then inspect how their dependency declarations relate to legacy iptables. Confirm the dependency behavior with the relevant OpenWrt packaging checks; done means the requested package relationships are changed only if the affected packages remain correctly installable.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100