Greetings, Mark Constable!
> On 5/5/18 5:43 PM, Janjaap Bos wrote:
>> To be able to ping a container macvlan interface, you need to have a
>> macvlan interface configured on the host.
> Thank you for the host macvlan snippet but I CAN actually ping the
> container from the host (but not the host
On 5/6/18 4:04 AM, Michel Jansens wrote:
how come I can ping the container from my host when I just set up
that container using macvlan?
Well, on my system with latest install of Ubuntu 18.04 and LXD 3.0,
the host can’t reach a container in macvlan setup. the container
can’t connect to the
Well, on my system with latest install of Ubuntu 18.04 and LXD 3.0, the host
can’t reach a container in macvlan setup. the container can’t connect to the
host either.
on a bridged network, it works.
Michel
> On 5 May 2018, at 12:30, Mark Constable wrote:
>
> On 5/5/18 5:43
On 5/5/18 5:43 PM, Janjaap Bos wrote:
To be able to ping a container macvlan interface, you need to have a
macvlan interface configured on the host.
Thank you for the host macvlan snippet but I CAN actually ping the
container from the host (but not the host from inside the container)
and that
To be able to ping a container macvlan interface, you need to have a
macvlan interface configured on the host.
Such as:
modprobe dummy
ip link set name dummy-mv dev dummy0
ip link set dev dummy-mv up
ip link add link dummy-mv mv-lxd type macvlan mode bridge
ip address add
Has something changed re networking with LXD 3.0 such that when
using a macvlan that the host CAN ping a container?
According to what I previously understood, and supported by this
comment..
https://github.com/lxc/lxd/issues/3871#issuecomment-333124249
and the main reason I hadn't bothered even