Is it possible to have a device from one interface to have an ip on another interface?

Fandangos

I was finally able to figure out how to setup VLANs here and I'm very satisfied with my setup still I'm trying to figure out how to do this:

I have an Unraid NAS running several services as docker containers.
I'm able to assign dedicated ips to those containers.
Example Gerbera DLNA Server for music have the ip address 11.22.33.190 as an example.

But I want to access it with my Android phone and many apps do not include any way to manually add this IP when you are connected in another network like my WIFI network that uses a different port and has a different range of IPs.

I already tried adding rules to allow this ip on my firewall but what I need is that the container shows up in another interface, not sure if possible at all.

So long story short, is it possible to have 11.22.33.190 to show up as 192.168.10.190 ?
And one more question, some IPs do not register on PfSense DHCP leases.

My router web ui , this docker container.
I can ping and access those from my PC but those are not present.
11.22.33.190 is not present on DHCP leases.

Could this be related?

Thanks once again for allowing me here posting some noob questions.

viragomann

@Fandangos
DLNA basically requires that the server and client are within the same L2 subnet to work. The protocol uses broadcasts to connect, which don't pass a router.
However, users wrote here, that they got it work across pfSense with the PIMD package:
DLNA over VLAN: A how (not?) to

I didn't try that, however, since as I set up my DLNA server, this was not an official pfSense package yet.

My DLNAs run in LXC containers and I bridged its virtual networks on pfSense, e.g. to the IoT VLAN, where my TV resides, so I can watch videos from the DLNA.

In your case, this would mean, you should separate the DLNA containers network first and connect it to a VLAN. Don't know if this is possible in Unraid. This VLAN can be bridged on pfSense then to where you need the DLNA.

11.22.33.190 is not present on DHCP leases.

Does the container pull its IP even from the DHCP?

Fandangos

Does the container pull its IP even from the DHCP?

@viragomann, no I set it up manually on the docker container.
So if an IP is not set up by DHCP it will not show up at DHCP leases. Makes sense.

I'm reading on PIMD but what you mentioned about a VLAN for docker containers seems way more useful than that but how is it possible?

When I'm doing a VLAN here, I have a smart managed switch that will tag the port connecting to PfSense and tag the ports I'm using to connect my devices to it.

Are you saying it's possible for a docker container when in Custom Br0 mode, which is the mode unraid uses, to give a dedicated ip address to a container also be tagged to be able to create a VLAN of containers?

The thing is, my Unraid server has tons of micro services, also VMs, SMB, NFS... I don't want to expose that to WIFI VLAN, only DLNA and Emby which wasn't a problem because I can manually set the desired ip address on the client side.

EDIT: Found it https://forums.unraid.net/topic/117906-how-to-assign-a-docker-to-a-vlan/

It will not work for me since I'm using a 2.5 gigabit unmanaged switch on the PfSense interface that my unraid nas Is connected to.

Isn't it possible to create virtual IP and NAT it somehow?

viragomann

@Fandangos said in Is it possible to have a device from one interface to have an ip on another interface?:

no I set it up manually on the docker container.
So if an IP is not set up by DHCP it will not show up at DHCP leases. Makes sense.

Exactly. You can see the IP in Diagnostic > ARP table, however, after a communication with it for 20 minutes.

If your intention is to use its host name to access it add a host override to your local DNS.

When I'm doing a VLAN here, I have a smart managed switch that will tag the port connecting to PfSense and tag the ports I'm using to connect my devices to it.

No, the VLAN has to be terminated on Unraid and pfSense. If there is a VLAN-capable switch in between both ports need to tag the packets with the proper VLAN tag.

Isn't it possible to create virtual IP and NAT it somehow?

NAT = translate the IP from one L2 subnet into another one.
As I wrote in my very first setence, DLNA requires both, server and client to reside within the same L2.