2.4.18 broke my home network

2.4.18 broke my home network

Post by Carlo Grazia » Sun, 10 Mar 2002 23:32:38



OK, here's a poser for you guys.

I'm running RH 7.1, kernel 2.4.9-21.  I have two NICs.  The 3C9xx looks out
onto the Internet, the other (Dec Tuliip chip) serves the inner home
network on 192.168.42.0.

All of this works fine.  But I need to upgrade the kernel, so I grabbed a
stock 2.4.18, built (modularized out the wazoo), installed modules.  Kernel
written to floppy (I'm not an idiot).

Boot from floppy.  Now I can see the Internet, but I can't see hosts on
192.168.42.0.

To simplify matters as much as possible, I turned off all
firewalling/forwarding.  My routing table looks like this:

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.42.0    0.0.0.0         255.255.255.0   U     0      0        0 eth1
64.47.26.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         64.47.26.1      0.0.0.0         UG    0      0        0 eth0

A ping to www.yahoo.com gives no problems, but a ping to 192.168.42.250
(which exists) returns "Destination Unreachable".  I even tried
'ping -I eth1 -r 192.168.42.250'.  Nothing.

Bizarrely enough, I can see the activity lights on the hublet and on the
pinged host go on when I ping, so I know the card is sending something
out.

According to ifconfig, eth1 has both RX and TX packets.

So I thought "Aha!"  I must have not configured the Dec Tulip chip card
(eth1) correctly when I built the kernel.  As a test, I swapped the two
interfaces.  Swapped cables, swapped configurations, restarted networking.

Same damn thing.  I can still get out to yahoo, still can't see the host
that's sitting on my desk.

To confirm that I didn't*up the swap, I booted back into the old
kernel.  No problem, I can see my home net and the Internet, even with
eth1 on the Internet and eth0 on the home net.

My best guess, at this point, is that there's a newly-introduced parameter
in /proc/sys/net/ipv4 that I haven't set or unset, or have set but
shouldn't, but I can't determine what that might be.  I don't think it's
necessarily a good guess, but damned if I can come up with something
better.  But if you can, I'm eager to hear it.

Thanks in advance,
Carlo

--
***************************************************************************
*  Carlo Graziani                                 (773) 702-7973 (Voice)  *
*  Department of Astronomy and Astrophysics       (773) 702-6645 (FAX)    *
*  University of Chicago                 carloAToddjobDOTuchicagoDOTedu   *
*  5640 South Ellis Avenue                                                *
*  Chicago, IL 60637                    "They misunderestimated me."      *
*                                                    - Dubya              *
***************************************************************************

 
 
 

2.4.18 broke my home network

Post by Paul » Mon, 11 Mar 2002 01:43:44



Quote:> OK, here's a poser for you guys.

> I'm running RH 7.1, kernel 2.4.9-21.  I have two NICs.  The 3C9xx looks
out
> onto the Internet, the other (Dec Tuliip chip) serves the inner home
> network on 192.168.42.0.

> All of this works fine.  But I need to upgrade the kernel, so I grabbed a
> stock 2.4.18, built (modularized out the wazoo), installed modules.
Kernel
> written to floppy (I'm not an idiot).

> Boot from floppy.  Now I can see the Internet, but I can't see hosts on
> 192.168.42.0.

> To simplify matters as much as possible, I turned off all
> firewalling/forwarding.  My routing table looks like this:

> Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
> 192.168.42.0    0.0.0.0         255.255.255.0   U     0      0        0
eth1
> 64.47.26.0      0.0.0.0         255.255.255.0   U     0      0        0
eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         64.47.26.1      0.0.0.0         UG    0      0        0
eth0

> A ping to www.yahoo.com gives no problems, but a ping to 192.168.42.250
> (which exists) returns "Destination Unreachable".  I even tried
> 'ping -I eth1 -r 192.168.42.250'.  Nothing.

> Bizarrely enough, I can see the activity lights on the hublet and on the
> pinged host go on when I ping, so I know the card is sending something
> out.

> According to ifconfig, eth1 has both RX and TX packets.

> So I thought "Aha!"  I must have not configured the Dec Tulip chip card
> (eth1) correctly when I built the kernel.  As a test, I swapped the two
> interfaces.  Swapped cables, swapped configurations, restarted networking.

> Same damn thing.  I can still get out to yahoo, still can't see the host
> that's sitting on my desk.

> To confirm that I didn't*up the swap, I booted back into the old
> kernel.  No problem, I can see my home net and the Internet, even with
> eth1 on the Internet and eth0 on the home net.

> My best guess, at this point, is that there's a newly-introduced parameter
> in /proc/sys/net/ipv4 that I haven't set or unset, or have set but
> shouldn't, but I can't determine what that might be.  I don't think it's
> necessarily a good guess, but damned if I can come up with something
> better.  But if you can, I'm eager to hear it.

> Thanks in advance,
> Carlo

> --

***************************************************************************
Quote:> *  Carlo Graziani                                 (773) 702-7973 (Voice)
*
> *  Department of Astronomy and Astrophysics       (773) 702-6645 (FAX)
*
> *  University of Chicago                 carloAToddjobDOTuchicagoDOTedu
*
> *  5640 South Ellis Avenue
*
> *  Chicago, IL 60637                    "They misunderestimated me."
*
> *                                                    - Dubya
*

***************************************************************************

I'm kinda new to Linux, but I recently did a similar upgrade and the
firewall was changed from 'ipchains' to 'iptables' -- maybe you should check
if the new firewall is causing a problem.

Paul Miner

 
 
 

2.4.18 broke my home network

Post by Carlo Grazia » Mon, 11 Mar 2002 02:20:51



>I'm kinda new to Linux, but I recently did a similar upgrade and the
>firewall was changed from 'ipchains' to 'iptables' -- maybe you should check
>if the new firewall is causing a problem.

>Paul Miner

Thanks for the response.

I did suspect the firewall.  I was using iptables already, but I found that
the new kenel required an upgraded version of iptables, otherwise iptables
just exited with errors.  So I upgraded to iptables-1.2.4 the errors went
away, and the firewall came up as normal.

However, one of the first things I did to try to isolate the problem is
strip away the firewall.  The problem occurs with INPUT, OUTPUT, and FORWARD
policies set to ACCEPT and no rules.  So the firewall is not implicated.

Carlo

--
***************************************************************************
*  Carlo Graziani                                 (773) 702-7973 (Voice)  *
*  Department of Astronomy and Astrophysics       (773) 702-6645 (FAX)    *

*  5640 South Ellis Avenue                                                *
*  Chicago, IL 60637                    "They misunderestimated me."      *
*                                                    - Dubya              *
***************************************************************************

 
 
 

2.4.18 broke my home network

Post by Carlo Grazia » Mon, 11 Mar 2002 03:25:59


One additional clue I just twigged to:  "Destination Host Unreachable" means
that the route is OK, but there is no ethernet card on the network claiming
to be the requested IP.  So the arp table is broken.  And, in fact,


PING 192.168.42.250 (192.168.42.250) from 192.168.42.1 : 56(84) bytes of data.
From 192.168.42.1: Destination Host Unreachable

Address                 HWtype  HWaddress           Flags Mask            Iface
192.168.42.250                  (incomplete)                              eth1
...

I'm guessing from this that the activity lights on the hublet are in fact the
arp packets, and the arp response is not being interpreted correctly by
the kernel.  Why this should be is utterly baffling.

Carlo

On Sat, 09 Mar 2002 14:32:38 GMT, Carlo Graziani


>OK, here's a poser for you guys.

>I'm running RH 7.1, kernel 2.4.9-21.  I have two NICs.  The 3C9xx looks out
>onto the Internet, the other (Dec Tuliip chip) serves the inner home
>network on 192.168.42.0.

>All of this works fine.  But I need to upgrade the kernel, so I grabbed a
>stock 2.4.18, built (modularized out the wazoo), installed modules.  Kernel
>written to floppy (I'm not an idiot).

>Boot from floppy.  Now I can see the Internet, but I can't see hosts on
>192.168.42.0.

>To simplify matters as much as possible, I turned off all
>firewalling/forwarding.  My routing table looks like this:

>Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
>192.168.42.0    0.0.0.0         255.255.255.0   U     0      0        0 eth1
>64.47.26.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
>127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
>0.0.0.0         64.47.26.1      0.0.0.0         UG    0      0        0 eth0

>A ping to www.yahoo.com gives no problems, but a ping to 192.168.42.250
>(which exists) returns "Destination Unreachable".  I even tried
>'ping -I eth1 -r 192.168.42.250'.  Nothing.

>Bizarrely enough, I can see the activity lights on the hublet and on the
>pinged host go on when I ping, so I know the card is sending something
>out.

>According to ifconfig, eth1 has both RX and TX packets.

>So I thought "Aha!"  I must have not configured the Dec Tulip chip card
>(eth1) correctly when I built the kernel.  As a test, I swapped the two
>interfaces.  Swapped cables, swapped configurations, restarted networking.

>Same damn thing.  I can still get out to yahoo, still can't see the host
>that's sitting on my desk.

>To confirm that I didn't*up the swap, I booted back into the old
>kernel.  No problem, I can see my home net and the Internet, even with
>eth1 on the Internet and eth0 on the home net.

>My best guess, at this point, is that there's a newly-introduced parameter
>in /proc/sys/net/ipv4 that I haven't set or unset, or have set but
>shouldn't, but I can't determine what that might be.  I don't think it's
>necessarily a good guess, but damned if I can come up with something
>better.  But if you can, I'm eager to hear it.

>Thanks in advance,
>Carlo

--
***************************************************************************
*  Carlo Graziani                                 (773) 702-7973 (Voice)  *
*  Department of Astronomy and Astrophysics       (773) 702-6645 (FAX)    *

*  5640 South Ellis Avenue                                                *
*  Chicago, IL 60637                    "They misunderestimated me."      *
*                                                    - Dubya              *
***************************************************************************
 
 
 

2.4.18 broke my home network

Post by Skylar Thompso » Mon, 11 Mar 2002 02:18:52



> My best guess, at this point, is that there's a newly-introduced parameter
> in /proc/sys/net/ipv4 that I haven't set or unset, or have set but
> shouldn't, but I can't determine what that might be.  I don't think it's
> necessarily a good guess, but damned if I can come up with something
> better.  But if you can, I'm eager to hear it.

Can you see your NICs with the new kernel? Try running ifconfig as root and
see if they're both detected. Also see if you can ping your server from one
of your other boxen.

--

 
 
 

2.4.18 broke my home network

Post by Scot » Mon, 11 Mar 2002 05:40:42




>A ping to www.yahoo.com gives no problems, but a ping to 192.168.42.250
>(which exists) returns "Destination Unreachable".  I even tried
>'ping -I eth1 -r 192.168.42.250'.  Nothing.

>Bizarrely enough, I can see the activity lights on the hublet and on the
>pinged host go on when I ping, so I know the card is sending something
>out.

Same thing happened to me yesterday, after upgrading from 2.4.17 to
2.4.19-pre2-ac2.  I'm not entirely certain what the cause was, but I
decided to upgrade a few semi-related packages with hopes that it might
solve the problem.  Grabbed the latest modutils, iptables, bind, and
bind-utils packages from Rawhide and installed them -- and the problem
vanished.

Scott

 
 
 

2.4.18 broke my home network

Post by Nico Kadel-Garci » Mon, 11 Mar 2002 08:47:04




> >I'm kinda new to Linux, but I recently did a similar upgrade and the
> >firewall was changed from 'ipchains' to 'iptables' -- maybe you should
check
> >if the new firewall is causing a problem.

> >Paul Miner

> Thanks for the response.

> I did suspect the firewall.  I was using iptables already, but I found
that
> the new kenel required an upgraded version of iptables, otherwise iptables
> just exited with errors.  So I upgraded to iptables-1.2.4 the errors went
> away, and the firewall came up as normal.

> However, one of the first things I did to try to isolate the problem is
> strip away the firewall.  The problem occurs with INPUT, OUTPUT, and
FORWARD
> policies set to ACCEPT and no rules.  So the firewall is not implicated.

> Carlo

That's not "stripping away". That's "setting to wide open". "Stripping away
the firewall" is running "/etc/rc.d/init.d/iptables stop" or a similar
command for your distribution.

I'm glad it works now, though!

 
 
 

2.4.18 broke my home network

Post by Carlo Grazia » Mon, 11 Mar 2002 08:52:06






>> I did suspect the firewall.  I was using iptables already, but I found
>that
>> the new kenel required an upgraded version of iptables, otherwise iptables
>> just exited with errors.  So I upgraded to iptables-1.2.4 the errors went
>> away, and the firewall came up as normal.

>> However, one of the first things I did to try to isolate the problem is
>> strip away the firewall.  The problem occurs with INPUT, OUTPUT, and
>FORWARD
>> policies set to ACCEPT and no rules.  So the firewall is not implicated.

>> Carlo

>That's not "stripping away". That's "setting to wide open". "Stripping away
>the firewall" is running "/etc/rc.d/init.d/iptables stop" or a similar
>command for your distribution.

>I'm glad it works now, though!

Just imprecise use of language.  Of course I meant using the initscript
to stop the firewall/forwarding.  The result, however, is everything set
to accept.  I know the risk, I only did it for a short while to make a clean
test.

And no, it doesn't work now.  What the test showed was that the problem is
independent of the firewall/forwarding.

It does appear to have something to do with arp.

Carlo

--
***************************************************************************
*  Carlo Graziani                                 (773) 702-7973 (Voice)  *
*  Department of Astronomy and Astrophysics       (773) 702-6645 (FAX)    *

*  5640 South Ellis Avenue                                                *
*  Chicago, IL 60637                    "They misunderestimated me."      *
*                                                    - Dubya              *
***************************************************************************

 
 
 

2.4.18 broke my home network

Post by Carlo Grazia » Mon, 11 Mar 2002 08:54:29


On Sat, 09 Mar 2002 17:18:52 GMT, Skylar Thompson


>On Sat, 09 Mar 2002 14:32:38 GMT, Carlo Graziani

>> My best guess, at this point, is that there's a newly-introduced parameter
>> in /proc/sys/net/ipv4 that I haven't set or unset, or have set but
>> shouldn't, but I can't determine what that might be.  I don't think it's
>> necessarily a good guess, but damned if I can come up with something
>> better.  But if you can, I'm eager to hear it.

>Can you see your NICs with the new kernel? Try running ifconfig as root and
>see if they're both detected. Also see if you can ping your server from one
>of your other boxen.

>--


Both NICs are configured, and appear to be operating properly.  I cannot
ping the server from a box on my inner net.

Carlo

--
***************************************************************************
*  Carlo Graziani                                 (773) 702-7973 (Voice)  *
*  Department of Astronomy and Astrophysics       (773) 702-6645 (FAX)    *

*  5640 South Ellis Avenue                                                *
*  Chicago, IL 60637                    "They misunderestimated me."      *
*                                                    - Dubya              *
***************************************************************************

 
 
 

2.4.18 broke my home network

Post by Carlo Grazia » Mon, 11 Mar 2002 08:57:39





>>A ping to www.yahoo.com gives no problems, but a ping to 192.168.42.250
>>(which exists) returns "Destination Unreachable".  I even tried
>>'ping -I eth1 -r 192.168.42.250'.  Nothing.

>>Bizarrely enough, I can see the activity lights on the hublet and on the
>>pinged host go on when I ping, so I know the card is sending something
>>out.

>Same thing happened to me yesterday, after upgrading from 2.4.17 to
>2.4.19-pre2-ac2.  I'm not entirely certain what the cause was, but I
>decided to upgrade a few semi-related packages with hopes that it might
>solve the problem.  Grabbed the latest modutils, iptables, bind, and
>bind-utils packages from Rawhide and installed them -- and the problem
>vanished.

>Scott

This seems very promising.  Unfortunately, upgrading to the rawhide kernel
and friends leads me into dependency hell, but I'll try to get around it.

Carlo

--
***************************************************************************
*  Carlo Graziani                                 (773) 702-7973 (Voice)  *
*  Department of Astronomy and Astrophysics       (773) 702-6645 (FAX)    *

*  5640 South Ellis Avenue                                                *
*  Chicago, IL 60637                    "They misunderestimated me."      *
*                                                    - Dubya              *
***************************************************************************

 
 
 

2.4.18 broke my home network

Post by Michael Heimin » Mon, 11 Mar 2002 09:59:01



[SNIP]

Quote:> My best guess, at this point, is that there's a newly-introduced
> parameter in /proc/sys/net/ipv4 that I haven't set or unset, or
> have set but
> shouldn't, but I can't determine what that might be.  I don't
> think it's necessarily a good guess, but damned if I can come up
> with something
> better.  But if you can, I'm eager to hear it.

Try, as root on the local boxes, you can't ping:

# echo "0" >  /proc/sys/net/ipv4/icmp_echo_ignore_all

If it helps, check your firewall script, for something like this.

Michael Heiming
--
Remove the +SIGNS case mail bounces.

 
 
 

2.4.18 broke my home network

Post by Tech » Mon, 11 Mar 2002 11:26:38



> OK, here's a poser for you guys.

> I'm running RH 7.1, kernel 2.4.9-21.  I have two NICs.  The 3C9xx looks
> out onto the Internet, the other (Dec Tuliip chip) serves the inner home
> network on 192.168.42.0.

> All of this works fine.  But I need to upgrade the kernel, so I grabbed a
> stock 2.4.18, built (modularized out the wazoo), installed modules.
> Kernel written to floppy (I'm not an idiot).

> Boot from floppy.  Now I can see the Internet, but I can't see hosts on
> 192.168.42.0.

> To simplify matters as much as possible, I turned off all
> firewalling/forwarding.  My routing table looks like this:

> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 192.168.42.0    0.0.0.0         255.255.255.0   U     0      0        0
> eth1
> 64.47.26.0      0.0.0.0         255.255.255.0   U     0      0        0
> eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         64.47.26.1      0.0.0.0         UG    0      0        0
> eth0

> A ping to www.yahoo.com gives no problems, but a ping to 192.168.42.250
> (which exists) returns "Destination Unreachable".  I even tried
> 'ping -I eth1 -r 192.168.42.250'.  Nothing.

> Bizarrely enough, I can see the activity lights on the hublet and on the
> pinged host go on when I ping, so I know the card is sending something
> out.

> According to ifconfig, eth1 has both RX and TX packets.

> So I thought "Aha!"  I must have not configured the Dec Tulip chip card
> (eth1) correctly when I built the kernel.  As a test, I swapped the two
> interfaces.  Swapped cables, swapped configurations, restarted networking.

> Same damn thing.  I can still get out to yahoo, still can't see the host
> that's sitting on my desk.

> To confirm that I didn't*up the swap, I booted back into the old
> kernel.  No problem, I can see my home net and the Internet, even with
> eth1 on the Internet and eth0 on the home net.

> My best guess, at this point, is that there's a newly-introduced parameter
> in /proc/sys/net/ipv4 that I haven't set or unset, or have set but
> shouldn't, but I can't determine what that might be.  I don't think it's
> necessarily a good guess, but damned if I can come up with something
> better.  But if you can, I'm eager to hear it.

> Thanks in advance,
> Carlo

Hi, what does type 'netstat -taup' in the console. What does it say about
your ports?

Tech

 
 
 

2.4.18 broke my home network

Post by Tech » Mon, 11 Mar 2002 11:30:17



> OK, here's a poser for you guys.

> I'm running RH 7.1, kernel 2.4.9-21.  I have two NICs.  The 3C9xx looks
> out onto the Internet, the other (Dec Tuliip chip) serves the inner home
> network on 192.168.42.0.

> All of this works fine.  But I need to upgrade the kernel, so I grabbed a
> stock 2.4.18, built (modularized out the wazoo), installed modules.
> Kernel written to floppy (I'm not an idiot).

> Boot from floppy.  Now I can see the Internet, but I can't see hosts on
> 192.168.42.0.

> To simplify matters as much as possible, I turned off all
> firewalling/forwarding.  My routing table looks like this:

> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 192.168.42.0    0.0.0.0         255.255.255.0   U     0      0        0
> eth1
> 64.47.26.0      0.0.0.0         255.255.255.0   U     0      0        0
> eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         64.47.26.1      0.0.0.0         UG    0      0        0
> eth0

> A ping to www.yahoo.com gives no problems, but a ping to 192.168.42.250
> (which exists) returns "Destination Unreachable".  I even tried
> 'ping -I eth1 -r 192.168.42.250'.  Nothing.

> Bizarrely enough, I can see the activity lights on the hublet and on the
> pinged host go on when I ping, so I know the card is sending something
> out.

> According to ifconfig, eth1 has both RX and TX packets.

> So I thought "Aha!"  I must have not configured the Dec Tulip chip card
> (eth1) correctly when I built the kernel.  As a test, I swapped the two
> interfaces.  Swapped cables, swapped configurations, restarted networking.

> Same damn thing.  I can still get out to yahoo, still can't see the host
> that's sitting on my desk.

> To confirm that I didn't*up the swap, I booted back into the old
> kernel.  No problem, I can see my home net and the Internet, even with
> eth1 on the Internet and eth0 on the home net.

> My best guess, at this point, is that there's a newly-introduced parameter
> in /proc/sys/net/ipv4 that I haven't set or unset, or have set but
> shouldn't, but I can't determine what that might be.  I don't think it's
> necessarily a good guess, but damned if I can come up with something
> better.  But if you can, I'm eager to hear it.

> Thanks in advance,
> Carlo

Check your routing table again, I think the problem may be with the last
address 0.0.0.0 -> 64.47.26.0.

Just a guess......

Tech

 
 
 

2.4.18 broke my home network

Post by Carlo Grazia » Mon, 11 Mar 2002 13:38:07


Well, the goodenough solution turns out to be downgrade to 2.4.17, and
upgrade modutils.  I'm actually not sure which of the two made the
difference, although I suspect the networking code in 2.4.18 is doing
something new, and requires new - and underdocumented - care and feeding.

Whatever.  Thanks for all your suggestions.

Carlo

--
***************************************************************************
*  Carlo Graziani                                 (773) 702-7973 (Voice)  *
*  Department of Astronomy and Astrophysics       (773) 702-6645 (FAX)    *

*  5640 South Ellis Avenue                                                *
*  Chicago, IL 60637                    "They misunderestimated me."      *
*                                                    - Dubya              *
***************************************************************************

 
 
 

1. 2.4.17 to 2.4.18 broke networking syn's?

G'Day, eh?
I just updated to 2.4.18, and found that www.crucial.com was inaccessable,
though I didn't connect the two events until a call to crucial's webprog
team: they said that my address was sending reset and ack packets, but not
the other kind ( sorry I don't remember the other kind of syn packet's
name, I mess-around in linux, rather than code it ).
  I'd /thought/ that crucial had become non-accessable due to some weird
permissions problem or something, because their site /was/ accessable from
within crucial.com, but not to me.
  A redirector could get me to their site, but I couldn't connect directly,
using Mozilla, Netscape, Opera, Konqueror, /or/ wget.

( redirection hack:
   ???http://a1.g.akamaitech.net/6/6/6/6/www.crucial.com/
  this redirector defeats censorware, just in case you're trying to reach
The Centre for Religious Tolerance and your library's censorware won't
allow that -- peacefire.org tuned me in to that, and dig also fair.org  : )

The firewall I use is "levy", on ppp0, but that doesn't make any difference
since the same iptables script runs when I'm booting into 2.4.17 as 2.4.18,
eh?

Anyways, this is obscure, so I figured I'd tell whom it concerns, and if
you can think of a question whose answer I could actually give you that'd
help nail this one, just ask. . .

         \m

--

2. linux graphics problem

3. Linux Kernel Crash - Vanilla 2.4.18/Redhat 2.4.18-5

4. building a shell library of scripts

5. Linux Kernel Crash - Vanilla 2.4.18/Redhat 2.4.18-5 (2nd try =) )

6. Mounting CD-ROM Drive

7. what is the difference between 2.4.18-14 and 2.4.18-17.8.0

8. Changed FSTAB. Will not boot?

9. Very High Load on Disk Activity in 2.4.18 (and 2.4.18-pre8)

10. broken compile fixes for 2.4.18 or 2.4.19-pre1

11. APM broken on 2.4.18 with IBM Thinkpad X21

12. Busmaster DMA broken in 2.4.18 on Alpha

13. ext2 module in 2.4.18-pre4 broken?