VLANs, Containers, and IPs - DHCP address issues

[BurntOC]

I'm finally starting to  get momentum in my move to Unraid, and hardware-wise my box is pretty well set up where I want it to be.  I've started moving media into my shares and adding containers, but I can't seem to get the networking side sorted out.  I'm trying to set up some of my containers (Plex, Jellyfin, Sonarr, etc.) in a VLAN separate from my PRIVNET VLAN which Unraid is on (VLAN 30), and I was thinking I'd have them grab IPs from my GUEST network of 192.168.60.0/24 (VLAN 60). 

 

The Unraid server seems to grab a secondary IP of 192.168.60.30 from my pfSense DHCP server just fine.  But when I set up the containers to use the custom VLAN 60 bridge of br0.60 with automatic IP allocation they get a different 192.168.60.0/24 IP and it's not coming from my pfSense DHCP server.   Maybe the Unraid server is creating and using it's own DHCP pool for this even though I've not told it to do so?

 

I've checked the switch port and it has VLAN 30 untagged and VLAN 60 tagged as needed.  I imagine I'll get into reverse proxy and such at some point to simplify some things, or using Heimdall or Organizr, but I need to nail down what's going on here first.  I don't like not knowing where that IP address is coming from, and the potential additional NAT considerations it may portend.  

 

Can someone help me sort out what's going on here?  I've been searching here, Reddit, and other places but I can't find anyone that really goes into why the IP behavior is what it is.  

 

I guess the absolute key question is - with a single physical interface and Unraid server, how do I get some containers and VMs to grab IPs from my DHCP server in their specified networks and VLANs, as the pfSense box, switches, etc. are ready to go and supporting this in other areas of my network?

 

 

 

 

 

Edited July 13, 2020 by BurntOC
clarification

[civic95man]

Sounds like the IP is being handed out by the docker network system since you have automatic assignment selected.

[BurntOC]

15 minutes ago, civic95man said:

Sounds like the IP is being handed out by the docker network system since you have automatic assignment selected.

Ah, yes, that makes sense.  Isn't there a way to have the container grab an IP from my pfSense server?  I have been able to grab IPs for various VLANs on my VMs in the past, but that was a long time ago and I don't recall having to do anything special.  I don't know if this is an Unraid limitation or something else. 

[civic95man]

2 minutes ago, BurntOC said:

Isn't there a way to have the container grab an IP from my pfSense server?

no, not that I know of. But you can manually assign one

3 minutes ago, BurntOC said:

have been able to grab IPs for various VLANs on my VMs in the past

Because the VM is grabbing it, not unraid

 

As far as I know, it would be a limitation of the Docker system

[BurntOC]

Thanks.  You're correct.  I look forward to someday having a DHCP client that the Docker system can leverage to support external DHCP servers. Until then I'll make some changes to my strategy.  Thanks agin.