> > I have compiled a kernel before so that shouldn't be too bad. I guess
> > > what I'm really asking is... is there a way to tell if IP_FORWARDING is
> > > active in a given kernel? I thought someone said that you could look in
> > > /proc/net somewhere, but I don't recall the exact details.
> >
> > If they did they are wrong, or at least wrong as far as "your" kernel
> > version. In kernel 2.0.29 this was NOT included, but IS presant in 2.0.30
> > and higher.
> > Anyway its not /proc/net its /proc/sys/net/ipv4 or 6 thesedays also.
> Well actually, whoever told him that is correct.
>
> The very first entry in /proc/net/snmp is a flag indicating whether
> IP_forwarding is enabled or not.
>
Yes indeed it is, but what people need to know is that the entry looks the
same even if you dont have IP_FORWARD in your kernel, to the naked (newbie)
eye its all mumbo jumbo, and he would not see that the only differance is on
the 4th line from the cat'ed /proc/net/snmp file, a 1 or a 2 is the
differance, 1 indicates Disabled and 2 indicates Enabled.
This would lead us to belive that we need to have a setting of 1 or 2 in
/proc/sys/net/ipv4/ip_forward however this is not the case.
1 == Enabled
0 == Disabled
So i must really appolagise for "wording" my message and saying "wrong",
its just near impossable to tell a newbie (if i may use that expression)
something like that and expect him or her to understand what is meant by
it.
As to my last message about scc interfaces just stopping transmitting, i
have found it to be memory problems which are apparent in the driver itself
and made even worse by kernel 2.0.31 which craches here under heavy loads.
Also my appoliges to the group, i sent some mails as RHS Linux user, yes i
have also defected from slackware to RedHat, i forgot to edit /etc/passwd
and enter my name.
-- Regards Richard, 73. inet soymsn.cfsjlm@hellea.be