Re: strange DHCP behaviour [SOLVED]

2018-10-25 Thread tony
On 24/10/2018 14:41, to...@tuxteam.de wrote: > On Wed, Oct 24, 2018 at 02:35:37PM +0200, tony wrote: > > [...] > >> Ew, this time it worked. I wonder why deleting the leases file was >> better than clearing it out? > > Some things you gotta delete *twice*. > > (Sigh. I guess everyone here knows

Re: strange DHCP behaviour [SOLVED]

2018-10-24 Thread Michael Stone
On Wed, Oct 24, 2018 at 02:35:37PM +0200, tony wrote: Ew, this time it worked. I wonder why deleting the leases file was better than clearing it out? Hard to say at this point, but are you sure you cleared every instance in the leases file? (Entries often appear more than once.)

Re: strange DHCP behaviour [SOLVED]

2018-10-24 Thread tomas
On Wed, Oct 24, 2018 at 02:35:37PM +0200, tony wrote: [...] > Ew, this time it worked. I wonder why deleting the leases file was > better than clearing it out? Some things you gotta delete *twice*. (Sigh. I guess everyone here knows _that_ feeling... :) Glad you found it -- t signature.asc D

Re: strange DHCP behaviour [SOLVED]

2018-10-24 Thread tony
On 24/10/2018 13:34, john doe wrote: > On 10/24/2018 1:28 PM, tony wrote: >> On 24/10/2018 08:19, Reco wrote: >>> Hi. >>> >>> On Tue, Oct 23, 2018 at 03:56:34PM +0200, Tony van der Hoff wrote: The DHCP server is another Stretch system, with the stanzas host tony-lt { hardware

Re: strange DHCP behaviour

2018-10-24 Thread john doe
On 10/24/2018 1:28 PM, tony wrote: > On 24/10/2018 08:19, Reco wrote: >> Hi. >> >> On Tue, Oct 23, 2018 at 03:56:34PM +0200, Tony van der Hoff wrote: >>> The DHCP server is another Stretch system, with the stanzas >>> host tony-lt { >>> hardware ethernet 0c:60:76:6c:e6:6f; >>> fixed-ad

Re: strange DHCP behaviour

2018-10-24 Thread tony
On 24/10/2018 08:19, Reco wrote: > Hi. > > On Tue, Oct 23, 2018 at 03:56:34PM +0200, Tony van der Hoff wrote: >> The DHCP server is another Stretch system, with the stanzas >> host tony-lt { >> hardware ethernet 0c:60:76:6c:e6:6f; >> fixed-address 192.168.1.199; >> } >> subnet

Re: strange DHCP behaviour

2018-10-24 Thread tony
On 24/10/2018 12:54, mick crane wrote: > On 2018-10-24 11:39, tony wrote: >> On 24/10/2018 12:11, mick crane wrote: >>> On 2018-10-24 09:40, tony wrote: >>> I've flushed the lease several times (The dhclient -r command mentioned above does that), and physically deleted the lease files.  N

Re: strange DHCP behaviour

2018-10-24 Thread mick crane
On 2018-10-24 11:39, tony wrote: On 24/10/2018 12:11, mick crane wrote: On 2018-10-24 09:40, tony wrote: I've flushed the lease several times (The dhclient -r command mentioned above does that), and physically deleted the lease files.  No good! Isn't that on the laptop and you need to get

Re: strange DHCP behaviour

2018-10-24 Thread tony
On 24/10/2018 12:11, mick crane wrote: > On 2018-10-24 09:40, tony wrote: > >> I've flushed the lease several times (The dhclient -r command mentioned >> above does that), and physically deleted the lease files.  No good! >> > > Isn't that on the laptop and you need to get rid of the entry on the

Re: strange DHCP behaviour

2018-10-24 Thread mick crane
On 2018-10-24 09:40, tony wrote: I've flushed the lease several times (The dhclient -r command mentioned above does that), and physically deleted the lease files. No good! Isn't that on the laptop and you need to get rid of the entry on the server ? mick -- Key ID4BFEBB31

Re: strange DHCP behaviour

2018-10-24 Thread tony
On 23/10/2018 21:57, deloptes wrote: > Tony van der Hoff wrote: > >> Any suggestions, please? > > I would put host declaration after subnet - don't think it makes difference > You're right -- it doesn't! > also check /etc/hosts for left overs and for the lease take care that your > computers up

Re: strange DHCP behaviour

2018-10-24 Thread tony
On 23/10/2018 21:03, mick crane wrote: > On 2018-10-23 14:56, Tony van der Hoff wrote: >> Hi, I havea laptop running fully up to date Stretch with NetworkManager, >> set to use DH|Cp via wireless. >> >> The DHCP server is another Stretch system, with the stanzas >> host tony-lt { >> hardware et

Re: strange DHCP behaviour

2018-10-24 Thread tony
On 23/10/2018 20:06, john doe wrote: > On 10/23/2018 7:49 PM, john doe wrote: >> On 10/23/2018 7:39 PM, tony wrote: >>> On 23/10/2018 18:36, john doe wrote: On 10/23/2018 5:14 PM, Martin wrote: > Shouldn't the host definition be inside the subnet definition? > > Am 23.10.18 um 15:5

Re: strange DHCP behaviour

2018-10-23 Thread Reco
Hi. On Tue, Oct 23, 2018 at 03:56:34PM +0200, Tony van der Hoff wrote: > The DHCP server is another Stretch system, with the stanzas > host tony-lt { > hardware ethernet 0c:60:76:6c:e6:6f; > fixed-address 192.168.1.199; > } > subnet 192.168.1.0 netmask 255.255.255.0 >

Re: strange DHCP behaviour

2018-10-23 Thread deloptes
Tony van der Hoff wrote: > Any suggestions, please? I would put host declaration after subnet - don't think it makes difference also check /etc/hosts for left overs and for the lease take care that your computers update time with ntp regularly regards

Re: strange DHCP behaviour

2018-10-23 Thread mick crane
On 2018-10-23 14:56, Tony van der Hoff wrote: Hi, I havea laptop running fully up to date Stretch with NetworkManager, set to use DH|Cp via wireless. The DHCP server is another Stretch system, with the stanzas host tony-lt { hardware ethernet 0c:60:76:6c:e6:6f; fixed-address 192

Re: strange DHCP behaviour

2018-10-23 Thread john doe
On 10/23/2018 7:49 PM, john doe wrote: > On 10/23/2018 7:39 PM, tony wrote: >> On 23/10/2018 18:36, john doe wrote: >>> On 10/23/2018 5:14 PM, Martin wrote: Shouldn't the host definition be inside the subnet definition? Am 23.10.18 um 15:56 schrieb Tony van der Hoff: > Hi, I have

Re: strange DHCP behaviour

2018-10-23 Thread john doe
On 10/23/2018 7:39 PM, tony wrote: > On 23/10/2018 18:36, john doe wrote: >> On 10/23/2018 5:14 PM, Martin wrote: >>> Shouldn't the host definition be inside the subnet definition? >>> >>> Am 23.10.18 um 15:56 schrieb Tony van der Hoff: Hi, I havea laptop running fully up to date Stretch with

Re: strange DHCP behaviour

2018-10-23 Thread tony
On 23/10/2018 18:36, john doe wrote: > On 10/23/2018 5:14 PM, Martin wrote: >> Shouldn't the host definition be inside the subnet definition? >> >> Am 23.10.18 um 15:56 schrieb Tony van der Hoff: >>> Hi, I havea laptop running fully up to date Stretch with NetworkManager, >>> set to use DH|Cp via w

Re: strange DHCP behaviour

2018-10-23 Thread john doe
On 10/23/2018 5:14 PM, Martin wrote: > Shouldn't the host definition be inside the subnet definition? > > Am 23.10.18 um 15:56 schrieb Tony van der Hoff: >> Hi, I havea laptop running fully up to date Stretch with NetworkManager, >> set to use DH|Cp via wireless. >> >> The DHCP server is another S

Re: strange DHCP behaviour

2018-10-23 Thread tony
On 23/10/2018 16:22, Roberto C. Sánchez wrote: > On Tue, Oct 23, 2018 at 03:56:34PM +0200, Tony van der Hoff wrote: >> >> So, my question: why is the server handing out .253, when it is >> configured to provide .199? >> What is this 'reuse-lease' all about? >> >> I've tried 'dhclient -r wlan 0; dhc

Re: strange DHCP behaviour

2018-10-23 Thread tony
On 23/10/2018 17:14, Martin wrote: > Shouldn't the host definition be inside the subnet definition? Thanks for the suggestion, Martin. The sample config file supplied with the DHCP package shows a host outside the subnet. Anyway, I tried it, and it made no difference. Thanks anyway. Cheers, Tony

Re: strange DHCP behaviour

2018-10-23 Thread Martin
Shouldn't the host definition be inside the subnet definition? Am 23.10.18 um 15:56 schrieb Tony van der Hoff: > Hi, I havea laptop running fully up to date Stretch with NetworkManager, > set to use DH|Cp via wireless. > > The DHCP server is another Stretch system, with the stanzas > host tony-lt

Re: strange DHCP behaviour

2018-10-23 Thread Roberto C . Sánchez
On Tue, Oct 23, 2018 at 03:56:34PM +0200, Tony van der Hoff wrote: > > So, my question: why is the server handing out .253, when it is > configured to provide .199? > What is this 'reuse-lease' all about? > > I've tried 'dhclient -r wlan 0; dhclient -v wlan0' on the laptop, to no > avail. > > An