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

Subject: Re: Frame errors with Cipe-Win32
From: "Damion K. Wilson" <dkw,AT,rcm,DOT,bm>
Date: Fri, 3 Nov 2000 16:27:06 +0100
In-reply-to: <Pine.OSF.4.10.10011030128050.10200-100000@kosh.hut.fi>

There is a known "issue" between Cipe-Win32 and Cipe 1.4.x. I don't know
what happened, but I think that a field changed position in the UDP frame.
It's only been reported to me 10 days or so ago. I don't have a Cipe 1.4.3
box setup and I'm currently rewriting Cipe-Win32. If you use Cipe 1.3.x,
everything will work fine.

Damion K. Wilson

*********** REPLY SEPARATOR  ***********

On 11/3/00 at 2:12 AM Ville Voipio wrote:

>Hi,
>
>I have been trying to set up a Cipe-based tunnel between a Windows NT
>machine and a Linux box. The network is as follows:
>
>
> Linux box:
> eth0: 1.2.3.90
> cipcb0: 192.168.101.225
>
>
> ISP router:
> dynamic address <-> 10.43.103.129
>
>
> DSL modem:
> eth: 10.43.103.129
>
>
> Windows NT:
> Etherlink: 10.43.103.130
> cipe1: 192.168.101.226
>
> 
>So, the other end (Linux box) has a fixed address. My end does not
>necessarily have a fixed public address as the ISP may change the way it
>maps the 10.x.x.x addresses to public addresses. However, there is no NAT
>in between, and all ports should be open.
>
>Pings go fine into both directions (without Cipe). With Cipe tunnel is
>formed.
>
>The Linux box seems to work fine, as we were able to set up a similar
>system with another Linux in the other end with the same addresses and
>ports. Cipe worked without slightest problems.
>
>This is how I have configured the CIPE1/(Untitled) adapter at the NT
>machine:
>
>
> Local IP:             0.0.0.0 : 1234
> Peer IP:             1.2.3.90 : 1234
>
> Local PTP IP:  192.168.101.226 mask 255.255.255.252 (from control panel)
> Peer PTP IP:   192.168.101.225
>
> Enabled: X
>
> Static key:    <128 bits of random noise>
> Timeout:       600
>
>
>The Linux options file looks like:
>
> ptpaddr  192.168.101.226
> ipaddr   192.168.101.225
> me       1.2.3.90:1234
> peer     0.0.0.0:1234
> maxerr=-1
> key      <same 128 bits of random noise>
>
>
>The NT routing table is as follows [Metrics removed for readability]:
>
>===========================================================================

>Interface List 
>0x1 ........................... MS TCP Loopback interface
>0x2 ...08 00 58 00 00 01 ...... DKW Heavy Industries VPN Adapter
>0x3 ...00 a0 24 43 89 3a ...... ELNK3 Ethernet Adapter
>===========================================================================

>===========================================================================

>Active Routes:
>Network Destination        Netmask          Gateway       Interface
>          0.0.0.0          0.0.0.0    10.103.43.129   10.103.43.130
>    10.103.43.128  255.255.255.248    10.103.43.130   10.103.43.130
>    10.103.43.130  255.255.255.255        127.0.0.1       127.0.0.1
>   10.255.255.255  255.255.255.255    10.103.43.130   10.103.43.130
>        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1
>  192.168.101.224  255.255.255.252  192.168.101.226  192.168.101.226
>  192.168.101.226  255.255.255.255        127.0.0.1       127.0.0.1
>  192.168.101.255  255.255.255.255  192.168.101.226  192.168.101.226
>        224.0.0.0        224.0.0.0    10.103.43.130   10.103.43.130
>        224.0.0.0        224.0.0.0  192.168.101.226  192.168.101.226
>  255.255.255.255  255.255.255.255  192.168.101.226  192.168.101.226
>===========================================================================

>
>
>
>This shouldn't be awfully wrong. The traffic to 192.168.101.224/30 is
>routed through the DKW Heavy Industries' interface. (This seems to be a
>bit different from that on Linux, as there the gw should be the _other_
>end). There is still one thing I do not get, and it is the route to the
>broadcast address 192.168.101.255, which is out of netmask range!
>
>Anyway, I can ping myself, i.e. pinging 192.168.101.226 gives an answer.
>Pinging 192.168.101.225 results in timeout. The Linux machine's Cipe
>daemon does not report any activity (kx or anything else), so the tunnel
>is not up.
>
>However, something does happen. When I monitor the traffic at the Linux
>end with tcpdump, there are UDP packets coming from my NT machine to the
>Linux machine to the right port. These packets are somehow ignored, and
>ifconfig reports an ever increasing FRAME (error) count (it icreases
>steadily by some ten packets each ten minutes or so).
>
>---
>
>Any ideas what might be going on? Yes, I'd love to use tcpdump on my NT
>machine, but unfortunately Bill G. hasn't included it. And, yes, I'd love
>to switch on some sort of debugging on the NT side, but I do not know how
>to do that. (Yes, f*** the registry and give me decent configuration
>files!)
>
>Some version information:
>
>  Linux Box: RH 6.1, Cipe 1.4.3
>  NT machine: Win NT 4 WS, SP6a (128-bit), Cipe-Win32 beta 11 (1 Sep 00)
>
>Any idea what might be wrong? Have I made some stupid mistake in the
>routing, or something?
>
>Thank you very much for any constructive input!
>
>- Ville
>
>
>
>
>
>--
>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 | >> ]