Bugzilla Bug 13136

First I guess it's a simple cut-n-paste-fault in the sample configuration file
of mol's dchpd-mol.conf

In the last section ("subnet 192.168.6.0 netmask 255.255.255.0") the host
parameter should be "host mol5" instead of "host mol4".

Second should there be a line with "ddns-update-style               ad-hoc;"
right under the option domain-name-servers line.

There are more users who had problems with this configuration faults.  Maybe the
sheep-driver in molrc.net should also become commented out?  Then mol would
start with network out of the box.

I'll look into this.

I am not sure about changing from the sheep-driver though, as it raises the
requirements quite a bit (i.e. iptables, etc).

I will check out the conf changes over next few days though, thanks.

FIx is comitted, rev bumped to -r1

Thanks

Will leave this bug as fixlater to look at changing the sheepnet driver and bump dependancies

Thanks, new version of mol (0.9.68 cvs snapshot) in portage, with fixed
configs.  CLosing this bug.

reopen to mark this bug as fixed

Due to a new version of mol and a new ebuild this bug can be marked as fixed.