Bug 357381 - apmscript takes down network (stopping packet forwarding) and doesn't bring it back up
apmscript takes down network (stopping packet forwarding) and doesn't bring i...
Product: Fedora
Classification: Fedora
Component: apmd (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Zdenek Prikryl
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-29 18:04 EDT by Chris Wilson
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 09:34:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
fixed apmscript (99.44 KB, application/x-rpm)
2007-10-30 05:17 EDT, Zdenek Prikryl
no flags Details

  None (edit)
Description Chris Wilson 2007-10-29 18:04:11 EDT
Description of problem:

case "$PROG" in
        if [ "$NET_RESTART" = "yes" ] ; then
                /sbin/service network stop

There is no counter-case in resume. suspend ensures that the originally active
devices are brought up via /var/run/apm-resume-post, but /etc/init.d/network
stop also stops packet forwarding:

          if [ -f /proc/sys/net/ipv4/ip_forward ]; then
                if [ `cat /proc/sys/net/ipv4/ip_forward` != 0 ]; then
                        action $"Disabling IPv4 packet forwarding: " sysctl -w

and since network is never started again, packet forwarding remains off after

If someone presses the power/suspend button on a router/firewall running apmd,
it will suspend and shut down packet forwarding, but on resume, packet
forwarding remains off and routing functions disabled.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. check that router/firewall is forwarding packets and running apm
2. press power/suspend button
3. wake up the box
4. check that it no longer forwards packets and /proc/sys/net/ipv4/ip_forward is 0
Actual results:

/proc/sys/net/ipv4/ip_forward is 0 after resume.

Expected results:

/proc/sys/net/ipv4/ip_forward should be reset to default value from
/etc/sysctl.conf by /etc/init.d/network start, which is never run.

Additional info:
Comment 1 Zdenek Prikryl 2007-10-30 05:16:13 EDT
Unfortunately, I do not have a hardware to test this now, co I create srpm with
a fix. Please, could you test it?. I'll create an attachment with srpm.

Comment 2 Zdenek Prikryl 2007-10-30 05:17:18 EDT
Created attachment 243091 [details]
fixed apmscript

Note You need to log in before you can comment on or make changes to this bug.