/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */


Good evening, Edmund,

> i seem to find that no matter where i exec it from, it still dont
> wanna play,whether its in the path or not...

        In reference to the following, I suspect.
        There has been a similar discussion going on on the ipchains
mailing list; another gentleman who used the strong ruleset also got
bitten by the hidden characters in that file.
        As a test, could you:
cd /etc/rc.d
mv rc.firewall rc.firewall.hold
touch rc.firewall
chmod 755 rc.firewall
mcedit rc.firewall      #Use your favourite editor and type in the 
                        #lines by hand.  Comments are optional
/etc/rc.d/rc.firewall

        I suspect that this version will work just fine.
        David - could you provide a sanitized version of the strong
ruleset?  Many thanks.
        Cheers,
        - Bill

On Sun, 5 Dec 1999, Edmund Craske wrote:

> I have Red Hat 6.0 and I want to share a 56k modem connection over my local
> LAN. I have the ppp connection working on my linux box already, and can
> successfully ping and hostname lookup on that connection.
> I am using ipchains which came with red hat, and the semi-strong ruleset from
> the ip-masq-howto 1.79. I have configured the ipchains ruleset correctly as
> far as i know with the correct ip addresses (192.168.100.*) at the top of the
> file, and set up the dynamic ip bit for getting my ip address like so:
> 
> #CRITICAL:  Enable IP forwarding since it is disabled by default since
> #
> #           Redhat Users:  you may try changing the options in
> /etc/sysconfig/network from:
> #
> #                       FORWARD_IPV4=false
> #                             to
> #                       FORWARD_IPV4=true
> #
> echo "1" > /proc/sys/net/ipv4/ip_forward
> 
> 
> # Get the dynamic IP address assigned via DHCP
> #
> extip="`/sbin/ifconfig ppp0 | grep 'inet addr' | awk '{print $2}' | sed -e
> 's/.*://'`"
> extint="ppp0"
> 
> # Assign the internal IP
> intint="eth0"
> intnet="192.168.100.0/24"
> 
> i hope that this is correct, it looks so, but i have not trained well enough
> to be an official linux boff yet, so i may overlook details somewhat.
> 
> I find that when i execute the script via the command line, it says:
> 
> bash: /etc/rc.d/rc.firewall: No such file or directory
> 
> I have checked, double checked and triple checked to see that i have typed
> right, put the script in the right place and set it all up correctly, but the
> error still appears. if you would like a copy of the whole rc.firewall file
> that i have, mail me and i will gladly send it to you.
> 
> I thought that it may just be saying that but ipmasq will still work, but i
> have followed the howto very closely on my other boxes to get them set up with
> gateways etc. and they cannot access the internet, or ping hosts or ip
> addresses. i can ping the linux box fine, and i have all the forwarding set to
> true and 1 on the linux box (i have read the howto VERY closely).

---------------------------------------------------------------------------
        Having Microsoft give us advice on open standards is like W.C. Fields 
giving moral advice to the Mormon Tabernacle Choir
        -- Scott McNealy, Sun Microsystems Inc.
(Courtesy of Michael Remski <[EMAIL PROTECTED]>)
--------------------------------------------------------------------------
William Stearns ([EMAIL PROTECTED]).  Mason, Buildkernel, named2hosts, 
and ipfwadm2ipchains are at: http://www.pobox.com/~wstearns/
--------------------------------------------------------------------------

_______________________________________________
Masq maillist  -  [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES 
UNSUBSCRIBING!
or email to [EMAIL PROTECTED]

PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.

Reply via email to