On 2023-03-10 01:51, David Wright wrote:
On Tue 07 Mar 2023 at 17:53:10 (+0100), daven...@tuxfamily.org wrote:
So I'm clearly being lazy this time. I'd rather find a solution which
is relatively "easy and fast" to implement, than work for free
chattr -i ?
Scripted of course.
Yeah,, I'm us
On Tue 07 Mar 2023 at 17:53:10 (+0100), daven...@tuxfamily.org wrote:
>
> So I'm clearly being lazy this time. I'd rather find a solution which
> is relatively "easy and fast" to implement, than work for free
chattr -i ?
Scripted of course.
Cheers,
David.
oodall wrote:
> > > > > On Fri, 3 Mar 2023, Max Nikulin wrote:
> > > > > >
> > > > > > dhclient running for enp2s0f0 should detect that VPN is
> > > > > > active and to avoid overwriting DNS settings that direct
> > >
On 2023-03-07 16:20, Max Nikulin wrote:
On 06/03/2023 19:17, davenull wrote:
On 2023-03-03 06:22, Max Nikulin wrote:
Perhaps the opposite. dhclient running for enp2s0f0 should detect
that
VPN is active and to avoid overwriting DNS settings that direct
requests to tun0.
Yes, indeed. I want
On 2023-03-07 05:01, David Wright wrote:
On Mon 06 Mar 2023 at 13:34:52 (+0100), daven...@tuxfamily.org wrote:
On 2023-03-03 16:00, Max Nikulin wrote:
> On 03/03/2023 13:29, Tim Woodall wrote:
> > On Fri, 3 Mar 2023, Max Nikulin wrote:
> > >
> > > dhclient running
;t anything aout cisco stuff. I'm more
familiar with openVPN
> >
> > Presumably you can do something here to renew dhcp leases or restore
> > resolv.conf.
>
> Perhaps the opposite. dhclient running for enp2s0f0 should detect that
> VPN is active and to avoid overwriting
On 06/03/2023 19:17, davenull wrote:
On 2023-03-03 06:22, Max Nikulin wrote:
Perhaps the opposite. dhclient running for enp2s0f0 should detect that
VPN is active and to avoid overwriting DNS settings that direct
requests to tun0.
Yes, indeed. I want dhclient to NOT overwrite /etc/resolv.conf
On Mon 06 Mar 2023 at 13:34:52 (+0100), daven...@tuxfamily.org wrote:
> On 2023-03-03 16:00, Max Nikulin wrote:
> > On 03/03/2023 13:29, Tim Woodall wrote:
> > > On Fri, 3 Mar 2023, Max Nikulin wrote:
> > > >
> > > > dhclient running for enp2s0f0 shoul
7;t anythig aout cisco stuff. I'm more
> familiar with openVPN
>
> > >
> > > Presumably you can do something here to renew dhcp leases or restore
> > > resolv.conf.
> >
> > Perhaps the opposite. dhclient running for enp2s0f0 should detect that
&g
On 2023-03-03 16:00, Max Nikulin wrote:
On 03/03/2023 13:29, Tim Woodall wrote:
On Fri, 3 Mar 2023, Max Nikulin wrote:
dhclient running for enp2s0f0 should detect that VPN is active and to
avoid overwriting DNS settings that direct requests to tun0.
The hook can create and delete a file
VPN, which I don't have access to, I can't do
anything which requires server-side access.
Plus, it's a Cisco VPN. I don't anythig aout cisco stuff. I'm more
familiar with openVPN
Presumably you can do something here to renew dhcp leases or restore
resolv.conf.
Per
n
> > > the problem happens again
> > > It seems that dhclient does it requests trying different interfaces
> > > EXCEPT tun0 (see syslog below)
> > >
> > > I looked into /etc/dhcp/dhclient.conf, which mostly commented. In the
> > > non-commented
David Wright writes:
[...]
>
> This is the job that packages like openresolv are designed
> to do. BTW if you look up that package in apt's lists, note
> that this is a case where you need man's section number, because
> man 8 resolvconf without the 8 will give you a systemd page.
+1
I have c
Hello
On 2023-03-03 05:21, David Wright wrote:
On Thu 02 Mar 2023 at 11:44:17 (+0100), daven...@tuxfamily.org wrote:
I finally had the time to dig into the logs from two days ago, when
the problem happens again
It seems that dhclient does it requests trying different interfaces
EXCEPT tun0
On Fri 03 Mar 2023 at 22:00:37 (+0700), Max Nikulin wrote:
> On 03/03/2023 13:29, Tim Woodall wrote:
> > On Fri, 3 Mar 2023, Max Nikulin wrote:
> > >
> > > dhclient running for enp2s0f0 should detect that VPN is active
> > > and to avoid overwriting DNS setting
On 03/03/2023 13:29, Tim Woodall wrote:
On Fri, 3 Mar 2023, Max Nikulin wrote:
dhclient running for enp2s0f0 should detect that
VPN is active and to avoid overwriting DNS settings that direct
requests to tun0.
The hook can create and delete a file like rhis:
tim@dirac:/etc/dhcp (none
renew dhcp leases or restore
resolv.conf.
Perhaps the opposite. dhclient running for enp2s0f0 should detect that VPN is
active and to avoid overwriting DNS settings that direct requests to tun0.
The hook can create and delete a file like rhis:
tim@dirac:/etc/dhcp (none)$ cat dhclient-enter
.
Perhaps the opposite. dhclient running for enp2s0f0 should detect that
VPN is active and to avoid overwriting DNS settings that direct requests
to tun0.
On Thu 02 Mar 2023 at 11:44:17 (+0100), daven...@tuxfamily.org wrote:
>
> I finally had the time to dig into the logs from two days ago, when
> the problem happens again
> It seems that dhclient does it requests trying different interfaces
> EXCEPT tun0 (see syslog below)
>
&g
David.
I?finally had the time to dig into the logs from two days ago, when the
problem happens again
It seems that dhclient does it requests trying different interfaces EXCEPT
tun0 (see syslog below)
New to this thread, so might be totally off-piste but openvpn has hooks
to run scripts like
m two days ago, when the
problem happens again
It seems that dhclient does it requests trying different interfaces
EXCEPT tun0 (see syslog below)
I looked into /etc/dhcp/dhclient.conf, which mostly commented. In the
non-commented part shown below
I don't see anything related to which inte
Hi.
On Wed, Dec 15, 2021 at 04:37:19PM +0100, Tuxo wrote:
> Can I configure dhclient on my router to discard lease offers from a certain
> subnet? I could also try to match the lease time, the 192.168.100/24 lease
> time
> is only several seconds (!!) short, the real one wil
Hi list
My router and my docsys modem power on at the same time. the modem is
handing out dhcp offers of 192.168.100/24 . I assume they are meant for
internal set up purposes and dhclient on my router should not catch or
respond to them. Only the final offer after modem bootup has completed
Started behaving on its own. I installed gateway host on monday, on
thursday the gateway was correct on client. I did not find any mention of
the old gateway address, but maybe it had gone away by the time I checked.
This may be because the new gateway host was Debian desktop, I just removed
the de
Tapio Lehtonen writes:
> This is tail from /var/lib/dhcp/dhclient.leases
> lease {
> interface "eth0";
> fixed-address 192.168.250.41;
> option subnet-mask 255.255.255.0;
> option routers 192.168.250.6;
> option dhcp-lease-time 3600;
> option dhcp-message-type 5;
> option domain-nam
On Mi, 06 ian 21, 15:41:27, Tapio Lehtonen wrote:
> Old gateway host broke down, so I made a new one. One host now does get
> from DHCP server the new gateway IP -address, but continues to use the old.
> I can fix it temporarily doing
>
> dhclient -r ; dhclient
>
> but aft
Old gateway host broke down, so I made a new one. One host now does get
from DHCP server the new gateway IP -address, but continues to use the old.
I can fix it temporarily doing
dhclient -r ; dhclient
but after boot it again uses the old gateway address. Another host also
running Debian 9
Greg Wooledge wrote:
> On Wed, Aug 26, 2020 at 10:56:30AM +0700, Victor Sudakov wrote:
> > I've made some changes to /etc/dhcp/dhclient.conf, now I need to make
> > dhclient reread it (and apply the changes to /etc/resolv.conf).
>
> There is nothing you can put
On Wed, Aug 26, 2020 at 10:56:30AM +0700, Victor Sudakov wrote:
> I've made some changes to /etc/dhcp/dhclient.conf, now I need to make
> dhclient reread it (and apply the changes to /etc/resolv.conf).
There is nothing you can put in dhclient.conf that will successfully
prevent dh
Reco wrote:
>
> On Wed, Aug 26, 2020 at 10:56:30AM +0700, Victor Sudakov wrote:
> > There seems to be no dhclient service in systemd, and I don't find
> > any info about signalling dhclient with "kill -HUP" etc.
>
> There is no need for "dhclient&q
Hi.
On Wed, Aug 26, 2020 at 10:56:30AM +0700, Victor Sudakov wrote:
> There seems to be no dhclient service in systemd, and I don't find
> any info about signalling dhclient with "kill -HUP" etc.
There is no need for "dhclient" service in systemd, as there&
Claudio Kuenzler wrote:
> On Wed, Aug 26, 2020 at 5:56 AM Victor Sudakov wrote:
>
> > Dear Colleagues,
> >
> > I've made some changes to /etc/dhcp/dhclient.conf, now I need to make
> > dhclient reread it (and apply the changes to /etc/resolv.conf).
> >
On Wed, Aug 26, 2020 at 5:56 AM Victor Sudakov wrote:
> Dear Colleagues,
>
> I've made some changes to /etc/dhcp/dhclient.conf, now I need to make
> dhclient reread it (and apply the changes to /etc/resolv.conf).
>
> There seems to be no dhclient service in systemd, and
Dear Colleagues,
I've made some changes to /etc/dhcp/dhclient.conf, now I need to make
dhclient reread it (and apply the changes to /etc/resolv.conf).
There seems to be no dhclient service in systemd, and I don't find
any info about signalling dhclient with "kill -HUP" et
Am Freitag, 17. Januar 2020, 11:12:07 CET schrieb Curt:
> On 2020-01-16, Rainer Dorsch wrote:
> > Am Mittwoch, 15. Januar 2020, 00:09:16 CET schrieb Pascal Hambourg:
> >> Le 14/01/2020 à 21:14, Rainer Dorsch a écrit :
> >> > prepend dhcp6.name-servers 2001:4860:4860::, 2001:4860:4860::8844;
>
On 2020-01-16, Rainer Dorsch wrote:
> Am Mittwoch, 15. Januar 2020, 00:09:16 CET schrieb Pascal Hambourg:
>> Le 14/01/2020 à 21:14, Rainer Dorsch a écrit :
>> > prepend dhcp6.name-servers 2001:4860:4860::, 2001:4860:4860::8844;
>> >
>> > avoids the error message, but has no visible effect I c
dhcp 1
request_prefix 1
I could not find a way to overwrite the DNS server for rdnssd, does anybody
know if that is possible?
According to the interfaces man page, dhclient should be responsible with the
dhcp method
iface eth0.1 inet6 dhcp
request_prefix 1
ifup shows the nameserver
On Tue, Jan 14, 2020 at 01:18:01PM -0500, Greg Wooledge wrote:
> On Tue, Jan 14, 2020 at 12:12:03PM -0500, Bob Weber wrote:
> > Just edit the file /etc/resolv.conf and make it immutable (chattr +i
[...]
> That is one of the options given on the wiki page.
>
> https://wiki.debian.org/resolv.conf
Le 14/01/2020 à 21:14, Rainer Dorsch a écrit :
prepend dhcp6.name-servers 2001:4860:4860::, 2001:4860:4860::8844;
avoids the error message, but has no visible effect I can see. The IPv6 DNS
servers still do not show in resolv.conf.
You may receive IPv6 DNS information from IPv6 Router Adv
h.
>
> Thank you for all the good replies to this thread.
>
> prepend dhcp6.name-servers 2001:4860:4860::, 2001:4860:4860::8844;
>
> avoids the error message, but has no visible effect I can see. The IPv6 DNS
> servers still do not show in resolv.conf.
>
> Unfortun
as no visible effect I can see. The IPv6 DNS
servers still do not show in resolv.conf.
Unfortunately,
root@home:~# cat /etc/dhcp/dhclient-enter-hooks.d/leave_my_resolv_conf_alone
make_resolv_conf() { :; }
root@home:~# ls -l /etc/dhcp/dhclient-enter-hooks.d/leave_my_resolv_conf_alone
-rwxr-xr-x 1
On Tue, Jan 14, 2020 at 12:12:03PM -0500, Bob Weber wrote:
> Just edit the file /etc/resolv.conf and make it immutable (chattr +i
> /etc/resolv.conf). At least you will know what is in the file and that it
> can't be changed (mistakes and all). I use this to keep chrome from
> changing the googl
Meanwhile, there are a few different ways to keep your resolv.conf
file untouched, rather than relying on isc-dhcp-client to continually
rewrite it in the form you want. The wiki page describes some of
those ways.
Personally, I do not understand the appeal of the "put lines in
configuration fi
On Tue, Jan 14, 2020 at 03:00:50PM +, Curt wrote:
> On 2020-01-14, Greg Wooledge wrote:
> > On Tue, Jan 14, 2020 at 09:37:05AM +0100, Rainer Dorsch wrote:
> >> I tried to switch to other servers, e.g. Google, but this does not work,
> >> since
> >>
> >> /etc/resolv.conf gets overwritten wit
On 2020-01-14, Greg Wooledge wrote:
> On Tue, Jan 14, 2020 at 09:37:05AM +0100, Rainer Dorsch wrote:
>> I tried to switch to other servers, e.g. Google, but this does not work,
>> since
>>
>> /etc/resolv.conf gets overwritten with a high frequency
>
> https://wiki.debian.org/resolv.conf
Actual
On 2020-01-14, Rainer Dorsch wrote:
>
> https://developers.google.com/speed/public-dns/docs/using
>
> and add to /etc/dhcp/dhclient.conf
>
> prepend domain-name-servers 2001:4860:4860::, 2001:4860:4860::8844;
>
> dhclient becomes unhappy (during an ifup eth0.1)
>
On Tue, Jan 14, 2020 at 09:37:05AM +0100, Rainer Dorsch wrote:
> I tried to switch to other servers, e.g. Google, but this does not work, since
>
> /etc/resolv.conf gets overwritten with a high frequency
https://wiki.debian.org/resolv.conf
>
>
>
> prependdomain-name-servers 2001:4860:4860::, 2001:4860:4860::8844;
>
> dhclient becomes unhappy (during an ifup eth0.1)
>
>
>
> /etc/dhcp/dhclient.conf line 26: semicolon expected.
>
> prepend domain-name-servers 2001:
>
> ^
>
> /e
/dhclient.conf does not accept ipv6 addresses like, since if I use
the instructions from
https://developers.google.com/speed/public-dns/docs/using
and add to /etc/dhcp/dhclient.conf
prepend domain-name-servers 2001:4860:4860::, 2001:4860:4860::8844;
dhclient becomes unhappy (during an ifup
Hi,
I configure a dhcp interface using systemd-networkd.
When a new lease is acquired I need to reload some services.
How can I do that?
In other words: I'm looking for a systemd equivalent to dhclient exit
hooks script.
I'm on Debian 9.
--
John Doe
Anybody seen this issue where dhclient does not send the user-class option in
it's solicit message. I have a minimal dhclient.conf file and when I start
dhclient I can see that option 15 isn't sent:
root@blldhcptest01:~# cat /etc/dhcp/dhclient.conf
senduser-clas
On Monday, 10 July 2017 11:28:12 CEST Franz Angeli wrote:
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
I had a similar issue due to a missing firmware. I think it was on a broadcom
card.
Please check the kernel logs (journalctl -k
On Mon, Jul 10, 2017 at 12:55:53PM +0200, Dejan Jocic wrote:
> On 10-07-17, Franz Angeli wrote:
> > Hi,
> >
> > i have a problem with dhclient:
> >
> > for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> > BCM5719 Gigabit
On Tue 11 Jul 2017 at 09:24:01 +0200, Dejan Jocic wrote:
> You are doing lspci as root, so with A10 it does not get to the kernel
> driver and module part. Can you see what is there by using A15 instead?
If the driver turns out to be tg3 then firmware from nonfree is required.
--
Brian.
nothing usefull...
one strange thing is that during debian installation all works fine
because i use net-install with a iso.
2017-07-11 9:27 GMT+02:00 Johann Spies :
> On 11 July 2017 at 08:29, Franz Angeli wrote:
>
>> i tried every other interface butt it's the same
>>
>> i tried also to dis
On 11 July 2017 at 08:29, Franz Angeli wrote:
> i tried every other interface butt it's the same
>
> i tried also to disable interface renaming but doesn't work.
What information do you get from /var/log/messages, /var/log/syslog
and dmesg about your interfaces?
Regards
Johann
On 11-07-17, Franz Angeli wrote:
> Hi,
>
> i have a problem with dhclient:
>
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
>
> root@:~# dhclient eno52 -v
> Internet Systems Consortium DHCP Cl
Hi,
i tried every other interface butt it's the same
i tried also to disable interface renaming but doesn't work.
2017-07-11 8:02 GMT+02:00 Johann Spies :
> On 11 July 2017 at 07:48, Franz Angeli wrote:
>> Hi,
>>
>> i have a problem with dhclient:
>>
>
On 11 July 2017 at 07:48, Franz Angeli wrote:
> Hi,
>
> i have a problem with dhclient:
>
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
>
> root@:~# dhclient eno52 -v
> Internet Systems C
Hi,
i have a problem with dhclient:
for example interface name eno52 (tg3, Broadcom Limited NetXtreme
BCM5719 Gigabit Ethernet PCIe (rev 01) :
root@:~# dhclient eno52 -v
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved
On 10-07-17, Franz Angeli wrote:
> Hi,
>
> i have a problem with dhclient:
>
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
>
> root@:~# dhclient eno52 -v
> Internet Systems Consortium DHCP Cl
Hi,
i have a problem with dhclient:
for example interface name eno52 (tg3, Broadcom Limited NetXtreme
BCM5719 Gigabit Ethernet PCIe (rev 01) :
root@:~# dhclient eno52 -v
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved
2017-03-08 15:24 GMT+08:00 Clark Wang :
> See following output from my system (Debian 8.6):
>
> root@debian:~# cat /etc/debian_version
> 8.6
> root@debian:~# pgrep -af dhc
> 506 dhclient -v -pf /run/dhclient.eth1.pid -lf
> /var/lib/dhcp/dhclient.eth1.leases et
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Mar 10, 2017 at 08:31:10AM -0500, Greg Wooledge wrote:
> On Fri, Mar 10, 2017 at 12:34:34PM +0100, to...@tuxteam.de wrote:
> > Also, more "w" in the ps:
> >
> > ps auxf | less
>
> >From ps(1):
>
>w Wide output. Use this o
On Fri, Mar 10, 2017 at 12:34:34PM +0100, to...@tuxteam.de wrote:
> Also, more "w" in the ps:
>
> ps auxf | less
>From ps(1):
w Wide output. Use this option twice for unlimited width.
You never need more than two.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Mar 10, 2017 at 01:23:36PM +, Jonathan Dowland wrote:
> On Fri, Mar 10, 2017 at 06:58:30PM +0800, Clark Wang wrote:
> > > There are 2 `dhclient` processes running for `eth0` (IPv4). Rebooting does
> >
On Fri, Mar 10, 2017 at 06:58:30PM +0800, Clark Wang wrote:
> > There are 2 `dhclient` processes running for `eth0` (IPv4). Rebooting does
> > not help for me.
> >
>
> Anyone else has the same problem?
I think I have sometimes seen this, but I do not know what prov
re there) and/or by having a look at /proc//fd.
Also, more "w" in the ps:
ps auxf | less
then search for dhclient. wider command line, parent-child relationships as
additional hints.
Good luck
- -- tomás
-BEGIN PGP SIGNATURE-
Version: G
2017-03-08 15:24 GMT+08:00 Clark Wang :
> See following output from my system (Debian 8.6):
>
> root@debian:~# cat /etc/debian_version
> 8.6
> root@debian:~# pgrep -af dhc
> 506 dhclient -v -pf /run/dhclient.eth1.pid -lf
> /var/lib/dhcp/dhclient.eth1.leases et
On Thu, 9 Mar 2017 13:51:40 +, Jonathan Dowland wrote:
> Edit /etc/network/interfaces and comment out the lines corresponding to
> your network interface, e.g. 'auto eth0', 'iface eth0 inet dhcp', etc.
Thank you, I did this work at last night and this morning when I turn on
my computer, the p
On Thu, Mar 09, 2017 at 09:26:40AM -0500, Henning Follmann wrote:
> Any interface defined in the /etc/network/interfaces is by default ignored
> by the NetwokManager.
> So you have to make the decision how to manage your interface. By removing
> it from that file, NetworkManager takes over control
install
> > on system, only `standard utilities', after finish the installation, I
> > did use `aptitude' to install xorg, gnome-shell, gnome-session and some
> > parts of GNOME without recomended packages.
> >
> > Now anytime on system booting, dhclient au
ation, I
> did use `aptitude' to install xorg, gnome-shell, gnome-session and some
> parts of GNOME without recomended packages.
>
> Now anytime on system booting, dhclient automatically connects the
> interface to network and I just know to use `ifdown' by root user to
&
lation, I did use `aptitude' to install xorg, gnome-shell,
> gnome-session and some parts of GNOME without recomended packages.
>
> Now anytime on system booting, dhclient automatically connects the
> interface to network and I just know to use `ifdown' by root user to
> turn
See following output from my system (Debian 8.6):
root@debian:~# cat /etc/debian_version
8.6
root@debian:~# pgrep -af dhc
506 dhclient -v -pf /run/dhclient.eth1.pid -lf
/var/lib/dhcp/dhclient.eth1.leases eth1
447 dhclient -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp
in my case 2 seconds were not enough - had to increase to 5 on one
machine and to 10 on another (slower) one.
is this issue fixed in stretch/sid?
On 24/02/16 22:13, Reco wrote:
> ...
> pkill -9 -f dhclient
> ifup --force eth0
> sleep 1800
> reboot
>
> If all goes well you would be able to re-attach to a existing screen
> session, and cancel the reboot.
> If anything goes wrong - you'll have your host alive a
Hi.
On Wed, Feb 24, 2016 at 08:54:50PM +1300, Richard Hector wrote:
> Anyone know if/how I can restart dhclient without stopping the network?
>
> It's the only process left holding open the old libc after the
> upgrade, and I'd rather avoid restarting the network (
Anyone know if/how I can restart dhclient without stopping the network?
It's the only process left holding open the old libc after the
upgrade, and I'd rather avoid restarting the network (or rebooting),
since I'm working remotely.
This is on a wheezy box. It shouldn't be usi
Hi,
I've had some weird problems with central hostname management. After a
week of pulling out my hair, I can say definitely that I've found a bug.
I'm fiddling with two different Debian sandbox PC's. They don't have any
'hardcoded' hostname definition, only 'localhost' in /etc/hostname and
'loca
* Stefan Pietsch [2015-04-29 10:50]:
> Dear list,
>
> a fresh installation of Debian jessie does not start dhclient for IPv6
> at boot.
>
> This is the interfaces file:
>
> ~
>
> source /etc/network/interfaces.d/*
>
> auto lo
> iface lo inet loopbac
Dear list,
a fresh installation of Debian jessie does not start dhclient for IPv6
at boot.
This is the interfaces file:
~
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
iface eth0 inet6 dhcp
~
Doing a manual "ifup eth0"
On Jo, 03 iul 14, 02:52:04, Bob Proulx wrote:
>
> That is the same as the Raspberry Pi. On the Pi they use a clever
> hack. At shutdown a file holds the timestamp of the time when the
> system shutdown. On boot the timestamp is used to set the current
> time for the system. That way the time d
78.88 and the other way round.
Hmm... I don't know what would cause that.
> Here are the logs from the client side:
>
> root@bokocube:/var/log# zgrep "dhclient" syslog.5.gz syslog.4.gz
> syslog.5.gz:Jan 1 01:00:07 bokocube dhclient: Listening on
> LPF/eth0/d0:
re the same IP address even though it
> had the same ethernet hardware address.
That is interesting information. The manpage of dhclient contains some
references on that.
>
> Is it possible that your client is somehow producing a DHCP request
> but using different client parameter
Rainer Dorsch wrote:
> my fritz.box is a DSL router from AVM, which unfortunately does not give me
> access to syslog.
Oh. I didn't realize that. The way you talked about it I thought it
was another Debian system.
> What I noticed is that 192.168.178.87 shows up without MAC address
> in the li
On Sun, 22 Jun 2014 23:16:32 +0200
Rainer Dorsch wrote:
> I think I will try first to get support from AVM on that topic. If
> that is not successful, I will look in more detail into the
> tcpdumps (although since I have to take that on the client side,
> that might be difficult during the startu
comes up with one IP address 192.168.178.87 via
> > dhclient, then after one day it gets eventually a different address
>
> > 192.168.178.88 from my fritz.box, which runs the dhcp server:
> On your fritz.box what does the dhcpd log to the syslog?
>
> grep dhcpd /var/log/
Rainer Dorsch wrote:
> Hello,
>
> I have a system which comes up with one IP address 192.168.178.87 via
> dhclient, then after one day it gets eventually a different address
> 192.168.178.88 from my fritz.box, which runs the dhcp server:
>
> Any hint what is going on here
Rainer Dorsch wrote:
> I have a system which comes up with one IP address 192.168.178.87 via
> dhclient, then after one day it gets eventually a different address
> 192.168.178.88 from my fritz.box, which runs the dhcp server:
On your fritz.box what does the dhcpd log to the syslog
On Fri, 20 Jun 2014 20:07:19 +0200
Rainer Dorsch wrote:
On the DHCP svr, what is in
/var/lib/dhcp/dhclient.leases & dhcpd.leases
before the lease renewing and after (the bad one)?
--
dylan : what do you think about abortion?
spidersnow : leave the choice to the kid.
signature.asc
Description:
Hello,
I have a system which comes up with one IP address 192.168.178.87 via
dhclient, then after one day it gets eventually a different address
192.168.178.88 from my fritz.box, which runs the dhcp server:
Jun 19 16:54:05 bokocube NetworkManager[338]: (eth0): DHCPv4 state
changed bound
Hi,
thanks for your quick and helpful reply!
On Thu, Oct 17, 2013 at 11:09 PM, Bob Proulx wrote:
> Steffen Dettmer wrote:
> Your indention is terrible!
Sorry, I'll improve.
>> I think I have to pass the option "-nw" to dhclient, but how do I do
>> that correc
Gregory Nowak wrote:
> Bob Proulx wrote:
> > Steffen Dettmer wrote:
> > > When booting and one of the DHCP interfaces has no cable attached,
> > > booting is delayed about around 60 seconds (seems to be value of
> > > dhclient.conf:timeout).
> >
> > Why isn't your DHCP server responding? Your dhc
On Thu, Oct 17, 2013 at 03:09:45PM -0600, Bob Proulx wrote:
> Steffen Dettmer wrote:
> > When booting and one of the DHCP interfaces has no cable attached,
> > booting is delayed about around 60 seconds (seems to be value of
> > dhclient.conf:timeout).
>
> Why isn't your DHCP server responding? Y
e the problem. Debug your dhcp problems first.
> I think I have to pass the option "-nw" to dhclient, but how do I do
> that correctly?
If you want dhclient not to wait then change the "auto" to
"allow-hotplug". Using "auto" means bring the int
option "-nw" to
dhclient, but how do I do that correctly? Apparently the dhclient
invocation call is hardcoded in ifupdown, but surely I didn't
understand the C source code (which is generated by a generated source
code generator).
I noticed that DHCP leases are kept as long as the
taching a machine with a new MAC. And, I've been able to
switch between two other machines, both with different MAC addresses. It's just
this third machine that's given me problems.
What I'm really stuck on right now is why does the dhclient log show that it's
sending DHCPDI
On Mon, 2013-08-26 at 06:46 -0400, Sean Alexandre wrote:
> On Mon, Aug 26, 2013 at 02:54:27PM +0530, Arun Khan wrote:
> > On Mon, Aug 26, 2013 at 2:01 PM, Sean Alexandre wrote:
> > > I have a machine that's not acquiring a DHCP lease from my ISP. I can see
> > >
On Mon, Aug 26, 2013 at 02:54:27PM +0530, Arun Khan wrote:
> On Mon, Aug 26, 2013 at 2:01 PM, Sean Alexandre wrote:
> > I have a machine that's not acquiring a DHCP lease from my ISP. I can see
> > that
> > dhclient is sending DHCPDISCOVER messages. My system log ha
1 - 100 of 419 matches
Mail list logo
