Description of problem:
iodine-server wants to run ifconfig (package net-tools), but its package does not have it in dependencies.
Version-Release number of selected component (if applicable):
Name : iodine-server
Version : 0.6.0
Release : 0.rc1.9.fc18.1
Steps to Reproduce:
1. do not have net-tools installed
2. install iodine-server
3. try to start it
# LANG=C iodined -D -D -f -P password 10.29.190.1/24 t.example.com
Debug level 2 enabled, will stay in foreground.
Add more -D switches to set higher debug level.
Setting IP of dns0 to 10.29.190.1
sh: /sbin/ifconfig: No such file or directory
LANG C is so that error message is in english, higher debug level does not help.
tunnel set up
iodine creates command line in tun.c that uses ifconfig to set ip address and uses system() to run it, so its package should depend on /sbin/ifconfig. It also need /sbin/route (or better it should use ip instead of ifconfig and route).
Thank you for your bugreport and willing make free software better!
Rawhide build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5249672
iodine-0.6.0-0.rc1.10.fc19 has been submitted as an update for Fedora 19.
iodine-0.6.0-0.rc1.10.fc18 has been submitted as an update for Fedora 18.
iodine-0.6.0-0.rc1.10.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
iodine-0.6.0-0.rc1.10.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.