Slight problem with dnet

[TheApe]

Any help would be gratefull.....

Got my main pc running dnet and the personal proxy with no probs, the local dnet client is getting it's wu's from 127.0.0.1:2064 without hassle..... however my laptopcant get units from the proxy? it can ping / use msnet working fine, but not get wu's

error I get is 'unable to create network endpoint, ENETDOWN: network down or not available'

any ideas?

 

[Viztech]

Can you post your Proxy.ini file?

We should be able to help you from there.

viz

 

[TheApe]

Here you go then.... Hope it helps........

[KeyServer]
ipaddress=proxy.teamanandtech.com
port=2064
connectperiod=600
connectivity=lurkonly
;bindip= ; IP to talk out to keyserver from
;uuehttpmode=0
; 0=normal,1=uue,2=http,3=http+uue
; 4=socks4,5=socks5,6=genproxy,7=genproxy+uue
;httpproxy=wwwproxy.corporation.com
;httpport=8080
;httpid=

[ports]
;listenaddress= ; IP to accept clients on
port=2064
;port2=23 ; must be root for ports < 1000
;port3=80
testport=3064
timeout=30

[console]
logfileconsole=
logfileconsolerotation=daily
consoleverbosity=&quot;general stats keyblock server client buffers timestamp attention errlow errsevere&quot;
timestampflags=130

[rc564]
logfilekeyblock=pproxyrc5
logfilekeyblockrotation=daily
minkeysready=10
maxkeysready=30
maxkeysdone=3

[desII]
logfilekeyblock=pproxydes
logfilekeyblockrotation=daily
minkeysready=0
maxkeysready=0
maxkeysdone=0
contestclosed=1

[ogr]
logfilekeyblock=pproxyogr
logfilekeyblockrotation=daily
minkeysready=0
maxkeysready=0
maxkeysdone=0

[csc]
logfilekeyblock=pproxycsc
logfilekeyblockrotation=daily
minkeysready=0
maxkeysready=0
maxkeysdone=0
contestclosed=1

[misc]
proxymessage=&quot;rc5des Personal Proxy!&quot;
pidfile=rc5desproxy.pid
statusperiod=30
periodicperiod=120
;logfilecompressor=logcompressor.sh

[ignoredip]

[allowedip]

Cheers

 

[Ken g6]

Sorry, but I have to ask: Your laptop isn't trying to get its WUs from 127.0.0.1, is it?

 

[TheApe]

I'm not quite that dumb, I've tried to connect to the main pc via name and IP address... no go on either.....

EDIT : Oh yeah also tried connecting on port 80 as well, no go on that either

 

[Wolfie]

Ken- I know where you are going with this. But it shows on his INI...


<< [KeyServer]
ipaddress=proxy.teamanandtech.com
port=2064
connectperiod=600
>>



I am curious tho.... There seems to be a little bit much in the INI. I don't have more then 10 lines in mine. I wonder if there is more there then there needs to be.....

Wolfie
[edit]Also, Ape What are you tring to crack? RC5 or OGR?[/edit]

 

[TheApe]

OK, worked it out, I was being dumb here's the ini for the client I had

[parameters]
id=distnet@ashleigh-paul.demon.co.uk

[misc]
project-priority=RC5,DES=0,OGR=0,CSC=0

[display]
progress-indicator=rate

[networking]
autofindkeyserver=no
keyserver=apc-whistler:2064
dialup-watcher=passive

[logging]
log-file=log.txt
log-file-type=fifo

[processor-usage]
priority=4

See the problem?


[parameters]
id=distnet@ashleigh-paul.demon.co.uk

[misc]
project-priority=RC5,DES=0,OGR=0,CSC=0

[display]
progress-indicator=rate

[networking]
autofindkeyserver=no
keyserver=apc-whistler:2064
dialup-watcher=disabled

[logging]
log-file=log.txt
log-file-type=fifo

[processor-usage]
priority=4

Oh well, it's late .... let me off..... Oh cracking RC5, this is more of a 'first step' into RC5, been cracking S@H for a while now, seeing what this is like...... Oh yeah, how do I get the proxy to flush (currently running as an NT service)

 

[Wolfie]

Ape
Sounds like a plan..... Good thing you figured it out.

/me lets TheApe off at the next stop.

Wolfie

 

[Viztech]

Wolfie-

That is the proxy.ini so that is why it is so long.

Ape-

Uhhh, that client it was waiting for you to dial-up, right?

I notice that your proxy.ini is set to lurkonly, so it will wait for a dial-up connection to connect to the team proxy as well. This is great as you apparently are on a dial-up connection.

Good to see that you got it going!

viz

 

[TheApe]

Yeah, got the proxy setup so it doesnt dial the connection all the time, hopefully downloading enough WU's for it so it wont have to work on random keys (as I'm online most days), Just a question without stopping the service, then starting it as a foreground app, how do I make the proxy flush/fetch?

Cheers

 

[Wolfie]

/me sticks his tounge out at Vis
I knew that. *snicker*

Wolfie

 

[JonB]

If you have it running in the foreground, a Ctrl-Break will force it to update. If it is running as a service, it will just have to manage for itself.

 

[TheApe]

Thought that was the case, OK, I'll have to right a cmd file and get it to net stop run flush net start, should be ok then

EDIT - So ok cant do that as there doesnt seem to be a command line option for the proxy to flush, is there one, or not?

Cheers

 

[Fardringle]

I'm not a Dnet expert but wouldn't running dnetc -update at the command prompt in the Dnet directory (or through a Windows shortcut) cause the client to fetch and flush?

 

[TheApe]

That would only flush the dnet client's buffers (to the proxy), need to flush the proxy (to the team proxy).........

 

[crYnOid]

i have this line in my proxy .ini file

[rc564]
maxkeysdone=10

this means that the proxy will flush after it has gathered 10 blocks.

 

[TheApe]

Had it set to 3, changed it to 10, makes more sence, cheers....

 

[Dougal]

JonB and all,

If you grab yourselves a copy of version 3.19 of the proxy it comes with a utility called &quot;proxysig&quot; which lets you send command line options to the proxy such as a &quot;update&quot;. You can create yourself a batch file then to force the update of a proxy running as a service any time you like.

Just my $.02 worth.

 

[TheApe]

Cheers for that 1, made my little cmd file for that.... cheers