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: Neil Booth <NeilB@example.com>
- Date: Thu, 25 Feb 1999 20:00:07 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- Organization: ...
- References: <36BC4027.F853B657@example.com> <14014.16061.666836.934319@example.com> <36C15DF9.EC11314B@example.com> <14019.37054.723432.15506@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
Stephen J. Turnbull wrote: > One other thing, for some reason 2.2 kernels (or maybe it's > pcmcia-cs-3.0.8?) seem to automatically set default routes and there > is often a problem (SIOADDR or something like that) with explicit > route commands. Check your syslog for routing errors, maybe? But > this doesn't seem to cause me any grief. I've tried again under kernel 2.2.2 this time, but still no luck getting PPP to work. Here is the comparison of a route, netstat and ifconfig under 2.0.36 which works and 2.2.2 which doesn't. The only difference in setup is the kernel; I boot the same disk for both. Here's 2.2.2: [root@example.com /root]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface hiperarc1-ariak * 255.255.255.255 UH 0 0 0 ppp0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default hiperarc1-ariak 0.0.0.0 UG 0 0 0 ppp0 [root@example.com /root]# netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 203.216.40.12 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 203.216.40.12 0.0.0.0 UG 0 0 0 ppp0 [root@example.com /root]# ifconfig ppp0 ppp0 Link encap:Point-to-Point Protocol inet addr:203.216.42.136 P-t-P:203.216.40.12 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1514 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 Here's the same under 2.0.36: [root@example.com /root]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface hiperarc1-ariak * 255.255.255.255 UH 0 0 0 ppp0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default hiperarc1-ariak 0.0.0.0 UG 0 0 1 ppp0 [root@example.com /root]# netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 203.216.40.12 0.0.0.0 255.255.255.255 UH 1514 0 0 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 3584 0 0 lo 0.0.0.0 203.216.40.12 0.0.0.0 UG 1514 0 0 ppp0 [root@example.com /root]# ifconfig ppp0 ppp0 Link encap:Point-to-Point Protocol inet addr:203.216.42.200 P-t-P:203.216.40.12 Mask:255.255.255.0 UP POINTOPOINT RUNNING MTU:1514 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Memory:5bdf038-5bdfc20 Note the difference in the ppp0 config (2.0.36 has NOARP and MULTICAST unlike 2.2.2), 2.0.36 has the default route usage count as 1 whereas 2.2.2 doesn't. Also, the MSS entries are zeroed under 2.2.2. I'm not really sure what all this means. ping works fine; so e.g. Netscape says "www.slashdot.org contacted, waiting for reply" and the modem appears to be actually receiving data. It just seems to go in the bitbucket though, and Netscape times out. If anyone has any hints, I'd really appreciate this. This is preventing me from running 2.2.2. Cheers, Neil. ------------------------------------------------------------------- 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
- Follow-Ups:
- Re: tlug: 2 Problems with Kernel 2.2.1 upgrade
- From: "Stephen J. Turnbull" <turnbull@example.com>
- 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>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: Scsi devices
- Next by Date: 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