Re: dhclient/autoconf in singleuser vs. ramdisk kernel

P and gateway setup is to specify it manually by entering the > specific relevant values, like: > > # ifconfig 12.34.56.78 0xff00 > # route add default 12.34.56.1 > > Neither 'dhclient ' or 'ifconfig inet autoconf' works. > > What am I missing? dhcpleased is not running.

dhclient/autoconf in singleuser vs. ramdisk kernel

values, like: # ifconfig 12.34.56.78 0xff00 # route add default 12.34.56.1 Neither 'dhclient ' or 'ifconfig inet autoconf' works. What am I missing? (The DHCP server assigns IP adresses based on MAC adresses. Not having to "invent"/remember IP adresses for various machines would be

Re: dhclient -d run0

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.

Re: dhclient -d run0

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,

Re: dhclient -d run0

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

Re: dhclient -d run0

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

Re: dhclient -d run0

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

Re: dhclient -d run0

everytime you eat, you will collect a negative reaction. 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

Re: dhclient -d run0

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

Re: dhclient -d run0

On 2022-12-21 15:04 UTC, Rodrigo Readi wrote: > Too much innovations, too much daemons ... :) Things kinda went downhill after CSRG disbanded.

Re: dhclient -d run0

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/dhcli

Re: dhclient -d run0

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".

Re: dhclient -d run0

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 wa

dhclient -d run0

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? Thanks Rod.

Re: dhclient on carp

he backup. i suggest using an address like one in 169.254.x.y/16 so the carps can elect. > > 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 th

Re: dhclient on carp

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

Re: dhclient on carp

> 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 >

Re: dhclient on carp

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 > rep

dhclient on carp

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 dhcp: dhcp vhid 11 carpdev em1 pass description "

Re: dhclient vio0 -> Segmentation fault

T 2019 >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP >> # dhclient -v -d vio0 >> vio0: DHCPDISCOVER - interval 1 >> vio0: DHCPOFFER from 169.254.169.254 (42:01:0a:80:00:01) >> Segmentation fault >> # ls -l /sbin/dhclient > > I don'

Re: dhclient vio0 -> Segmentation fault

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 > # d

dhclient vio0 -> Segmentation fault

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 vio0: DHCPDISCOVER - interval 1 vio0: DHCPOFFER from

Re: [SOLVED] Re: apu2 em0/dhclient problems

Edgar Pettijohn [ed...@pettijohn-web.com] wrote: > > Don't know why it works, but em1 works. I guess I'll rewrite my config files. > This shouldn't be an acceptable solution to you. Unless the port is physically damaged, you should figure out what's going on. Tcpdump is a great start. Chris

[SOLVED] Re: apu2 em0/dhclient problems

On Tue, Jan 29, 2019 at 12:03:23PM -0600, Edgar Pettijohn wrote: > > On Jan 29, 2019 11:01 AM, Marcus MERIGHI wrote: > > > > Hello, > > > > ed...@pettijohn-web.com (Edgar Pettijohn), 2019.01.27 (Sun) 18:44 (CET): > > > I'm trying to replace my dieing soekris box with an apu2 dmesg below. > > >

Re: apu2 em0/dhclient problems

On Jan 29, 2019 11:01 AM, Marcus MERIGHI wrote: > > Hello, > > ed...@pettijohn-web.com (Edgar Pettijohn), 2019.01.27 (Sun) 18:44 (CET): > > I'm trying to replace my dieing soekris box with an apu2 dmesg below. > > However, I can't seem to get em0 to connect to my isp. It will work > > when

Re: apu2 em0/dhclient problems

Hello, ed...@pettijohn-web.com (Edgar Pettijohn), 2019.01.27 (Sun) 18:44 (CET): > I'm trying to replace my dieing soekris box with an apu2 dmesg below. > However, I can't seem to get em0 to connect to my isp. It will work > when connecting to the soekris box though. So I don't think its the >

Re: apu2 em0/dhclient problems

was able to connect directly to my laptop and get a lease immediately. Its odd... With base dhclient it goes something like: em0 no link em0. got link and then nothing. I installed isc-dhcp-client and it actually goes through the steps of the whole DHCPDISCOVER...etc,etc. Unfortunantly

Re: apu2 em0/dhclient problems

