On Saturday 12 November 2005 13:51, Theetjuh wrote: > when i run "dhclient eth0" it doesn't even work, it gives the error: "eth0: > not found" > > dhclient goes wrong ... en there for dhcdbd goes wrong. > > So .. why doesn't dhclient work ... dhcpcd does work. > > Slackware doesn't use dhclient anywhere, and i heard from alien at > [EMAIL PROTECTED] that happens often. > Perhaps Slackware lacks support for LPF ? Try recompiling dhclient with '#define USE_SOCKETS' uncommented in dhcp-3.0.3/includes/site.conf . I've never tested dhclient in this mode, nor used slackware much, and I do not have access to a slackware system to test. Perhaps it might be an idea for you to simply try getting the stock ISC dhclient working first by downloading and compiling: ftp://ftp.isc.org/isc/dhcp/dhcp-3.0.3.tar.gz Try emailing '[EMAIL PROTECTED]' if you are unable to get the stock dhclient working on slackware. What advantages do you perceive slackware having over FC-4 / FC-5 ? Regards, Jason. > On 11/4/05, Jason Vas Dias <[EMAIL PROTECTED]> wrote: > > > > Hi Theetjuh - > > > > I suspect that your dhcp is compiled to use different paths than > > dhcdbd is expecting. > > > > dhcdbd depends on the file /var/run/dhclient-$IF.pid file being > > created by dhclient, for example, and dhclient needs the > > /var/lib/dhclient/ directory. Check that the paths in dhcdbd.h > > match with the paths used by your dhclient. > > > > All I know is that the system works fine on RedHat FC-4 / FC-5 - > > I have no Slackware system on which to test. If you cannot > > debug what is going on with your customized versions of > > dhcp and dhcdbd on Slackware, consider upgrading to FC-4 / FC-5 . > > > > Regards, > > Jason > > > > On Friday 04 November 2005 14:04, Theetjuh wrote: > > > Haven't heard about this anymore ... any progress ? > > > > > > On 10/25/05, Theetjuh <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi Jason, > > > > > > > > > > > > I'm running Slackware 10.2 with 2.6.13 kernel > > > > > > > > I build all my packages from source, with the following patches from > > > > Gentopia (which i attached), cause those would build right: > > > > > > > > dhcp: > > > > dhcp-3.0.2-extended_option_environment.patch > > > > dhcp-3.0.2-dhclient-no_isc_blurb.patch > > > > dhcp-3.0.2-dhclient_nodelay.patch > > > > dhcp-3.0.2-dhclient_decline_backoff.patch > > > > dhcp-3.0.2-dhclient_script_fast+arping-1.patch > > > > dhcp-3.0.2-dhclient-script-dbus-dhcdbd.patch > > > > dhcp-3.0.2-slackware-ify.patch > > > > dhclient-ntp.patch > > > > > > > > dhcdbd: > > > > dhcdbd-1.9-slackware-ify.patch > > > > > > > > networkmanager: > > > > networkmanager-slackware-ify.patch > > > > > > > > On 10/25/05, Jason Vas Dias <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > Hi Theetjuh - > > > > > > > > > > What OS are you using ? > > > > > > > > > > Is there any reason why you can't download the latest NetworkManager > > > > > source rpms and dependencies: > > > > > > > > > > > > ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/NetworkManager-0.5.1-2.src.rpm > > > > > > > ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/dhcdbd-1.9-1.src.rpm > > > > > > > > > > > > > > > > > ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/dhclient-3.0.3-10.src.rpm > > > > > > > > > > > > ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/bind-9.3.1-20.src.rpm > > > > > > > > > > > > ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/dbus-0.50-1.src.rpm > > > > > > > > > > And simply rebuild them with 'rpmbuild --rebuild $srcrpm' ? > > > > > > > > > > > > Oct 22 14:30:51 poseidon dhclient: Internet Systems Consortium > > > > > > > DHCP Client V3.0.3 > > > > > > > > > > This shows you are not running the Red Hat patched dhclient, whose > > > > > version string > > > > > would be : > > > > > DHCP Client V3.0.3-RedHat > > > > > > > > > > > > Oct 22 14:30:51 poseidon dhclient: > > > > > > > Oct 22 14:30:51 poseidon dhcdbd: Unrequested down ?:3 > > > > > > > > > > dhclient has exited abnormally, perhaps because it does not > > recognize > > > > > the '-x' > > > > > option, support for which is provided by the Red Hat dhclient > > patches - > > > > > specifically, > > > > > 'dhcp-3.0.2-extended_option_environment.patch' . You can stop dhcdbd > > > > > supplying the -x > > > > > option by compiling dhcdbd with > > -DDHCLIENT_EXTENDED_OPTION_ENVIRONMENT=0 > > > > > , but then > > > > > it will be unable to handle user-defined DHCP options. > > > > > > > > > > > > And this in /var/log/syslog: > > > > > > > Oct 22 14:30:51 poseidon dhclient: eth0: not found > > > > > > > > > > Since eth0 was not configured, dhcdbd has no record of it . > > > > > > > > > > > > Oct 22 14:31:29 poseidon NetworkManager: <WARNING>^I (): > > > > > > > nm_spawn_process('/etc/rc.d/rc.howl restart'): could not spawn > > > > > > > process. (Failed to execute child process > > > > > > > "/etc/rc.d/rc.howl" (No such file or directory)) > > > > > > > > > > NetworkManager depends on howl ? Perhaps you should consider > > installing > > > > > howl: > > > > > > > ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/howl-0.9.8-4.src.rpm > > > > > > > > > > > > > > > > > Oct 22 14:31:43 poseidon NetworkManager: compute_nameservers: > > > > > > > assertion `config != NULL' failed > > > > > > > > > > > > > > > > > It looks like you may be missing some NetworkManager patches also. > > > > > > > > > > I strongly suggest just rebuilding from the latest src rpms . > > > > > > > > > > Regards, > > > > > Jason Vas Dias > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Greetz > > > > Theetjuh > > > > > > > > > > > > > > > > -- > > > > > > > > > Greetz > > > Theetjuh > > > > > > > > > -- > > > Greetz > Theetjuh > _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
