On Tue, 27.05.14 22:14, Kirill Elagin (kirela...@gmail.com) wrote:
> >
> > The container usecase alone is already the reason why I am so very sure
> > I want this stuff, and that it needs to be in networkd, and just work. I
> > want this fully automatic, so that we can create a hundred of veth
> >
On Tue, 27.05.14 14:48, Tollef Fog Heen (tfh...@err.no) wrote:
>
> ]] Lennart Poettering
>
> > If we set up links (and especially, create them like
> > we do for veth), then hel, yeah we should be prepared to make sure
> > everybody gets an address on it.
>
> Should we also include BGP, OSPF,
On Tue, 2014-05-27 at 13:39 +0200, David Herrmann wrote:
> I strongly disagree. One major example is Wifi-P2P which requires a
> DHCP-Server for ad-hoc P2P connections. A network-daemon manages the
> local address-space, so it should also be responsible of assigning
> those ranges to an ad-hoc DHCP
On Tue, 27.05.14 16:04, Eelco Dolstra (eelco.dols...@logicblox.com) wrote:
> > I am very sure this should be in networkd.
> [snip]
>
> That sounds reasonable. However, to be honest, I've never really understood
> why
> networkd needs to be part of systemd in the first place. It seems to
> me th
On Tue, 27.05.14 14:28, Michael Biebl (mbi...@gmail.com) wrote:
>
> 2014-05-27 14:00 GMT+02:00 Lennart Poettering :
> >
> > In many ways, if people complain about a dhcp server in networkd, then
> > it's like complaining about the fact that pppd also can assign addresses
> > to the other side...
Am 27.05.2014 20:14, schrieb Kirill Elagin:
> The container usecase alone is already the reason why I am so very sure
> I want this stuff, and that it needs to be in networkd, and just work. I
> want this fully automatic, so that we can create a hundred of veth
> tunnels, and trivi
>
> The container usecase alone is already the reason why I am so very sure
> I want this stuff, and that it needs to be in networkd, and just work. I
> want this fully automatic, so that we can create a hundred of veth
> tunnels, and trivially easy (simply by setting DHCPServer=yes for their
> .ne
On 05/27/2014 03:20 PM, Tom Gundersen wrote:
On Tue, May 27, 2014 at 2:48 PM, Tollef Fog Heen wrote:
>]] Lennart Poettering
>
>>If we set up links (and especially, create them like
>>we do for veth), then hel, yeah we should be prepared to make sure
>>everybody gets an address on it.
>
>Shou
]] Tom Gundersen
> On Tue, May 27, 2014 at 2:48 PM, Tollef Fog Heen wrote:
> > ]] Lennart Poettering
> >
> >> If we set up links (and especially, create them like
> >> we do for veth), then hel, yeah we should be prepared to make sure
> >> everybody gets an address on it.
> >
> > Should we also
On Tue, May 27, 2014 at 4:04 PM, Eelco Dolstra
wrote:
> However, to be honest, I've never really understood why
> networkd needs to be part of systemd in the first place. It seems to me that
> it
> would work just as well as a separate package with its own releases. To me as
> a
> downstream tha
On Tue, May 27, 2014 at 2:48 PM, Tollef Fog Heen wrote:
> ]] Lennart Poettering
>
>> If we set up links (and especially, create them like
>> we do for veth), then hel, yeah we should be prepared to make sure
>> everybody gets an address on it.
>
> Should we also include BGP, OSPF, RIP, ISIS (and t
El 27/05/14 07:39, David Herrmann escribió:
> I strongly disagree. One major example is Wifi-P2P which requires a
> DHCP-Server for ad-hoc P2P connections.
OOk. that convinced me, thanks..
--
Cristian
"I don't know the key to success, but the key to failure is trying to
please everybody."
___
El 27/05/14 10:04, Eelco Dolstra escribió:
¿
That sounds reasonable. However, to be honest, I've never really understood why
networkd needs to be part of systemd in the first place.
For the start, to share a large amount code..
It seems to me that it
would work just as well as a separate pac
Hi,
On 27/05/14 13:50, Lennart Poettering wrote:
>> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
>>> When enabled in [Network] it will set up a dhcp server on the interface,
>>> listening
>>> on one of its statically configured IPv4 addresses and with a fixed size
>>> pool of
]] Lennart Poettering
> If we set up links (and especially, create them like
> we do for veth), then hel, yeah we should be prepared to make sure
> everybody gets an address on it.
Should we also include BGP, OSPF, RIP, ISIS (and their IPv6 variants) to
make sure it's possible to push routes?
2014-05-27 14:00 GMT+02:00 Lennart Poettering :
>
> In many ways, if people complain about a dhcp server in networkd, then
> it's like complaining about the fact that pppd also can assign addresses
> to the other side...
I don't see pppd implementing a DHCP server.
--
Why is it that all of the i
On Tue, 27.05.14 13:39, David Herrmann (dh.herrm...@gmail.com) wrote:
> Hi
>
> On Tue, May 27, 2014 at 12:41 PM, Michael Biebl wrote:
> > 2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
> >> before looking at the code, a couple of general questions:
> >> - does the DHCP server have to be
On Tue, 27.05.14 04:38, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
> > When enabled in [Network] it will set up a dhcp server on the interface,
> > listening
> > on one of its statically configured IPv4 addresses and
Hi
On Tue, May 27, 2014 at 12:41 PM, Michael Biebl wrote:
> 2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
>> before looking at the code, a couple of general questions:
>> - does the DHCP server have to be part of networkd? Isn't the job
>> of acquiring addresses and giving out address
On Tue, May 27, 2014 at 12:41 PM, Michael Biebl wrote:
> 2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
>> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
>>> When enabled in [Network] it will set up a dhcp server on the interface,
>>> listening
>>> on one of its staticall
2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
>> When enabled in [Network] it will set up a dhcp server on the interface,
>> listening
>> on one of its statically configured IPv4 addresses and with a fixed size
>> pool of
Hi Zbyszek,
On 27 May 2014 04:38, "Zbigniew Jędrzejewski-Szmek"
wrote:
>
> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
> > When enabled in [Network] it will set up a dhcp server on the
interface, listening
> > on one of its statically configured IPv4 addresses and with a fixed
Hi Cristian,
>>> When enabled in [Network] it will set up a dhcp server on the interface,
>>> listening
>>> on one of its statically configured IPv4 addresses and with a fixed size
>>> pool of
>>> leases determined from it.
>> Hi Tom,
>> before looking at the code, a couple of general questions:
El 26/05/14 22:38, Zbigniew Jędrzejewski-Szmek escribió:
On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
When enabled in [Network] it will set up a dhcp server on the interface,
listening
on one of its statically configured IPv4 addresses and with a fixed size pool of
leases dete
On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote:
> When enabled in [Network] it will set up a dhcp server on the interface,
> listening
> on one of its statically configured IPv4 addresses and with a fixed size pool
> of
> leases determined from it.
Hi Tom,
before looking at the cod
When enabled in [Network] it will set up a dhcp server on the interface,
listening
on one of its statically configured IPv4 addresses and with a fixed size pool of
leases determined from it.
Example:
[Match]
Name=ve-arch-tree
[Network]
Address=192.168.12.5/24
DHCPServer=yes
[Route]
Gateway=192
26 matches
Mail list logo
