Red Hat Bugzilla – Bug 14467
Generic CIPE issues.
Last modified: 2008-05-01 11:37:56 EDT
If /etc/sysconfig/cipe doesn't exist, /etc/rc.d/init.d/cipe can't
get $DEVICE, $PEER, and $PORT settings from anywhere. Perhaps it'd better
die right out?
Also, are dynamic configurations supported, ie. dialup (when the interface
isn't really up at boot..)? This might require extra checking considering
the way IP address is obtained using ifconfig.
Default /etc/sysconfig/cipe is empty. Settings for it have to
reverse-engineered from init.d/cipe. It should at least be commented
somehow. An example file is attached.
/etc/cipe/options is also all-commented out. This has to be edited
to get CIPE to work. The only options you have to set are ptpaddr, ipaddr,
and key, really. Maxerr could be set to -1 by default, I think. In the
file, device=, me=, and peer= could be more clearly separated from the
Some really obscure private space IP addresses could be used as private
tunnel endpoints (e.g. 172.16.100.1 and 172.16.100.2); I doubt they'd clash.
Cipe also generates some debug messages by default. Appending the
following to /etc/modules.conf would avoid that:
options cipcb cipe_debug=0
Created attachment 1467 [details]
An example of /etc/sysconfig/cipe
Thanks, will be fixed in the next release of the cipe package.