RE: Connecting 2 subnets via cipe|
"Kevin Herzig" <Kevin,AT,Herzig,DOT,net>|
Wed, 2 May 2001 05:14:12 +0200|
You didn't mention, you are using different ports for the second connection,
Also, I believe you should have a different ip-up script for each because
your second network should have different routing entries, as in
Instead of different ip-up scripts, you could pass the subnet necessary for
the other route into the same ip-up script but I don't remember how.
If this doesn't work, do you see any output in your system logs?
From: owner-cipe-l,AT,inka,DOT,de [mailto:owner-cipe-l,AT,inka,DOT,de Behalf
Sent: Tuesday, May 01, 2001 9:17 PM
Subject: Re: Connecting 2 subnets via cipe
> This is not a limitation of CIPE because I do this all the time.
> Send to the list sanitized versions of your options files and the commands
> you use to start the cipe daemons.
here they come:
me <my ip>:9999
peer <other ip>:9999
key < I won't display it here... :) >
optins2 looks the same but has other ptpaddr, ipaddr and peer addresses
and a different key.
I start the server on B (fixed IP) with
# cipe-cb -o /etc/cipe/peers/options1
This one works and I can establish a connection from A to B. The process
is also shown by ps.
when I try to start the server for B-C connection (options2) in the same
way, just nothing happens. No process for the second one is shown and no
connection from C is possible.
What am I missing here?
Message sent by the cipe-l,AT,inka,DOT,de mailing list.
Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: