Relay

[Placemate]

"In preparation for version 1.00, we will be extending the Relay capability to allow networking."

Just curious on the status/eta for this.

[Lax]

The best I can tell you at the moment is it's in development, and is expected in the next few updates

[Placemate]

Woot, I see you added this feature, but I'm having a little trouble getting it working.

First I changed the XML to
<Set ID="3" Name="Remote">
<Setting Name="enable incoming">1</Setting>
<Setting Name="incoming port">10101</Setting>
<Setting Name="name">Dually</Setting>

and restated InnerSpace.

Then I did .. from another machine
Uplink RemoteUplink -connect 192.168.1.143


Then I Typed
Uplink Sessions

and it showed
is1
Dually.is1

so then I tried
uplink relay Dually.is1 "echo HI"
and that does nothing.

uplink relay is2 "echo hi"
will work for me, btw.

Thoughts?

[Lax]

I had tested this and it worked fine at the time I may have only tested one direction though. Two questions...
1. Is Name set in BOTH files?
2. Have you tried both directions, or just one?

[Placemate]

Ya the other Computer I tried naming "main" and "beef"

I've tried both directiions and neither work.

[Lax]

Fixed (hopefully) in version 0.96 build 2110. Please let me know if you still can't get it to work properly

[Placemate]

Well.

I got it to work kinda.

I loaded up one session in each computer and got nothing. But when I loaded a second session on one and did a "relay all" it did nothing is is1 but worked in is2.

I think I'll try reinstalling innerspace to see if that helps.

[Placemate]

Ok here is what I figured.

First I reinstalled Innerspace and it wouldn't even connect.
Then I figured out I needed to change

<Setting Name="enable">1</Setting>

to

<Setting Name="enable incoming">1</Setting>

Looks like the default XML got messed up.

Second I started up and connected fine, but it wouldn't relay. I loaded up 2 sessions on one machine and the second one would relay. I logged off all then loaded one session on each machine and it WORKED! It looks like it remembers old connections and if you start a sessions with a connect already existing it will work.

[Lax]

Ah, yep. The InnerSpace.xml setting name was wrong if InnerSpace.xml did not previously exist. And that probably contributed to the problem

When it wouldnt relay currently (not before the patch), could you use the "sessions" uplink command and see the session(s) it wouldnt relay to?

[Placemate]

Yes. When you connect for the first time it will show the remote session but won't relay to it. However when you load up your sessions and a connection already exists, it will both show the remote connection and relay works.

[Lax]

Gotcha. Verified this, will see what I can do.

[Lax]

All fixed in next build. Thanks for your patience, and for the help tracking bugs down

[Placemate]

No problem, thanks for the great feature.

[Placemate]

Unfortuately this still doesn't seem to be working quite right for me.

With Beta 0.96 Build 2128 I still can't relay with pre-existing sessions.

Also I've been playing around with more than 2 computers too.

Today I tested it with 4 and this is what happens

Had one computer connect to the other 3 so "uplink sessions" looks like this:
Inner Space sessions
-----------------------
is1
Dually.is1
Gamer.is1
Dying.is1

The other computer all looked like this

Inner Space sessions
-----------------------
Beef.is1
is1


-Now with pre-existing sessions nothing works


The follow for sessions loaded after the connection
- On Beef (The one connected to everything) Only is1 and Dually.is1 relays
- On the other 3 computers relay works for the is1 and beef.is1

Next I went to Dually and connected it to Gamer and restated the sessions
-Now those 3 will relay to each other
-Beef still can't relay to Dying

Finally I connect Gamer to Dying and Dually to Dying and restarted all 3
- Now everything will talk to each other

[Lax]

I will revisit this over the weekend, have to help my sister move tomorrow though.