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

To: SBNelson,AT,thermeon,DOT,com, cipe-l,AT,inka,DOT,de
Subject: Re: XP routing problems
From: Michael Piko <michael,AT,piko,DOT,com,DOT,au>
Date: Fri, 29 Aug 2003 08:38:27 +1000
References: <7DB0958915FDD611961400A0C98F184633953A@WINTRIX.thermeon.com>
Reply-to: Michael Piko <michael,AT,piko,DOT,com,DOT,au>

----- Original Message -----
From: <SBNelson,AT,thermeon,DOT,com>
To: <michael,AT,piko,DOT,com,DOT,au>; <cipe-l,AT,inka,DOT,de>
Sent: Thursday, August 28, 2003 11:06 PM
Subject: RE: XP routing problems

Very common problem.

When you change the default route, that affects the ciped daemon too -- When
it tries to send out the UDP packets to the linux system, it looks up the
route to that system, doesn't find one so it uses the DEFAULT route.

    Exactly what I want it to do.

So, if you want your default route via the cipe link, then you need to add
routes to the linux system that does NOT use the default route.

    ????? Not sure I understand what you mean.
    The linux machine is set up as a router. I have tried a static route
that points back to the XP end     for any traffic for the 192.168.100.0/24
network (VPN), but that didnt make a difference.

> -----Original Message-----
> From: Michael Piko [SMTP:michael,AT,piko,DOT,com,DOT,au
> Sent: Wednesday, August 27, 2003 9:10 PM
> To: cipe-l,AT,inka,DOT,de
> Subject: XP routing problems
>
> Hi
>
> I have set up a cipe tunnel between my XP Laptop and my RH server. The
> linux server is acting as a router between my private network and the
> internet.
>
> When I bring up the vpn and set the other end to the default gateway, I
> cannot get out.
>
> I believe that the problem is with XP. I have used windump and can comfirm
> that when I do try to get out, the packets don't go throught the vpn.
>
> Has anyone had this happen and know of a remedy?
>
>
>
> Here is the route table:
>
> c:\>route print
> ==========================================================================
> =
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 50 56 c0 00 08 ...... VMware Virtual Ethernet Adapter (Network
> Address
> Translation (NAT) for VMnet8)
> 0x3 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter (basic
> host-only
> support for VMnet1)
> 0x4 ...00 00 39 b1 d6 3f ...... Intel(R) PRO/100 VE Network Connection -
> Packet
> Scheduler Miniport
> 0x10006 ...08 00 58 00 00 01 ...... CIPE VPN Adapter - Cisco Systems VPN
> Adapter
>
> ==========================================================================
> =
> ==========================================================================
> =
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 255.255.255.255 192.168.100.10 192.168.100.15
> 20
> 10.0.0.0 255.255.255.0 10.0.0.15 10.0.0.15
> 30
> 10.0.0.15 255.255.255.255 127.0.0.1 127.0.0.1
> 30
> 10.255.255.255 255.255.255.255 10.0.0.15 10.0.0.15
> 30
> 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.15 192.168.100.15
> 30
> 192.168.100.15 255.255.255.255 127.0.0.1 127.0.0.1
> 30
> 192.168.100.255 255.255.255.255 192.168.100.15 192.168.100.15
> 30
> 192.168.142.0 255.255.255.0 192.168.142.1 192.168.142.1
> 30
> 192.168.142.1 255.255.255.255 127.0.0.1 127.0.0.1
> 30
> 192.168.142.255 255.255.255.255 192.168.142.1 192.168.142.1
> 30
> 192.168.189.0 255.255.255.0 192.168.189.1 192.168.189.1
> 30
> 192.168.189.1 255.255.255.255 127.0.0.1 127.0.0.1
> 30
> 192.168.189.255 255.255.255.255 192.168.189.1 192.168.189.1
> 30
> 224.0.0.0 240.0.0.0 10.0.0.15 10.0.0.15
> 30
> 224.0.0.0 240.0.0.0 192.168.100.15 192.168.100.15
> 30
> 224.0.0.0 240.0.0.0 192.168.142.1 192.168.142.1
> 30
> 224.0.0.0 240.0.0.0 192.168.189.1 192.168.189.1
> 30
> 255.255.255.255 255.255.255.255 10.0.0.15 10.0.0.15
> 1
> 255.255.255.255 255.255.255.255 192.168.100.15 192.168.100.15
> 1
> 255.255.255.255 255.255.255.255 192.168.142.1 192.168.142.1
> 1
> 255.255.255.255 255.255.255.255 192.168.189.1 192.168.189.1
> 1
> Default Gateway: 192.168.100.10
> ==========================================================================
> =
> Persistent Routes:
> None
>
>
> results of ping:
> c:\>ping www.piko.com.au <http://www.piko.com.au>
>
> Pinging www.piko.com.au <http://www.piko.com.au> [203.147.185.5] with 32
> bytes of data:
>
> Destination host unreachable.
> Destination host unreachable.
> Destination host unreachable.
> Destination host unreachable.
>
> Ping statistics for 203.147.185.5:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
> c:\>
>
> and a tracert:
> c:\>tracert www.piko.com.au <http://www.piko.com.au>
>
> Tracing route to www.piko.com.au <http://www.piko.com.au> [203.147.185.5]
> over a maximum of 30 hops:
>
> 1 Destination host unreachable.
>
> Trace complete.
>
> c:\>
>
>
> Michael Piko
> michael,AT,piko,DOT,com,DOT,au <mailto:michael,AT,piko,DOT,com,DOT,au>

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