Okay,
it was not as easy as just killing avahi-autoipd service when up (or any
dhcp) event took place in dispatcher. This approach led to new ipv4ll
address because, when avahi-autoipd re-started some other party reported
"conflict" with that old address and avahi-autoipd selected new one. This
was
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
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
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
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.
_
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
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
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
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
On Slackware, the expectation is for output of "hostname" without options
to be the same as "hostname --short" whereas "hostname --fqdn" would be
used if the full hostname+domain is desired.
With NM-1.2.x, using persistent hostname setting and pulling it from
/etc/HOSTNAME, it gets set to the fqdn
10 matches
Mail list logo
