Return to Question

I am trying to get a macvlan network to work on Docker. It has been deployed properly, but I cannot get it to be accessible. See related question by me on Server Fault.

I have tried deploying it on my laptop, desktop and on an Oracle VM. I have tried activating promiscuous mode everywhere with sudo ip link set promisc on and also in my VM's settings. Also turning it on simultaneously for the host, the VM and the docker adapter.

An unexpected behaviour I have noticed reading the output of docker network ls is that the containers won't get a mac address unless I manually assign them one.

Nothing has worked. Also, sometimes, I inspect the network with ip -d link and promiscuous mode has a "2" instead of a "1" next to it. I don't know why that would be the case.

I have tried looking up whether my wireless card on my laptop is able to do promiscuous mode at all, but I cannot find relevant information online. Is there a reliable way to find out whether my network cards are capable of using it or not?

I should also mention, that the same behaviour happens when I tried through a wired connection.

I am trying to get a macvlan network to work on Docker. It has been deployed properly, but I cannot get it to be accessible. See related thread by me on Server Fault.

I have tried deploying it on my laptop, desktop and on an Oracle VM. I have tried activating promiscuous mode everywhere with sudo ip link set promisc on and also in my VM's settings. Also turning it on simultaneously for the host, the VM and the docker adapter.

An unexpected behaviour I have noticed reading the output of docker network ls is that the containers won't get a mac address unless I manually assign them one.

Nothing has worked. Also, sometimes, I inspect the network with ip -d link and promiscuous mode has a "2" instead of a "1" next to it. I don't know why that would be the case.

I have tried looking up whether my wireless card on my laptop is able to do promiscuous mode at all, but I cannot find relevant information online. Is there a reliable way to find out whether my network cards are capable of using it or not?

I should also mention, that the same behaviour happens when I tried through a wired connection.

I am trying to get a macvlan network to work on Docker. It has been deployed properly, but I cannot get it to be accessible.

I have tried deploying it on my laptop, desktop and on an Oracle VM. I have tried activating promiscuous mode everywhere with sudo ip link set promisc on and also in my VM's settings. Also turning it on simultaneously for the host, the VM and the docker adapter.

An unexpected behaviour I have noticed reading the output of docker network ls is that the containers won't get a mac address unless I manually assign them one.

Nothing has worked. Also, sometimes, I inspect the network with ip -d link and promiscuous mode has a "2" instead of a "1" next to it. I don't know why that would be the case.

I have tried looking up whether my wireless card on my laptop is able to do promiscuous mode at all, but I cannot find relevant information online. Is there a reliable way to find out whether my network cards are capable of using it or not?

I should also mention, that the same behaviour happens when I tried through a wired connection.

I am trying to get a macvlan network to work on Docker. It has been deployed properly, but I cannot get it to be accessible. See related question by me on Server Fault.

I have tried deploying it on my laptop, desktop and on an Oracle VM. I have tried activating promiscuous mode everywhere with sudo ip link set promisc on and also in my VM's settings. Also turning it on simultaneously for the host, the VM and the docker adapter.

An unexpected behaviour I have noticed reading the output of docker network ls is that the containers won't get a mac address unless I manually assign them one.

Nothing has worked. Also, sometimes, I inspect the network with ip -d link and promiscuous mode has a "2" instead of a "1" next to it. I don't know why that would be the case.

I have tried looking up whether my wireless card on my laptop is able to do promiscuous mode at all, but I cannot find relevant information online. Is there a reliable way to find out whether my network cards are capable of using it or not?

I should also mention, that the same behaviour happens when I tried through a wired connection.

I am trying to get a macvlan network to work on Docker. It has been deployed properly, but I cannot get it to be accessible.

I have tried deploying it on my laptop, desktop and on an Oracle VM. I have tried activating promiscuous mode everywhere with sudo ip link set promisc on and also in my VM's settings. Also turning it on simultaneously for the host, the VM and the docker adapter.

An unexpected behaviour I have noticed reading the output of docker network ls is that the containers won't get a mac address unless I manually assign them one.

Nothing has worked. Also, sometimes, I inspect the network with ip -d link and promiscuous mode has a "2" instead of a "1" next to it. I don't know why that would be the case.

I have tried looking up whether my wireless card on my laptop is able to do promiscuous mode at all, but I cannot find relevant information online. Is there a reliable way to find out whether my network cards are capable of using it or not?

Also, I am new to this. Should maybe the router also be configured to accept promiscuous mode? I haven't found any setting that indicates so.

I am trying to get a macvlan network to work on Docker. It has been deployed properly, but I cannot get it to be accessible.

I have tried deploying it on my laptop, desktop and on an Oracle VM. I have tried activating promiscuous mode everywhere with sudo ip link set promisc on and also in my VM's settings. Also turning it on simultaneously for the host, the VM and the docker adapter.

An unexpected behaviour I have noticed reading the output of docker network ls is that the containers won't get a mac address unless I manually assign them one.

Nothing has worked. Also, sometimes, I inspect the network with ip -d link and promiscuous mode has a "2" instead of a "1" next to it. I don't know why that would be the case.

I have tried looking up whether my wireless card on my laptop is able to do promiscuous mode at all, but I cannot find relevant information online. Is there a reliable way to find out whether my network cards are capable of using it or not?

I should also mention, that the same behaviour happens when I tried through a wired connection.