Quote Originally Posted by Moorea View Post
Problem 1
--------------
Step 1: 2 computers A and B; B sharing the A's internet connection (Windows built in ICS feature, need 2 interfaces)
Step 2: start mojo on both
Step 3: on A (the computer which has 2 ips) you'll get a black screen for the B mojo
Step 4: on A go to advanced connection settings; pick 192.168.0.1 instead of "let the operating system choose"
Step 5: 2 mojos are now blue on both A and B and everything now works (which shows it's "fixable")

The bug is step 3 and the need for step 4

My personal opinion again on the fix is that sending both IPs in the UDP packet and having the slave try the second one if the first one doesn't succeed would fix it easily and simply with no downside I can see


Problem 2
--------------
Step 6: Add a 3rd computer C on the "internet" side of A (ie not on same network as B)
Step 7: Start Mojo on C: C is yellow picture (in computers section) and purple text (in geeky stuff section) on A - 3rd column of text shows "C" (B is still blue with "AC"); A is yellow on C; B's screen shows A,B blue unchanged (doesn't see C which is normal)
Step 8: pick the other IP; C becomes blue too

So here again, trying both automatically will fix the problem - More work (and not necessary imo; would introduce complexity), i.e write a proxy, would be needed for C to see B and B to see A (proxied through A)


Diagram

B --------------------> A (ICS share) -------------> C
"private ICS side" ................... "internet side"
(aka 'inside') .............................(aka 'outside')

internet side isn't really the internet; just another network that's not the ICS private one and happens to also have the router to the actual internet


If problem 2 is confusing - just look at problem 1 as fixing it will fix both

Note btw this problem is not specific to ICS - any computer with 2 interfaces where you can't route/access 1 of the IP from the other side will have the exact same problem (ie will advertise the same IP on both side which won't work on one of the network, with again an ez fix (a cleaner fix would actually be to get the IP of each interface and broadcast separately but that's more work and unnecessary)


Thanks

ps: It's 3am here so hopefully this is clear enough - and if not - well I'll try again some other day as I need sleep now
Thank you very much for taking time to explain this clearly. This is what I needed in the first place. All the time we spent going back and forth about this last night -- what a waste.

Here's my summary of what happened. Please correct me if I misunderstand.

You had to adjust a setting manually (using the drop down list) to make the computers connect.

After you adjusted the setting by clicking on a drop down list, the program worked perfectly.

You're calling that a bug.

That's my summary. Is that correct?

Please let me know if the program worked perfectly after you clicked on the drop down list. I need to know. Thank you.