Bug 11487 - WIO can cause IPFire box shutdown
Summary: WIO can cause IPFire box shutdown
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: x86_64 Linux
: Will only affect a few users Crash
Assignee: Stephan Feddersen
QA Contact: Alexander Marx
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-08 17:01 UTC by Jon
Modified: 2019-09-15 09:14 UTC (History)
2 users (show)

See Also:

Attachments
WIO Log (2.75 KB, text/rtf)
2017-09-08 17:01 UTC, Jon 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jon 2017-09-08 17:01:09 UTC 
Created attachment 535 [details]
WIO Log

After I first installed WIO, it shutdown (powered off) the firewall. This has only happened one time. WIO has been running for a few days.


See:
https://forum.ipfire.org/viewtopic.php?f=52&t=19377&hilit=bugzilla
Comment 2 Jon 2019-06-20 17:56:44 UTC 
Stephan - I'm not sure how to test this.  If it needs git, I do not have git installed on my production ipfire.  I'd be happy to test on a VM if you can tell me how to test.
Comment 3 ChrisK 2019-09-06 06:40:18 UTC 
I think we have to separate two things here:

- The fact that WIO starts a shutdown if just ONE of the clients went offline is definetly a bug.

- The fact that WIO tries to shutdown the host when "Shutdown when all clients are offline" is ticked is AFAIS a feature.

From my understanding this tool was developed for hosts that SHALL be shutdown if there's no access from clients any more. Just think of something like a NAS in your home network.

So IMHO the best solution would be to remove this option completely from the IPFire port of this tool.
Comment 4 Stephan Feddersen 2019-09-15 09:14:51 UTC 
Problem is solved with the patch from 04.06.2019, because the IPFire box shutdown when a single client was tested manually and the result of the test was that the single client was offline.