Hi Lennart,
>> this nl80211 is based on generic netlink, you would need to do a lot
>> to just add simple support for it. Also for all network interfaces
>> that have complex physical devices as base (including Bluetooth) it
>> is never that dead simple.
>
> Well, sooner or later I figure sd-rtnl
On Thu, 02.10.14 13:06, Marcel Holtmann (mar...@holtmann.org) wrote:
> this nl80211 is based on generic netlink, you would need to do a lot
> to just add simple support for it. Also for all network interfaces
> that have complex physical devices as base (including Bluetooth) it
> is never that dea
Hi Lennart,
>>> 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. Basical
On Fri, 26.09.14 16:28, James Lott (ja...@lottspot.com) 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 ethernet interfaces into the
On Thu, 25.09.14 10:21, Marcel Holtmann (mar...@holtmann.org) wrote:
> Hi James,
>
> > 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 ma
Figured out that 'ip link set netns ' works much the same as 'iw
phy set netns ', but I still can't seem to figure out what types
of interfaces --network-interface will accept. If anyone happens to have a good
example of how to use it, I would love to take a look at it.
> On Sep 26, 2014, at
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 ethernet interfaces into the container. I'm
getting the same error, so I presume it's for the same re
Shame on me for not spending more time trying to figure this out before
responding. Please ignore my previous sad plea for help, I understand fully
now exactly what you're saying, and was able to successfully move the phy0
interface into my container.
At this point, my challenge is going to be
Hi Zbyszek,
Thanks for all your help! This is a new concept to me though, as I have never
tried to refer to a process inside of a container from outside of the container
before (I did not realize this was possible). Since specifying PID 1 would
obviously be referring to the host system's init
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 | grep -v grep | grep systemd-nspawn
> root 143 0.0
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 | grep -v grep | grep systemd-nspawn
root 143 0.0 0.3 2884 728 ?Ss 08:42 0:00
/usr/bin/systemd-nspawn --netw
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 to run something like:
>
> iw phy phy0 set netns
>
> Unfortunately I'm having some trouble trying to figure out the network
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
Hi James,
> 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
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
15 matches
Mail list logo
