Build 19: Active window tracking

[Moorea]

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

[Aragent]

This is a know problem with Windows ICS.

ICS is Windows Native Nat Router software. {Last I checked ICS does not use a standard NAT trasnlation]

What Moorea is experiancing is that his one machine that he is using to Route out to the internet must have 2 IP adresses. one recived by his IP provider to go out to the internet, and a internal private address which his network uses.

On that one machine that is acting as his router Mojo is finding and using the IP provided by his IP provider, and not his internel private address. thus Mojo on that maching is not conecting properly to the other till he goes in and tells that mojo to use the private network.

I suppose to fix that you could put in an algorithm to priortise a private network befor a standard network ip.

However ICS is not considered very efficent Nat Router software so not sure how many serious Multi boxers will use ICS [Internet Conncetion Sharing]

And this can allready be solved on that one pc by going under MOJO connection settings under more optiens and add the private network this then should make it use that network as default.

[Moorea]

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

[...]

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)

Aragent, Fur ^^^

[Aragent]

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)

True But thats pretty standard in Subnetwork protocol. and normmaly when you want it to pass you setup addvanced network Rounting and port forwarding. but now your getting into more advanced networking, and Those who use subnetworking should be a bit more advanced than the average user and shouldn't have problems with changing the ip address under mojo.

[Freddie]

You guys are assuming that the OS always picks the "wrong" IP address in this situation.

Do you have some basis for believing that the OS's algorithm works this way?

[Aragent]

You guys are assuming that the OS always picks the "wrong" IP address in this situation.

Do you have some basis for believing that the OS's algorithm works this way?

I havent looked at what your using for a discovery protocol, I am making a couple assumptins here. and I will try to look latter and see what MOJO is acually using.

I am assuming your using DHCP discovery when detecting network addresses and UDP ARP for detecting other running Mojo clients.

Last I looked it was standard when discovering 2 Network IP's especially on one network card, to give Priorty to a Public IP address over a Private one.

I Might have a couple suggestions however I think I should try and see if I can find the accual Code first befor I do.

[Freddie]

I havent looked at what your using for a discovery protocol, I am making a couple assumptins here. and I will try to look latter and see what MOJO is acually using.

I am assuming your using DHCP discovery when detecting network addresses and UDP ARP for detecting other running Mojo clients.

Last I looked it was standard when discovering 2 Network IP's especially on one network card, to give Priorty to a Public IP address over a Private one.

I Might have a couple suggestions however I think I should try and see if I can find the accual Code first befor I do.

I explained what it does earlier in the thread. It broadcasts a UDP datagram. It doesn't use DHCP. It doesn't detect network addresses. It doesn't look at the network in any way.

The only thing it does with addresses is ask the operating system for a list of IP addresses that belong to the PC it's running on.

If you want to look at the code, it's in class cFinder in the mojo_engine project.

If you want to understand the whole connection mechanism, you'll also have to look at class cPool, which handles TCP communications.

[Freddie]

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.