Den 27-01-2019 kl. 19:45 skrev trondd: On Sun, January 27, 2019 12:44 pm, Edgar Pettijohn wrote: I'm trying to replace my dieing soekris box with an apu2 dmesg below. However, I can't seem to get em0 to connect to my isp. It will work when connecting to the soekris box though. So I don't think

Re: apu2 em0/dhclient problems

My ISP locks the connection to a certain MAC for a number of hours. Tech > support can probably delete the old lease. > > Best regards, > > Mikkel > I don't think this is the case. I was able to connect directly to my laptop and get a lease immediately. Its odd... With base dhcli

Re: apu2 em0/dhclient problems

On Sun, January 27, 2019 12:44 pm, Edgar Pettijohn wrote: > I'm trying to replace my dieing soekris box with an apu2 dmesg below. > However, I can't seem to get em0 to connect to my isp. It will work > when connecting to the soekris box though. So I don't think its the > interface that is the

apu2 em0/dhclient problems

I'm trying to replace my dieing soekris box with an apu2 dmesg below. However, I can't seem to get em0 to connect to my isp. It will work when connecting to the soekris box though. So I don't think its the interface that is the problem. But everything I try seems to rule out eachother as the

dhclient hang on OpenBSD 6.3 on sis network card

the interface statically and _then_ run netstart, it also hangs as it does in the boot process. air# echo "dhcp" >/etc/hostname.sis0 air# /etc/netstart -n sis0 ifconfig sis0 down;dhclient sis0 air# /etc/netstart sis0 At this point the machine stops responding and must be hard-reset. ^C doesn'

Re: dhclient release a lease?

On Mon, 14 May 2018 19:36:12 -0400 Quartz <qua...@sneakertech.com> 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 rel

Re: dhclient release a lease?

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

dhclient release a lease?

How do I get dhclient to release its DHCP lease? I want to be clear that I'm not interested in having it RENEW the lease but RELEASE it- in other words send the signal to the DHCP server "I'm going bye-bye, go ahead and put this IP address back in your free pool". Other versions o

Re: 6.3 - dhclient not working on wireless

On 05/06/18 11:39, Stefan Sperling wrote: > On Sat, May 05, 2018 at 11:03:52PM +0200, Riccardo Mottola wrote: […] > A commit of mine accidentally broke WEP support back in August 2017. > This was eventually fixed in -current 2 weeks ago. Nobody noticed > that WEP was broken for 8 months... […]

WEP broken (was: Re: 6.3 - dhclient not working on wireless)

On Fri, May 11, 2018 at 04:56:19PM +0200, Riccardo Mottola wrote: > Is a backport possible to "stable"? I don't think it is worth the effort for us. You are literally the only person I know of who has requested an official backport of this fix. WEP was already broken in OpenBSD 6.2 which was

Re: 6.3 - dhclient not working on wireless

Hi, Stefan Sperling wrote: The keyword 'nwkey' indicates you are using WEP. Is that correct? Yes! A commit of mine accidentally broke WEP support back in August 2017. This was eventually fixed in -current 2 weeks ago. Nobody noticed that WEP was broken for 8 months... I did notice that

Re: 6.3 - dhclient not working on wireless

On Sat, May 05, 2018 at 11:03:52PM +0200, Riccardo Mottola wrote: > Hi, > > I upgraded to 6.3 and I cannot connect to a certain WiFi network anymore, > or, better, ifconfig says it is connected and the LED says it is too, but > then dhclient fails to get a lease from it.

6.3 - dhclient not working on wireless

Hi, I upgraded to 6.3 and I cannot connect to a certain WiFi network anymore, or, better, ifconfig says it is connected and the LED says it is too, but then dhclient fails to get a lease from it. I can connect to the same network through wired ethernet and dhclient correctly gets an address

Re: dhclient expects IPv4 address in dhclient.conf

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 i

Re: dhclient expects IPv4 address in dhclient.conf

t's right. Maybe, i stick to v4 resolvers for now or add it by | hand, when i reboot it. 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 ev

Re: dhclient expects IPv4 address in dhclient.conf

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

Re: dhclient expects IPv4 address in dhclient.conf

fferent name for IPv6 nameservers. Does the base > dhclient recognize these different options, or do i have to give > isc-dhcp-client a try for this? > Since manpage doesn't mention v6 namespace at all, I'd wager you would have to run something else to pick up v6 resolvers. --

Re: dhclient expects IPv4 address in dhclient.conf

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

