dhcp server

[jim]

Binary package hint: firestarter

Firestarter cannot launch the dhcp server

first i installed the package dhcp
but firestarter changes the configuration in /etc/dhcp3/dhcpd.conf instead of /etc/dhcpd.conf. Probably because dhcp3-client is installed by default.
now i have dhcp3-server installed but i had to symlink /etc/init.d/dhcp3-server to /etc/init.d/dhcpd because firestarter always launches /etc/init.d/dhcpd.
firestarter works perfectly now.

maybe adapt the firestarter.sh script so it knows what runscript it has to choose as it already can for the configuration script.

[Jérémie Corbier (jcorbier)]

From the other bug report:

jens_acamedia wrote:
> ok - thanks jeremie. i had dhcp installed rather than dhcp3-server...
>
> why dont we add dhcp3-server as a dependecy in firestarter to avoid this
> confusion? it is after all a normal function to share internet with dhcp...
>
> thanks for your help.

Do you have dhcp installed instead of dhcp3-server?

[jens_acamedia (commercial-acamedia)]

ok jeremy - like this.

i discovered while using firestarter that i did not have a dhcp
server. obviously this should have been a dependency to firestarter
since one of firestarters main functions depends on it...

instead i did an apt-get on dhcp which seemed the right thing...

turns out that there were more than one dhcp servers available and
when i installed dhcp3-server instead it all worked correctly...

all this could have been avoided if dhcp3-server was a dependency for
firestarter...

hope this makes sense...

[Jérémie Corbier (jcorbier)]

Thanks a lot for the feedback. If Jim could confirm this, this would be great.

[Nafallo Bjälevik (nafallo)]

I'm working on this.

[Nafallo Bjälevik (nafallo)]

 firestarter (1.0.3-1.3ubuntu2) feisty; urgency=low
 .
   * debian/control:
     - Add a suggest on dhcp3-server since it's functionality
       is on upstreams key features list.
   * debian/patches/02_*.dpatch:
     - Detect dhcp3 in use via dhcpd.confs location rather than
       /etc/dhcp3 existing. dhcp3-client have that directory.
     - Added patch to look for and restart dhcp3-server as well.
     + Closes: #48006

[jim (hesoez)]

Hi,

I installed edgy a few weeks ago and still had the same problem with firestarter. I installed dhcp3-server along with it but i still had to symlink /etc/init.d/dhcp3-server to /etc/init.d/dhcpd to get it working.

It's good to see it fixed now, i will try it again when i install feisty :-).
thanks

[Roman Polach (rpolach)]

I have dhcp3-server and firestarter installed
"ln -s /etc/init.d/dhcp3-server /etc/init.d/dhcpd"
did not solve this problem for me..
I still get:
  Failed to start the firewall
  An Unknown error occured
when I tried to enable DHCP server in firestarter GUI preferences.

Also changing /etc/firestarter/firestarter.sh
according to https://launchpad.net/ubuntu/+source/firestarter/+bug/43784
did not solve this problem...

[Roman Polach (rpolach)]

Still a problem in Feisty!

a) Even with dhcpcd or dhcp3-server installed: DHCP option disabled during Firestarter wizard (but available then in Preferences dialog).
b) dhcp3-server installed: When enabled DHCP server in Preferences dialog, it show error message about starting dhcp server.
c) dhcpcd installed: When enabled DHCP server in Preferences dialog, it does not show any message, but "sudo ps -A w grep dhcp" shows nothing, so dhcp server does not run.

[jim (hesoez)]

It works here,
i installed dhcp3-server and firestarter.

In the wizard it is not possible to setup the local network but this can be set in preferences later.
I had a little problem with dhcp too but i reconfigured the dhcp settings in firestarter (clear the lowest and highest ip fields and fill in the correct values again) and now it works without having to touch the terminal.

If you can't get dhcp to start, try to start it in the terminal (/etc/init.d/dhcp3-server restart) to see what error it gives.