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
lient gives me following error:
>>
>> em1: /etc/dhclient.conf line 17: expecting IPv4 address.
>> em1: prepend domain-name-servers "::1"
>> em1: ^
>> dhclient.conf ist plain simple:
>> ~ $ grep -v "#" /etc/dhclien
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 I
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
On 07 May 2016, Stuart Henderson wrote:
> On 2016-05-06, Mark Carroll wrote:
(snip)
>> pf ... because it otherwise doesn't realize that 'self'
>> includes the address eventually assigned by PPP.
>
> Use "(self)" not "self".
Interesting! Thank you: I'd previously missed this part of the
pf.conf(5
On 2016-05-06, Mark Carroll wrote:
> On 06 May 2016, Duncan Patton a. Campbell wrote:
>
>> Is there any similar tag to access the addess assigned by dhcp?
>> What other mechanisms exist to update dynamic dns assignments?
>
> Could ifstated(8) help here? I've separately wondered if I ought to be
>
On Fri, May 06, 2016 at 04:35:47AM -0600, Duncan Patton a Campbell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> Back when the script tag was removed from dhclient.conf the
> functionality to do external commands was ostensibly moved
> into hostname.if
On Fri, May 06, 2016 at 06:21:00AM -0600, Duncan Patton a Campbell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Fri, 06 May 2016 12:06:58 +0100
> Mark Carroll wrote:
>
> > On 06 May 2016, Duncan Patton a. Campbell wrote:
> >
> > > Is there any similar tag to access the adde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 06 May 2016 12:06:58 +0100
Mark Carroll wrote:
> On 06 May 2016, Duncan Patton a. Campbell wrote:
>
> > Is there any similar tag to access the addess assigned by dhcp?
> > What other mechanisms exist to update dynamic dns assignments?
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 6 May 2016 11:56:31 +0100
Raf Czlonka wrote:
> On Fri, May 06, 2016 at 11:35:47AM BST, Duncan Patton a Campbell
> wrote:
> >
> > Back when the script tag was removed from dhclient.conf the
> > functionality to
On 06 May 2016, Duncan Patton a. Campbell wrote:
> Is there any similar tag to access the addess assigned by dhcp?
> What other mechanisms exist to update dynamic dns assignments?
Could ifstated(8) help here? I've separately wondered if I ought to be
using it to kick pf because it otherwise doesn
On Fri, May 06, 2016 at 11:35:47AM BST, Duncan Patton a Campbell wrote:
>
> Back when the script tag was removed from dhclient.conf the
> functionality to do external commands was ostensibly moved
> into hostname.if via the
>
> !command mechanism.
>
> in man hostname
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Back when the script tag was removed from dhclient.conf the
functionality to do external commands was ostensibly moved
into hostname.if via the
!command mechanism.
in man hostname.if it says
"It is worth noting that ``\$if'
had in FreeBSD was this entry in /etc/dhclient.conf:
>
> alias {
> interface "vr0";
> fixed-address 192.168.1.200;
> option subnet-mask 255.255.255.0;
> }
>
> This seems to be silently ignored on OpenBSD 5.7 and the dhclient.conf
>
> > ...I can live without the alias address, it would have been
> > a convinient way to access the ADSL modem on the WAN side from inside
> > the LAN network.
>
> Perhaps you could add an ifconfig(8) command to rc.local(8) to set
> the alias.
As previously said any ifconfig aliasing command r
On Mon, Jul 27, 2015 at 01:34:09PM +0300, Kimmo Paasiala wrote:
> ...I can live without the alias address, it would have been
> a convinient way to access the ADSL modem on the WAN side from inside
> the LAN network.
Perhaps you could add an ifconfig(8) command to rc.local(8) to set
the alias.
Or
. I want to have a static
>>>>> alias address on an interface that is otherwise configured with DHCP.
>>>>> What I had in FreeBSD was this entry in /etc/dhclient.conf:
>>>>>
>>>>> alias {
>>>>> interface "vr0";
>
came across a minor problem. I want to have a static
alias address on an interface that is otherwise configured with DHCP.
What I had in FreeBSD was this entry in /etc/dhclient.conf:
alias {
interface "vr0";
fixed-address 192.168.1.200;
option subnet-mas
To: misc@openbsd.org
Subject: dhclient.conf alias declarations?
Hello,
I'm in the process of migrating my router/firewall system from FreeBSD to
OpenBSD and I came across a minor problem. I want to have a static alias
address on an interface that is otherwise configured with DHCP.
What I h
m FreeBSD
>>> to OpenBSD and I came across a minor problem. I want to have a static
>>> alias address on an interface that is otherwise configured with DHCP.
>>> What I had in FreeBSD was this entry in /etc/dhclient.conf:
>>>
>>> alias {
>>>
>> alias address on an interface that is otherwise configured with DHCP.
>> What I had in FreeBSD was this entry in /etc/dhclient.conf:
>>
>> alias {
>> interface "vr0";
>> fixed-address 192.168.1.200;
>> option subn
this entry in /etc/dhclient.conf:
alias {
interface "vr0";
fixed-address 192.168.1.200;
option subnet-mask 255.255.255.0;
}
This seems to be silently ignored on OpenBSD 5.7 and the dhclient.conf
manual page makes no mention of alias declarations. How am I supposed
Hello,
I'm in the process of migrating my router/firewall system from FreeBSD
to OpenBSD and I came across a minor problem. I want to have a static
alias address on an interface that is otherwise configured with DHCP.
What I had in FreeBSD was this entry in /etc/dhclient.conf:
On Thu, Jul 09, 2015 at 04:36:33PM -0700, Seth wrote:
> I'm trying to use the following statement in /etc/dhclient.conf
>
> supersede domain-name-servers [127.0.0.1]:40;
don't wrap the ip address in square [] brackets.
should clear it up
--ryan
>
> But when the mach
> On Thu, Jul 09, 2015 at 10:01:01PM -0600, Theo de Raadt wrote:
> > The 4.4BSD chflags model of "security" on inodes is unmaintained, and
> > the utilitization of this is not realized OpenBSD.
> >
> > To be honest, I doubt any of us see much benefit in it, relative to
> > other features of the sy
On Thu, Jul 09, 2015 at 10:01:01PM -0600, Theo de Raadt wrote:
> The 4.4BSD chflags model of "security" on inodes is unmaintained, and
> the utilitization of this is not realized OpenBSD.
>
> To be honest, I doubt any of us see much benefit in it, relative to
> other features of the system. When
> On Thu, 09 Jul 2015 18:18:37 -0700, Edgar Pettijohn
> wrote:
>
> > # chflags schg /etc/resolv.conf
> >
> > Just keep in mind you have to go to single user mode to undo the above.
>
> That's an interesting workaround I hadn't considered. The problem is that
> this setting must be deployed v
On Thu, 09 Jul 2015 19:40:05 -0700, Philip Guenther
wrote:
Uh, so you want to _ignore_ the option from the server? Then add
ignore domain-name-servers;
to your dhclient.conf and put the desired nameserver line in your
resolv.conf.tail file.
That was the missing link, problem solved
On Thu, Jul 9, 2015 at 4:36 PM, Seth wrote:
> I'm trying to use the following statement in /etc/dhclient.conf
>
> supersede domain-name-servers [127.0.0.1]:40;
>
> But when the machine boots and the network starts it fails to apply the
> setting. The error message is:
>
On Thu, 09 Jul 2015 18:18:37 -0700, Edgar Pettijohn
wrote:
# chflags schg /etc/resolv.conf
Just keep in mind you have to go to single user mode to undo the above.
That's an interesting workaround I hadn't considered. The problem is that
this setting must be deployed via an Ansible playbo
On Thu, 09 Jul 2015 18:01:42 -0700, Ryan Freeman wrote:
don't wrap the ip address in square [] brackets.
should clear it up
The square brackets are necessary when specifying a non-standard DNS port
[1]
nameserver IPv4 address (in dot notation) or IPv6 address (in hex-and-
# chflags schg /etc/resolv.conf
Just keep in mind you have to go to single user mode to undo the above.
On 07/09/15 18:36, Seth wrote:
I'm trying to use the following statement in /etc/dhclient.conf
supersede domain-name-servers [127.0.0.1]:40;
But when the machine boots and the ne
I'm trying to use the following statement in /etc/dhclient.conf
supersede domain-name-servers [127.0.0.1]:40;
But when the machine boots and the network starts it fails to apply the
setting. The error message is:
/etc/dhclient.conf line 4: expecting decimal octet.
supersede domain
to allow dynamic dns updates
> via nsupdate from a dhcp clients where addresses
> are subject to change. I have a solution that
> will remain stable so long as the !command
> hook in hostname.if remains stable. This is
> not as good as the dhclient.conf script interface
> as
olution that
> > will remain stable so long as the !command
> > hook in hostname.if remains stable. This is
> > not as good as the dhclient.conf script interface
> > as it can't exclude calls that don't change
> > the interface, but hey...
> >
>
On 2014-09-30, sven falempin wrote:
>
> I also parse and do custom action with the lease file,
> so i forgot all concern about the absence of script hook.
> I also regurlarly monitor the lease, so i did not use
>
> http://entrproject.org/ , looks good stuff
It is. This isn't quite what it was de
On Mon, Sep 29, 2014 at 8:42 PM, Stuart Henderson wrote:
> On 2014-09-29, Duncan Patton a Campbell wrote:
>> On Mon, 29 Sep 2014 05:28:27 -0600
>> Duncan Patton a Campbell wrote:
>>
>>> /etc/dhclient.conf used to contain a
>>>
>>> script "
On 2014-09-29, Duncan Patton a Campbell wrote:
> On Mon, 29 Sep 2014 05:28:27 -0600
> Duncan Patton a Campbell wrote:
>
>> /etc/dhclient.conf used to contain a
>>
>> script "tosomfile" ;
>>
>> option that could, amongst other things, be used to
in hostname.if remains stable. This is
> not as good as the dhclient.conf script interface
> as it can't exclude calls that don't change
> the interface, but hey...
>
> # more /etc/hostname.nfe0
> dhcp
> !/usr/local/sbin/dydns.sh $if
This is executed only during b
ve a solution that
> > will remain stable so long as the !command
> > hook in hostname.if remains stable. This is
> > not as good as the dhclient.conf script interface
> > as it can't exclude calls that don't change
> > the interface, but hey...
> >
remains stable. This is
> not as good as the dhclient.conf script interface
> as it can't exclude calls that don't change
> the interface, but hey...
>
> # more /etc/hostname.nfe0
> dhcp
> !/usr/local/sbin/dydns.sh $if
>
> more /usr/local/sbin/dydns.sh
> #!/bi
My purpose here is to allow dynamic dns updates
via nsupdate from a dhcp clients where addresses
are subject to change. I have a solution that
will remain stable so long as the !command
hook in hostname.if remains stable. This is
not as good as the dhclient.conf script interface
as it can&#
On 29.09.2014 13:39, Duncan Patton a Campbell wrote:
On Mon, 29 Sep 2014 05:28:27 -0600
Duncan Patton a Campbell wrote:
/etc/dhclient.conf used to contain a
script "tosomfile" ;
option that could, amongst other things, be used to
set a dynamic assigned dns address to a named ser
On Mon, Sep 29, 2014 at 05:28:27AM -0600, Duncan Patton a Campbell wrote:
> /etc/dhclient.conf used to contain a
>
> script "tosomfile" ;
>
> option that could, amongst other things, be used to
> set a dynamic assigned dns address to a named server.
>
> This
On Mon, 29 Sep 2014 05:28:27 -0600
Duncan Patton a Campbell wrote:
> /etc/dhclient.conf used to contain a
>
> script "tosomfile" ;
>
> option that could, amongst other things, be used to
> set a dynamic assigned dns address to a named server.
>
> This funct
/etc/dhclient.conf used to contain a
script "tosomfile" ;
option that could, amongst other things, be used to
set a dynamic assigned dns address to a named server.
This functionality has been removed and I am trying to
figure out if there was some other mechanism to accomplish
this b
ility.
--
Unfortunately the dhcp server is not under my purview.
Hacking code is not in my skillset. :[
I am interested in parameters in the event of not being able to contact a
server (PROTOCOL TIMING section - timeout, etcetera).
The way I read dhclient.conf(5) is lease features are able to be specifi
) which get their ip's from dhcp.
> wi0, being wireless, is prone to lose it's connection.
> I want to change the timeout, etcetera for wi0 in dhclient.conf.
> I can't see the information in dhclient.conf(5).
>
The timeout is set by the DHCP server when it provides the IP.
t to change the timeout, etcetera for wi0 in dhclient.conf.
I can't see the information in dhclient.conf(5).
Best wishes,
David
Hi James.
Thanks for the reply.
I was thinking of timeout, retry, reboot (to minimize startup hangs),
initial-interval and link-timeout (the PROTOCOL TIMING section).
As I understand dhclient.conf(5), the man page deals with system wide
settings for these items but does not explain the per
aces (fxp0 and wi0) which get their ip's from dhcp. wi0,
> being wireless, is prone to lose it's connection.
> I want to change the timeout, etcetera for wi0 in dhclient.conf.
> I can't see the information in dhclient.conf(5).
>
> Can someone point me in the right direction?
>
> Best wishes,
> David
Hiya.
I have 2 interfaces (fxp0 and wi0) which get their ip's from dhcp. wi0,
being wireless, is prone to lose it's connection.
I want to change the timeout, etcetera for wi0 in dhclient.conf.
I can't see the information in dhclient.conf(5).
Can someone point me in the right d
On Mon, Oct 15, 2007 at 02:56:14PM +0200, Vincent GROSS wrote:
> Hi folks,
>
> I found a misleading statement in dhclient.conf.5 : the description of
> the 'script' statement is in the lease declaration section, which can
> lead someone to think the script statemen
meh, forgot the demimer ... thank you Nick.
here is the inlined patch.
$ diff -Naur dhclient.conf.5.orig dhclient.conf.5
--- dhclient.conf.5.origSun Oct 14 22:01:48 2007
+++ dhclient.conf.5 Sun Oct 14 22:00:03 2007
@@ -345,19 +345,6 @@
.Nm dhclient.conf ,
the value that the user
Hi folks,
I found a misleading statement in dhclient.conf.5 : the description of
the 'script' statement is in the lease declaration section, which can
lead someone to think the script statement is a part of the static
lease declaration.
The joined gzip'ed patch fix that,
"/etc/hostname." I found the place to put the stuff:
> /etc/dhclient.conf. Seemed to work well until I tried it on my laptop
> having two ifaces (wired and wireless).
>
> As soon as I define several alias { ... } statements in dhclient.conf,
> following dhclient
Hello misc@,
I finally got around to setup a dhcpd in my local LAN.
All hosts get their IP by dhcp, but also need an alias (as secure VPN
inside LAN) on each interface, after playing around with
"/etc/hostname." I found the place to put the stuff:
/etc/dhclient.conf. Seemed to work we
61 matches
Mail list logo
