Re: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor

2017-02-10 Thread Iblis Lin
On Fri, Feb 10, 2017 at 04:10:41PM +0200, Konstantin Belousov wrote: > On Fri, Feb 10, 2017 at 05:29:54AM -0800, David Wolfskill wrote: > > This was head @r313544; previous successful build/smoke test was > > @r313467 (yesterday). > > > > Here's an excerpt from a typescript I made of some "poking

Re: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor

2017-02-10 Thread Hans Petter Selasky
On 02/10/17 15:10, Konstantin Belousov wrote: On Fri, Feb 10, 2017 at 05:29:54AM -0800, David Wolfskill wrote: This was head @r313544; previous successful build/smoke test was @r313467 (yesterday). Here's an excerpt from a typescript I made of some "poking around"; subsequent to that, I was

Re: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor

2017-02-10 Thread David Wolfskill
On Fri, Feb 10, 2017 at 04:10:41PM +0200, Konstantin Belousov wrote: > ... > Please try this. > > diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c > index 70cdcdc6f75..1f2cceaf7a6 100644 > --- a/sys/kern/vfs_vnops.c > +++ b/sys/kern/vfs_vnops.c > @@ -351,8 +351,8 @@ vn_open_vnode(struct

Re: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor

2017-02-10 Thread Konstantin Belousov
On Fri, Feb 10, 2017 at 05:29:54AM -0800, David Wolfskill wrote: > This was head @r313544; previous successful build/smoke test was > @r313467 (yesterday). > > Here's an excerpt from a typescript I made of some "poking around"; > subsequent to that, I was able to set the IP address, netmask, and

Re: dhclient sucks cpu usage...

2014-06-10 Thread Alexander V. Chernikov
On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though there is space for 16k), I was still not getting as good as performance using nc between machines, so I decided to generate some flame

Re: dhclient sucks cpu usage...

2014-06-10 Thread John-Mark Gurney
Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 13:17 +0400: On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though there is space for 16k), I was still not getting as

Re: dhclient sucks cpu usage...

2014-06-10 Thread Alexander V. Chernikov
On 10.06.2014 20:24, John-Mark Gurney wrote: Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 13:17 +0400: On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though there is

Re: dhclient sucks cpu usage...

2014-06-10 Thread Bryan Venteicher
- Original Message - On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though there is space for 16k), I was still not getting as good as performance using nc between

Re: dhclient sucks cpu usage...

2014-06-10 Thread Alexander V. Chernikov
On 10.06.2014 22:11, Bryan Venteicher wrote: - Original Message - On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though there is space for 16k), I was still not getting as good as

Re: dhclient sucks cpu usage...

2014-06-10 Thread John-Mark Gurney
Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 22:21 +0400: On 10.06.2014 22:11, Bryan Venteicher wrote: - Original Message - On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer

Re: dhclient sucks cpu usage...

2014-06-10 Thread John-Mark Gurney
Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 21:33 +0400: On 10.06.2014 20:24, John-Mark Gurney wrote: Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 13:17 +0400: On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So,

Re: dhclient sucks cpu usage...

2014-06-10 Thread Alexander V. Chernikov
On 10.06.2014 22:56, John-Mark Gurney wrote: Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 21:33 +0400: On 10.06.2014 20:24, John-Mark Gurney wrote: Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 13:17 +0400: On 10.06.2014 07:03, Bryan Venteicher wrote:

Re: dhclient sucks cpu usage...

