Two NICs, Two Networks through one Docker? Possible?

[TheBawse]

So I came across a video back in december from a YTuber name SpaceInvader One who did a video about using unraid as an IP camera system.  This particular video was about setting up the Shinobi IP camera app in a docker container to be configured either using a VLAN on a managed switch or through a 2nd NIC on a separate network from the main LAN with an un-managed switch.  I went with the latter as I already had a spare NIC and old un-managed POE switch.  I popped in my card and is now eth1 in unraid. As well as the switch and a test IP camera.  Unfortunately from there I've spent hours fiddling around with no success in getting Shinobi to work as it did in the YT video.  The video itself focuses more on setting up a VLAN instead of using a 2nd NIC. This setup was appealing to me as I liked the fact of having the non-name cameras not having direct access to my main LAN or the internet.

The problem I'm having is when after I install the docker container and go through the setup.  When I to open the WebUI, the browser won't connect to the IP i've set for eth1 / Br1.  When in bridge or host I can access Shinobi as I do with my other installed docker (Plex, Krusader, Cadvisor).  What am I doing wrong here?

 

 

 

Edited February 9, 2020 by TheBawse

[bonienl]

You created a second network 192.168.5.x. For Unraid to be able to reach this network, it will use your router (gateway) to get there.

 

In other words you must configure your router to participate and relay (route) between the two networks 192.168.0.x and 192.168.5.x

 

Another approach is to reserve eth1 solely for Docker containers and these containers reside in the same network as Unraid itself.

Do the following under Docker setttings (stop the Docker service):

 

1. Uncheck the assignment of eth0 (eth0 is not used for Docker)

2. Specify the assignment of eth1 as 192.168.0.0/24 with gateway 192.168.0.1.

3. Define a DHCP pool for br1 which does not conflict with your router's DHCP. Eg. 192.168.0.128/25

4. Give your container a fixed IP address, e.g. 192.168.0.10

 

[TheBawse]

Hi,

I don't want my dockers to be run through eth1, only specifically the Shinobi docker.  I have other dockers like PLEX that are accessible by several media devices in my home through eth0 that also need internet access.  I wanted a new separate network (eth1) through a 2nd NIC just for the IP cameras and have them isolated from all my devices and the internet of eth0.  I only wanted Shinobi to have access to eth1 through unraid and I would in turn block all devices of eth1 from seeing any network past unraid by blocking IP's in the Shinobi settings.  Sorry if I'm not making sense.  I've never been great with custom network setups but I hope this diagram I made might clarify what my end goal is.  Thanks for your help.

Edited January 31, 2020 by TheBawse

[bonienl]

36 minutes ago, TheBawse said:

I wanted a new separate network (eth1) through a 2nd NIC just for the IP cameras and have them isolated from all my devices and the internet

Do the following:

 

- In network settings assign eth1 with address 192.168.5.1 /24 and NO gateway

- In docker settings check the eth1 network (no modifications required)

- In docker settings: Enable host access to custom networks

- Configure your docker container to use br1 and a fixed address, e.g. 192.168.5.10

 

[TheBawse]

On 1/31/2020 at 11:31 AM, bonienl said:

Do the following:

 

- In network settings assign eth1 with address 192.168.5.1 /24 and NO gateway

- In docker settings check the eth1 network (no modifications required)

- In docker settings: Enable host access to custom networks

- Configure your docker container to use br1 and a fixed address, e.g. 192.168.5.10

 

Thanks Craftsman.  I finally found time to try the settings in your post.  I still cannot get it to work.  This issue I'm now having is when I start the docker and click to open the WebUI.  The browser times out on the set IP address (192.168.5.3:8080) and the shinobi login won't come up.

 

 

Edited February 9, 2020 by TheBawse

[TheBawse]

bump

[PackMwM]

I'm having the same issues. I'm wondering if you ever found a solution?

[TheBawse]

Hi,

Nope.  I continued searching for answers on the forum but to no avail.  I eventually gave up and haven't looked at giving another shot since.

[jamesbaker]

You have to install the FireFox docker on Unraid.

Then use that to connect to the Webui of the dockers you connected to your secondary lan.

 

This works if you add the second lan as a "ip4 custom network" and set "Host access to custom networks: Enbled" in the Docker setting.

Edited June 27, 2020 by jamesbaker