>
> The only thing that still works is phys, at least in Vmware virtual
> machines and the new kernel 5.0X
Any idea how can we make macvlan work again?
> Philip
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.
Greetings, Michel Jansens!
> In the case of LXD, I suppose the macvlan bridge mode is used?
Last I checked, no. By default, LXC/LXD did not use macvlans.
> It also mentions that although VMs cannot directly communicate with the
> host, you can add another macvlan sub-interface and assign it to t
On Fri, May 4, 2018 at 10:34 AM, Michel Jansens
wrote:
> Hi,
>
> I just stumbled on this site and thought it would be nice to share:
>
> https://hicu.be/bridge-vs-macvlan
>
> It nicely explains how Macvlan work and how it compares with normal bridges.
> In the case of LXD, I suppose the macvlan br
s.linuxcontainers.org] On Behalf
>Of Michel Jansens
>Sent: Friday, May 04, 2018 9:34 AM
>To: LXC users mailing-list
>Subject: [lxc-users] Macvlan explained
>
>Hi,
>
>
>I just stumbled on this site and thought it would be nice to share:
>
>https://hicu.be/bridge-vs-m
Hi,
I just stumbled on this site and thought it would be nice to share:
https://hicu.be/bridge-vs-macvlan
It nicely explains how Macvlan work and how it compares with normal bridges.
In the case of LXD, I suppose the macvlan bridge mode is used?
It also mentions that although VMs cannot directl
I clearly need to take a step back and make sure my user's in the lxd
group and the "my first container" demo
https://www.stgraber.org/2016/03/19/lxd-2-0-your-first-lxd-container-312/
works. It doesn't here anymore. Having polluted two ubuntu 16.04
systems here,
I'm going to head back home where
I'm playing with macvlan, too, which is a challenge as I am quite
ignorant about it, bridges, and lxc.
Novice gotchas so far:
- I have to run lxc under sudo (I think?), and after I do that,
.config/lxc is owned by root, and I can't even do lxc --help :-(
- I keep typing lxc when I mean lxd and vic
tainers.org"
Subject: [lxc-users] Macvlan setup issues
Hi all. I'm really new to LXC/LXD as well as with macvlan setup, so bear
with me. I'm having all kinds of trouble getting the macvlan setup to work
on my Ubuntu 16.04 VM. The documentation isn't terribly clear, or at
On Fri, Apr 29, 2016 at 7:39 PM, Mark Haney wrote:
> Well, as this is a VM running on an ESXi 6 cluster, I'm having a hard time
> believing that would be the case. However, just to make certain, I've
> created the bridge manually and still have the same problem. If our
> switches (Cisco 3750s) h
Well, as this is a VM running on an ESXi 6 cluster, I'm having a hard time
believing that would be the case. However, just to make certain, I've
created the bridge manually and still have the same problem. If our
switches (Cisco 3750s) had issues with running multiple MACs on the IBM
Blade Server
On Fri, Apr 29, 2016 at 12:02 AM, Mark Haney wrote:
> Hi all. I'm really new to LXC/LXD as well as with macvlan setup, so bear
> with me. I'm having all kinds of trouble getting the macvlan setup to work
> on my Ubuntu 16.04 VM. The documentation isn't terribly clear, or at least
> it seems to
Hi all. I'm really new to LXC/LXD as well as with macvlan setup, so bear
with me. I'm having all kinds of trouble getting the macvlan setup to work
on my Ubuntu 16.04 VM. The documentation isn't terribly clear, or at least
it seems to be missing something that is keeping my containers from being
On Mon, Jun 1, 2015 at 8:10 PM, Dave Smith wrote:
> I never
> could fine anything on a bridgeless veth setup and I would be curious to
> read about this. If someone could point me to the link that would be great.
https://lists.linuxcontainers.org/pipermail/lxc-users/2015-February/008553.html
Re
For those googling later , if you are using macvlan the IP has to be on the
same subnet as the "host device" which was not the case. I ended up using
a bridge with an non public IP as suggested and that worked fine. I never
could fine anything on a bridgeless veth setup and I would be curious to
r
On Sun, May 31, 2015 at 3:22 AM, Dave Smith wrote:
> I am trying to setup a public IP via macvlan to a container. The host has a
> public IP and then 2 extra static public IP's on one physical interface
> (bond1) that is assigned to it by my upstream vendor. In my config I have
Did your upstream
I am trying to setup a public IP via macvlan to a container. The host has a
public IP and then 2 extra static public IP's on one physical interface
(bond1) that is assigned to it by my upstream vendor. In my config I have
lxc.network.type = macvlan
lxc.network.flags = up
lxc.network.link = bond1
l
On Tue, Feb 24, 2015 at 11:50 AM, Serge Hallyn wrote:
> Quoting Fajar A. Nugraha (l...@fajar.net):
>> On Wed, Feb 18, 2015 at 12:27 AM, Serge Hallyn
>> wrote:
>> > Quoting Fajar A. Nugraha (l...@fajar.net):
>> >> # c1's veth name on host side
>> >> auto v-c1-0
>> >> iface v-c1-0 inet static
>> >
Quoting Fajar A. Nugraha (l...@fajar.net):
> On Wed, Feb 18, 2015 at 12:27 AM, Serge Hallyn
> wrote:
> > Quoting Fajar A. Nugraha (l...@fajar.net):
> >> # c1's veth name on host side
> >> auto v-c1-0
> >> iface v-c1-0 inet static
> >
> > I'm probably just ignorant here, but - does this not cause
On Wed, Feb 18, 2015 at 12:27 AM, Serge Hallyn wrote:
> Quoting Fajar A. Nugraha (l...@fajar.net):
>> # c1's veth name on host side
>> auto v-c1-0
>> iface v-c1-0 inet static
>
> I'm probably just ignorant here, but - does this not cause 'ifup -a' to
> fail when the containers are not up?
ifup th
Quoting Fajar A. Nugraha (l...@fajar.net):
> On Mon, Feb 16, 2015 at 9:52 PM, Serge Hallyn wrote:
> > Quoting overlay fs (overla...@gmail.com):
>
> >> > > However veth works
> >> > > just fine. And you don't have to put your public link (e.g. eth0) on
> >> > > bridge mode to have a working contai
On Mon, Feb 16, 2015 at 9:52 PM, Serge Hallyn wrote:
> Quoting overlay fs (overla...@gmail.com):
>> > > However veth works
>> > > just fine. And you don't have to put your public link (e.g. eth0) on
>> > > bridge mode to have a working container with veth network.
>> >
>> > FWIW what it would tak
Quoting overlay fs (overla...@gmail.com):
> Quoting Serge Hallyn (serge.hallyn at ubuntu.com):
> > On Thu Feb 12, 2015 at 11:18 Fajar A. Nugraha wrote:
> > > On Thu, Feb 12, 2015 at 5:29 PM, Purcareata Bogdan > > freescale.com> wrote:
> > > > On 10.02.2015 19:22, Christian Brauner wrote:
> > > >>
Quoting Serge Hallyn (serge.hallyn at ubuntu.com):
> On Thu Feb 12, 2015 at 11:18 Fajar A. Nugraha wrote:
> > On Thu, Feb 12, 2015 at 5:29 PM, Purcareata Bogdan > freescale.com> wrote:
> > > On 10.02.2015 19:22, Christian Brauner wrote:
> > >>
> > >> Hello,
> >> >
>> >> is it currently possible t
Quoting Fajar A. Nugraha (l...@fajar.net):
> On Thu, Feb 12, 2015 at 5:29 PM, Purcareata Bogdan
> wrote:
> > On 10.02.2015 19:22, Christian Brauner wrote:
> >>
> >> Hello,
> >>
> >> is it currently possible to use macvlan interfaces with unprivileged
> >> containers?
> >
> >
> > +1 I noticed too
On Thu, Feb 12, 2015 at 5:29 PM, Purcareata Bogdan wrote:
> On 10.02.2015 19:22, Christian Brauner wrote:
>>
>> Hello,
>>
>> is it currently possible to use macvlan interfaces with unprivileged
>> containers?
>
>
> +1 I noticed too that it wasn't possible. This might a limitation of the
> user nam
On 10.02.2015 19:22, Christian Brauner wrote:
Hello,
is it currently possible to use macvlan interfaces with unprivileged
containers?
+1 I noticed too that it wasn't possible. This might a limitation of the
user namespace itself, since the lower device you're attaching to is
still in the hos
Hello,
is it currently possible to use macvlan interfaces with unprivileged
containers?
Best,
Christian
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
> No, it shouldn't be the same.
>
> br0 -> bridge (on host)
> bond0 -> bond interface, which has eth0 as slave (on host)
> vethXXX -> veth interface for the container (on host)
> eth0 (on container) -> the pair of vethXXX on host
>
> Unless I misunderstood something?
This is correct except a min
On Mon, Sep 15, 2014 at 4:19 PM, Adam Gold wrote:
>> The "official" networking guide for lxc on Ubuntu :
>> https://help.ubuntu.com/14.04/serverguide/lxc.html#lxc-network
>>
>> At first glance your config looks correct, but the most obvious
>> possible source of problem would be "-i eth0". You sai
> The "official" networking guide for lxc on Ubuntu :
> https://help.ubuntu.com/14.04/serverguide/lxc.html#lxc-network
>
> At first glance your config looks correct, but the most obvious
> possible source of problem would be "-i eth0". You said that your
> public IP is now on br0. I'd try to remov
On Mon, Sep 15, 2014 at 3:34 PM, Adam Gold wrote:
>> Just a wild guess, I'm assuming macvlan has problems with bridge interface.
>>
>> Have you tried using a physical interface (e.g. eth0) as
>> lxc.network.link? Or better yet, since you already create a bridge,
>> use lxc.network.type = veth?
>>
> Just a wild guess, I'm assuming macvlan has problems with bridge interface.
>
> Have you tried using a physical interface (e.g. eth0) as
> lxc.network.link? Or better yet, since you already create a bridge,
> use lxc.network.type = veth?
>
I should give just a little bit more context. I'm try
On Mon, Sep 15, 2014 at 7:58 AM, Adam Gold wrote:
> Hello. I'm just starting to learn about containers so apologies for the
> basic question (I couldn't find an exact answer from my non-exhaustive
> review of the archives).
>
> I'm trying to create a private container network using macvlan
> inte
Hello. I'm just starting to learn about containers so apologies for the
basic question (I couldn't find an exact answer from my non-exhaustive
review of the archives).
I'm trying to create a private container network using macvlan
interfaces. I'm running ubuntu 14.04 on the host and on the conta
Quoting bogdan.purcare...@freescale.com (bogdan.purcare...@freescale.com):
> Hello,
>
> I'm running LXC 1.0 with a config file inspired from the lxc-macvlan.conf
> available in the repo. I get this error:
>
> root@sandbox:~# cat lxc-macvlan.conf
> # Container with network virtualized using the m
Hello,
I'm running LXC 1.0 with a config file inspired from the lxc-macvlan.conf
available in the repo. I get this error:
root@sandbox:~# cat lxc-macvlan.conf
# Container with network virtualized using the macvlan device driver
lxc.utsname = alpha
lxc.network.type = macvlan
lxc.network.flags = u
Quoting e (florian.engelm...@gmail.com):
> Hi,
>
> is it possible to use network type macvlan on tagged VLANs?
While I haven't used tagged VLAN's via the macvlan interface, I have
achieved something similar to this using a routing topology. This may
or may not be relevant to your needs.
>From t
that sounds very exciting! drop a line in the mailing list if you do
opensource some bits. Im trying out similar stuff but the HA layer is done
by L7 tools (mostly due to limitations imposed by public clouds and
latencies), also the tooling setup (including container management) is done
using chef.
Tangentially related story: I have a highly dynamic topology (many
VLANs created/destroyed frequently). I use the following structure:
Host = 2 x NICs, joined as 1 x bond0 interface with failover
VLANs = bond0 interface linked, negotiated dynamically based upon
requirements of hosted containers, a
Quoting e (florian.engelm...@gmail.com):
> Hi,
>
> is it possible to use network type macvlan on tagged VLANs?
Looks like noone has tried this. If you come up with an answer
please do report back as it'd be interestinng to know.
-serge
___
lxc-users m
Hi,
is it possible to use network type macvlan on tagged VLANs?
I tried it like this:
ubuntu host configuration:
auto lo
iface lo inet loopback
auto p3p3
iface p3p3 inet static
address 192.168.222.11
netmask 255.255.255.0
gateway 192.168.222.1
dns-nameservers 2xx.xxx.xxx.xxx 2xx.xxx.xxx.xx
41 matches
Mail list logo
