Force local IP

[Ebuechner]

I've had a situation arise a few times where I lose the internet on my home network. I traced it down to the computer that I use for sequencing which most times I don't close xlights. A lot of times when I'm done sequencing I just save and walk away leaving xlights open. I have 2 ethernet cards running in the same computer one for the home network one for the lights. Everything in xlights is set for unicast so I'm a little confused why I see data output going into the home network loading it down. I used the force local IP and it seems to cure the problem but I'm asking questions in case there's something that I missed. Home network IP 192.168.1.6 ethernet card for the lights set to a static IP of  193.161.1.10

[keithsw1111]

Not sure why Windows doesn't send the data to the controller that is obviously on the right subnet.

[Gilrock]

A so what if xlights was transmitting on your home network that shouldn't be able to shut down your internet.

[Ebuechner]

I don't get how it's locking up the internet either. You're right it shouldn't be able to generate enough traffic to do that.
On two occasions I've had my internet completely locked up first time I unplugged that computer from the home network to cure it. The second time I shut down xlights. After I reopened it and turned on light control I saw outgoing activity in task manager on that ethernet connection.
Then I turned on force local IP which got rid of that activity completely. I'm still not sure if that was The Cure but it definitely is coming from that computer.