Re: NM changes DHCP address too easily

2016-06-08 Thread matti kaasinen
Thanks for this information, This sounds like dhclient bug > https://bugzilla.redhat.com/show_bug.cgi?id=1093803 > > The internal DHCP plugin (from systemd's network library) doesn't have > issue with resetting time. > I hope internal DHCP plugin can also tolerate/ignore IPv4LL addresses so that I

Re: NM changes DHCP address too easily

2016-06-08 Thread Thomas Haller
On Wed, 2016-06-08 at 12:14 +0300, matti kaasinen wrote: > Hi! > > I got into same conclusion as as Eli (http://billauer.co.il/blog/2012 > /10/dhcp-ip-ntpdate-rtc/) that dhclient notices that time has > advanced over lease "expire" moment after time jump due to ntpdate. > As a consequence it rejec

Re: NM changes DHCP address too easily

2016-06-08 Thread matti kaasinen
Hi! I got into same conclusion as as Eli ( http://billauer.co.il/blog/2012/10/dhcp-ip-ntpdate-rtc/) that dhclient notices that time has advanced over lease "expire" moment after time jump due to ntpdate. As a consequence it rejects old IP and claims new one. I tried more elegant way to get this so

Re: NM changes DHCP address too easily

2016-05-17 Thread matti kaasinen
Hi! Some more information - lease log from board after re-installation and dhcp server log: lease { interface "eth0"; fixed-address 111.111.3.15; option subnet-mask 255.255.252.0; option dhcp-lease-time 7200; option routers 111.111.1.2; option dhcp-messa

Re: NM changes DHCP address too easily

2016-04-25 Thread matti kaasinen
It is dedicated dhcp server for local area network called dhcpd3. I don't know how many free leases it has, but it do have very much free addressing space. I don't beleave server changes addres for lack of addresses. There are only couple of workstations (below 10) using dhcp addressing and basical

Re: NM changes DHCP address too easily

2016-04-25 Thread José Queiroz
2016-04-25 2:24 GMT-03:00 matti kaasinen : > dhcpd3 > > Sorry. I didn't make myself clear. Which device is your DHCP server? A router (maybe wifi)? A dedicated/generic router? A server? How many free leases the DHCP server have, now? ___ networkmanager

Re: NM changes DHCP address too easily

2016-04-24 Thread matti kaasinen
dhcpd3 2016-04-22 18:05 GMT+03:00 José Queiroz : > > > 2016-04-22 11:59 GMT-03:00 matti kaasinen : > >> >> 2016-04-22 17:07 GMT+03:00 José Queiroz : >> >>> Shouldn't the DHCP address be managed by the DHCP server? Even if the >>> client releases the previous lease, the server should send the same

Re: NM changes DHCP address too easily

2016-04-22 Thread Thomas Haller
On Fri, 2016-04-22 at 10:02 -0500, Dan Williams wrote: > On Fri, 2016-04-22 at 16:40 +0300, matti kaasinen wrote: > > > > 2016-04-22 16:12 GMT+03:00 Beniamino Galvani : > > > > > > > > > > > Do you mean that the board is getting a different address at > > > every > > > boot? In order to reuse t

Re: NM changes DHCP address too easily

2016-04-22 Thread José Queiroz
2016-04-22 11:59 GMT-03:00 matti kaasinen : > > 2016-04-22 17:07 GMT+03:00 José Queiroz : > >> Shouldn't the DHCP address be managed by the DHCP server? Even if the >> client releases the previous lease, the server should send the same address >> on the next DISCOVER, as long as it is free, that's

Re: NM changes DHCP address too easily

2016-04-22 Thread Dan Williams
On Fri, 2016-04-22 at 16:40 +0300, matti kaasinen wrote: > 2016-04-22 16:12 GMT+03:00 Beniamino Galvani : > > > > > Do you mean that the board is getting a different address at every > > boot? In order to reuse the same lease, a persistent connection > > must > > be used (i.e. a connection writte

Re: NM changes DHCP address too easily

2016-04-22 Thread matti kaasinen
2016-04-22 16:12 GMT+03:00 Beniamino Galvani : > Do you mean that the board is getting a different address at every > boot? In order to reuse the same lease, a persistent connection must > be used (i.e. a connection written on disk and not the in-memory one > automatically generated by NM at every

Re: NM changes DHCP address too easily

2016-04-22 Thread matti kaasinen
2016-04-22 15:55 GMT+03:00 Thomas Haller : > Which plugin are you using? Does it change when setting "dhcp=internal" > or "dhcp=dhclient"? > Unfortunately I'm still tied to NM v.0.9.8.10 for couple of months. So I don't have chcp=internal option. I have been using dhclient. _

Re: NM changes DHCP address too easily

2016-04-22 Thread Beniamino Galvani
On Fri, Apr 22, 2016 at 03:28:43PM +0300, matti kaasinen wrote: > Hi! > > I have found NM switching DHCP address quite frequently, which is pretty > annoying as this happens on embedded board that has only internet access > available. Do you mean that the board is getting a different address at e

Re: NM changes DHCP address too easily

2016-04-22 Thread Thomas Haller
On Fri, 2016-04-22 at 15:28 +0300, matti kaasinen wrote: > Hi! > > I have found NM switching DHCP address quite frequently, which is > pretty annoying as this happens on embedded board that has only > internet access available. I read from web that you have borrowed > Connman internal DHCP client

NM changes DHCP address too easily

2016-04-22 Thread matti kaasinen
Hi! I have found NM switching DHCP address quite frequently, which is pretty annoying as this happens on embedded board that has only internet access available. I read from web that you have borrowed Connman internal DHCP client to your latest releases. I hope you have also adopted Connman convent