Omapi, Just Getting Started

   *** From dhcp-server -- To unsubscribe, see the end of
this message. ***

	It looks like everybody else is having different trouble
with
omapi than I am having, but I haven't gotten it to do
anything yet
except make me scratch my head.

	First, is it okay to use the same omapi secret key as is
used
to update DNS?  DNS updates work just fine from the dhcp
server.

	For that matter, can one have a different omapi key present
without messing up the DNS updates?  When I thought I tried
that,
dhcpd complained about a missing ; on a line that actually
had one so
it was obviously very confused about something I did.  The
omapi part
of dhcpd.conf looks like:

key myomapikey {
     algorithm hmac-md5;
     secret "SHSHSH_Don't tell anybody.";
};
omapi-port 7911;
omapi-key myomapikey;

	myomapikey is also presently the key to the DNS.  What I
tried
that seemed to confuse things was:
key myomapikey {
     algorithm hmac-md5;
     secret "SHSHSH_Don't tell anybody.";
};

key anotheromapikey {
     algorithm hmac-md5;
     secret "another_secret";
};
omapi-port 7911;
omapi-key anotheromapikey;

	That, in theory would have let dhcpd use myomapikey to
update
DNS and anotheromapikey for omshell, only.

	I also tried an omshell script I downloaded which follows:

#!/usr/local/bin/bash
# ARG1 Address of DHCP SERVER
. $HOME/keys/omshell.conf
cat << EOF |omshell
server $1
port $MYPORT
key $KEY $SECRET
connect
new failover-state
set name="$MYFAILOVER"
open
EOF 

	The omshell.conf file stuffs most of the variables.

MYPORT=7911
KEYNAME=myomapikey
SECRET="SHSHSH_Don't tell anybody."

	When I run it all, I get the following errors:

> > > > dhcpctl_connect: not found
> not connected.
> no open object.
> not connected.
> <STDIN> line 1: unknown token: EOF
EOF 
^
> 

	This server is actually not yet running in failover mode
with
a peer.  What would be a good test command to give it that
isn't
likely to actually change anything?

	We are running
Internet Systems Consortium DHCP Server V3.0.1rc14

	Thanks.

Martin McCormick WB5AGZ  Stillwater, OK 
OSU Information Technology Department Network Operations
Group

------------------------------------------------------------
-----------
List Archives : http://www.isc.org/ops/
lists/
Unsubscribe   : http://www.
isc.org/sw/dhcp/dhcp-lists.php    
-or-          : mailto:dhcp-server-requestisc.org?Subject=unsubscribe  
------------------------------------------------------------
-----------

   *** From dhcp-server -- To unsubscribe, see the end of
this message. ***



Are you sure you are specifying the server name on the
command line?
It seems to want that:
> server $1

John
PS, "cat << EOF |omshell" is wierd,
"omshell <<EOF" would be preferred"


> #!/usr/local/bin/bash
> # ARG1 Address of DHCP SERVER
> . $HOME/keys/omshell.conf
> cat << EOF |omshell
> server $1
> port $MYPORT
> key $KEY $SECRET
> connect
> new failover-state
> set name="$MYFAILOVER"
> open
> EOF 
> 
> 	The omshell.conf file stuffs most of the variables.
> 
> MYPORT=7911
> KEYNAME=myomapikey
> SECRET="SHSHSH_Don't tell anybody."
> 
> 	When I run it all, I get the following errors:
> 
> > > > > dhcpctl_connect: not found
> > not connected.
> > no open object.
> > not connected.
> > <STDIN> line 1: unknown token: EOF
> EOF 
> ^

------------------------------------------------------------
-----------
List Archives : http://www.isc.org/ops/
lists/
Unsubscribe   : http://www.
isc.org/sw/dhcp/dhcp-lists.php    
-or-          : mailto:dhcp-server-requestisc.org?Subject=unsubscribe  
------------------------------------------------------------
-----------