HELP! 'networkupdate' fails
Hello ! Actually I'm testing the ripe-dbase-software (release 2.03). In near future we want to use the ripe-dbase-software to store internal data (i.e. customer data, infrastructure data ...) and to run a secondary of the ripe database at our site. We're running under Solaris 2.5 with the special perl4.036-hack (from here many thanks to Peter Haag) which is avaiable on your ftp-server. Everything is running fine, i.e - all kinds of queries - handling of new, own database objects - running with different sources in split-mode - set-up of the database. 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. 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. 'whoisd -V -D' gives me the following trace: (europa is the server-machine, x11 is the client-machine) # europa: whoisd -V -D # whoisd daemon (6827) - running in debug mode # whoisd daemon (6827) - will connect to port: 43 with protocol: 6 # whoisd daemon (6827) - changing (UID,GID) from: (0,1 14 12 9 8 7 6 5 4 3 2 0 1) to: (500,200) # whoisd daemon (6827) - changed (UID,GID) to: (500,200 14 12 9 8 7 6 5 4 3 2 0 1) # (6832) child connection x11.NIC.DTAG.DE (194.25.1.107) # (6832) got in parse # (6832) left parse, searchstring: # (6832) whoisd called with flags:U:Vnp2.0 # (6832) whoisd lookup: # (6832) whoisupdate(name:'x11.NIC.DTAG.DE',ip:'194.25.1.107',log:'mb localhost') called # (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 # (6832) exit connection [194.25.1.107] After calling 'networkupdate - h europa' on the client-machine it terminates immediately! After accepting the whoisupdate the connection is terminated by the whoisd! I checked our ripedb-config file more than one time and I thing that everything inside is correct. Maybe I make something wrong or this effect has something to do with running under Slowaris 2.5 ... ? Or is there a tricky way to setup the possibility for networkupdates ? Is somebody able to help me ? Kind regards Markus
Hi, I'm sorry for the delayed response. In the configuration file, set the WHOISUPDFROM to hold the IP numbers of the hosts from which you want to accept direct update with the 'networkupdate' program. Example: WHOISUPDFROM 193\.0\.0\.1[2345][0-9] I hope this helps. Carol Orange RIPE NCC In message <199609051636.SAA27165@zeus.NIC.DTAG.DE>, Markus Bock writes:
Hello ! Actually I'm testing the ripe-dbase-software (release 2.03). In near future we want to use the ripe-dbase-software to store internal data (i.e. customer data, infrastructure data ...) and to run a secondary of the ripe database at our site. We're running under Solaris 2.5 with the special perl4.036-hack (from here many thanks to Peter Haag) which is avaiable on your ftp-server. Everything is running fine, i.e - all kinds of queries - handling of new, own database objects - running with different sources in split-mode - set-up of the database. 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. 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.
'whoisd -V -D' gives me the following trace: (europa is the server-machine, x11 is the client-machine)
# europa: whoisd -V -D # whoisd daemon (6827) - running in debug mode # whoisd daemon (6827) - will connect to port: 43 with protocol: 6 # whoisd daemon (6827) - changing (UID,GID) from: (0,1 14 12 9 8 7 6 5 4 3 2 0 1) to: (500,200) # whoisd daemon (6827) - changed (UID,GID) to: (500,200 14 12 9 8 7 6 5 4 3 2 0 1) # (6832) child connection x11.NIC.DTAG.DE (194.25.1.107) # (6832) got in parse # (6832) left parse, searchstring: # (6832) whoisd called with flags:U:Vnp2.0 # (6832) whoisd lookup: # (6832) whoisupdate(name:'x11.NIC.DTAG.DE',ip:'194.25.1.107',log:'mb localhost') called # (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 # (6832) exit connection [194.25.1.107]
After calling 'networkupdate - h europa' on the client-machine it terminates immediately! After accepting the whoisupdate the connection is terminated by the whoisd!
I checked our ripedb-config file more than one time and I thing that everything inside is correct.
Maybe I make something wrong or this effect has something to do with running under Slowaris 2.5 ... ?
Or is there a tricky way to setup the possibility for networkupdates ?
Is somebody able to help me ?
Kind regards
Markus
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 ;-). ---
participants (3)
-
Carol Orange -
davidk＠ISI.EDU -
Markus Bock