NetRemote errors in Gider om VM

[Mastiff]

I'm having these on my VM Girder:

EventHandler: ...ogram Files\Promixis\Girder5\luascript\NetRemote.lua:148 4: attempt to concatenate local `port' (a nil value)
stack traceback:
...ogram Files\Promixis\Girder5\luascript\NetRemote.lua:148 4: in function <...ogram Files\Promixis\Girder5\luascript\NetRemote.lua:148 1>


Any idea what's happening?

[Rob H]

I have noticed here that payloads to events seem to be shifted by one when using Girder2Girder.

The code in question is checking for the NR client closing :-


local ipAddress = params[1]
local port = tonumber(params[2])
NRFPrint('Connection closing '..ipAddress..':'..port)

If the parameters are shifted then params[2] will actually be the IP address/host name. Converting that to a number would result in port being nil.

The solution would be to not forward the events 'New Client Connection' and 'Close Connection'.

[Mastiff]

Sorry, Rob. Forgot to say that this isn't forwarded, it's directly connected to the VM Girder (since I only use a few NR clients that was easier to change).

[Rob H]

Are you sure they're not being forwarded as well?

[Mastiff]

Yes, because I'm using the IP address 192.168.0.18 in NetRemote, and that computer isn't set to forward anything. It's the .1 that forwards to .18.

[Rob H]

And that's the only Girder plugin instance in that copy of NR?

[Mastiff]

Yep. There can be only one... (Quote: Highlander) :D

[Mastiff]

Rob, changing to the new server I found the reason! It was my son's Atom Exec and my daughter's PocketLoox. They don't work with Zyxel WPA2 (which is what I have on my internal network), so they are connected to the external network (which is on the outside of my server, but inside the Linux firewall I use). Turned out routing and remote access it was set to forward port 20004 to the Girder VM, not port 20005, as it should have been! Which is why it got to the Girder installation on the "physical" server and got forwarded to the Girder VM.

With that plus that pesky modem problem fixed (which coincidentally also was a RAS problem) I have a totally isolated Girder installation on the VM, only catering to the internal network and my children's NetRemote instances. And since I went virtual I haven't had any problems with Phidgets, crashes or lockups. I think part of the problem was that I was running the main Girder installation on the server with two network cards on different subnets.

[Rob H]

Cool, glad that's sorted now.