search

jpetazzo / pipework

Software-Defined Networking tools for LXC (LinuX Containers)
Apache License 2.0
4.22k stars 727 forks source link

Docker + plex + pipework , stuck with connection issues #17

Closed spiroid closed 4 years ago

spiroid commented 10 years ago

Hi,

First, thanks a lot for your work on pipework, it is great :+1: I wasn't sure on how to contact you about an issue with pipework in my specific situation so i ended up describing it in this github issue.

I'm working on a docker + plex image docker-plex. All the work on pipework integration is commited on a pipework branch in the git repository. As plex needs to access my local network i was trying to run my container with pipework to make an eth1 network interface with a private ip address in my local network.

However i didn't figure out how to make all pieces communicate.

  1. First i started my container with pipework --wait to wait for eth1 to become available before launching plex.
  2. Then i followed pipework readme file and on the host server i launched : sudo pipework wlan0 $CONTAINERID 192.168.111.16/24@192.168.111.254.

It exit successfully and the eth1 interface was set up with the given ip address. I also checked that the default gateway was correcly set which was the case.

However i couldn't make the container communicate with the outside world and with other computers on the private network. It wasn't reachable from other servers either. The only working network trafic was on the network set up by docker with the docker0 bridge (172.17.42.1 ip address on host).

Can you help me to make it all work ? Did i miss something here ?

jpetazzo commented 10 years ago

Since the interface name is wlan0, I suppose that this is some wireless LAN, right? If it is using some kind of encryption, it might be the reason why it doesn't work. Disclaimer: I don't know the WPA/WEP standards well enough to be 100% sure about that, but I believe that somehow, the MAC address is involved (at least for WPA), which means that if you are connected to a WPA-secured network, you cannot use bridging (unless you take special steps to ensure it works properly).

Can you test on a non-crypted network (or on a wired network)? If it works, then we will know that it is the problem, and can find a better solution. If it doesn't work, it means that it's something else :-)

spiroid commented 10 years ago

I tested with eth0 connected with an ethernet cable instead of the wireless connection. Unfortunatly i was stuck at the same point.

The eth1 interface in the docker container is successfully initialized and the default gateway was changed, but no way to see other devices on the same network. (tested ping and ssh)

jpetazzo commented 10 years ago

Hmm, unfortunately, this is the only setup that I can't replicate locally (by lack of physical machines to test with) :-(

Can you describe the local machines involved, how they are connected, etc., so that someone can reproduce? (Me, if I can get my hands on a couple of unused boxen :-))

jpetazzo commented 9 years ago

Closing older issues.