Re: dhclient expects IPv4 address in dhclient.conf

Am 2. Mai 2018 16:24:50 MESZ schrieb Janne Johansson <icepic...@gmail.com>: >2018-05-02 16:06 GMT+02:00 Marc Peters <m...@mpeters.org>: > >> Hi misc, >> dhclient hates me. I would like to prepend an IPv6 nameserver in the >> dhclient configuration on

Re: dhclient expects IPv4 address in dhclient.conf

2018-05-02 16:06 GMT+02:00 Marc Peters <m...@mpeters.org>: > 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

dhclient expects IPv4 address in dhclient.conf

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: prepend domain-name-servers "::1

Re: Return back dhclient lease time displaying after renew an IP address manually

It was favourable to have lease information visible without any additional commands right after new lease has been obtained... On 4/26/2018 11:21 PM, Daniel Melameth wrote: > On Thu, Apr 26, 2018 at 2:11 PM, Denis wrote: >> After upgrading 6.2amd64 -> 6.3amd64 there is no

Re: Return back dhclient lease time displaying after renew an IP address manually

On Thu, Apr 26, 2018 at 2:11 PM, Denis wrote: > After upgrading 6.2amd64 -> 6.3amd64 there is no lease time info present > by renewing an IP address using '#sh /etc/netstart if0' command. > > Manually run dhclinent shows MAC address of a dhcpd server (very useful) > but lease

Return back dhclient lease time displaying after renew an IP address manually

