well that was the search
after everything is up how do I restart a single device so it will
work in the meantime...
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Yes; I thnk instead it's a DHCP issue; since the device has no address
to start, adding the tunnel endpoing to that socket without an address
seems to be failing. It has to wait until the DHCP signal, and then
it really needs the DHCP address to update the tunnel endpoint
configuration.
On Mon, F
Am Mon, 29 Feb 2016 19:12:11 -0800
schrieb J Decker :
> I would have thought that naming 00-eth0.network; 01-eth1.network or
> something would start devices in that order?
No... It does say nothing about order in your sense. It's just ordering
which configuration overwrites another when options a
On Mon, Feb 29, 2016 at 7:12 PM, J Decker wrote:
> systemd 229-3
>
> I recently updated my Arch Linux.
>
> https://wiki.archlinux.org/index.php/IPv6_tunnel_broker_setup
>
> using a hurricane electric tunnel...
>
> and now the tunnel device wants to start and add all the static
> addresses that are
systemd 229-3
I recently updated my Arch Linux.
https://wiki.archlinux.org/index.php/IPv6_tunnel_broker_setup
using a hurricane electric tunnel...
and now the tunnel device wants to start and add all the static
addresses that are specified on other physical net devices in fact
the HE is att
On Sun, Feb 28, 2016 at 8:26 PM, G D'Arezzo wrote:
> "You probably want to use [Service] instead."
>
> Thanks for the suggestion, Auke. Unfortunately, Service and
> DefaultEnvironment don't go together:
>
> [/home/temp/.config/systemd/user/test.service.d/user.conf:2] Unknown
> lvalue 'DefaultEnvi
Am Mon, 29 Feb 2016 16:38:59 +0800 (CST)
schrieb kennedy :
> I think it will be routed, I tied ping 169.254.x.x container to
> container, and it's successed. And, I created the systemd-nspawn
> container after 5 minus ago, the container's host0 network auto turns
> ip on 169.254.x.x rather than 1
Hello
I think it will be routed, I tied ping 169.254.x.x container to container, and
it's successed.
And, I created the systemd-nspawn container after 5 minus ago, the container's
host0 network auto turns ip on 169.254.x.x rather than 10.0.0.x .
--
Yours Sincerely
Han
At 2016-02-29 15:4
