. I need to issue this command:
ip token set ::2/64 dev br0
1. after the bridge device is created
2. before IP address is configured on it
netctl still seems a lot more capable than systemd-networkd...
And netctl runs separate services (line netctl@eth0.service) for separate
interfaces unlike
Re
CADPrc803kq_c76b1oqp3PksvDgyP5MD+zqLGqcsxk=eCT2iYRA@mail.gmail.comCADPrc803kq_c76b1oqp3PksvDgyP5MD+zqLGqcsxk=eCT2iYRA@mail.gmail.com51f10221.1080...@hadt.biz,
Michael Hampicke said:
Tanks. I will give netctl a try in a VM. For now, on real machines, I
am going with the unit you suggested
Heyo!
I saw some of the recent threads about NetworkManager and other
alternatives, and I wanted to share about one I tried and have liked so
far: netctl[0]. It is specifically designed for systemd by ArchLinux, so
if you are using a different init system, sorry for the noise in your
inbox
On Thursday 25 July 2013 17:23:56 I wrote:
Systemd will not read /etc/conf.d/net like /etc/init.d/net.*
scripts do. You need some service that will prepare the
network.
I personally prefer netctl, it is KISS enough. It was me who
asked the devs to add it to the tree :)
I tried NM too, it does
= for static
address.
Here is another problem. I need to issue this command:
ip token set ::2/64 dev br0
1. after the bridge device is created
2. before IP address is configured on it
netctl still seems a lot more capable than systemd-networkd...
And netctl runs separate services (line netctl
NetworkManager altogether, avoiding a load of dependencies if you don't
use GNOME.
For typical wireless networks, wpa_gui is more than adequate for
configuration.
I concur, I switched to systemd-netword over two months ago. This replaced
netctl on my desktop, and both netctl and NetworkManager on my
ExecStart, some suggested Arch's netctl which
seems to support static addresses and brings a systemd unit file.
At the moment, following the KISS principle, I tend to a customized unit
file.
What do you use - and what are the benefits of your method?
Have a nice day,
Mike
signature.asc
that will prepare the network.
I personally prefer netctl, it is KISS enough. It was me who asked the devs
to add it to the tree :)
I tried NM too, it does not work out of the box with systemd, there are
several issues.
[1] mailto:m...@hadt.biz
suggest installing net-misc/netctl. Postup will be possible.
1. after the bridge device is created
2. before IP address is configured on it
This seems like a useful feature and should be simple to implement.
Can't promise to work on that any time soon though, but, again,
patches would be appreciated.
netctl still seems a lot more capable than systemd
.
If you use systemd net-misc/netctl has a nice curses UI but I've only tried on
Arch.
--
Fernando Rodriguez
+ networkmanager (workstations, laptops).
Some suggested creating your own network unit and manually start
ifconfig/route or ip via ExecStart, some suggested Arch's netctl which
seems to support static addresses and brings a systemd unit file.
At the moment, following the KISS principle, I tend
,
they want something small for simple cases, and if you need more you
can use NetworkManager, connman, iproute2, or whatever.
But then you had to configure it yourself.
[snip]
And, by the way, someone make me notice that netctl is an Arch'ism,
and that the command-line front-end for networkd
me notice that netctl is an Arch'ism,
and that the command-line front-end for networkd is actually
networkctl.
Yes, it was taken from Arch in order to allow better network support for
advanced configurations whitout requiring to write yet another tool.
Nothing was taken from Arch, I
in
corporation relationships, innovation mentoring or software adoption
constraints. The cabale remains tempting as it can explain everything.
Anyway, systemd-networkd (introduced in systemd-209) is written to fill
this gap. Good news.
Nothing was taken from Arch, I believe. networkctl and netctl had
/net if you don't make
your own systemd unit.
I suggest installing net-misc/netctl. Postup will be possible.
OK, thanks -- I will look at that.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
cov...@ccs.covici.com
pages of netctl too and am horrified
at the lack of what i would call enterprise features.
this is by no means a definitive list.
I just thought that i would share what i had found.
please correct me if i am wrong in any of these.
please add to the list for technical items only.
thanks!
pros
1
The 23/02/14, Canek Peláez Valdés wrote:
networkd (again, netctl is the command-line front-end) is not for
enterprise networks; on the contrary, is for the trivial cases. For
example, in a little web server I administer I have:
$ cat /etc/systemd/system/network.service
[Unit
creating your own network unit and manually start
ifconfig/route or ip via ExecStart, some suggested Arch's netctl which
seems to support static addresses and brings a systemd unit file.
At the moment, following the KISS principle, I tend to a customized unit
file.
What do you use - and what
) compared to OpenRC.
Yes.
My current itch to scratch: set up a bonding of 2 physical NICs with
systemd on gentoo. I didn't google for very long but didn't find much
aside from arch linux howtos using netctl etc (which I don't know and
therefore trust so much)
And the network.service-files I copied
questions about the socket activator.
i've also been going through the man pages of netctl too and am horrified
at the lack of what i would call enterprise features.
networkd (netctl is just the command-line front-end) is not intended
for enterprise; it's for little servers where you only need static
questions about the socket activator.
i've also been going through the man pages of netctl too and am
horrified
at the lack of what i would call enterprise features.
networkd (netctl is just the command-line front-end) is not intended
for enterprise; it's for little servers where you only need
you forgot that you need),
chroot still works.
So, there is a workaround if you want to keep using chroot for jailed
services, and there's a better alternative.
[ snip ]
networkd (again, netctl is the command-line front-end) is not for
enterprise networks; on the contrary, is for the trivial
stuff (for example, boot from
a non-systemd LiveCD and emerge something you forgot that you need),
chroot still works.
So, there is a workaround if you want to keep using chroot for jailed
services, and there's a better alternative.
[ snip ]
networkd (again, netctl is the command-line front
24 matches
Mail list logo
