Hi Markus,
Markus Bock writes :
For writing database front ends which manipulate and visualisize the stored data we want to use the 'networkupdate' program to have access to the database from different workstations via LAN.
This function is indeed present for this purpose.
But it is not working at our side, it is not possible to forward objects via STDIN to the whoisd after calling the networkupdate programm.
Most people suggested that you might have forgotten to add your clienthost IP to the access lists. However, I don't believe this is your problem. The debugging output you sent suggests that an update is indeed accepted:
# (6832) whoisd called with flags:U:Vnp2.0 # (6832) checking 194.25.1.107=~ /194.25.1.107/ # (6832) update from: 194.25.1.107 accepted, regular: 194.25.1.107 # (6832) whoisupdate accepted
Also, the server should have said something like this when the update was not accepted: % ERROR: ***You are not authorized to do networkupdates***
I checked our ripedb-config file more than one time and I thing that everything inside is correct.
I believe that you are right ...
Maybe I make something wrong or this effect has something to do with running under Slowaris 2.5 ... ?
May be, may be not. Could you try the C version of networkupdate (available from ftp.ripe.net/tools/whois-tools*) and see if the same problem happens ? Could you try 'networkupdate -h whois.ripe.net'. You should get a message back that tells you that you are not authorized to network updates. The problem is problably in the client side of the software if you don't get this message. Please contact <ripe-dbm@ripe.net> and see if they can help you with extra debugging code in the whoisd daemon/whois client to do a more detailed trace of what is happening in the server software. I hope this helps, David K. PS Please don't expect any fast responses right now since I am still busy with moving & am not working yet. I have, however, already built a new computer & got a ppp account at ISI so I am not completely disconnected anymore ;-). ---