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
On Fri, 15.08.14 09:12, Michael Olbrich ([email protected]) wrote:
>
> On Thu, Aug 14, 2014 at 05:38:05PM +0200, Lennart Poettering wrote:
> > On Fri, 25.07.14 09:48, Michael Olbrich ([email protected]) wrote:
> >
> > > What I'm _not_ seeing, and what usually comes when anything el
On Thu, Aug 14, 2014 at 05:38:05PM +0200, Lennart Poettering wrote:
> On Fri, 25.07.14 09:48, Michael Olbrich ([email protected]) wrote:
>
> > What I'm _not_ seeing, and what usually comes when anything else changes in
> > the network configuration is:
> > systemd-timesyncd[348]: Network co
On Fri, 25.07.14 09:48, Michael Olbrich ([email protected]) 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, t
On Thu, 24.07.14 10:49, Tom Gundersen ([email protected]) 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
> > discove
On Fri, Jul 25, 2014 at 11:19 AM, Michael Olbrich
wrote:
> Hi,
>
> On Fri, Jul 25, 2014 at 11:00:27AM +0200, Brendan Hide wrote:
>> On 24/07/14 14:05, Marcel Holtmann wrote:
>> >[snip]
>> >>... you already are getting
>> >>assigned the correct IP address at first, and then only later does
>> >>thi
Hi,
On Fri, Jul 25, 2014 at 11:00:27AM +0200, Brendan Hide wrote:
> On 24/07/14 14:05, Marcel Holtmann wrote:
> >[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
>
On Fri, Jul 25, 2014 at 11:00 AM, Brendan Hide
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 out
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
any
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
> 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
On Thu, Jul 24, 2014 at 10:54 PM, Zbigniew Jędrzejewski-Szmek
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 setting of
On Thu, Jul 24, 2014 at 10:54 PM, Zbigniew Jędrzejewski-Szmek
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 setting of
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 setting of 0
is a brain damaged trap.
Zbyszek
___
On Thu, Jul 24, 2014 at 5:59 PM, Michael Olbrich
wrote:
> 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
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
On 24/07/14 10:49, Tom Gundersen wrote:
On Thu, Jul 24, 2014 at 10:16 AM, Michael Olbrich
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. It is valid to just get a
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 sho
On Thu, Jul 24, 2014 at 10:16 AM, Michael Olbrich
wrote:
> On Wed, Jul 23, 2014 at 04:46:26PM +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
>> >>
On Wed, Jul 23, 2014 at 04:46:26PM +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 serv
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 back
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 yo
On Wed, Jul 23, 2014 at 12:47:37PM +0200, Tom Gundersen wrote:
> On Wed, Jul 23, 2014 at 9:50 AM, Michael Olbrich
> 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
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 ex
On Wed, Jul 23, 2014 at 9:50 AM, Michael Olbrich
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 for
> networkd.
> The m
Hi,
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 for
networkd.
The most common use-case I have is rather simple: One ethernet inte
25 matches
Mail list logo
