Incorrect local IP on WAN IP change

[bkai 2]

I noticed something strange the last few days when my WAN IP address changed (twice, which causes my local devices to lose an IP because of a script I have that automatically reboots the modem and the router).  The server automatically assumed my local IP was in the 10.0... range, which it is not (should be 192.168... range).  I tried rebooting the Emby server with no change and I tried rebooting my Shield TV to see if maybe it would pick it up or somehow get the server to recheck the IP.  I didn't try to reboot my physical server (I probably should have) but clearing app cache on the Shield seems to have worked.  I'll be honest though, I didn't recheck the server IP after I got it working on the Shield.  In the network settings on the Emby server I have the IP address field left blank as it is supposed to be optional.   When my WAN IP changed a second time I decided to simply add my local IP in this field and that got it working just fine.  So my question is: is there an issue with the Emby server defaulting to a 10. address when a local IP becomes unavailable and then for some reason not wanting to clear that out when a local IP address becomes available?

[Luke 42093]

Hi, it doesn't default to a 10 address, rather it queries the system for network interfaces and gets their ip address. 

[bkai 2]

Ok, so why would mine be sticking with a 10. address?  I've never used this range and when I check the local IP, it returns a 192. range.  I don't mind statically defining this IP in Emby settings, I just found it very strange that it would pick up a 10. address.

EDIT: I might have found where it's grabbing the 10. address from... I have a DockerNAT defined in my IP configuration using 10. but I don't have docker running on this machine currently and have never set up Emby in Docker on here either.  However, this DockerNAT entry is first in my IP configuration list.  So it would seem that for whatever reason Emby is picking this up instead of my default Eth3 entry.  Does this sound right?

Edited September 23, 2020 by bkai

[Luke 42093]

Yes that could be right.

[bkai 2]

I'm guessing my best option at this point would simply be to just get rid of this DockerNAT entry then... not sure when/if I'll ever use Docker on it in the future but I guess I can worry about that when it happens.

[Luke 42093]

That would seem to make sense to me, but of course you can also just set it in emby like you've figured out.

[bkai 2]

Yeah, that too.  Guess I could make that IP static for this machine

[Carlo 4561]

3 hours ago, bkai said:

I'm guessing my best option at this point would simply be to just get rid of this DockerNAT entry then... not sure when/if I'll ever use Docker on it in the future but I guess I can worry about that when it happens.

Your best option would be to assign an IP to each machine or device and not rely on DHCP.  I'd do this especially for your Emby Server machine and any NAS storage boxes.  You can do the same for other devices but not as important as your "infrastructure" boxes.

Next best is to assign reserved addresses in DHCP.