Erling Westenvik wrote:
> Hi,
>
> When booting bsd.rd I can do:
>
> # ifconfig inet autoconf
>
> and it will negotiate a working IP and gateway setup from my DHCP
> server.
>
> However, when booting 'boot -s' (singleuser) the only way to have a
> working IP and gateway setup is to specify it
On 2022-12-22, Geoff Steckel wrote:
> Are routes and resolv.conf the only things dhcpleased modifies beyond
> configuring the interface with the leased IP?
dhcpleased only sets IP/mask and routes, and sends a nameserver proposal
on the route socket, which resolvd picks up if running.
IP/mask/DN
On Fri Dec 23, 2022 at 1:23 AM CET, Geoff Steckel wrote:
> My objection to dhcpleased is not whether the program does useful things.
> I'm sure it does "what it should".
>
> Adding this sentence to the dhcpleased man page would make
> it clear what it does beyond leasing the IP:
>
> "By default, it
Geoff Steckel wrote:
> My objection to dhcpleased is not whether the program does useful things.
> I'm sure it does "what it should".
>
> Adding this sentence to the dhcpleased man page would make
> it clear what it does beyond leasing the IP:
>
> "By default, it replaces the DNS server in /etc
My objection to dhcpleased is not whether the program does useful things.
I'm sure it does "what it should".
Adding this sentence to the dhcpleased man page would make
it clear what it does beyond leasing the IP:
"By default, it replaces the DNS server in /etc/resolv.conf
and replaces the defaul
On 22.12.2022 01:57, Geoff Steckel wrote:
On 12/21/22 09:05, Crystal Kolipe wrote:
On Wed, Dec 21, 2022 at 01:39:47PM +, Rodrigo Readi wrote:
The command "dhclient -d run0" with or without "-d" seems to
demonize,
always, and is till now completely silent.
Is this new behaviour normal?
we were the last operating system to have dynamic resolv.conf
management and then the whiners who had left the operating systems
with dynamic resolv.conf and come here for static resolv.conf
became upset.
i am very sorry they got upset. not going to change it. after 2-3 years
of small changes, th
On 12/21/22 09:05, Crystal Kolipe wrote:
On Wed, Dec 21, 2022 at 01:39:47PM +, Rodrigo Readi wrote:
The command "dhclient -d run0" with or without "-d" seems to demonize,
always, and is till now completely silent.
Is this new behaviour normal? How I get it the old way?
You might want to lo
On 2022-12-21 15:04 UTC, Rodrigo Readi wrote:
> Too much innovations, too much daemons ... :)
Things kinda went downhill after CSRG disbanded.
On Wed, Dec 21, 2022 at 03:04:01PM +, Rodrigo Readi wrote:
> Am Mi., 21. Dez. 2022 um 14:06 Uhr schrieb Crystal Kolipe
> :
>
> > You might want to look at the commit message for version 1.727 of
> > dhclient.c:
> >
> > http://cvsweb.openbsd.org/src/sbin/dhclient/dhclient.c
>
> And also /var/l
Am Mi., 21. Dez. 2022 um 14:06 Uhr schrieb Crystal Kolipe
:
> You might want to look at the commit message for version 1.727 of
> dhclient.c:
>
> http://cvsweb.openbsd.org/src/sbin/dhclient/dhclient.c
And also /var/log/messages: "dhclient will go away, stop using it".
Before dhclient I do "ifcon
On Wed, Dec 21, 2022 at 01:39:47PM +, Rodrigo Readi wrote:
> The command "dhclient -d run0" with or without "-d" seems to demonize,
> always, and is till now completely silent.
>
> Is this new behaviour normal? How I get it the old way?
You might want to look at the commit message for version
> On 23 Jul 2020, at 22:28, Guy Godfroy wrote:
>
> Doesn't work better.
> I guess Sebastian is right, carp has to be assigned an IP to come up.
yeah, i just read the code a bit. they have to be able to communicate to be
able to elect which one is the active and which is the backup. i suggest
Doesn't work better.
I guess Sebastian is right, carp has to be assigned an IP to come up.
Le 23/07/2020 à 03:15, David Gwynne a écrit :
On 22 Jul 2020, at 22:59, Guy Godfroy wrote:
Hello,
So I read in 6.7 release note that it's finally possible to use dhclient on
CARP interface. That's g
> On 22 Jul 2020, at 22:59, Guy Godfroy wrote:
>
> Hello,
>
> So I read in 6.7 release note that it's finally possible to use dhclient on
> CARP interface. That's great news.
>
> However, I'm not sure how to use it on a hostname.if file. I tried to replace
> inet instruction directly with
Guy Godfroy(guy.godf...@gugod.fr) on 2020.07.22 14:59:53 +0200:
> Hello,
>
> So I read in 6.7 release note that it's finally possible to use dhclient
> on CARP interface. That's great news.
>
> However, I'm not sure how to use it on a hostname.if file. I tried to
> replace inet instruction dire
Update to a newer snapshot.
On 2019-04-06, Matthew Graybosch wrote:
> On Thu, Apr 4, 2019, at 1:19 AM, Greg Steuck wrote:
>> April 2 snapshot misbehaves badly on Google Compute Engine.
>>
>> # dmesg | head
>> OpenBSD 6.5 (GENERIC.MP) #839: Tue Apr 2 20:38:19 MDT 2019
>> dera...@amd64.openbs
On Thu, Apr 4, 2019, at 1:19 AM, Greg Steuck wrote:
> April 2 snapshot misbehaves badly on Google Compute Engine.
>
> # dmesg | head
> OpenBSD 6.5 (GENERIC.MP) #839: Tue Apr 2 20:38:19 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> # dhclient -v -d vio0
> vi
On Mon, 14 May 2018 19:36:12 -0400
Quartz wrote:
> > Currently there is no facility in dhclient(8) to issue RELEASE
> > messages. I had no recollection of adding such a thing, and a
> > quick
>
> > confirmed there is no DHCPRELEASE related code.
>
> Ergh. OK thanks, that's super annoying th
Currently there is no facility in dhclient(8) to issue RELEASE
messages. I had no recollection of adding such a thing, and a
quick
confirmed there is no DHCPRELEASE related code.
Ergh. OK thanks, that's super annoying that it's not there.
Which
signal(s) are used elsewhere to trigger RELEAS
On Thu, May 03, 2018 at 12:05:40PM +0200, Paul de Weerd wrote:
> Stick a v6 recursor in /etc/resolv.conf.tail. When dhclient updates
> /etc/resolv.conf, it'll append the contents of /etc/resolv.conf.tail
> to it and you will have your v6 resolver availble that way. You could
> even ignore the v4
On Thu, May 03, 2018 at 10:44:18AM +0200, Marc Peters wrote:
| On Thu, May 03, 2018 at 10:31:27AM +0200, Janne Johansson wrote:
| >Since manpage doesn't mention v6 namespace at all, I'd wager you would
| >have to
| >run something else to pick up v6 resolvers.
|
| Yeah, that's right. Ma
On Thu, May 03, 2018 at 10:31:27AM +0200, Janne Johansson wrote:
>Since manpage doesn't mention v6 namespace at all, I'd wager you would
>have to
>run something else to pick up v6 resolvers.
Yeah, that's right. Maybe, i stick to v4 resolvers for now or add it by
hand, when i reboot it.
2018-05-02 18:07 GMT+02:00 Marc Peters :
> On Wed, May 02, 2018 at 04:24:50PM +0200, Janne Johansson wrote:
> > Seems common on other dhcpd's too:
> > https://lists.isc.org/pipermail/dhcp-users/2012-May/015511.html
> >
>
> ah, the option has a different name for IPv6 nameservers. Does the base
> d
On Wed, May 02, 2018 at 04:24:50PM +0200, Janne Johansson wrote:
> Seems common on other dhcpd's too:
> https://lists.isc.org/pipermail/dhcp-users/2012-May/015511.html
>
ah, the option has a different name for IPv6 nameservers. Does the base
dhclient recognize these different options, or do i hav
Am 2. Mai 2018 16:24:50 MESZ schrieb Janne Johansson :
>2018-05-02 16:06 GMT+02:00 Marc Peters :
>
>> Hi misc,
>> dhclient hates me. I would like to prepend an IPv6 nameserver in the
>> dhclient configuration on my router when connecting to my ISP, but
>> dhclient gives me following error:
>>
>> em
2018-05-02 16:06 GMT+02:00 Marc Peters :
> Hi misc,
> dhclient hates me. I would like to prepend an IPv6 nameserver in the
> dhclient configuration on my router when connecting to my ISP, but
> dhclient gives me following error:
>
> em1: /etc/dhclient.conf line 17: expecting IPv4 address.
> em1: p
On Sun, Feb 11, 2018 at 5:05 AM, Kenneth R Westerback wrote:
> Extraneous "bound to ..." messages are no longer logged on renewal.
>
> So the original "bound to ..." message remains valid until something
> changes.
>
> If you look at the leases file you should see it get a new 'epoch' (the
> time
On 02/11/18 05:12, Christer Solskogen wrote:
On Sun, Feb 11, 2018 at 12:47 AM, wrote:
What is the output of:
$ hostname
hugs# hostname
hugs.antarctica.no
hugs# hostname -s
hugs
I'm out of ideas. Pretty sure it won't like a hostname without 2 parts ie:
my.domain
Looks like there has
On Sun, Feb 11, 2018 at 12:47 AM, wrote:
> What is the output of:
>
> $ hostname
>
>
hugs# hostname
hugs.antarctica.no
hugs# hostname -s
hugs
On Feb 10, 2018 5:07 PM, Christer Solskogen
wrote:
>
> On Sat, Feb 10, 2018 at 11:16 PM, Edgar Pettijohn
> wrote:
>
> > try:
> > supersede host-name "my.hugs";
> >
> >
> Still same warning. But I think this comes from the dhcp server of my ISP.
> Even without the options it says so.
What is th
On Sat, Feb 10, 2018 at 11:16 PM, Edgar Pettijohn
wrote:
> try:
> supersede host-name "my.hugs";
>
>
Still same warning. But I think this comes from the dhcp server of my ISP.
Even without the options it says so.
On 02/10/18 15:43, Christer Solskogen wrote:
On Sat, Feb 10, 2018 at 8:44 PM, Mihai Popescu wrote:
Upgraded to latest current snapshot, and it looks like dhclient doesn't
renew the ip anymore. I'm > running it in debug mode now, to see if there
is anything in the log.
Thank you for lettin
On Sat, Feb 10, 2018 at 8:44 PM, Mihai Popescu wrote:
> > Upgraded to latest current snapshot, and it looks like dhclient doesn't
> renew the ip anymore. I'm > running it in debug mode now, to see if there
> is anything in the log.
>
> Thank you for letting people know.
> It will take forever if
> Upgraded to latest current snapshot, and it looks like dhclient doesn't renew
> the ip anymore. I'm > running it in debug mode now, to see if there is
> anything in the log.
Thank you for letting people know.
It will take forever if it is not correctly setup.
http://www.openbsd.org/faq/faq1.
On Mon, Jun 19, 2017 at 10:11 AM, Stuart Henderson
wrote:
> On 2017-06-18, Christer Solskogen wrote:
> > I'm running the latest snapshot, and I suspect that there is something
> > wrong with dhclient.
> > (or at least, that is the symptom)
> >
> >
> > Jun 18 20:50:14 tugs dhclient[79331]: DHCPDI
On 2017-06-18, Christer Solskogen wrote:
> I'm running the latest snapshot, and I suspect that there is something
> wrong with dhclient.
> (or at least, that is the symptom)
>
>
> Jun 18 20:50:14 tugs dhclient[79331]: DHCPDISCOVER on re2 - interval 1
> Jun 18 20:50:14 tugs dhclient[79331]: DHCPOFF
On Sun, Jun 18, 2017 at 10:54 PM, Edgar Pettijohn
wrote:
>
> What is the `host-name` that it claims to be invalid?
>
I have no idea. dhclient.conf is empty.
On 06/18/17 14:38, Christer Solskogen wrote:
I'm running the latest snapshot, and I suspect that there is something
wrong with dhclient.
(or at least, that is the symptom)
Jun 18 20:50:14 tugs dhclient[79331]: DHCPDISCOVER on re2 - interval 1
Jun 18 20:50:14 tugs dhclient[79331]: DHCPOFFER fr
Kenneth Westerback was kind enough to give detailed explanation but
forgot to CC misc@, with his permission here it is:
++
Date: Thu, 4 Feb 2016 10:18:39 -0500
From: Kenneth Westerback
Subject: re: dhclient iwn0 *and* run0
| DHCPREQUEST on iwn0 to 255.255.255.255
| DHCPACK from 192.168.188.189 (80:1f:02:c1:fd:86)
| bound to 192.168.188.104 -- renewal in 900 seconds.
|
| DHCPREQUEST on run0 to 255.255.255.255
| DHCPACK from 192.168.188.189 (80:1f:02:c1:fd:86)
| bound to 192.168.188.105 -- renewal in 898 seconds.
Subn
On Wed, Sep 23, 2015 at 01:27:27PM +0100, Stuart Henderson wrote:
> On 2015/09/23 08:16, Kurt Mosiejczuk wrote:
> > Can you point me at the bug fix? I was looking at cvsweb again and the
> > newest change I could see there is 2 weeks ago...
> I believe this is the issue fixed by this commit - if
On Wed, Sep 23, 2015 at 07:37:05AM +, Stuart Henderson wrote:
> On 2015-09-22, Kurt Mosiejczuk wrote:
> > I just updated my current box to yesterdays (2015-09-21) snapshot. Now
> > it won't keep a network address.
> That's a recent bug - should be fixed if you update again.
Excellent. I'
On 2015/09/23 08:16, Kurt Mosiejczuk wrote:
> On Wed, Sep 23, 2015 at 07:37:05AM +, Stuart Henderson wrote:
> > On 2015-09-22, Kurt Mosiejczuk wrote:
> > > I just updated my current box to yesterdays (2015-09-21) snapshot. Now
> > > it won't keep a network address.
>
> > That's a recent bu
On 2015-09-22, Kurt Mosiejczuk wrote:
> I just updated my current box to yesterdays (2015-09-21) snapshot. Now
> it won't keep a network address.
That's a recent bug - should be fixed if you update again.
> I'm seeing a note on the current FAQ from the 12th indicating the
> ifmedia options ha
On 2014-06-23, Kenneth Westerback wrote:
> Alternatively you can monitor the leases file or use the '-L' option
> to write out the offered and effective lease information if you want
> complete information on what is being received and used. Some people
> use the entr port (/usr/ports/sysutils/ent
kwesterb...@gmail.com (Kenneth Westerback), 2014.06.23 (Mon) 18:53 (CEST):
> On 23 June 2014 06:24, Avi Cohen wrote:
> > In my application (it is a router in the access) I'm initially running
> > dhclient daemon without any interface specified for dhcp.
> > Then - on user request - we add in
On 23 June 2014 06:24, Avi Cohen wrote:
> Hello
> In my application (it is a router in the access) I'm initially running
> dhclient daemon without any interface specified for dhcp.
> Then - on user request - we add interfaces to dhclient.conf on run-time
>
> I have 3 questions - that I'll
On Sun 27/04, Kenneth R Westerback wrote:
> On Fri, Apr 25, 2014 at 12:31:16PM +0200, Alessandro DE LAURENZIS wrote:
> > On Tue 22/04, Kenneth Westerback wrote:
> > > >
> > > > Another thing: as highlighted in my initial message, I'm using the
> > > > loopback i/f as router address in the lease dec
On Mon, Apr 21, 2014 at 4:29 PM, Alessandro DE LAURENZIS <
just22@gmail.com> wrote:
> Hello,
>
> 5.4-Rel here, GENERIC.MP kernel.
>
> Rather often I need to connect my laptop to networks without DHCP service
> (sometimes I use a direct connection through a crossover cable, too); so
> it would
On Thu, Mar 27, 2014 at 6:58 PM, sven falempin wrote:
> On Thu, Mar 27, 2014 at 6:42 PM, Alexander Hall wrote:
>> On 03/27/14 23:36, Adam Thompson wrote:
>>
>>> my $src = system('/usr/bin/pkill -HUP -f "^dhclient: trunk0"');
>>
>>
>> my $src = system('/usr/bin/pkill', '-HUP', '-f', '^dhclient:
On 03/27/14 23:58, sven falempin wrote:
On Thu, Mar 27, 2014 at 6:42 PM, Alexander Hall wrote:
On 03/27/14 23:36, Adam Thompson wrote:
my $src = system('/usr/bin/pkill -HUP -f "^dhclient: trunk0"');
my $src = system('/usr/bin/pkill', '-HUP', '-f', '^dhclient: trunk0');
/Alexander
T
On Thu, Mar 27, 2014 at 6:42 PM, Alexander Hall wrote:
> On 03/27/14 23:36, Adam Thompson wrote:
>
>> my $src = system('/usr/bin/pkill -HUP -f "^dhclient: trunk0"');
>
>
> my $src = system('/usr/bin/pkill', '-HUP', '-f', '^dhclient: trunk0');
>
> /Alexander
>
Thank you all, i'll put the begin
On 03/27/14 23:36, Adam Thompson wrote:
my $src = system('/usr/bin/pkill -HUP -f "^dhclient: trunk0"');
my $src = system('/usr/bin/pkill', '-HUP', '-f', '^dhclient: trunk0');
/Alexander
On 2014-03-27 17:07, Philip Guenther wrote:
> On Thu, Mar 27, 2014
at 3:00 PM, Philip Guenther wrote:
>
>> On Thu,
Mar 27, 2014 at 2:28 PM, sven falempin
wrote:
>>
>>> Sometimes i feel curse (or maybe just tired) :
main::(/bin/check_network.pl:164): my $src = system('/usr/bin/pkill -HUP
-f "
On 03/27/14 23:26, Alexander Hall wrote:
On 03/27/14 23:07, Philip Guenther wrote:
On Thu, Mar 27, 2014 at 3:00 PM, Philip Guenther
wrote:
On Thu, Mar 27, 2014 at 2:28 PM, sven falempin
wrote:
Sometimes i feel curse (or maybe just tired) :
main::(/bin/check_network.pl:164): my $src =
s
On 03/27/14 23:07, Philip Guenther wrote:
On Thu, Mar 27, 2014 at 3:00 PM, Philip Guenther wrote:
On Thu, Mar 27, 2014 at 2:28 PM, sven falempin wrote:
Sometimes i feel curse (or maybe just tired) :
main::(/bin/check_network.pl:164): my $src =
system('/usr/bin/pkill -HUP -f "dhclient: t
On Thu, Mar 27, 2014 at 3:00 PM, Philip Guenther wrote:
> On Thu, Mar 27, 2014 at 2:28 PM, sven falempin
> wrote:
>> Sometimes i feel curse (or maybe just tired) :
>>
>> main::(/bin/check_network.pl:164): my $src =
>> system('/usr/bin/pkill -HUP -f "dhclient: trunk0"');
>> DB<2> n
>> main
On Thu, Mar 27, 2014 at 2:28 PM, sven falempin wrote:
> Sometimes i feel curse (or maybe just tired) :
>
> main::(/bin/check_network.pl:164): my $src =
> system('/usr/bin/pkill -HUP -f "dhclient: trunk0"');
> DB<2> n
> main::(/bin/check_network.pl:165):if ($src) {
> DB<2> p $src
>
On Wed, Mar 26, 2014 at 3:13 PM, Theo de Raadt wrote:
>> Using pkill(1) correctly should be more efficient than opening a
>> file, reading its contents, then passing those as an argument to
>> kill(1).
>
> None of the mechanisms removes the race.
>
> However, of all the mechanisms, pidfiles are th
> previously on this list Adam Thompson contributed:
>
> > The flip side is that correct usage of pkill in the face of proctitle
> > alterations is far from obvious.
>
> It's never been a problem for me and I thought avoiding pid files was
> going against the grain. Glad I was doing it right aft
previously on this list Adam Thompson contributed:
> The flip side is that correct usage of pkill in the face of proctitle
> alterations is far from obvious.
It's never been a problem for me and I thought avoiding pid files was
going against the grain. Glad I was doing it right after all. If you
> Using pkill(1) correctly should be more efficient than opening a
> file, reading its contents, then passing those as an argument to
> kill(1).
None of the mechanisms removes the race.
However, of all the mechanisms, pidfiles are the worst. They
even persist over reboot.
On 2014-03-26 13:31, sven falempin wrote:
> On Wed, Mar 26, 2014
at 1:55 PM, Jan Stary wrote:
>
>> On Mar 26 09:29:16,
sven.falem...@gmail.com [1]wrote:
>>
>>> Listing process takes also
times,
>> pkill doesn't list anything. No really, read the manpage.
>>
>>> and deleting the listed PID m
On Wed, Mar 26, 2014 at 1:55 PM, Jan Stary wrote:
> On Mar 26 09:29:16, sven.falem...@gmail.com wrote:
>> Listing process takes also times,
>
> pkill doesn't list anything.
> No really, read the manpage.
>
>> and deleting the listed PID may also
>> end in deleting another process in a race conditi
On Mar 26 09:29:16, sven.falem...@gmail.com wrote:
> Listing process takes also times,
pkill doesn't list anything.
No really, read the manpage.
> and deleting the listed PID may also
> end in deleting another process in a race condition case.
> Or is there some kind of smart lock inside pkill ?
On Tue, Mar 25, 2014 at 4:02 PM, Theo de Raadt wrote:
>> well openBSD is so neat it provides a nice call:
>>
>> http://www.openbsd.org/cgi-bin/man.cgi?query=pidfile&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html
>>
>> but i failed to patch :'( this make the dhclient quit instea
Hi Adam,
Adam Thompson wrote on Tue, Mar 25, 2014 at 03:11:49PM -0500:
> .Sh SIGNALS
> While running,
> .Nm
> uses a privilege-separation model, so there will be two processes
> (one with [priv] in its process title and one without),
> either of which will react to a few different signals:
>
> (
On Tue 25 Mar 2014 03:02:19 PM CDT, Theo de Raadt wrote:
[...] the fact there is two process may also explain why
there is no pidfile. One is root he other dropped privilege, all of
this is just giving me a headache at the moment.
Based on 5.4-RELEASE, then, since I agree the situation is conf
> well openBSD is so neat it provides a nice call:
>
> http://www.openbsd.org/cgi-bin/man.cgi?query=pidfile&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html
>
> but i failed to patch :'( this make the dhclient quit instead of
> going background, the fact there is two process may
On Tue, Mar 25, 2014 at 3:44 PM, Adam Thompson wrote:
> On Tue 25 Mar 2014 02:08:17 PM CDT, Josh Grosse wrote:
>>
>> On 2014-03-25 14:49, sven falempin wrote:
>>
>>> # pgrep -f "dhclient: vr0 [priv] (dhclient)"
>>> # pgrep -f "dhclient: vr0 [priv]"
>>> # pgrep -f "dhclient: vr0"
>>> 12556
>>> 2182
> On Tue, Mar 25, 2014 at 1:11 PM, Jan Stary wrote:
> > On Mar 25 11:19:12, sven.falem...@gmail.com wrote:
> >> Dealing with the removal of user script for dhclient is ok.
> >> On the other where's the PID file of this daemon
> >> This soft answer HUP,INT.QUIT,USR1 et 2 yet i dont find a way
On Mar 25 14:49:23, sven.falem...@gmail.com wrote:
> On Tue, Mar 25, 2014 at 1:11 PM, Jan Stary wrote:
> > On Mar 25 11:19:12, sven.falem...@gmail.com wrote:
> >> Dealing with the removal of user script for dhclient is ok.
> >> On the other where's the PID file of this daemon
> >> This soft a
On Tue 25 Mar 2014 02:08:17 PM CDT, Josh Grosse wrote:
On 2014-03-25 14:49, sven falempin wrote:
# pgrep -f "dhclient: vr0 [priv] (dhclient)"
# pgrep -f "dhclient: vr0 [priv]"
# pgrep -f "dhclient: vr0"
12556
21826
Where do I kill ? (there is also a few other dhclient running)
kill(1) isn't
On Tue, Mar 25, 2014 at 3:08 PM, Josh Grosse wrote:
> On 2014-03-25 14:49, sven falempin wrote:
>
>> # pgrep -f "dhclient: vr0 [priv] (dhclient)"
>> # pgrep -f "dhclient: vr0 [priv]"
>> # pgrep -f "dhclient: vr0"
>> 12556
>> 21826
>>
>>
>> Where do I kill ? (there is also a few other dhclient runn
On 2014-03-25 14:49, sven falempin wrote:
# pgrep -f "dhclient: vr0 [priv] (dhclient)"
# pgrep -f "dhclient: vr0 [priv]"
# pgrep -f "dhclient: vr0"
12556
21826
Where do I kill ? (there is also a few other dhclient running)
kill(1) isn't actually required. Try:
# ifconfig vr0 down
On Tue, Mar 25, 2014 at 1:11 PM, Jan Stary wrote:
> On Mar 25 11:19:12, sven.falem...@gmail.com wrote:
>> Dealing with the removal of user script for dhclient is ok.
>> On the other where's the PID file of this daemon
>> This soft answer HUP,INT.QUIT,USR1 et 2 yet i dont find a way to get
>>
On Mar 25 11:19:12, sven.falem...@gmail.com wrote:
> Dealing with the removal of user script for dhclient is ok.
> On the other where's the PID file of this daemon
> This soft answer HUP,INT.QUIT,USR1 et 2 yet i dont find a way to get
> the pid (listing process is dirty)
No it's not: pkill(1)
On 5 February 2014 06:35, Holger Glaess wrote:
> Am 03.02.2014 17:54, schrieb Kenneth Westerback:
>
>> Reactivating the dhclient-script is not going to happen.
>>
>> I am interested in what you would see syntax in dhclient.conf looking
>> like.
>>
>> Would multi-path routing modifications to all r
Am 03.02.2014 17:54, schrieb Kenneth Westerback:
Reactivating the dhclient-script is not going to happen.
I am interested in what you would see syntax in dhclient.conf looking like.
Would multi-path routing modifications to all routes be needed? How should this
be combined with supersede/defaul
Em 03-02-2014 14:54, Kenneth Westerback escreveu:
> Reactivating the dhclient-script is not going to happen.
>
> I am interested in what you would see syntax in dhclient.conf looking like.
>
> Would multi-path routing modifications to all routes be needed? How should
> this
> be combined with supe
Reactivating the dhclient-script is not going to happen.
I am interested in what you would see syntax in dhclient.conf looking like.
Would multi-path routing modifications to all routes be needed? How should this
be combined with supersede/default/append commands for the relevant
options? Would i
Quoting Holger Glaess :
Am 30.01.2014 13:10, schrieb Giancarlo Razzolini:
Em 29-01-2014 18:13, Holger Glaess escreveu:
hi
i try to setup and multipath configuration with 2 line provider
1 cable with dhcp(client)
1 with pppoe
just dynamic ips.
the pppoe config create well the new default ro
Am 30.01.2014 13:10, schrieb Giancarlo Razzolini:
Em 29-01-2014 18:13, Holger Glaess escreveu:
hi
i try to setup and multipath configuration with 2 line provider
1 cable with dhcp(client)
1 with pppoe
just dynamic ips.
the pppoe config create well the new default route with -math
but dhclien
Em 29-01-2014 18:13, Holger Glaess escreveu:
> hi
>
> i try to setup and multipath configuration with 2 line provider
>
> 1 cable with dhcp(client)
> 1 with pppoe
>
> just dynamic ips.
>
> the pppoe config create well the new default route with -math
> but dhclient dont.
>
> [snip pppoe config]
>
>
On 05/13/13 15:19, Kenneth R Westerback wrote:
On Mon, May 13, 2013 at 09:40:59AM +0100, Mike Williams wrote:
Hi,
I have been upgrading my machines to 5.3 this weekend and I am
seeing some strange behaviours with dhclient. The config is simple:
/etc/dhclient.conf
send host-name "pc-1";
reques
On Mon, May 13, 2013 at 09:40:59AM +0100, Mike Williams wrote:
> Hi,
>
> I have been upgrading my machines to 5.3 this weekend and I am
> seeing some strange behaviours with dhclient. The config is simple:
>
> /etc/dhclient.conf
> send host-name "pc-1";
> request subnet-mask, broadcast-address,
On Thu, May 09, 2013 at 07:38:55AM -0400, Jiri B wrote:
> On Wed, May 08, 2013 at 07:58:26PM -0700, Chris Cappuccio wrote:
> > For now you'll need to call your dns script from dhclient. A system() will
> > do the trick.
>
> Is planned to have an ability to fire a script/command from dhclient
> in
On Wed, May 08, 2013 at 07:58:26PM -0700, Chris Cappuccio wrote:
> For now you'll need to call your dns script from dhclient. A system() will do
> the trick.
Is planned to have an ability to fire a script/command from dhclient
in the future? I used to be putting on/off various dns servers for
my
For now you'll need to call your dns script from dhclient. A system() will do
the trick.
Scott [8f27e...@gmail.com] wrote:
> Hi everyone,
>
> Migrated to v5.3. I had a mod to the former dhclient-script that would fire
> a "wget" to my dns provider, which in turn, would act as a dynamic update
>
On Sun, Apr 28, 2013 at 6:39 PM, Kenneth R Westerback
wrote:
> On Sun, Apr 28, 2013 at 05:29:05PM -0400, David Higgs wrote:
>> On Sun, Apr 28, 2013 at 4:00 PM, Kenneth R Westerback
>> wrote:
>> > On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
>> >> Confirmed in 5.3-current downloade
On Sun, Apr 28, 2013 at 05:29:05PM -0400, David Higgs wrote:
> On Sun, Apr 28, 2013 at 4:00 PM, Kenneth R Westerback
> wrote:
> > On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
> >> Confirmed in 5.3-current downloaded several minutes ago.
> >>
> >> Steps to reproduce:
> >> - Boot bsd
On Sun, Apr 28, 2013 at 05:29:05PM -0400, David Higgs wrote:
> On Sun, Apr 28, 2013 at 4:00 PM, Kenneth R Westerback
> wrote:
> > On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
> >> Confirmed in 5.3-current downloaded several minutes ago.
> >>
> >> Steps to reproduce:
> >> - Boot bsd
On Sun, Apr 28, 2013 at 4:00 PM, Kenneth R Westerback
wrote:
> On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
>> Confirmed in 5.3-current downloaded several minutes ago.
>>
>> Steps to reproduce:
>> - Boot bsd.rd
>> - Select upgrade, hit enter until dhclient gets and assigns an addre
On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
> Confirmed in 5.3-current downloaded several minutes ago.
>
> Steps to reproduce:
> - Boot bsd.rd
> - Select upgrade, hit enter until dhclient gets and assigns an address
> - Complete upgrade or control-C, then restart the upgrade proce
On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
> Confirmed in 5.3-current downloaded several minutes ago.
>
> Steps to reproduce:
> - Boot bsd.rd
> - Select upgrade, hit enter until dhclient gets and assigns an address
> - Complete upgrade or control-C, then restart the upgrade proce
On 02/28/2013 06:58 PM, Marc Peters wrote:
> Hi misc,
>
> i am using OpenBSD on my home router connected to cable internet. A re
> nic is facing the wild and gets its public IP via DHCP from my ISP. I
> have running a 5.3-beta from Feb. 1st, as this one has the powersaving
> fix for athn in HostAP
On Sun, Mar 03, 2013 at 03:10:38PM -0800, Jeff Richards wrote:
> I have been trying to configure a HP Pavilion dv5000(5210us) laptop to connect
> to a WEP network.? I have tried OBSD 5.2 and CURRENT without success using WEP
> but can connect with WPA --personal hotspot.
>
>
> The network interfa
On 02/28/2013 06:58 PM, Marc Peters wrote:
> Hi misc,
>
> i am using OpenBSD on my home router connected to cable internet. A re
> nic is facing the wild and gets its public IP via DHCP from my ISP. I
> have running a 5.3-beta from Feb. 1st, as this one has the powersaving
> fix for athn in HostAP
On Thu, Feb 28, 2013 at 12:58 PM, Marc Peters wrote:
> dhclient
I've noticed a lot of dhclient changes in cvs over the past few
weeks.You might try a newer snapshot.
Chris
1 - 100 of 162 matches
Mail list logo