After upgrading 6.2amd64 -> 6.3amd64 there is no lease time info present by renewing an IP address using '#sh /etc/netstart if0' command. Manually run dhclinent shows MAC address of a dhcpd server (very useful) but lease time has been deprecated since 6.2 (very useful for different dhcp servers

Re: dhclient not renewing

ook at the leases file you should see it get a new 'epoch' (the > time > the lease was obtained) on renewals. > The thing is that when dhclient is doing a renew the ip address doesn't attach to the interface: em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 l

Re: dhclient not renewing

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:

Re: dhclient not renewing

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

Re: dhclient not renewing

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

Re: dhclient not renewing

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.

Re: dhclient not renewing

On 02/10/18 15:43, Christer Solskogen wrote: On Sat, Feb 10, 2018 at 8:44 PM, Mihai Popescu <mih...@gmail.com> 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 i

Re: dhclient not renewing

On Sat, Feb 10, 2018 at 8:44 PM, Mihai Popescu <mih...@gmail.com> 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

Re: dhclient not renewing

> 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.

dhclient not renewing?

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.

6.2: dhclient -L option appends, not overwrites

I just upgraded from 6.1 to 6.2 (amd64) and I'm noticing a differing behavior with dhclient. I use the -L option to write out the offered and effective leases. With 6.1, when a lease was renewed, the -L lease file was overwritten with the new information. With 6.2, when a lease is renewed

Re: Bug in dhclient, isc_named or misconfiguration ?

I did that already (statically) but I find that as workaround. I think bug is in dhclient however I did not have time to investigate more. Thanks Sent from iPhone Zbyszek > Wiadomość napisana przez Florian Ermisch <florian.ermi...@mailbox.org> w dniu > 09.09.2017, o godz. 10

Re: Bug in dhclient, isc_named or misconfiguration ?

t; >Recently i come up with this problem: running isc_named + dhclient >cause isc_named to periodically loose binding to TCP port: > >Sep 7 13:45:02 ns dhclient[12533]: DHCPREQUEST on vio0 to >169.254.169.254 >Sep 7 13:45:02 ns dhclient[12533]: DHCPACK from 169.254.169.254 >(f

Bug in dhclient, isc_named or misconfiguration ?

Hi group, Recently i come up with this problem: running isc_named + dhclient cause isc_named to periodically loose binding to TCP port: Sep 7 13:45:02 ns dhclient[12533]: DHCPREQUEST on vio0 to 169.254.169.254 Sep 7 13:45:02 ns dhclient[12533]: DHCPACK from 169.254.169.254 (fe:00:00:88:fe:63

Re: dhclient won't get any IP

On Mon, Jun 19, 2017 at 10:11 AM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2017-06-18, Christer Solskogen <christer.solsko...@gmail.com> wrote: > > I'm running the latest snapshot, and I suspect that there is something > > wrong with dhclient. > >

Re: dhclient won't get any IP

On 2017-06-18, Christer Solskogen <christer.solsko...@gmail.com> 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 - i

Re: dhclient won't get any IP

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.

Re: dhclient won't get any IP

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

dhclient won't get any IP

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 from 51.174.112.1 (00:02:00:01:00:01) Jun 18 20:50

Re: Using isc-dhcp-client as alternate dhclient - Alias working (I think)

"isc-dhclient.conf" In it, following the isc dhclient.conf man page, I added an "alias" section, e.g.: alias { interface "em0"; fixed-address 10.0.0.0; option subnet-mask 255.255.255.0; } Now, it seems, the isc dhclient modifies things on t

Re: Using isc-dhcp-client as alternate dhclient

On 2016-09-20, Theodore Wynnychenko <t...@uchicago.edu> wrote: > First, I can't get the isc-dhcp-client to assign an alias to the interface, > despite the documentation that states it should. It seems to work if you preset the alias address on the interface before running dhclient.

Re: Using isc-dhcp-client as alternate dhclient

On 16-09-20 15:36:52, Theodore Wynnychenko wrote: > Hello > I would like to get the isc-dhcp-client working as a replacement for the base > dhclient. > > The primary reason for this is so that I can assign an alias to the interface. > > But, I can't seem to figure out how

Using isc-dhcp-client as alternate dhclient

Hello I would like to get the isc-dhcp-client working as a replacement for the base dhclient. The primary reason for this is so that I can assign an alias to the interface. But, I can't seem to figure out how to get this done. I have two issues. First, I can't get the isc-dhcp-client to assign

dhcp-class-identifier in dhclient

Hey, is there any reason to no setting dhcp-class-indentifier by default in dhclient? My guess is that this is probably not mandatory? //mxb

simple dhclient question

Hello Misc, is it possible to change the defaul right access of leases info $ cat /var/db/dhclient.leases.em0 cat: /var/db/dhclient.leases.em0: Permission denied I have no secret in this file, but a user might want to check the routers list, or if the lease is still valid. Is there a reason

Re: dhclient iwn0 *and* run0 -> lease duration confusion

ct: re: dhclient iwn0 *and* run0 -> lease duration confusion That message does not report the lease time, it reports the real time left before the lease expires after the bind completes.. Configuring the interface can take finite time after receiving the lease and starting the binding. If you want to

Re: dhclient iwn0 *and* run0 -> lease duration confusion

| 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.

dhclient iwn0 *and* run0 -> lease duration confusion

Hello, it seems dhclient gets confused about lease durations when getting leases for two (wlan) interfaces from the same dhcp server. I'm not sure this is a bug or done that way intentionally. While working on the ds47d issue (bugs@) I had left an additional WLAN stick connected

carp dhclient

Dear Readers, Without IP carp is marked as inactive, i tried to set up a stupid IP on it and then call dhclient. It sends packet but does configure interface. :'( Any particular reason for this ? Thank you

Re: carp dhclient

Josh Grosse wrote: On 2016-02-01 11:32, sven falempin wrote: Dear Readers, Without IP carp is marked as inactive, See https://sites.google.com/site/bsdstuff/dhcarp and adapt to your requirements. The Book of PF, 3rd Edition A No-Nonsense Guide to the OpenBSD Firewall by Peter N. M.

Re: carp dhclient

On 2016-02-01 11:32, sven falempin wrote: Dear Readers, Without IP carp is marked as inactive, i tried to set up a stupid IP on it and then call dhclient. It sends packet but does configure interface. :'( Any particular reason for this ? Thank you. Carp requires static addresses. You can

Re: dhclient broken on 2015-09-21 amd64 snapshot

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.

Re: dhclient broken on 2015-09-21 amd64 snapshot

he newest change I could see there is 2 weeks ago... > > Did the dhclient change get overlooked? Am I doing something else > > obviously wrong? > This is unrelated, but dhclient just needed recompiling with the updated > headers ("include files") to know about the la

Re: dhclient broken on 2015-09-21 amd64 snapshot

xed by this commit - if you saved the > previous kernel before updating, you might be able to boot with that > instead. Ah. So the bug is even more unrelated to dhclient than I was thinking. A newer snapshot (from yesterday, 2015-09-22) was on my mirror today, and booting from the bsd

Re: dhclient broken on 2015-09-21 amd64 snapshot

Q from the 12th indicating the > ifmedia options have been extended to 64 bits. I'm seeing a change to > ifconfig in the tree for this, but I don't see a corresponding change to > dhclient in the tree (looking at cvsweb). > > Did the dhclient change get overlooked? Am I doing so

dhclient broken on 2015-09-21 amd64 snapshot

I just updated my current box to yesterdays (2015-09-21) snapshot. Now it won't keep a network address. eisenhower# dhclient -d em0 DHCPREQUEST on em0 to 255.255.255.255 DHCPACK from 129.21.208.254 (d0:c2:82:f2:94:00) SIOCAIFADDR failed (129.21.208.29): File exists bound to 129.21.208.29

5.7: dhclient ignoring routers option

Hello dhclient on 5.7 won't set the client default gateway if other static routes are present (same problem exists on 5.6, at least). dhcpd server is running 5.6 stable with aprox 400 workstations and appliances/printers with mixed OSs and versions all working fine. At least both -windows

Re: 5.7: dhclient ignoring routers option (SOLVED?)

According to this: http://undeadly.org/cgi?action=articlesid=20140204080515mode=expanded This is expected behaviour as: Note that classless-static-routes overrides the router option, and that a default route must always be specified! There's no such warning in the man pages for dhclient

dhclient lease declarations broken in current snapshots

; rebind 4 2020/12/31 23:59:59 UTC; expire 4 2020/12/31 23:59:59 UTC; } root@poseidon:[~] dhclient iwn0 /etc/dhclient.conf line 24: wrong interface name. interface trunk0 ^ Segmentation fault Commenting out the lease section, all works as expected. Am I missing something

Re: thinkpad wifi/dhclient issue

the last part of this saga is, that i have moved to a new place, and the issue went away. so it seems it was router related. just another strange story from the home router front. -f -- i have nothing to say, but i can say it loudly.

Re: thinkpad wifi/dhclient issue

frantisek holop, 25 Sep 2014 17:28: for everybody out there who likes a good mystery, the 900 ping issue has happened mid-day as well for the first time. it is the equivalent of yanking the ethernet cable. so it is not an exclusively resume connected, but resume (and startup) is a way to

Re: thinkpad wifi/dhclient issue

when dhclient went to grab a new lease, it started spinning and had to be killed. so i made a debug version and hope to gdb attach to it. perhaps it is not a timeout, because network activity must be present, if i dont start pinging, connections never come back. so perhaps it is filling up some

thinkpad wifi/dhclient issue

the lease, connections do not work. if i rerun dhclient, i get the lease again, and still no connections. but the strange thing is, that some ~900 pings later (~15 minutes), dhclient kicks in life again, gets another lease, and voila, i have connections. the 2 dhclient outputs look the same

Re: Multiple, simultaneous interfaces using dhclient

It sounds like that your default inet route is overwritten after dhclient on vlan1 is issued. Did you have a look at the route table before and after each call of dhclient? On 13 Jul 2014, at 02:49, Rogier Krieger rkrie...@gmail.com wrote: Dear list, as my ISP is migrating to a new

Re: Multiple, simultaneous interfaces using dhclient

On Sun, Jul 13, 2014 at 10:11 AM, Björn Ketelaars bjorn.ketela...@hydroxide.nl wrote: It sounds like that your default inet route is overwritten after dhclient on vlan1 is issued. That's not something I'd expect, given that the dhclient instances should be in separate routing domains

Multiple, simultaneous interfaces using dhclient

won't return until I manually re-issue dhclient vlan0. Upon lease renewal, the same occurs, lest I kill the dhclient instance for vlan1. I wonder if I'm doing something silly. Is the having two simultaneous dhclient instances a supported setup? The second instance is for an IPTV set-top-box (STB

Re: dhclient question

kwesterb...@gmail.com (Kenneth Westerback), 2014.06.23 (Mon) 18:53 (CEST): On 23 June 2014 06:24, Avi Cohen av...@rad.com 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

Re: dhclient question

/ports/sysutils/entr, http://entrproject.org/) to monitor the file(s). FWIW, I'm doing this to monitor nameserver changes, here's an example. Note that it relies on support that was added to dhclient post-5.5. (entr is from packages; it's a nice simple kqueue watcher, so it works by a trigger when

dhclient question

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 appreciate if you can answer 1

Re: dhclient question

On 23 June 2014 06:24, Avi Cohen av...@rad.com 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

  1   2   3   4   >