Update [Compiled on 29/06/2009 at 23:09:38.51 BST]

Hopefully fixes any problems people are having with UDP.

(If you're wondering why UDP suddenly broke - I entirely rewrote the UDP socket code in the last build to fix some stability problems).

http://oinc.aquadasoft.com/OINC.zip

Judging by the 404 Not Found error, I take it this version isn't yet fixed?

Works fine here, not sure why you can't fetch it.

i should have updated... i was able to get the latest as well...

I should point out that I still can't get UDP messages when I use the klikfarm server

Running the latest server version now.
Perhaps the client < UDP > server now works?

Yes, I can confirm that I'm having 100% success sending UDP packets from Austin, TX to server.klikfarm.com

I have a request for server side. I would like banning to be a little more flexible. Say if someone tries to connect with a username of X and IP of X.X.X.* and MAC address of X:X:X:X:X:X then ban.
This way it should fix users with dynamic IP addresses.
MAC address banning coupled with and IP range would be handy as it pretty much scuppers any-ones chances of connecting.

dont know if this is a known issue or not, but restarting the server from the web interface doesnt seem to release the server from its port before resetting. doesnt seem to really make a difference. the server doesnt malfunction or go down. just noticed it.

[20:28:09] Loading server...
[20:28:09] Compiled on 29/06/2009 at 23:26:35.46 BST
[20:28:09] Checking for updates...
[20:28:09] Server is up to date
[20:28:09] Opened log file OINC_Server.log
[20:28:09] Hosting OINC server on port 49152
[20:28:09] Hosting web interface on port 6122
[20:28:09] Web interface is unsecured - set a password in OINC_Server.ini
[20:28:09] Checking for components...
[20:28:09] No components found
[20:43:57] Waiting 1 second...
[20:43:58] Server restarting
[20:43:58] Restart requested
[20:43:58] Loading server...
[20:43:58] Compiled on 29/06/2009 at 23:26:35.46 BST
[20:43:58] Checking for updates...
[20:43:58] Server is up to date
[20:43:58] Opened log file OINC_Server.log
[20:43:58] Hosting OINC server on port 49152
[20:43:58] Error - The port is already in use
[20:43:58] Hosting web interface on port 6122
[20:43:58] Web interface is unsecured - set a password in OINC_Server.ini
[20:43:58] Checking for components...
[20:43:58] No components found

Looks great! I noticed something reading the log file, the deafault port is commented out, and there is no way to enable ONLY certian IP adresses and names rather than disabling. Otherwise I love it!

Oh! Jamie; did reverse lookup ip-DNS get added?

No, but I can add that easily enough! I'll stick it in one of the upcoming builds for you.

Lifesaver! :D

Oh how can I host web server now? It's gone. If I open an old project it will still use the option but I can't see it in a new project.

I'm splitting that off into a new extension.

Jamie - quick question; does the current build support retaining connection over frames?

Yes, it does.

Thanks Looki - I could have tested but was being lazy (shame mode activated)

It's released, now anyway :)

Enumerate netowrk doesn't seem to help in getting the IP address. I tried getting local IP into edit text but nothing comes out after device enumeration on startup.

Same for Hostname
XP Pro SP3

Jamie usernames will stay in a server forever if your internet is disconnected while connected to an OINC server! There needs to be a user timeout in the server host or something, because I don't know when any servers will restart.

Eh? I doubt it.. that hasn't been reported before.

Semi confirmed _LB

[14:02:26] Loading server...
[14:02:26] Compiled on 29/06/2009 at 23:26:35.46 BST
[14:02:26] Checking for updates...
[14:02:26] Server is up to date
[14:02:26] Opened log file OINC_Server.log
[14:02:26] Hosting OINC server on port 49152
[14:02:26] Hosting web interface on port 6122
[14:02:26] Web interface is unsecured - set a password in OINC_Server.ini
[14:02:26] Checking for components...
[14:02:26] No components found
[14:03:21] Client ID 0 connected from 192.168.1.33
[14:03:21] Client ID 0 set their name to cecil1
[14:03:21] Client ID 0 joined the channel SEU
[14:04:33] Client ID 1 connected from 192.168.1.33
[14:04:33] Client ID 1 set their name to cecil1
[14:04:34] Client ID 1 joined the channel SEU
[14:04:47] Client ID 0 disconnected
[14:05:04] Client ID 1 disconnected
[14:05:07] Client ID 1 connected from 192.168.1.33
[14:05:07] Client ID 1 set their name to cecil1
[14:05:07] Client ID 1 joined the channel SEU
[14:05:28] Client ID 1 disconnected

ok so when disabled my network card on the computer with the client. the server still thinks that that user IS connected. like
_LB said, there needs to be a user timeout. the ghost connection did not disconnect until i reenabled my network card, and logged in again. as you can see it connected me to one then disconnected the ghost user. but the connection for the client hung, and i never actually received anything back from the server. so i logged out and logged back in. normally it should connect you to the lowest possible id but it connected me again to id 1, even though id 0 should be 'available'

also back to my last post

[20:43:57] Waiting 1 second...
[20:43:58] Server restarting
[20:43:58] Restart requested
[20:43:58] Loading server...
[20:43:58] Compiled on 29/06/2009 at 23:26:35.46 BST
[20:43:58] Checking for updates...
[20:43:58] Server is up to date
[20:43:58] Opened log file OINC_Server.log
[20:43:58] Hosting OINC server on port 49152
[20:43:58] Error - The port is already in use
[20:43:58] Hosting web interface on port 6122
[20:43:58] Web interface is unsecured - set a password in OINC_Server.ini
[20:43:58] Checking for components...
[20:43:58] No components found

ive just found out that this DOES affect the server. the next time anyone tries to connect the server crashes.

Also, when sending a stack message of 512 byes, sometimes it reports an error "Message is too large to blast, try sending it instead" or something like that. Is this a typo or a bug?

A new version (1.0b) will be released tonight (BST) that fixes all known bugs/crashes and removes the upper limit on all messages.