Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: 2 Problems with Kernel 2.2.1 upgrade
- To: tlug@example.com
- Subject: Re: tlug: 2 Problems with Kernel 2.2.1 upgrade
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Thu, 25 Feb 1999 22:06:09 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <36D52D37.444A3D84@example.com>
- References: <36BC4027.F853B657@example.com><14014.16061.666836.934319@example.com><36C15DF9.EC11314B@example.com><14019.37054.723432.15506@example.com><36D52D37.444A3D84@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "Neil" == Neil Booth <NeilB@example.com> writes: Neil> Note the difference in the ppp0 config (2.0.36 has NOARP and Neil> MULTICAST unlike 2.2.2), 2.0.36 has the default route usage Neil> count as 1 whereas 2.2.2 doesn't. Also, the MSS entries are Neil> zeroed under 2.2.2. I'm not really sure what all this means. MSS stands for "maximum segment size". I don't know what that means, but it being zero doesn't look good at all to me. Look up the man page for route and figure out how to set that MSS bigger than zero. Neil> ping works fine; so e.g. Netscape says "www.slashdot.org Neil> contacted, waiting for reply" and the modem appears to be Neil> actually receiving data. It just seems to go in the Neil> bitbucket though, and Netscape times out. MSS only applies to TCP connections, ping uses a lower level protocol so it wouldn't be affected. Don't ask me why it doesn't affect ethernet and loopback connections. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules." ------------------------------------------------------------------- Next Nomikai: March 19 (Fri), 19:30 Tengu TokyoEkiMae 03-3275-3691 Next Technical Meeting: April 10 (Sat), 12:30 place: Temple Univ. ------------------------------------------------------------------- more info: http://tlug.linux.or.jp Sponsor: PHT
- References:
- tlug: 2 Problems with Kernel 2.2.1 upgrade
- From: Neil Booth <NeilB@example.com>
- tlug: 2 Problems with Kernel 2.2.1 upgrade
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Re: tlug: 2 Problems with Kernel 2.2.1 upgrade
- From: Neil Booth <NeilB@example.com>
- Re: tlug: 2 Problems with Kernel 2.2.1 upgrade
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Re: tlug: 2 Problems with Kernel 2.2.1 upgrade
- From: Neil Booth <NeilB@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: "boot failed". Period.
- Next by Date: Re: tlug: "boot failed". Period.
- Prev by thread: Re: tlug: 2 Problems with Kernel 2.2.1 upgrade
- Next by thread: Re: tlug: 2 Problems with Kernel 2.2.1 upgrade
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links