| Subject: | Re: CIPE ports (was Re: CIPE, windows 2000 configuration (SOLVED)) |
| From: | Damion Wilson <dwilson,AT,ibl,DOT,bm> |
| Date: | Fri, 30 Aug 2002 15:56:54 +0200 |
| In-reply-to: | <15726.27154.188207.228523@saint.heaven.net> |
Well, this is certainly unexpected behaviour on my part and I have been designing all my installations with port forwarding on the fixed tunnel packets. Now I'll probably have to change CIPE-Win32 to match if Olaf confirms that this is the designed in behaviour. Olaf ? Are you listening ? DKW On Thursday 29 August 2002 06:05 pm, Dick St.Peters wrote: > Well, I don't consider it a "problem" ... and I was not involved in > configuring the user's adsl router. The adsl comes from another ISP; > I only provide the CIPE tunnel (and static virtual IP address). > > The port changing is probably the NAT box in action, and CIPE letting > it change is probably necessary for CIPE to work well with NAT'd > configurations. The only problem this caused was in some early > diagnostics looking for packets from the specified port.