Re: dhclient busted for -current?
This may explain my problem with the excite@home/attbi.com change over. According to them it is pure dhcp. Since it has always just worked when I needed it, I haven't really tested. ed Quoting Warner Losh [EMAIL PROTECTED]: In message [EMAIL PROTECTED] Pierre Y. Dampure writes: : Are you asking for specific options (my dhclient.conf is empty)? are you using a reservation? I'm 100% sure it worked before the upgrade. :-(. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dhclient busted for -current?
In message [EMAIL PROTECTED] Pierre Y. Dampure writes: : Are you asking for specific options (my dhclient.conf is empty)? are you using a :reservation? I'm 100% sure it worked before the upgrade. :-(. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dhclient busted for -current?
On Sat, 8 Dec 2001 02:07:22 -0500, Jeremy Parker [EMAIL PROTECTED] wrote: I have also experienced this issue, caused me a lot of trouble. The only workaround I have figured out, is to bring up the interface with an IP address, then start dhclient and it seems to work. This is a very recent problem for me as well. Running -current from Thursday evening on a Latitude CPx with a 3Com 3C575, dhclient to a FreeBSD 4.4-stable server, no issues. Are you asking for specific options (my dhclient.conf is empty)? are you using a reservation? Best Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
dhclient busted for -current?
% ifconfig -a ... wi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ... status: associated ssid X % dhclient wi0 dhclient: wi0: not found dhclient: exiting Has anybody else seen this? I've seen this on two machines now, including one from yesterday. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dhclient busted for -current?
I have also experienced this issue, caused me a lot of trouble. The only workaround I have figured out, is to bring up the interface with an IP address, then start dhclient and it seems to work. This is a very recent problem for me as well. Jeremy Warner Losh([EMAIL PROTECTED])@Fri, Dec 07, 2001 at 07:16:43PM -0700: % ifconfig -a ... wi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ... status: associated ssid X % dhclient wi0 dhclient: wi0: not found dhclient: exiting Has anybody else seen this? I've seen this on two machines now, including one from yesterday. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
