No need to recompile if using the stock kernel from 5.0 (2.0.32). But...
[root@firewall /root]# cat /etc/sysconfig/network
NETWORKING=yes
FORWARD_IPV4=yes
HOSTNAME=firewall.internal.bgcorp.com
DOMAINNAME=internal.bgcorp.com
# GATEWAY=
# GATEWAYDEV=
[root@firewall /root]#
That second line is set to "no" by default. What happens is that forwarding
(which is used by masq) is built into the kernel but _by default in RedHat's
distribution_ is then turned off by this setup script. By changing this line
forwarding will be turned on when you reboot. Check the status by:
[root@firewall /root]# cat /proc/sys/net/ipv4/ip_forward
1
[root@firewall /root]#
If you get a "0" then forwarding has been turned off.You can turn it on
without rebooting by doing
cat "1" > /proc/sys/net/ipv4/ip_forward
and forwarding (and therefore masq) should work. I think there is a good
reason to update from 2.0.31 to 2.0.32, but masq should work on either one.
Jann Linder wrote:
>
> I have redhat v5...
>
> I have an internal network setup on 192.168.1.x and am wanting my other
> linux machines to be on the net through 192.168.1.10 which is redhat v5
> (kernal 2.0.31)
--
Ed Jaeger, CFO, Bohlender Graebener Corporation
[EMAIL PROTECTED]
http://www.bgcorp.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