2014-06-09 Thread Bryan Venteicher
Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though there is space for 16k), I was still not getting as good as performance using nc between machines, so I decided to generate some flame graphs to try to identify issues... (Thanks

Re: dhclient can't limit bpf descriptor?

2013-12-15 Thread Pawel Jakub Dawidek
On Sat, Dec 14, 2013 at 12:12:23PM -0800, Tim Kientzle wrote: Opened up an old VM from a month or so ago (r257910) and dhclient won’t start. Specifically, dhclient complains (when run by root): “can’t limit bpf descriptor: Bad address” and then immediately exits. What does this mean? I

Re: dhclient can't limit bpf descriptor?

2013-12-14 Thread Darren Pilgrim
On 12/14/2013 12:12 PM, Tim Kientzle wrote: Opened up an old VM from a month or so ago (r257910) and dhclient won’t start. Specifically, dhclient complains (when run by root): “can’t limit bpf descriptor: Bad address” and then immediately exits. Are you running a custom kernel without the

Re: dhclient can't limit bpf descriptor?

2013-12-14 Thread Tim Kientzle
On Dec 14, 2013, at 3:16 PM, Darren Pilgrim list_free...@bluerosetech.com wrote: On 12/14/2013 12:12 PM, Tim Kientzle wrote: Opened up an old VM from a month or so ago (r257910) and dhclient won’t start. Specifically, dhclient complains (when run by root): “can’t limit bpf descriptor:

Re: dhclient failure with Realtek 8111E Ethernet on new MSI motherboard

2013-11-08 Thread Thomas Mueller
For a future test of any updates to re driver, it might be best if I comment out device re in kernel config and test the update by building the module. I never built just a single module before, not sure if I would do it the correct way. Simply make in /usr/src/sys/modules/re and then make

Re: dhclient failure with Realtek 8111E Ethernet on new MSI motherboard

2013-11-08 Thread Thomas Mueller
from Daniel Nebdal: Ethernet without DHCP is fairly doable. Assuming that the network is 192.168.0.x , that .100 is free, and your router has .1 : ifconfig re0 192.168.0.100/24 route add default 192.168.0.1 As for DNS, I'd suggest checking on another machine what servers you get from

Re: dhclient failure with Realtek 8111E Ethernet on new MSI motherboard

2013-11-07 Thread Yonghyeon PYUN
On Thu, Nov 07, 2013 at 02:25:18AM +, Thomas Mueller wrote: I tried the patch on 9.2-STABLE, rebuilt the kernel and modules, installed to the correct place on USB stick, /media/zip0/boot/kernelre USB stick was mounted on /media/zip0 when I did this. Then I umounted, took the USB stick

Re: dhclient failure with Realtek 8111E Ethernet on new MSI motherboard

2013-11-06 Thread Thomas Mueller
I tried the patch on 9.2-STABLE, rebuilt the kernel and modules, installed to the correct place on USB stick, /media/zip0/boot/kernelre USB stick was mounted on /media/zip0 when I did this. Then I umounted, took the USB stick to new computer with MSI Z77 MPOWER motherboard. I booted that USB

Re: dhclient failure with Realtek 8111E Ethernet on new MSI motherboard

2013-11-05 Thread Yonghyeon PYUN
On Wed, Nov 06, 2013 at 02:36:07AM +, Thomas Mueller wrote: from Yonghyeon PYUN: Thomas, would you try attached patch on your system? [-- Attachment #2: re.8168evl.diff --] [-- Type: text/x-diff, Encoding: 7bit, Size: 3.6K --] Content-Type:

Re: dhclient: send_packet: No buffer space available

2013-11-01 Thread hiren panchasara
On Fri, Nov 1, 2013 at 8:32 AM, Matthias Apitz g...@unixarea.de wrote: Hello, Since I have updated my netbook to r255948 I see from time to time in the console the message: Nov 1 16:20:28 tiny-r255948 dhclient[696]: send_packet: No buffer space available Yes, this is a knownish issue

Re: dhclient: send_packet: No buffer space available

2013-11-01 Thread Adrian Chadd
On 1 November 2013 08:45, hiren panchasara hiren.panchas...@gmail.com wrote: On Fri, Nov 1, 2013 at 8:32 AM, Matthias Apitz g...@unixarea.de wrote: Hello, Since I have updated my netbook to r255948 I see from time to time in the console the message: Nov 1 16:20:28 tiny-r255948

Re: dhclient cause up/down cycle after 239356 ?

2012-08-23 Thread John Baldwin
On Wednesday, August 22, 2012 9:35:34 pm Peter Jeremy wrote: BTW to jhb: Can you check your mailer's list configuration. You appear to be adding freebsd-current@freebsd.org and leaving curr...@freebsd.org in the Cc list. It's a feature of kmail that the kmail developers refuse to provide an

Re: dhclient cause up/down cycle after 239356 ?

2012-08-23 Thread John Baldwin
On Wednesday, August 22, 2012 9:35:34 pm Peter Jeremy wrote: On 2012-Aug-22 15:35:01 -0400, John Baldwin j...@freebsd.org wrote: Hmm. Perhaps we could use a debouncer to ignore short link flaps? Kind of gross (and OpenBSD doesn't do this). For now this change basically ignores link up

Re: dhclient cause up/down cycle after 239356 ?

2012-08-22 Thread Vitalij Satanivskij
ok next round :) dhclient updated to Revision 239564 with fxp : Aug 22 20:06:48 home kernel: fxp0: link state changed to DOWN Aug 22 20:06:48 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:06:48 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:06:48 home

Re: dhclient cause up/down cycle after 239356 ?

2012-08-22 Thread John Baldwin
On Wednesday, August 22, 2012 1:28:22 pm Vitalij Satanivskij wrote: ok next round :) dhclient updated to Revision 239564 with fxp : Aug 22 20:06:48 home kernel: fxp0: link state changed to DOWN Aug 22 20:06:48 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:06:48 home

Re: dhclient cause up/down cycle after 239356 ?

2012-08-22 Thread Adrian Chadd
Ew. Be careful. Your admin may decide to change the VLAN you're on (for example.) You definitely want to renegotiate your link state then. Adrian On 22 August 2012 12:35, John Baldwin j...@freebsd.org wrote: On Wednesday, August 22, 2012 1:28:22 pm Vitalij Satanivskij wrote: ok next round :)

Re: dhclient cause up/down cycle after 239356 ?

2012-08-22 Thread Peter Jeremy
On 2012-Aug-22 15:35:01 -0400, John Baldwin j...@freebsd.org wrote: Hmm. Perhaps we could use a debouncer to ignore short link flaps? Kind of gross (and OpenBSD doesn't do this). For now this change basically ignores link up events if they occur with 5 seconds of the link down event. The 5 is

Re: dhclient cause up/down cycle after 239356 ?

2012-08-22 Thread Warner Losh
On Aug 22, 2012, at 7:35 PM, Peter Jeremy wrote: On 2012-Aug-22 15:35:01 -0400, John Baldwin j...@freebsd.org wrote: Hmm. Perhaps we could use a debouncer to ignore short link flaps? Kind of gross (and OpenBSD doesn't do this). For now this change basically ignores link up events if they

Re: dhclient cause up/down cycle after 239356 ?

2012-08-22 Thread YongHyeon PYUN
On Thu, Aug 23, 2012 at 11:35:34AM +1000, Peter Jeremy wrote: On 2012-Aug-22 15:35:01 -0400, John Baldwin j...@freebsd.org wrote: Hmm. Perhaps we could use a debouncer to ignore short link flaps? Kind of gross (and OpenBSD doesn't do this). For now this change basically ignores link up

Re: dhclient cause up/down cycle after 239356 ?

2012-08-21 Thread Garrett Cooper
On Tue, Aug 21, 2012 at 2:55 AM, Vitalij Satanivskij sa...@ukr.net wrote: Hi all, After last update my home machine begin doin some strange things - ... Try reverting r239356 -- if that works, then please let jhb@ know. -Garrett ___

Re: dhclient cause up/down cycle after 239356 ?

2012-08-21 Thread Vitalij Satanivskij
Garrett Cooper wrote: GC On Tue, Aug 21, 2012 at 2:55 AM, Vitalij Satanivskij sa...@ukr.net wrote: GC Hi all, GC GC After last update my home machine begin doin some strange things - GC GC ... GC GC Try reverting r239356 -- if that works, then please let jhb@ know. GC -Garrett Yes i'm

Re: dhclient cause up/down cycle after 239356 ?

2012-08-21 Thread Peter Jeremy
On 2012-Aug-21 19:42:17 +0300, Vitalij Satanivskij sa...@ukr.net wrote: Look's like dhclient do down/up sequence - Not intentionally. Aug 21 19:21:00 home kernel: fxp0: link state changed to UP Aug 21 19:21:01 home kernel: fxp0: link state changed to DOWN Aug 21 19:21:01 home dhclient: New IP

Re: dhclient cause up/down cycle after 239356 ?

2012-08-21 Thread YongHyeon PYUN
On Wed, Aug 22, 2012 at 08:27:01AM +1000, Peter Jeremy wrote: On 2012-Aug-21 19:42:17 +0300, Vitalij Satanivskij sa...@ukr.net wrote: Look's like dhclient do down/up sequence - Not intentionally. Aug 21 19:21:00 home kernel: fxp0: link state changed to UP Aug 21 19:21:01 home kernel:

Re: dhclient em0: not found rev r230054

2012-01-17 Thread Gleb Smirnoff
On Tue, Jan 17, 2012 at 01:57:48PM +0200, Octavian Rinciog wrote: O Hello! O O After updating to FreeBSD 10.0-CURRENT #0 r230054, I can't do anymore O dhclient on em0. O O [root@freebsd ~]# uname -a O FreeBSD freebsd 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r230054: Fri Jan O 13 14:29:36 EET 2012

Re: dhclient em0: not found rev r230054

2012-01-17 Thread Doug Barton
On 01/17/2012 03:57, Octavian Rinciog wrote: Jan 13 14:41:58 freebsd dhclient[1734]: em0: not found You need to update your world and kernel together. The ability to run new kernel on an old world (as is the usual upgrade method) was broken a little while ago, and the compatibility shims to fix

Re: dhclient em0: not found rev r230054

2012-01-17 Thread David Wolfskill
On Tue, Jan 17, 2012 at 01:57:48PM +0200, Octavian Rinciog wrote: Hello! After updating to FreeBSD 10.0-CURRENT #0 r230054, I can't do anymore dhclient on em0. [root@freebsd ~]# uname -a FreeBSD freebsd 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r230054: Fri Jan 13 14:29:36 EET 2012

Re: dhclient/ipfw conflict on boot

2003-09-25 Thread Conrad J. Sabatier
On Wed, Sep 24, 2003 at 05:51:56AM -0700, David Wolfskill wrote: From: Conrad J. Sabatier [EMAIL PROTECTED] Subject: dhclient/ipfw conflict on boot I just ran into this today after upgrading. It seems that dhclient is unable to initialize properly at boot time, due to the prior

Re: dhclient/ipfw conflict on boot

2003-09-24 Thread David Wolfskill
Date: Wed, 24 Sep 2003 00:58:12 -0500 From: Conrad J. Sabatier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: dhclient/ipfw conflict on boot I just ran into this today after upgrading. It seems that dhclient is unable to initialize properly at boot time, due to the prior initialization of

Re: dhclient bug

2003-09-09 Thread Martin Blapp
Hi, with a missing dhcpserver or non-existent interface, this works. however, it does not when i unplug the ethernet cable. in that case, i get back true after the timeout, not 2. can someone verify this? is it a bug that must be fixed from the freebsd side or should a bug report to the

Re: dhclient problem with xl0

2003-08-14 Thread Martin Blapp
Hi, Here is the output of dhclient -v -d xl0 I I checked. Dhclient still initializes the interface and brings it up itself. So there is only one possibility: You don't have a working link. Maybe it helps if you add a interface define in /etc/dhclient.conf wit the possible media. Martin

Re: dhclient problem with xl0

2003-08-14 Thread Matthew N. Dodd
On Sat, 9 Aug 2003, Martin Blapp wrote: Isn't there a way to see that the card doesn't support reporting media status ? If the card does report this, I could add code to dhclient and all would be fine. Yes; check the media status word for IFM_AVALID. (whitespace damaged) %%% --- dhclient.c

Re: dhclient problem with xl0

2003-08-14 Thread Matthew N. Dodd
On Sat, 9 Aug 2003, Martin Blapp wrote: dhclient is still relying on behavior from the kernel that isn't guaranteed. I know. But I'd consider that as a kernel bug, not dhclient fault. Would it help the set the card into promisc. mode anyway, even if we don't have link ? Except that you've

Re: Dhclient fix for systems with media settings

2003-08-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Martin Blapp [EMAIL PROTECTED] writes: : Is this going to cure the cases where using DHCP results in my network : link going dead about ~30 minutes after getting a lease? At that point : it starts spitting out timeout errors and stuff, and i have to :

Re: dhclient problem with xl0

2003-08-14 Thread Martin Blapp
Argl, of course the patch was wrong. Ok, this should work now ... --- contrib/isc-dhcp/client/dhclient.c.orig Thu Aug 7 16:58:46 2003 +++ contrib/isc-dhcp/client/dhclient.c Sat Aug 9 21:47:14 2003 @@ -3288,19 +3288,24 @@ return (HAVELINK);

Re: dhclient problem with xl0

2003-08-14 Thread Martin Blapp
Hi, Adapted to the newst source-version, the patch will look like this. After I got home, I'll test it. Martin Index: client/dhclient.c === RCS file: /home/ncvs/src/contrib/isc-dhcp/client/dhclient.c,v retrieving revision 1.30

Re: dhclient problem with xl0

2003-08-14 Thread Matthew N. Dodd
On Sat, 9 Aug 2003, Craig Rodrigues wrote: I just did a cvsup of -CURRENT and rebuilt the world. dhclient doesn't seem to work for me any more. It looks like a problem with dhclient, and not the kernel, because an older version of dhclient works fine. Here is the output of dhclient -v -d xl0

Re: Dhclient fix for systems with media settings

2003-08-14 Thread Eirik Oeverby
Hi, Then I shall provide what I possibly can. When using dhclient to configure my wi-driven lucent card (latest firmware), it will work for a while (varying number of minutes - up to 30 or so) and then stop working, while spitting out messages like: wi0: bad alloc 55c != 2a2, cur 0 nxt 0 wi0:

Re: dhclient problem with xl0

2003-08-14 Thread Martin Blapp
Hi, xl0: Polling interface state xl0: client state of 2 xl0: link = 0 xl0: No Link on interface Erm. What does 'ifconfig xl0' show you ? For dhclient it looks like you have no link. Martin ___ [EMAIL PROTECTED] mailing list

Re: dhclient problem with xl0

2003-08-14 Thread Craig Rodrigues
On Sat, Aug 09, 2003 at 06:21:43PM +0200, Martin Blapp wrote: Hi, Adapted to the newst source-version, the patch will look like this. After I got home, I'll test it. OK, this is weird. I did not use your change to dhclient. However, I did use Matthew Dodd's change to if_xl.c. I rebuilt

Re: dhclient problem with xl0

2003-08-14 Thread Martin Blapp
Have you done a ifconfig xl0 0.0.0.0 up before ? xl0: No Link on interface I think I'll have to support this, if the interface is not initialized. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: Dhclient fix for systems with media settings

2003-08-11 Thread Eirik Oeverby
Hi, Is this going to cure the cases where using DHCP results in my network link going dead about ~30 minutes after getting a lease? At that point it starts spitting out timeout errors and stuff, and i have to unplug/replug the card and re-start dhclient to get connectivity again.. Thanks for the

Re: dhclient problem with xl0

2003-08-10 Thread Matthew N. Dodd
On Sat, 9 Aug 2003, Martin Blapp wrote: You don't have a working link. Maybe it helps if you add a interface define in /etc/dhclient.conf wit the possible media. dhclient is still relying on behavior from the kernel that isn't guaranteed. I posted a patch to if_xl.c that should correct the

Re: dhclient problem with xl0

2003-08-10 Thread Martin Blapp
Hi, Except that you've added code to dhclient that makes poor assumptions about the ifmedia status word. Its optional; for hardware that you can detect media status it can be used to display the status. For other hardware, we shouldn't have to lie about media status; if the hardware

Re: dhclient problem with xl0

2003-08-10 Thread Martin Blapp
Hi, dhclient is still relying on behavior from the kernel that isn't guaranteed. I know. But I'd consider that as a kernel bug, not dhclient fault. Would it help the set the card into promisc. mode anyway, even if we don't have link ? I posted a patch to if_xl.c that should correct the link

Re: dhclient problem with xl0

2003-08-09 Thread Matthew N. Dodd
On Sat, 9 Aug 2003, Matthew N. Dodd wrote: Try this (cut paste): The patch I posted was incorrect as I forgot to do a register window select before reading media status. ftp://ftp.jurai.net/users/winter/patches/xl_media.patch -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E |

Re: dhclient problem with xl0

2003-08-09 Thread Craig Rodrigues
On Sat, Aug 09, 2003 at 12:28:45PM +0200, Martin Blapp wrote: Hi, Here is the output of dhclient -v -d xl0 I I checked. Dhclient still initializes the interface and brings it up itself. So there is only one possibility: You don't have a working link. Maybe it helps if you add a

Re: Dhclient fix for systems with media settings

2003-08-06 Thread Martin Blapp
Hi, Is this going to cure the cases where using DHCP results in my network link going dead about ~30 minutes after getting a lease? At that point it starts spitting out timeout errors and stuff, and i have to unplug/replug the card and re-start dhclient to get connectivity again.. Unless

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Martin Blapp
Hi, I have the following dhclient.conf file that USED TO WORK to find the right SSID depending on where I am. It now doesn't. Yes, there have been some changes. The most important was the interface polling addition, but that should not make any difference here. Can you start dhclient with

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Matthew N. Dodd
On Mon, 4 Aug 2003, Martin Blapp wrote: Yes, there have been some changes. The most important was the interface polling addition, but that should not make any difference here. Read the code. dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Larry Rosenman
--On Monday, August 04, 2003 10:09:34 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Monday, August 04, 2003 16:42:08 +0200 Martin Blapp [EMAIL PROTECTED] wrote: Hi, I have the following dhclient.conf file that USED TO WORK to find the right SSID depending on where I am. It now

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Larry Rosenman
--On Monday, August 04, 2003 11:08:21 -0400 Matthew N. Dodd [EMAIL PROTECTED] wrote: On Mon, 4 Aug 2003, Martin Blapp wrote: Yes, there have been some changes. The most important was the interface polling addition, but that should not make any difference here. Read the code.

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Martin Blapp
Hi, polling addition, but that should not make any difference here. Read the code. dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible media settings. interface_active() doesn't bail out. It returns 1, which means ok, and all should be

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Martin Blapp
hi, Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:- wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 207.136.3.254

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Larry Rosenman
--On Monday, August 04, 2003 17:45:49 +0200 Martin Blapp [EMAIL PROTECTED] wrote: hi, Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:- wepkey 4:- 1 DHCPDISCOVER

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Larry Rosenman
--On Monday, August 04, 2003 10:48:59 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Monday, August 04, 2003 17:45:49 +0200 Martin Blapp [EMAIL PROTECTED] wrote: hi, Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback Trying medium

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Martin Blapp
Hi, Please look if you can get a 2-3 month old dhclient and I'm sure you'll see the same behaviour there. Negative. It was working with the WI driver from 5.0 through 5.1-CURRENT until my make world last nite/this am. oh, and 4.6-4.8 as well. Ok, You told me that it is working the

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Larry Rosenman
--On Monday, August 04, 2003 18:22:04 +0200 Martin Blapp [EMAIL PROTECTED] wrote: Hi, Please look if you can get a 2-3 month old dhclient and I'm sure you'll see the same behaviour there. Negative. It was working with the WI driver from 5.0 through 5.1-CURRENT until my make world last

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Martin Blapp
Hi, How could dhclient see then that you were in a new network ? Do you mean which dhclient was running changing networks ? Or kill dhclient and restart it ? reboot. I.E. I shutdown between home and office and vice versa. SOMETHING seriously changed here. Ahh ! I see now the change.

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Larry Rosenman
--On Monday, August 04, 2003 20:19:05 +0200 Martin Blapp [EMAIL PROTECTED] wrote: Hi, How could dhclient see then that you were in a new network ? Do you mean which dhclient was running changing networks ? Or kill dhclient and restart it ? reboot. I.E. I shutdown between home and office

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Martin Blapp
Hi, dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible media settings. Ok, problem understood now. I'm working on a fix. Martin ___ [EMAIL PROTECTED] mailing list

Re: dhclient/dhclient.conf change in -CURRENT?

2003-08-04 Thread Martin Blapp
Hi Larry, This patch should fix the issues. It is not perfect, because polling here is a bit complicated. Maybe it does the right thing, but I think dhclient should at least check if one of the conditions is suddenly right (we are associated, or we really have link). So this needs definitly

Re: dhclient/dhclient.conf change in -CURRENT? (fwd)

2003-08-04 Thread Larry Rosenman
Forwarding to the list... Forwarded Message Date: Monday, August 04, 2003 20:18:28 -0500 From: Larry Rosenman [EMAIL PROTECTED] To: Martin Blapp [EMAIL PROTECTED] Cc: Subject: Re: dhclient/dhclient.conf change in -CURRENT? It did NOT do the right thing at boot

Re: dhclient script in rc.d doesn't use ${dhcp_program}(conf/53007)

2003-06-07 Thread Mike Makonnen
On Sat, 7 Jun 2003 03:18:18 -0600 John Nielsen [EMAIL PROTECTED] wrote: I just submitted a PR for a bug I noticed in the dhclient script. Namely, it ignores the setting of dhcp_program from rc.conf. A one-line fix did the trick for me, although there may be ramifications I'm not aware of.

Re: dhclient in background?

2003-01-10 Thread Daniel O'Connor
On Fri, 2003-01-10 at 21:16, Dario Freni wrote: Hi everybody. I'm a developer of the FreeSBIE project (just another FreeBSD-on-a-live-cd project). As default network configuration, we've reasonally chosen a dhcp configuration, which is great on a dhcp network, but ugly when it has to wait for

Re: dhclient in background?

2003-01-10 Thread Ceri Davies
On Fri, Jan 10, 2003 at 11:13:34PM +1030, Daniel O'Connor wrote: On Fri, 2003-01-10 at 21:16, Dario Freni wrote: Hi everybody. I'm a developer of the FreeSBIE project (just another FreeBSD-on-a-live-cd project). As default network configuration, we've reasonally chosen a dhcp

Re: dhclient in background?

2003-01-10 Thread Dario Freni
Reply to both and in ML You could use the timeout option in dhclient.conf.. IMHO it's a risk. From man dhclient: The client can also be instructed to become a daemon imme- diately, rather than waiting until it has acquired an IP address. This can be done by

Re: dhclient in background?

2003-01-10 Thread Ceri Davies
On Fri, Jan 10, 2003 at 03:03:57PM +0100, Dario Freni wrote: Reply to both and in ML You could use the timeout option in dhclient.conf.. IMHO it's a risk. From man dhclient: The client can also be instructed to become a daemon imme- diately, rather than waiting

Re: dhclient

2001-12-15 Thread PaZt
Sounds more like a non-reachable dhcp server On Thu, 13 Dec 2001, Edwin Culp wrote: Is anyone using dhclient successfully with Current of the last week or so? I don't use it all the time but I have been trying for the last couple of days without success. It accesses the server and

Re: dhclient

2001-12-14 Thread Robert Watson
On Thu, 13 Dec 2001, Edwin Culp wrote: Is anyone using dhclient successfully with Current of the last week or so? I don't use it all the time but I have been trying for the last couple of days without success. It accesses the server and changes the interface ip to 0.0.0.0 netmask

Re: dhclient

2001-12-14 Thread Edwin Culp
Robert, I got it working by adding a dhclient configuration file rather than using the empty file that I have always used. I'm not sure why but it works:-) I'll break out ethereal a little later and see if I can figure it out. Thanks, ed Quoting Robert Watson [EMAIL PROTECTED]: On Thu,

Re: dhclient

2001-12-13 Thread Emiel Kollof
* Edwin Culp ([EMAIL PROTECTED]) wrote: Is anyone using dhclient successfully with Current of the last week or so? I don't use it all the time but I have been trying for the last couple of days without success. It accesses the server and changes the interface ip to 0.0.0.0 netmask

Re: dhclient

2001-12-13 Thread David Wolfskill
Date: Thu, 13 Dec 2001 06:15:32 -0800 From: Edwin Culp [EMAIL PROTECTED] Is anyone using dhclient successfully with Current of the last week or so? Sure; hadn't noticed any problems with it. I don't use it all the time but I have been trying for the last couple of days without success. It

Re: dhclient

2001-12-13 Thread Edwin Culp
Emiel, Thanks a lot for the feedback. I have to look further. Hmmm... Maybe it is my dhcp server but the problem originated with the excite@home service change to attbi.com and their dhcp. Neither work:-( ed Quoting Emiel Kollof [EMAIL PROTECTED]: * Edwin Culp ([EMAIL PROTECTED]) wrote:

Re: dhclient

2001-12-13 Thread Edwin Culp
Thanks, David. I'm going to have to go through the whole troubleshooting process. Both the server and the client, my laptop, are running current and to make it worse I did a portupgrade -Rria on both since I used dhcp the last time. At least I know that it should work:-) Thanks, again. ed

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

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,

Re: dhclient fails on -current

2001-09-11 Thread David O'Brien
On Tue, Sep 11, 2001 at 01:28:12PM -0500, Michael Harnois wrote: For the last five days or so, dhclient from isc-dhcp2 has not worked with -current on my machine. It reports dc0: not found. Some others reported a similar problem with postfix which was cured by recompiling. The same solution

Re: dhclient fails on -current

2001-09-11 Thread Michael Harnois
On Tue, 11 Sep 2001 13:05:57 -0700, David O'Brien [EMAIL PROTECTED] said: Why are you using the client from isc-dhcp2 when that is the same client in the base system? In fact, having looked at my rc.conf now, I am using the one from the base system. -- Michael D. Harnois