llrnet is easy to run on a LAN.
You already have the clients installed just edit the server and port in the llr-clientconfig files.

EX
--Assuming a private IP for the server.
server = "192.168.0.100"
port = 7009


The server itself is easy to setup, just set the port you wan't to use in llr-serverconfig.txt
You can run it on any flavour of Windows. XP or Vista.
You don't need to be running a Server OS.

EX
serverName = "Somebodys-llrserver"
-- port that the server listen to (make sure clients are configured
-- with the same number)
port = 7009
-- maximum number of concurrent connections
maxConnections = 150

The input file for the server is called knpairs.txt.
Format of the file is what your used too already
Make sure it is in the same directory as llrserver.exe.

Here is a snippet of a knpairs.txt file.
6000000000000:M:1:2:258
2941 200003
2931 200005
2937 200006
2929 200007
2935 200007
2949 200007
2929 200009
2949 200011
2937 200012


Important thing here is the header, it must be present at the top of the file.
Long number is the sieve depth, rest of the header after the M tells the client what form to process.

Header in above example will work for Reisel base 2.

There is a section in the llrcientconfig that you may wish to uncomment that will produce a primes.txt file for you.
I find it easier to check that than trawl through the results file.

Server doesn't need any command line options just start it by running llrserver.exe
You may want to right click the tray icon and install as a service.
I run it that way as it starts automatically when the PC restarts.

[quote=henryzz;165385]have we ever found any limits to ironbit's linux servers?[/quote]
No, not yet. Of course, David's internet connection is a full business-class line, so it can probably handle a lot more load than a residential connection can; nonetheless, LLRnet doesn't have that terribly much overhead in its communication protocol anyway, so even the G4000 and G8000 servers, which are running on a residential connection, have proven to handle some pretty substantial loads, and in fact we don't have a solid upper limit defined for them either. The only difference with them is the fact that there's a dynamic IP address in play, but that only messes things up once in a while and as long as the IP remains the same, the servers seem to be able to handle plenty of load. :smile:

Thanks Max and Brian. It seems that the version of LLRNET that I downloaded doesn't have the llr-serverconfig.txt and llrserver.exe files. The links provided are dead (Rieselsieve). Any idea where I can get them now (and any other files I may be missing)? The rest seems easy to follow.

I have zipped up the llr server software i am using.
[URL="http://www.itsoapbox.com/llrserver.zip"]http://www.itsoapbox.com/llrserver.zip[/URL]

[quote]
I have zipped up the llr server software i am using.
[URL]http://www.itsoapbox.com/llrserver.zip[/URL]
[/quote]

Thanks Brian. As soon as I get some sleep, I'll give it a try.

Couldn't wait. Works just fine. Thanks all.

Indeed. If Gary would get a fixed IP (not that hard to do), then he could run all the Servers for his pet projects. :wink:

[quote=mdettweiler;165393]The only difference with them is the fact that there's a dynamic IP address in play[/quote]

[quote=IronBits;165457]Indeed. If Gary would get a fixed IP (not that hard to do), then he could run all the Servers for his pet projects. :wink:[/quote]
Well, Gary and I had discussed that a bit, and in fact we think we've figured out how to keep the IP address from changing most of the time even with a dynamic IP. It turns out that all the IP changes coincided directly with times when Gary had to power-cycle his wireless router, which as I explained in a PM a while back, triggers a DHCP "refresh", which more often than not ends up obtaining a new IP address from the ISP. He hasn't needed to power-cycle his router since then, and we haven't had a single IP change during that time frame. So, it looks like we've unlocked the secret to minimizing these IP changes. :smile:

That is well known problem. It's a really good idea to put that cable modem/DSL device on a UPS so it never get's turned off or reset. :wink:

[QUOTE]Well, Gary and I had discussed that a bit, and in fact we think we've figured out how to keep the IP address from changing most of the time even with a dynamic IP. It turns out that all the IP changes coincided directly with times when Gary had to power-cycle his wireless router, which as I explained in a PM a while back, triggers a DHCP "refresh", which more often than not ends up obtaining a new IP address from the ISP. He hasn't needed to power-cycle his router since then, and we haven't had a single IP change during that time frame. So, it looks like we've unlocked the secret to minimizing these IP changes. :smile:[/QUOTE]

Why not just disable DHCP?

[quote=MyDogBuster;165467]Why not just disable DHCP?[/quote]
For that to work, you've got to have a static IP, and that costs extra money. I remember Gary considering this, not sure if he ever got it...

DHCP is for his internal LAN to automatically hand out local LAN IPs to his computers, has nothing to do with the PUBLIC IP address that is assigned to his cable modem/DSL device by his ISP.
His ISP uses DHCP to assign his PUBLIC IP address to his cable modem/DSL device.
If he went with a static IP address, his ISP would assign a PUBLIC IP to his device, thus solving the problem completely.