NPLB LLRnet server discussion

[em99010pepe]

New server address for testing.

IP: 192.168.200.37
Port: 80

It will be up and running just for a few hours. The candidates in the server are from a range reserved by me so you guys will be doing some double check work

[Mini-Geek]

Originally Posted by em99010pepe

New server address for testing.

IP: 192.168.200.37
Port: 80

It will be up and running just for a few hours. The candidates in the server are from a range reserved by me so you guys will be doing some double check work

We won't be able to access that address. That is in one of the sets of IP addresses that aren't routed, so they're LAN-only. Please give something else, preferably something usable (i.e., not in 10.*.*.*, 172.16-31.*.*, or 192.168.*.*)
http://en.wikipedia.org/wiki/Private_network

[em99010pepe]

Originally Posted by Mini-Geek

We won't be able to access that address. That is in one of the sets of IP addresses that aren't routed, so they're LAN-only. Please give something else, preferably something usable (i.e., not in 10.*.*.*, 172.16-31.*.*, or 192.168.*.*)
http://en.wikipedia.org/wiki/Private_network

Sorry.

[IronBits]

Can someone make me up a small knpairs file so I can start up a real Server to see how it goes?
llrnet.no-ip.info will be the Server
port = 500
and exactly how I put them in the server directory so they can be found and used?
No one has sent me the 'tutorial', so just taking it one step at a time, and gleaning all the information from so many places.

[mdettweiler]

Originally Posted by IronBits

Can someone make me up a small knpairs file so I can start up a real Server to see how it goes?
llrnet.no-ip.info will be the Server
port = 500
and exactly how I put them in the server directory so they can be found and used?
No one has sent me the 'tutorial', so just taking it one step at a time, and gleaning all the information from so many places.

I've reserved 316.6-316.8 for your LLRnet server, you can get it from the link here.

Simply put it in the LLRnet server directory and rename it to knpairs.txt before starting the LLRnet server.

After you've done that, you can periodically copy off the results.txt and email it to both me and Karsten. (Just stop the server, move the results.txt file to another folder, start the server again, and email me and Karsten the file. )

[em99010pepe]

Originally Posted by Anonymous

I've reserved 316.6-316.8 for your LLRnet server, you can get it from the link here.

Rename the file to knpairs.txt and put it on the server folder. Then run llrserver.exe. Tell me when you're done to fire up my quady.

[em99010pepe]

Originally Posted by Anonymous

(Just stop the server, move the results.txt file to another folder, start the server again, and email me and Karsten the file. )

You don't need to stop the server, just move the file results.txt to another folder.

[IronBits]

Ok, it's there. All I see is
NPLB_LLRserver
nil

Hope it works. Thanks!

Edit, yup!
NPLB_LLRserver500 current status :
nil
connection request from 8ecf055:63716 (socket 1452)
Proposing pair 409/316601 to Free-DC_em99010pepe
Proposing pair 421/316601 to Free-DC_em99010pepe
Proposing pair 507/316601 to Free-DC_em99010pepe
Proposing pair 511/316601 to Free-DC_em99010pepe
connection request from 8ecf055:63717 (socket 1480)
Proposing pair 525/316601 to Free-DC_em99010pepe
Proposing pair 579/316601 to Free-DC_em99010pepe
connection closed (socket 1452)
Proposing pair 631/316601 to Free-DC_em99010pepe
Proposing pair 675/316601 to Free-DC_em99010pepe
Proposing pair 691/316601 to Free-DC_em99010pepe
connection request from 8ecf055:63718 (socket 1452)
Proposing pair 711/316601 to Free-DC_em99010pepe
Proposing pair 907/316601 to Free-DC_em99010pepe
connection closed (socket 1480)
Proposing pair 949/316601 to Free-DC_em99010pepe
Proposing pair 405/316602 to Free-DC_em99010pepe
connection request from 8ecf055:63719 (socket 1480)
Proposing pair 413/316602 to Free-DC_em99010pepe
Proposing pair 551/316602 to Free-DC_em99010pepe
Proposing pair 587/316602 to Free-DC_em99010pepe
Proposing pair 651/316602 to Free-DC_em99010pepe
connection closed (socket 1452)
Proposing pair 695/316602 to Free-DC_em99010pepe
Proposing pair 735/316602 to Free-DC_em99010pepe
Proposing pair 755/316602 to Free-DC_em99010pepe
connection closed (socket 1480)

w00t! :D

[em99010pepe]

Originally Posted by IronBits

Ok, it's there. All I see is
NPLB_LLRserver
nil

Hope it works. Thanks!

It's working. My quady will eat those pairs in less than 14 hours...
Edit: First results are in, make a copy of the results.txt and open it to familiarize with its output written. Thank you. I'm going to work now.

[IronBits]

Originally Posted by em99010pepe

It's working. My quady will eat those pairs in less than 14 hours...

Yikes, guess I should get more knpairs <grin>

I suppose I should stop using a personal proxy and shift over to the real server eh?
How do I back off my personal proxy server so I don't leave anything hanging, and I don't care if my knpairs are to help get rid of the low end stuff you have been working on.

It's here for you guys, you tell me what to stick in knpairs, and I'll put it there.
I have 4GB of ram in this beast, so if I need to run multiple servers/ports, I can.

[IronBits]

Originally Posted by Anonymous

I've reserved 316.6-316.8 for your LLRnet server, you can get it from the link here.

Simply put it in the LLRnet server directory and rename it to knpairs.txt before starting the LLRnet server.

After you've done that, you can periodically copy off the results.txt and email it to both me and Karsten. (Just stop the server, move the results.txt file to another folder, start the server again, and email me and Karsten the file. )

Ok, send me an email with both email addresses so I don't make any mistakes there.
ironbits AT cox dot net :)
Let me know if you want me to do more, add more servers, whatever.