auto find keyserver :stopped

[cpars]

I will spare you the long story behind this post for now, but I cannot stop the client from connecting to dnets keyserver when it fails to resolve my dns server to the pproxy. I guess i could set the buffers so high I could always manually connect, but would rather have a medium setting of around 500-1000 so I can leave unattended.
already set in the .ini
autofindkeyserver=no

 

[DSmarty]

Add this in your dnetc.ini: (in the [rc5] section)

nofallback=true

 

[cpars]

just tried that and it still fetched. I am purposely giving it a bogus keyserver to get it to timeout. The reason being I noticed it did find a keyserver this morning and flush and not to my pproxy. Iam guessing that my dns server may have been down temporarily so It politely just went and found another. I did not have logging on at the time but I do now

 

[Nohr]

Try going in to the buffer options config. Set "5) Disable buffer updates from/to a keyserver" to yes. Or if you'd rather edit the ini file try adding this:

[networking]
disabled=yes

That should do it for you.


edit: fixed ptyos

 

[cpars]

Tried that Nohr, and of course that may stop it from finding keyserver when auto updating but still has not stopped it while doing a manual which is my only way without sending a large amount of blocks. Well I guess I could move the existing buff files and change the amount to something small and try....but you (I) would think there is some way to disable that sucker to not hunt a keyserver !

In the meantime I have just upped my buffers to 10,000 to each machine :Q

 

[osmo]

cpars-

In the client config menu system:

Menu 2.5 = No
Menu 2.6.2 = No
Menu 2.6.3 = xxx.xxx.xxx.xxx (Proxy of choice)
Menu 2.6.5 = Yes

Restart the client and these settings should keep it from connecting to DNet directly unless the admin of your "Proxy of choice" has the dns pointing directly to DNet (possibly while performing maintenance or upgrades). Good Luck

Osmo.

 

[Nohr]

Okay, so the problem is when you manually flush it, it tries to find your proxy, but for whatever reason the DNS server isn't working, and so it gives up on that and just flushes to a dnet server?

Just did an experiment and got the same thing. Turned off my ICS software (to simulate a DNS problem) and tried flushing a machine on the network. It tried the proxy twice, than a dnet server, than gave up and just went back to cracking. I don't know how you can solve that.

Perhaps give the client your proxy's ip rather than it's name address, then it doesn't have to bother with the DNS server. That'll only work well if your proxy has the same ip for a reasonable length of time though.

 

[Nohr]

What Osmo suggested worked for me. Thanks Osmo!

 

[cpars]

[Jun 04 20:57:57 UTC] Could not update to/from the net. Network down?

Now most folks might frown at that, but thats exactly what I wanted to see.
Thanks osmo It was the 2,6,5 I believe.

 

[osmo]

Just as a point of clarity, the menu item 2.6.5 corresponds to the nofallback=true ini config parameter mentioned earlier by DSmarty, however, it needs to be in the [networking] section. Regardless, I'm glad to see you two up and running the way you want to be.

Osmo.

 

[cpars]

yes I see it now in the [networking] section, whereas I had added it to the [rc5] section earlier.
thanks for your help too Nohr & DSmarty,I shoulda known to put that in networking.