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

Subject: RE: Problems with CIPE 2.0pre9 on Win2k
From: ewheeler,AT,kaico,DOT,com
Date: Mon, 8 Oct 2001 07:57:00 +0200
In-reply-to: <PDEMJGBEDHNIKIENAAJNOEFGDHAA.jbarnhill@nc.rr.com>

See www.regedit.com for changing MTU in 9x/w2k.

Yes; I think that 1472 is the MTU your workstation should be set to so you
don't fragment packets.

--Eric
On Sun, 7 Oct 2001, Jeffrey Barnhill wrote:

> I'm not sure how to check this.  It seems that 1500
> is the default for ethernet, but it is not explicitly
> listed in the registry.  Speedeguide.net (tcp/ip analyzer)
> tells me that my MTU is 1500 (but that's probably from
> my firewall (which is masquerading for my win2k box).
> Unless there's an easy way to check this, I'll add this
> to the list of "things to try" - explicity set both
> adapters on both ends to 1500.
> 
> If the cipe packets are being encapsulated, shouldn't the
> cipe MTU be set to like 1472(?) ?
> 
> -Jeff
> 
>  
> 
> > -----Original Message-----
> > From: ewheeler,AT,kaico,DOT,com [mailto:ewheeler,AT,kaico,DOT,com
> > Sent: Friday, October 05, 2001 3:07 PM
> > To: Jeffrey Barnhill
> > Cc: cipe-l,AT,inka,DOT,de
> > Subject: Re: Problems with CIPE 2.0pre9 on Win2k
> > 
> > 
> > 
> > Jeff-
> > 
> > Make sure your w2k system's MTU is the same as your MTU on the cipcbX
> > interfaces.  You're probably waiting on ip fragmentation.
> > 
> > -Eric
> > 
> > 
> > 
> > On Fri, 5 Oct 2001, Jeffrey Barnhill wrote:
> > 
> > > Earlier tonight, a friend and I setup CIPE (2.0pre9) on
> > > our Win2k machines.  The idea is to play games through
> > > each of our firewalls, while only having to punch 1 hole
> > > through the firewalls (1 ipchains, 1 LinkSys).
> > > 
> > > We got the connection to work (with 10-60ms ping times),
> > > tried an ftp connection....so far so good. The problems
> > > occurred after a few seconds of online-gaming, the games
> > > sporadically halted with each "halt" getting longer and
> > > (if not stopped) after 2-5 seconds, would cause the machine
> > > to stop responding (or reboot). (We tried Serious Sam and
> > > Quake 2.)  These were peer-to-peer games with one of us
> > > hosting, the other joining (we tested both machines as
> > > the host).  The host of the Serious Sam game would see some
> > > log messages about "resending sequences <xxx-yyy> or something
> > > like that.
> > > 
> > > We didn't have time, but our next 2 things to try were: 
> > >  1. Try different large UDP/TCP transfers
> > >  2. Take the firewalls out of the equation
> > > 
> > > 
> > > Has anyone seen any issues like this ? Any ideas ?
> > > 
> > > 
> > > Thanks,
> > > Jeff
> > > 
> > > --
> > > 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>
> > > 
> > 
> > -- 
> > 
> > Eric Wheeler
> > Network Administrator
> > KAICO
> > 20417 SW 70th Ave.
> > Tualatin, OR 97062
> > www.kaico.com
> > Voice: 503.692.5268
> > 
> > 
> > 
> > 
> 

-- 

Eric Wheeler
Network Administrator
KAICO
20417 SW 70th Ave.
Tualatin, OR 97062
www.kaico.com
Voice: 503.692.5268





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