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

Subject: RE: cipe 1.4.5 tunnel not working
From: SBNelson,AT,thermeon,DOT,com
Date: Wed, 31 Oct 2001 15:48:04 +0100

Check
1) that you have ip forwarding enabled
2) that your firewall rules are not interfering with the udp packets (at
least port 7283 between the two IP addresses)
3) that your firewall rules are not interfering with the cipcb0 interface
4) that your firewall rules allow packets to be forwarded to/from cipcb0 and
eth1

The next problem you will have, is that you can ping between the two
machines but not between the two LANs.  This is a routing problem.  Make
sure you issue a route command from the ip-up script:
        Machine A:
                route add -net 10.2.1.0/24 gw $5   (check me on $5 -- that
is from memory)
        Machine B:
                route add -net 10.1.1.0/24 gw $5

Hope this helps.  Scott.

> Hello, I have two machines running cipe 1.4.5, with the following configs:
> 
> machine A:
> Linux 2.4.9, CIPE 1.4.5
> network:
>       eth0    63.xxx.xxx.xxx/27
>       eth1    10.1.1.1/24
> /etc/cipe/options:
>       device  cipcb0
>       ipaddr  10.1.1.1
>       ptpaddr 10.2.1.1
>       me      63.xxx.xxx.xxx:7283
>       peer    63.yyy.yyy.yyy:7283
>       key     ################################
> 
> 
> machine B:
> Linux 2.4.2, CIPE 1.4.5
> network:
>       eth0    63.yyy.yyy.yyy/27
>       eth1    10.2.1.1/24
> /etc/cipe/options:
>       device  cipcb0
>       ipaddr  10.2.1.1
>       ptpaddr 10.1.1.1
>       me      63.yyy.yyy.yyy:7283
>       peer    63.xxx.xxx.xxx:7283
>       key     ################################
> 
> 
> The two machines can talk to each other just fine via the 63. addresses
> (over the net), and cipe starts up fine, but nothing comes or goes through
> the tunnel.  On machine B, i ping 10.1.1.1 (using nmap -sP -e cipcb0
> 10.1.1.1) and get no response, and it doesn't respond to any other sort of
> packets either.  Same in reverse.  I've tried changing the 10. addresses
> to 192. addresses just for fun, and that gets me nowhere as well.
> 
> Cipe was started manually on both machines, with the command "ciped-cb -o
> /etc/cipe/options".  This is an excerpt from messages after starting cipe
> on machine B:
> 
> Oct 30 12:02:25 artemis kernel: cipcb: CIPE driver vers 1.4.5 (c) Olaf
> Titz 1996-2000, 100 channels, debug=1
> Oct 30 12:02:25 artemis kernel: cipcb: cipe_alloc_dev 0
> Oct 30 12:02:25 artemis kernel: cipcb0: alloc
> Oct 30 12:02:25 artemis kernel: cipcb0: setpar
> Oct 30 12:02:25 artemis kernel: cipcb0: setkey
> Oct 30 12:02:25 artemis kernel: cipcb0: attach
> Oct 30 12:02:25 artemis kernel: cipcb0: opened
> Oct 30 12:02:25 artemis kernel: cipcb0: cipe_recvmsg
> Oct 30 12:02:33 artemis kernel: cipcb0: cipe_sendmsg
> Oct 30 12:02:33 artemis kernel: cipcb0: setkey
> Oct 30 12:02:33 artemis kernel: cipcb0: cipe_recvmsg
> 
> And I get one of these in /var/log/cipe.log:
> 
> Oct 30 12:02:25 UP   cipcb0 63.197.25.194:7283 875 10.2.1.1 10.1.1.1
> 
> I get identical messages on machine A.
> 
> 
> Please Help!
> 
> Colin Rognlie
> lucifex,AT,fryballs,DOT,net
> 
> 
> --
> 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:
> <URL:http://sites.inka.de/~bigred/devel/cipe.html>





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