Here is all I have to set up my gateway machine.
I noted you didn't mention ip_forward in your post. That might be the
problem.
Fill in your values for the $VARIABLES noted below.
As I understand it, you can ping the gateway machine from your daughter's
computer. That suggests that packets are going nicely through your gateway
machine. Maybe you are not masquerading these packets, and they are being
rejected out on the internet because they are a private ip number? Wild guess, here.
What do you see with tcpdump? Can your gateway machine ping beyond the
network gateway?
Joel


#! /bin/bash
case "$1" in
 start)
echo 1 > /proc/sys/net/ipv4/ip_forward <---are you doing this?
echo Restoring ipchains   <---Don't forget firewall issues
           /sbin/ipchains -F
           cat /root/ipchains.saved | /sbin/ipchains-restore -f
#entry to enable ftp through firewall  <---you may need these
            insmod /usr/src/linux/net/ipv4/ip_masq_ftp.o    
            insmod /usr/src/linux/net/ipv4/ip_masq_quake.o    
            insmod /usr/src/linux/net/ipv4/ip_masq_raudio.o    
            insmod /usr/src/linux/net/ipv4/ip_masq_mfw.o 
#entry to redirect internet traffic to internal hosts
ipmasqadm mfw -I -m 2 -r 192.168.0.6 80  <--- you may not need these
ipmasqadm mfw -I -m 3 -r 192.168.0.6 6699 
ipmasqadm mfw -I -m 4 -r 192.168.0.6  14
ipmasqadm mfw -I -m 5 -r 192.168.0.7  6346 
/sbin/ifconfig lo 127.0.0.0
route add -net 127.0.0.0 netmask 255.0.0.0 lo
/sbin/ifconfig eth0 192.168.0.2 netmask 255.255.255.0 up <--internal ip
route add -net 192.168.1.0 netmask 255.255.255.0 eth0
/sbin/ifconfig eth1 $IPADDR netmask $NETMASK broadcast $BROADCAST
/sbin/route add -net default gw $GATEWAY eth1
 ;;
 stop)

Here is my routing table for comparison.
Kernel IP routing table
Destination     Gateway Genmask     Flags Metric Ref   Use Iface
192.168.1.0  0.0.0.0   255.255.255.0   U     0      0   0 eth0
192.168.0.0  0.0.0.0   255.255.255.0   U     0      0   0 eth0
68.33.0.0    0.0.0.0   255.255.248.0   U     0      0   0 eth1
127.0.0.0    0.0.0.0   255.0.0.0       U     0      0   0 lo
0.0.0.0     68.33.0.1  0.0.0.0         UG    0      0   0 eth1


Joel

On Sun, Jan 13, 2002 at 12:46:03PM +1000, Keith Antoine wrote:
> 
> I never use this excuse normally but: I have XP for the moment on dual boot, 
> very rarely use it. However after setting up the 'sharing' for a 98 machine 
> downstairs (my daughters), the connection works fine. That said.
> 
> I had Mandrake up till last tuesday and it had a gui for setting up sharing 
> of internet access which worked fine till reboot, then I had to reconfigure 
> it. Since then I am back with Suse for a while, giving it another thumping, 
> but it will not share the cable access.
> 
> /sbin/route says::
> 
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 172.16.68.0     *               255.255.255.0   U     0      0        0 vmnet1
> 192.168.4.0     *               255.255.255.0   U     0      0        0 vmnet8
> 192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
> CPE-203-45-128- *               255.255.240.0   U     0      0        0 eth1
> default         CPE-203-45-128- 0.0.0.0         UG    0      0        0 eth1
> 
> >From the machine downstairs I can ping, 192.168.0.1 (this machine as per 
> ifconfig) I can ping 203.45.140.190; I cannot ping anything past this machine.
> 
> I have an IP set there of 192.168.0.2 plus netmask, Gateway 192.168.0.1.....
> I seem to remember possibly 2 defaults on the mandrake when it was working. 
> 
> So what is it I am mising and how do I correct it.
> 
> -- 
> Keith Antoine aka 'skippy'
> 18 Arkana St, The Gap, Queensland 4061 Australia PH:61733002161
> Retired Geriatric, Sometime Electronics Engineer, Knowall, Brain in storage
> 
> _______________________________________________
> Linux-users mailing list
> Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
_______________________________________________
Linux-users mailing list
Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users

Reply via email to