Everything works great now, thanks for all of your help!
> On Oct 10, 2014, at 2:13 AM, Lennart Poettering
> wrote:
>
>> On Thu, 09.10.14 23:53, James Lott (ja...@lottspot.com) wrote:
>>
>> I am using a setup which retains the CAP_NET_ADMIN capability inside t
:12:02 you wrote:
> On Fri, Oct 10, 2014 at 12:13 AM, James Lott wrote:
> > Trying to start up an openvpn connection yields the following error:
> >
> > Thu Oct 9 15:01:52 2014 ERROR: Cannot open TUN/TAP dev /dev/net/tun:
> > Operation not permitted (errno=1)
>
Whoops.. Meant to send the message:
Installing the latest systemd from git fixed this issue. Thanks again for
pointing that out!
On Thursday 09 October 2014 15:14:18 James Lott wrote:
> Hi Lennart!
>
> Thanks for your response! I observed this issue on Arch Linux ARM running
> s
14:08:07 Lennart Poettering wrote:
> On Fri, 03.10.14 10:58, James Lott (ja...@lottspot.com) wrote:
> > Hello,
> >
> > A little bit back I wrote in about having some difficulties adding network
> > devices to containers. With some help from the list, I figured out how to
process as it attempts to setup the connection. Please let me know if there's
anything else I can provide to be helpful, and thanks again for the help!
On Wednesday 08 October 2014 15:59:03 you wrote:
> On Fri, Oct 3, 2014 at 7:46 PM, James Lott wrote:
> > Hello, list!
> >
> &
Does anyone have any feedback on this thread? If it's not possible for a
container to create its own /dev/net/tun device (or use the host system's),
I'll just move on to finding a less preferable solution.
> On Oct 3, 2014, at 10:46 AM, James Lott wrote:
>
> Hello,
Hello,
A little bit back I wrote in about having some difficulties adding network
devices to containers. With some help from the list, I figured out how to add
my network devices to an already running container using 'iw phy' and 'ip
link'.
However, I have not yet successfully added an interfa
Hello, list!
In some work I've been doing with systemd-nspawn containers, I've been trying
to connect one of my containers to an openvpn network. This conteiner is being
run with the --network-bridge flag to setup its networking, so according to the
documentation, should retain CAP_NET_ADMIN ca
t.
> On Sep 26, 2014, at 4:28 PM, James Lott wrote:
>
> Hello again!
>
> Once again, thanks for all the help with getting my wireless interface moved
> into the container! Now I just have one more interface I'm having trouble
> with. I can't seem to move my et
/net/eth0
lrwxrwxrwx 1 root root 0 Dec 31 1969 eth1 ->
../../devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/net/eth1
On Thursday 25 September 2014 17:05:34 James Lott wrote:
> Shame on me for not spending more time trying to figure this out before
> responding. Please
to be coordinating the movement of this
interface within a service file, so I don't need to do it manually when
starting the container... but I suppose I can write an ExecStartPost script
which can manage this.
Thanks again for all your help!
On Thursday 25 September 2014 16:25:02 James
ent solution. I guess
that's what I get for living life on the edge ;)
On Thursday 25 September 2014 18:23:47 Leonid Isaev wrote:
> Hi,
>
> On Wed, Sep 24, 2014 at 08:14:55PM -0700, James Lott wrote:
> > Hello,
> >
> > There is no .network file for the br
>> On Thu, Sep 25, 2014 at 10:40:42AM -0700, James Lott wrote:
>> Hi Mantas,
>>
>> Thanks for the clarification. The first thing I tried actually was using the
>> PID
>> of the systemd-nspawn instance, like so
>>
>> [root@host01 lanvpn]# ps aux | g
that?
On Thursday 25 September 2014 20:11:56 Mantas Mikulėnas wrote:
> On Thu, Sep 25, 2014 at 7:49 PM, James Lott wrote:
> > Hi Marcel,
> >
> > Thanks for the help pointing that one out! With your guidance I was able
> > to
> > figure out that I'll need
Hi Marcel,
Thanks for the help pointing that one out! With your guidance I was able to
figure out that I'll need to run something like:
iw phy phy0 set netns
Unfortunately I'm having some trouble trying to figure out the network
namespace PID to assign the phy0 interface to. Although I defini
Hello again!
I'm having another issue with private networking in systemd-nspawn. This one
I'm not so certain is a bug, but probably some kind of mistake on my part.
Base on my reading of the systemd-nspawn man page though, I can't figure out
what the problem is. Basically, all I'm tring to do i
service is included in that email
as well).
On Wednesday 24 September 2014 22:44:17 Leonid Isaev wrote:
> Hi,
>
> On Wed, Sep 24, 2014 at 07:16:03PM -0700, James Lott wrote:
> > However, when I try to acquire a dhcp lease through the bridge
> > interface, I am unable to do so
Hello!
With some help from the kind people on this list, I was able to get my basic
network interfaces up and runnign with systemd-networkd. Now I've moved on to
playing with some slightly more complex setups, and have run into some issues
that as far as I can tell may be bugs (but I'm not quit
be? I
want to make sure I keep my eyes peeled for it!
On Friday 19 September 2014 23:04:40 Tom Gundersen wrote:
> On Fri, Sep 19, 2014 at 6:37 PM, James Lott wrote:
> > I am trying to setup and play around with some of the private networking
> > features of systemd, and one of the
Holy smokes, that did it! Many thanks for taking time out of your day to help
me find my silly mistake :)
On Friday 19 September 2014 22:51:41 Tom Gundersen wrote:
> On Fri, Sep 19, 2014 at 6:59 PM, James Lott wrote:
> > Hello again!
> >
> > I've been eager to play wi
Hello again!
I've been eager to play with networking features, in case you couldn't tell ;)
This patricular issue seems separate from my first one though, so I thought it
would be best to discuss separately.
I am trying to use systemd-networkd to essentially replace vconfig. I am using
eth0 as
t@utility01 ~]# pacman -Q systemd
systemd 216-3
I'm happy to run any additional tests or provide any additional information
needed to help try to reproduce. Thanks in advance for any help!
--
James Lott
___
systemd-devel mailing list
systemd-de
22 matches
Mail list logo
