Propably the problem that got me too:
[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.
One thing that can keep the link up if you have several clients masquerading
is DNS requests. We run a caching only nameserver (named) on the masquerade
box and the clients use the IP of the masquerade box as primary DNS, which
seems to help.
Jim Rainville wrote:
>
> So close! I checked my ifconfig output against yours and realized that my
> ppp link is being set up by some request at startup. So I tried to do some
> Internet stuff from the Linux machine and sure enough it worked like a
> charm. The problem now is that requests from remote machines aren't getting
> through for some reason. This is strange because I can ping the Linux
> machine and access it's drives via samba. I saw some posts about a similair
> situation recently so I need to do a little hunting. This is by far the
> toughest thing I've had to set up on this machine so far but I'm getting
> closer and closer (mostly thanks to you!).
>
> Thanks,
> Jim
>
> >
--
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]
