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

Subject: RE: Unable to ping remote interface from cipe-win32 NT
From: "Kevin Herzig" <Kevin,AT,Herzig,DOT,net>
Date: Thu, 3 May 2001 15:55:37 +0200
In-reply-to: <80256A40.00634AFB.00@elle.hal.co.uk>

What's the routing table on the other machine?  What's your output on both
machines for ipchains -L -n?

-----Original Message-----
From: owner-cipe-l,AT,inka,DOT,de [mailto:owner-cipe-l,AT,inka,DOT,de Behalf 
Of Steve
Rubie-Todd
Sent: Wednesday, May 02, 2001 2:06 PM
To: cipe-l,AT,inka,DOT,de
Cc: Jon Frankcom
Subject: Unable to ping remote interface from cipe-win32 NT

Hi

Can anyone help with the following?

We are setting up a CIPE configuration where (stand-alone) HostA connects
to a network via a dial-up PPP connection. HostA can ping HostB's peer IP
(193.195.74.58) and ptp ip (192.168.230.2) addresses, and receive replies.
HostB can ping HostA's ptp ip (192.168.100.2) address and receive a reply.

The difficulty is in getting HostA to ping HostB's 192.168.230.1 interface.
 Issuing pings from a command prompt on HostA, once the link is up, we get
the following results:

"ping 192.168.230.2" will receive replies

"ping 192.168.230.1" will not get out past the modem on HostA (the Tx light
 does not flash).

Further details of the configuration are as follows:

HostA -- ppp0 ------------- Internet

Internet ----------------- (193.195.74.58) HostB (192.168.230.1)

HostA is a PC running MS Windows NT 4.0 Workstation SP6, and running
Cipr-Win32 v2.0-pre9.

HostB is running Linux, and CIPE v1.5.1.

The CIPE settings on HostA are as follows:

LAN IP Settings
---------------
LAN IP Address:          0.0.0.0         (udp port 31002)
Peer IP Address:    193.195.74.58  (udp port 31002)

PTP IP Settings
---------------
Local PTP:          192.168.100.2
Peer PTP:      192.168.230.2

key       <key here>

The CIPE settings (ie. options file) on HostB are as follows:

ipaddr         192.169.230.1
ptpaddr        192.168.100.2

me        192.195.74.58:31002
peer      193.195.74.18:31002

key       <key here>

HostA's routing table looks like this when the dial-up link and the CIPE
adapter and service are up. The entries with a network destination of
192.168.230.x have been added to the table "manually" (ie. using the "route
 add ..." command).

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    62.25.191.168   62.25.191.168      1
         62.0.0.0        255.0.0.0    62.25.191.168   62.25.191.168      1
    62.25.191.168  255.255.255.255        127.0.0.1       127.0.0.1      1
   62.255.255.255  255.255.255.255    62.25.191.168   62.25.191.168      1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1      1
    192.168.100.0    255.255.255.0    192.168.100.2   192.168.100.2      1
    192.168.100.2  255.255.255.255        127.0.0.1       127.0.0.1      1
    192.168.230.1  255.255.255.255    192.168.100.2   192.168.100.2      1
    192.168.230.2  255.255.255.255    192.168.100.2   192.168.100.2      1
        224.0.0.0        224.0.0.0    62.25.191.168   62.25.191.168      1
        224.0.0.0        224.0.0.0    192.168.100.2   192.168.100.2      1
  255.255.255.255  255.255.255.255    62.25.191.168   62.25.191.168      1

Regards

Steve Rubie-Todd

--
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 | >> ]