NAT is irrelevant to CIPE as long as the UDP packets
reach their destination and you send something originating
from the NATed side to bring up the connecton. Most
NATs have a timeout for how long it will remember the
destinations for UDP so you may have to do something
periodically if you need the tunnel to stay open for
----- Original Message -----
From: "Pablo Sanchez" <pablo,AT,purecarbon,DOT,com>
To: "CIPE-L" <cipe-l,AT,inka,DOT,de>
Sent: Wednesday, October 03, 2001 12:26 PM
Subject: Cipe behind a NAT Win2K machine - SOCKS5 solution?
> Excuse my ignorant question. :)
> I use a satellite connection to get to the internet. What I'm
> planning on doing is setting up CIPE between my home machine and our
> work machine. The twist is that I need to run a special accelerator
> software on the Win2K machine. The Win2K machine is setup to do NAT
> (ICS). Pictorially, here's how my setup looks:
> [work]<->[Sat Modem]<->[Win2K]<->[Linux FW running CIPE]
> My questions are:
> 1) Do I need to setup CIPE on the Linux box to talk to a SOCKS5
> 2) I've tried 1) -- <grin> --- and get the following error message:
> socks5_cmd: server: Address type not supported
> All pointers are appreciated!
> Pablo Sanchez mailto:pablo,AT,purecarbon,DOT,com
> Ph : 303.939.8897 Fax: 603.720.7723
> Cell: 303.717.5889
> 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: