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

Subject: Re: CIPE-Win32 routing guestion
From: Jari Meklin <jmeklin,AT,masto,DOT,uku,DOT,fi>
Date: Tue, 28 Aug 2001 10:19:34 +0200
In-reply-to: <Pine.SOL.4.10.10108271119180.21231-100000@masto.uku.fi>

On Mon, 27 Aug 2001, Jari Meklin wrote:

> 
> Hi,
> 
> I am having a simple cipe connection between two WinNT-hosts (or should I
correction "I am trying to have a..."

> say routers, because there is no underlying net), one at my home and
> one at my school. With no much experience with the routing issues I found
> it hard to figure the correct routing. With Linux config I only had to add
> one route command with each host:
> 
> For the 10.20.30.1 host: 
> route add -net 10.20.20.0 netmask 255.255.255.0 gw 10.20.30.1
> 
> and for the 10.20.20.1 host:
> route add -net 10.20.30.0 netmask 255.255.255.0 gw 10.20.20.1
> 
> I simply tried to do the same with NT-boxes with no luck at all.
> While pinging the hosts (routers) I get "request timed out" error.
> 
> Now I am turning to this cipe-l with a request to help me. The
> other host's routing table follows.
> 
> at 10.20.30.1:
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 e0 29 11 58 ae ...... DEC DC21041 PCI Ethernet Adapter
> 0x3 ...08 00 58 00 00 01 ...... DKW Heavy Industries VPN Adapter.
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination        Netmask          Gateway       Interface  Metric
>         0.0.0.0          0.0.0.0         real__gw       real___ip       1
>         0.0.0.0          0.0.0.0       10.20.20.1      10.20.30.1       1
>        real_net    255.255.255.0        real___ip       real___ip       1
>       real___ip  255.255.255.255        127.0.0.1       127.0.0.1       1
>        10.20.20.0    255.255.255.0       10.20.30.1      10.20.30.1       1
>        10.20.30.0    255.255.255.0       10.20.30.1      10.20.30.1       1
>        10.20.30.1  255.255.255.255        127.0.0.1       127.0.0.1       1
>    10.255.255.255  255.255.255.255        real___ip       real___ip       1
>       127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
>       224.0.0.0        224.0.0.0        real___ip       real___ip       1
>       224.0.0.0        224.0.0.0       10.20.30.1      10.20.30.1       1
>   255.255.255.255  255.255.255.255        real___ip       real___ip       1
> ===========================================================================
> 
> So - what seems to be the problem with my routing table?
> 
> (Comment: real__ip is not really real. I am using an adsl-connection.)

Additions to my previous message,

While pinging the local cipe address and doing some packet sniffering I
get only one UDP-packet, which is from local ip to the remote ip (i.e.
local real address to remote real address). I keep getting these
UDP-packet from real local ip to real remote ip doing nothing - so they
are not the result from my ping, but just normal tries. I figure the
remote is not responding and I can not find any useful information from
that one UDP-packet (Info says: Source port:6543 Destination port: 6543).

What I am also trying to ask with my rather inaccurate english is that
should I be seeing something with my packet sniffer while pinging the
local fake address (10.20.30.1)?

Jari 





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