Re: dhclient busted for -current?

2001-12-12 Thread Edwin Culp
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

Re: dhclient busted for -current?

2001-12-11 Thread Warner Losh
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

Re: dhclient busted for -current?

2001-12-08 Thread Pierre Y. Dampure
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

dhclient busted for -current?

2001-12-07 Thread Warner Losh
% 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.

Re: dhclient busted for -current?

2001-12-07 Thread Jeremy Parker
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,