UDP output set to send data to myself error

[mrgimmeone]

I'm trying to get my show going this year but i'm getting this error and I have no output to any of my lights at all. This happened after an SD card failure an redownload and setup of a new FPP instance. My tune to sign works fine but my show PI isn't outputting to lights. Anyone else ever have this issue?

[MikeKrebs]

Check your outputs and turn off any that are not correct.

[mrgimmeone]

they are all correct. I think it may be the way my network is setup on my F48 since ISP change to a different company. they use .4.xxx - .7.xxx as usable networks an my old ISP only used .1.xxx. i had the F48 set to .100.xxx with the 255 subnet. i changed the subnet to the 252 which my current ISP uses and still nothing so i'm wondering if i need to change the F48s ip to one of the other networks available so it will output.

[Poporacer]

they are all correct.

If you are getting that error, then they are not correct. Make sure that in the outputs you don't have an IP listed for this device. 
In xLights make sure that any FPP based controller has the active status set to xLights Only.
How about some screenshots, like your networking pages in FPP and your controller.

i had the F48 set to .100.xxx with the 255 subnet. i changed the subnet to the 252 which my current ISP uses

But does that put it in the same subnet as your ISP?

[mrgimmeone]

network screen for fpp.

[mrgimmeone]

You cannot view this attachment.xlights screen.

[mrgimmeone]

output page

[Poporacer]

On your eth0 interface on your Pi, turn off the forwarding and then the update button. 
On your wlan0 interface, set the IP forwarding to Masquerading/NAT and then the update button.
Reboot the PI and see if you are still getting the error

[mrgimmeone]

yes. the error is still there. dunno if it matters but the eth0 address is the ip address for my F48.

[Poporacer]

dunno if it matters but the eth0 address is the ip address for my F48.

That is exactly the problem, every interface needs its own IP address. So your output "looks" like it is sending data to the F48, but it is sending it to itself. You need to change one of them to a different IP

[mrgimmeone]

it is odd considering the falcons address of 192.168.100.205 and the eth0 on pi was same address and it worked fine for 8 years set that way. has something changed where the ip for eth0 on pi needs to be different from the ip of falcon controller? if so i'm completely lost on how all the ips need to be set now. when i hit play on fpp there's no activity from ethernet port on pi while plugged to pi and controller.

[Poporacer]

it is odd considering the falcons address of 192.168.100.205 and the eth0 on pi was same address and it worked fine for 8 years set that way

This will usually cause very slight to major lag or jitters, but you probably didn't notice it.

has something changed where the ip for eth0 on pi needs to be different from the ip of falcon controller?

No, this has been the rules for networking since it was created. There were many people having problems with their show because of this mis-configuration and that is why the developers added the warning message. That warning message is somewhat new.

if so i'm completely lost on how all the ips need to be set now.

Just change the eth0 IP address to anything else. Maybe 192,168.100.200?

when i hit play on fpp there's no activity from ethernet port on pi while plugged to pi and controller.

Did you read the last part of that error message?

[mrgimmeone]

if i change the eth0 to .200 and then ping it i get 100% packet loss. if i leave it on .205 i get 0% packet loss.

[mrgimmeone]

i think i got it working now i hope. it's all disconnected from the light as i was test this but the ethernet ports are blinking with activity now. i won't be able to check this till i get home tomorrow but if it is thank you so much for your help.