| Summary: | upnpd (linux-idg) should [re]start after firewall | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Henry Yang <henryy> |
| Component: | [OLD] Server | Assignee: | John Mylchreest (RETIRED) <johnm> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Henry Yang
2003-08-21 12:37:22 UTC
can i ask you to make the changes to /etc/init.d/upnpd.
in the depend() section can you add
after iptables
so it looks something like
depend() {
need net
after iptables
}
and report back as to your findings.
im afraid i dont have the resources to test right now.
if this does the desired effect i shall commit changes
No response in over a year. John, can you mark this RESOLVED/{NEEDINFO|TEST-REQUEST|FIXED} depending on what you want to do with it?
Closing. I can't say anything about other firewall scripts, but at least with shorewall you can configure shorewall itself to restart upnpd as needed: add to /etc/shorewall/stop: /etc/init.d/upnpd stop add to /etc/shorewall/started: /etc/init.d/upnp restart It should be sufficient to start upnpd with 'start' but 'restart' works just fine here. This has the added benefit that if you stop/start/reload/etc shorewall from commandline without using the init script then upnpd will also be restarted. |