On Wed, 2014-07-23 at 16:46 +0200, Marcel Holtmann wrote:
Hi Michael,
I think the lease should be remembered and reused in this case.
Hm, this sounds like a bug somewhere. When the new discover is sent
out it should send the same identifying information to the server, and
hence be
On Thu, Aug 14, 2014 at 05:38:05PM +0200, Lennart Poettering wrote:
On Fri, 25.07.14 09:48, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
What I'm _not_ seeing, and what usually comes when anything else changes in
the network configuration is:
systemd-timesyncd[348]: Network
On Fri, 15.08.14 09:12, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
On Thu, Aug 14, 2014 at 05:38:05PM +0200, Lennart Poettering wrote:
On Fri, 25.07.14 09:48, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
What I'm _not_ seeing, and what usually comes when anything else
On Thu, 24.07.14 10:49, Tom Gundersen (t...@jklm.no) wrote:
I think there was some misunderstanding here. I don't want to keep the
lease across reboots. I don't care about that. I think networkd should
remember the lease when restarting networkd only and not send a new dhcp
discover.
On Fri, 25.07.14 09:48, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
What I'm _not_ seeing, and what usually comes when anything else changes in
the network configuration is:
systemd-timesyncd[348]: Network configuration changed, trying to establish
connection.
I would expect, that
Hi,
On Thu, Jul 24, 2014 at 11:58:15PM +0200, Tom Gundersen wrote:
On Thu, Jul 24, 2014 at 10:54 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Thu, Jul 24, 2014 at 09:18:14PM +0200, Tom Gundersen wrote:
A quick fix would be to set
On 24/07/14 14:05, Marcel Holtmann wrote:
Hi Tom,
[snip]
... you already are getting
assigned the correct IP address at first, and then only later does
this change. What is causing your DHCP server to send out a different
IP address later on, I don't know, but it seems unlikely that this is
On Fri, Jul 25, 2014 at 11:00 AM, Brendan Hide
bren...@swiftspirit.co.za wrote:
On 24/07/14 14:05, Marcel Holtmann wrote:
Hi Tom,
[snip]
... you already are getting
assigned the correct IP address at first, and then only later does
this change. What is causing your DHCP server to send
Hi Tom,
I think the lease should be remembered and reused in this case.
Hm, this sounds like a bug somewhere. When the new discover is sent
out it should send the same identifying information to the server, and
hence be given the same lease back again. Wireshark should tell you if
the
On 24/07/14 10:49, Tom Gundersen wrote:
On Thu, Jul 24, 2014 at 10:16 AM, Michael Olbrich
m.olbr...@pengutronix.de wrote:
On Wed, Jul 23, 2014 at 04:46:26PM +0200, Marcel Holtmann wrote:
There is no mandate that the server has to give you the same address
after 10 minutes when you ask again.
On Thu, Jul 24, 2014 at 02:05:24PM +0200, Marcel Holtmann wrote:
Right, I spoke too quickly. What I don't want is to preserve state
between reboots, preserving it between restarts of networkd would
indeed be fine. We already serialize the dhcp leases to /run, so I'd
be happy to take a
On Thu, Jul 24, 2014 at 10:54 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Thu, Jul 24, 2014 at 09:18:14PM +0200, Tom Gundersen wrote:
A quick fix would be to set
/proc/sys/net/ipv4/conf/all/promote_secondaries
to 1.
Wouldn't it be nice to set it to 1 always. The default
On Wed, Jul 23, 2014 at 9:50 AM, Michael Olbrich
m.olbr...@pengutronix.de wrote:
I've been experimenting with systemd-networkd to see where it fits my
use-cases. I'm looking for some insight if the issues I'm seeing are bugs,
features just not implemented yet or if my use-case is out of scope
Am 23.07.2014 12:47, schrieb Tom Gundersen:
I think the lease should be remembered and reused in this case.
In general, saving the lease to disk is probably not a good idea. We
would need to store it on /var, and we may need to start the DHCP
server before /var has been mounted. To the extent
On Wed, Jul 23, 2014 at 12:47:37PM +0200, Tom Gundersen wrote:
On Wed, Jul 23, 2014 at 9:50 AM, Michael Olbrich
m.olbr...@pengutronix.de wrote:
I've been experimenting with systemd-networkd to see where it fits my
use-cases. I'm looking for some insight if the issues I'm seeing are bugs,
Hi Michael,
I think the lease should be remembered and reused in this case.
Hm, this sounds like a bug somewhere. When the new discover is sent
out it should send the same identifying information to the server, and
hence be given the same lease back again. Wireshark should tell you if
the
On 23.07.2014 16:46, Marcel Holtmann wrote:
Hi Michael,
I think the lease should be remembered and reused in this case.
Hm, this sounds like a bug somewhere. When the new discover is sent
out it should send the same identifying information to the server, and
hence be given the same lease
17 matches
Mail list logo
