On Wed, Nov 6, 2013 at 12:32 PM, Lennart Poettering
wrote:
> On Wed, 06.11.13 02:57, Tom Gundersen (t...@jklm.no) wrote:
>
>> >> Gateway=192.168.1.1
>> >> Address=label@192.168.1.23/24
>> >> Address=fe80::9aee:94ff:fe3f:c618/64
>> >
>> > Hmm, what's the plan regarding confguration of scopes and ot
> A native and fast DHCP client will be part of it, yes, it is needed in
> the initrd.
> Not sure though when we will get there though.
nice to hear. and right, having it in initrd is nice too.
>
> > currently we integrate http://0pointer.de/lennart/projects/ifplugd/
>
> Urks, the 90s calling.
On Thu, 07.11.13 16:03, Holger Winkelmann [TP] (h...@travelping.com) wrote:
>
> Hi,
>
> > To clarify this: systemd-networkd is supposed to cover the initrd,
> > container, server and (some) embedded usecases. However, use NM or
> > connman for the "interactive" stuff (like wlans and suchlike) yo
On Thu, Nov 7, 2013 at 4:03 PM, Holger Winkelmann [TP]
wrote:
>> To clarify this: systemd-networkd is supposed to cover the initrd,
>> container, server and (some) embedded usecases. However, use NM or
>> connman for the "interactive" stuff (like wlans and suchlike) you need
>> on laptops/desktops
Hi,
> To clarify this: systemd-networkd is supposed to cover the initrd,
> container, server and (some) embedded usecases. However, use NM or
> connman for the "interactive" stuff (like wlans and suchlike) you need
> on laptops/desktops and mobile.
Will this cover the UseCase of having a DHCP ena
On Thu, 07.11.13 01:45, Tom Gundersen (t...@jklm.no) wrote:
>
> On Wed, Nov 6, 2013 at 7:56 AM, Holger Winkelmann [TP]
> wrote:
> > We really like to see this direct, how ever would it not better to join
> > efforts for network management. I.e. arch Linux claims with netctl [1]
> > to do network
On Wed, Nov 6, 2013 at 7:56 AM, Holger Winkelmann [TP]
wrote:
> We really like to see this direct, how ever would it not better to join
> efforts for network management. I.e. arch Linux claims with netctl [1]
> to do network management "the systems way. and there are a few other
> attempts to do n
On Wed, Nov 6, 2013 at 5:00 AM, David Strauss wrote:
> Another critical feature for server configs is bonding. It's possible right
> from Kickstart and with the normal configurations in Fedora. We use it on
> every bare-metal server we manage to get HA networking.
Bonding (or probably teaming ins
On Wed, Nov 6, 2013 at 3:13 AM, Jan Engelhardt wrote:
>
> On Wednesday 2013-11-06 02:57, Tom Gundersen wrote:
>>
Gateway=192.168.1.1
Address=label@192.168.1.23/24
Address=fe80::9aee:94ff:fe3f:c618/64
>>>
>>The @ syntax is my invention, but i'm very happy to
>>change it if anyone has
On Wed, Nov 6, 2013 at 3:08 AM, Kok, Auke-jan H
wrote:
> On Tue, Nov 5, 2013 at 4:33 PM, Tom Gundersen wrote:
>> This daemon listens for and configures network devices tagged with
>> 'systemd-networkd'. By default, no devices are tagged so this daemon
>> can safely run in parallel with existing n
At Wed, 6 Nov 2013 07:56:32 +0100 (CET),
Holger Winkelmann [TP] wrote:
> how ever would it not better to join
> efforts for network management. I.e. arch Linux claims with netctl [1]
> to do network management "the systems way.
...
> [1] https://wiki.archlinux.org/index.php/netctl
> https://git
Hi.
This daemon is an offline daemon: it exposes no means for controlling it that
other programs or users can
manipulate. It is a standalone program that does what it does and cannot be
spoken to.
A DBus interface is, IMO, absolutely essential, and discussing your work
without that ability to
On Wed, Nov 6, 2013 at 1:32 AM, Colin Guthrie wrote:
> 'Twas brillig, and Kok, Auke-jan H at 06/11/13 02:08 did gyre and gimble:
>> alright, I'll comment, but it took me 5 minutes to clear the coffee
>> off my monitor...
>>
>> Looking at the feature list, why are you not contributing to connman
>>
On 11/06/2013 12:33 AM, Tom Gundersen wrote:
[Match]
MACAddress=
Path=
Driver=
Type=
Name=
[Network]
Description=
[IP]
Gateway=192.168.1.1
Address=label@192.168.1.23/24
Address=fe80::9aee:94ff:fe3f:c618/64
Hmm..
Cant we try to follow the same construct as the other units?
Something like th
On Wed, 06.11.13 15:09, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
>
> On 11/06/2013 03:00 PM, Lennart Poettering wrote:
> >On Wed, 06.11.13 14:14, Mantas Mikulėnas (graw...@gmail.com) wrote:
> >
> >>On Wed, Nov 6, 2013 at 1:32 PM, Lennart Poettering
> >> wrote:
> >>>I have my suspicions t
On 11/06/2013 03:00 PM, Lennart Poettering wrote:
On Wed, 06.11.13 14:14, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Wed, Nov 6, 2013 at 1:32 PM, Lennart Poettering
wrote:
I have my suspicions that that won't work out since there already are
quite a few properties for addresses, no? Ther
On Wed, 06.11.13 14:14, Mantas Mikulėnas (graw...@gmail.com) wrote:
> On Wed, Nov 6, 2013 at 1:32 PM, Lennart Poettering
> wrote:
> > I have my suspicions that that won't work out since there already are
> > quite a few properties for addresses, no? There's scope, flags,
> > label. For Point-To-P
On Wed, Nov 6, 2013 at 1:32 PM, Lennart Poettering
wrote:
> I have my suspicions that that won't work out since there already are
> quite a few properties for addresses, no? There's scope, flags,
> label. For Point-To-Point stuff the address needs to be paired with a
> local one, and in other case
Hi Lennart,
>> +struct Link {
>> +uint64_t ifindex;
>
> Hmm is this really an uint64_t? if_nametoindex(3) suggestes it's an
> "unsigned"?
actually using if_nametoindex() is bad idea as well. That should be turned into
an async RTNL call as well. We better just cache the ifname to ifind
On Wed, 06.11.13 02:57, Tom Gundersen (t...@jklm.no) wrote:
> >> Gateway=192.168.1.1
> >> Address=label@192.168.1.23/24
> >> Address=fe80::9aee:94ff:fe3f:c618/64
> >
> > Hmm, what's the plan regarding confguration of scopes and other
> > attributes of addresses? Is the "label@" syntax your inventi
Hi ScotX,
>>> Looking at the feature list, why are you not contributing to connman
>>> instead? It seems you're going to be duplicating a ton of code And
>>> connman does what your goal is, meaning you can pre-provision static
>>> configurations without any of the more involved dependencies. I
'Twas brillig, and Kok, Auke-jan H at 06/11/13 02:08 did gyre and gimble:
> alright, I'll comment, but it took me 5 minutes to clear the coffee
> off my monitor...
>
> Looking at the feature list, why are you not contributing to connman
> instead?
AFAIK, Tom has had plenty discussions with Marcel
On 11/06/2013 09:37 AM, Marcel Holtmann wrote:
Looking at the feature list, why are you not contributing to connman
instead? It seems you're going to be duplicating a ton of code And
connman does what your goal is, meaning you can pre-provision static
configurations without any of the more in
Hi Auke,
>> This daemon listens for and configures network devices tagged with
>> 'systemd-networkd'. By default, no devices are tagged so this daemon
>> can safely run in parallel with existing network daemons/scripts.
>>
>> Networks are configured in /etc/systemd/network/*.network. The first .n
good morning,
We really like to see this direct, how ever would it not better to join
efforts for network management. I.e. arch Linux claims with netctl [1]
to do network management "the systems way. and there are a few other
attempts to do network managent. I.e. netconfd [2] of openWRT is doing
n
Another critical feature for server configs is bonding. It's possible right
from Kickstart and with the normal configurations in Fedora. We use it on
every bare-metal server we manage to get HA networking.
___
systemd-devel mailing list
systemd-devel@list
On Wednesday 2013-11-06 02:57, Tom Gundersen wrote:
>
>>> Gateway=192.168.1.1
>>> Address=label@192.168.1.23/24
>>> Address=fe80::9aee:94ff:fe3f:c618/64
>>
>The @ syntax is my invention, but i'm very happy to
>change it if anyone has a better suggestion.
Be sure to support
Address=192.16
On Tue, Nov 5, 2013 at 4:33 PM, Tom Gundersen wrote:
> This daemon listens for and configures network devices tagged with
> 'systemd-networkd'. By default, no devices are tagged so this daemon
> can safely run in parallel with existing network daemons/scripts.
>
> Networks are configured in /etc/s
On Wed, Nov 6, 2013 at 2:25 AM, Lennart Poettering
wrote:
> On Wed, 06.11.13 01:33, Tom Gundersen (t...@jklm.no) wrote:
>> Short-term TODO:
>> - make rtnl calls asynchronous
>
> Don't wait for too long for this! The longer you wait the more code you
> have to rework for this. And you shouldn't un
On Wed, 06.11.13 01:33, Tom Gundersen (t...@jklm.no) wrote:
> Short-term TODO:
> - make rtnl calls asynchronous
Don't wait for too long for this! The longer you wait the more code you
have to rework for this. And you shouldn't underestimate how complex
changes from sync to async are...
> Gateway
This daemon listens for and configures network devices tagged with
'systemd-networkd'. By default, no devices are tagged so this daemon
can safely run in parallel with existing network daemons/scripts.
Networks are configured in /etc/systemd/network/*.network. The first .network
file that matches
31 matches
Mail list logo
