<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: 2nd CIPE connections won't come up - More info ....
From: SD <sdtechnet,AT,yahoo,DOT,com>
Date: Wed, 5 Jun 2002 22:41:19 +0200

I am hoping you can help me.  I have a CIPE install
working great between two machines (machine A and
machine B)  I am trying to install a second CIPE
tunnel between machine A and machine C.  I cannot get
the second instance (cipcb1) to come up.  Do you have
any thoughts?  I installed per the following
instructions:  

 

http://www.extra300.nl/diagram.htm

 

My info looks like:

 

Machine A

Options.cipcb0

 

device cipcb0

me machinea.pointclark.net:1111

ipaddr 192.168.254.1

ptpaddr 192.168.254.254

peer machineb.pointclark.net:1112

key aaaaaa(key)

maxerr -1

 

Machine A

Options.cipcb1

 

device cipcb1

me machinea.pointclark.net:1113

ipaddr 192.168.254.1

ptpaddr 192.168.254.254

peer machinec.pointclark.net:1114

key bbbbbb(key)

maxerr -1

 

 

Machine C

Options.cipcb0

 

device cipcb0

me machinec.pointclark.net:1114

ipaddr 192.168.254.254

ptpaddr 192.168.254.1

peer machinea.pointclark.net:1113

key bbbbbb(key)

maxerr -1

 

 

The only other place I can think it would be is the
ciped file or the ip-up file.  Both are listed below. 

 

Ciped

 

http://www.extra300.nl/ciped.txt

 

 

ip-up

 

--------------------------

 

#!/bin/sh

# ip-up <interface> <myaddr> <daemon-pid> <local>
<remote> <arg>

 

# Sample of the ip-up script.

# This is called when the CIPE interface is opened.

# Arguments:

#  $1 interface     the CIPE interface

#  $2 myaddr        our UDP address

#  $3 daemon-pid    the daemon's process ID

#  $4 local         IP address of our CIPE device

#  $5 remote        IP address of the remote CIPE
device

#  $6 arg           argument supplied via options

 

# Purposes for this script: set up routes, set up
proxy-arps, etc.

# start daemons, logging...

 

umask 022

PATH=/sbin:/bin:/usr/sbin:/usr/bin

 

if [ "'uname -r | cut -d. -f1-2'" = "2.0" ]; then

  # Under Linux 2.0, a minimal route to the remote
CIPE is needed.

  # 2.1 and later sets this one by itself.

  route add -host $5 dev $1

fi

 

# If this becomes our default route...

#route add default gw $5

 

# just a logging example

now=`date "+%b %d %T"`

echo "$now UP   $*" >> /var/log/cipe.log

 

# Create/update PID file. Note: PKCIPE needs this.

echo "$3 $1" >/var/run/cipe/${6:-$1}.pid

 

# Trigger the key exchange procedure, useful when
we're using SOCKS

# This _must_ run delayed and in the background

#(sleep 10; ping -c5 $5) &

route add -net 192.168.2.0 netmask 255.255.255.0 gw $5

route add -net 192.168.3.0 netmask 255.255.255.0 gw $5

# If the system runs gated, tell it what has happened

#gdc interface

 

# The following are just ideas for further
consideration

 

# Interconnect two 10. subnets through the Internet!

# Assuming $4 is in 10.1 and $5 in 10.2

#route add -net 10.2.0.0 netmask 255.255.0.0 gw $5

 

# Proxy-ARP the peer's address on eth0

#arp -i eth0 -Ds $5 eth0 pub

 

# Evil tricks department: masquerade the CIPE peer's
/24 network to our IP

#NA=`expr $5 : '\([0-9]*\.[0-9]*\.[0-9]*\.\)'`

#ipfwadm -F -a accept -m -b -S $NA.0/24 -D 0.0.0.0/0

# the usual way for this would be a case selection on
$5 or $6, however

 

exit 0

  

Thank you in advance,

 

Todd

todd.bailey,AT,27blue,DOT,com

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com





<< | Thread Index | >> ]    [ << | Date Index | >> ]