i have connect adsl sucess but fail in forward ip as in lan

i want to build one gateway with adsl-linux for my lan-gateway.

i have connect adsl in my rh sucess and browse with lynx ok. but once i want to set it as what i have done in my lan-work for a gateway between to interface, i fail.

i have two net adapter eth0 for adsl and eth1 for lan-gateway.
i config eth1 192.168.0.254,
then set ip_forward=yes.

restart network, then adsl-start, then ppp0 appear in ifconfig list.

normally the route will work and i can access the computers what locate in the other subnet via this gateway, but this time, it did not work.

i wonder, it may cause by none masq or nat. so i type in:
ipchaise -A forward -i ppp0 -j masq
alas, it echo that: protocal not available.

i do not know what my fault or what should i do.

could somebody give me some tips?

thanks ahead.
frederick

ok, its 2 something and im all out of mountain dew. I have read through every single linux book i have, and tried the man pages, and i have kind of the same problem. I have tried so many combinations of
route add blah blah blah im so confused =(
i have a netork on eth0, sharing an internet connection on my dialup modem ppp0.
here is my routing table when the modem is not connected:
destination gateway etc etc etc Iface
192.168.0.0 * eth0

when the modem is connected it is:
destination gateway etc etc Iface
209.247.23.46 0.0.0.0 ppp0
192.168.0.0 0.0.0.0 eth0
0.0.0.0 209.247.23.46 ppp0


what route command would allow a computer on the 192.168.0.0 network to have access to the dialup connection?



p.s. i dont know if its of an importance but the display from ifconfig ppp0 is
inet addr:63.214.125.83 P-t-P:209.247.23.46

thanks so much

the route command that you need to run on the computers on the lan that want to connect through the gateway is

where 192.168.0.1 should be replaced with the (private) internal address of the gateway machine. If the other computers on the lan have more than one ethernet card then you will have to check/change the eth0 to correspond to the device they use to connect to the gateway.

jaa

"protocol not available" is a little misleading: the masquerading module is not loaded

modprobe ip_masquerade

to the other problem (route):
pppd starts the script /etc/ppp/ip-up upon connecting and passes the new IP as parameter. this is where you should setup routing and firewalling. if you don´t, your route might be dropped when the IP changes.
make sure you have "nodefaultroute" in /etc/ppp/options.ppp0

[edit]
oops, sorry, didn´t read thoroughly enough. the clients of course need the gateway´s IP as default gateway.
[/edit]

[another edit]
"masq" has to be capital letters - this could be the problem too
[/another edit]

thanks, i tried it again