Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
Well...after starting Pixie(on Linux host) with command rndr -r 24666 i get message:"Active at 192.168.1.3:24666". But net scanning show that Pixie use(send and listen) 127.0.0.1. Under Windows Pixie use 192.168.1.2 and net scanning show that net messages come to Linux host. Luxrender on the same port and IP addresses work good(i use it to check out net rendering capability). I get confused.
On my FreeBSD host where I compiled from source pixie 2.2.5, I don't have that issue.
rndr -r 24666 says it's active on my main IP, but actually it's supposed to be listening to every IPv4 on every interface (line 489 of rndr.cpp), and indeed I can connect with it either through the loopback 127.0.0.1 or through the network interface (from a distant computer).
I don't know what kind of net scanner you are using, but from the source it's normal that pixie listens on 127.0.0.1, and maybe your scan is missing that pixie also listens on other interfaces.
I use Wireshark. Scanner run under Linux(192.168.1.3). On the Window host(192.168.1.2) i type "rndr -k 192.168.1.3:24666". Scanner capture packets on eth0 from 192.168.1.2. The same command on Linux host "rndr -k 192.168.1.2:24666" - and eth0 is clean. All messages are registering on 127.0.0.1.
I give up. Exactly just right now i've tested net rendering with Indigo - it's work. May be i must recompile Pixie with some mysthical power switch? something like "make --please-give-me-net-rendering"? Please, some Linux net guru say something.