OK...
My system is similar to yours so what I did should work for you too.

Setting up Masquerading on your machine:

1: In /etc/sysconfig/network 
I changed the value of 
FORWARD_IPV4="false" to
FOWARD_IPV4="yes"
as this is set to false by default.

2: In /etc/rc.d/rc.local I put:

# fix network unreachable madness
/sbin/route add -host 255.255.255.255 dev eth0

# setting up IP masquerading for local network for 2.2.x and above (ipchains)
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -j MASQ -s 192.168.1.0/24 -d 0.0.0.0/0

# NOTE THE IP - CHANGE TO WHAT EVER IS APPROPRIATE FOR YOUR SETUP

# setting up IP masquerading for local network for 2.0.x (ipfwadm)
# /sbin/ipfwadm -F -p deny
# /sbin/ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0

# NOTE THE IP - CHANGE TO WHAT EVER IS APPROPRIATE FOR YOUR SETUP

# enable IP masquerading specifically for everything available
# /sbin/modprobe ip_gre.o
# /sbin/modprobe ip_autofw.o
# /sbin/modprobe ip_masq_mfw.o
# /sbin/modprobe ip_masq_portfw.o
# /sbin/modprobe ipip.o
/sbin/modprobe ip_masq_cuseeme.o
/sbin/modprobe ip_masq_ftp.o
/sbin/modprobe ip_masq_irc.o
/sbin/modprobe ip_masq_quake.o
/sbin/modprobe ip_masq_raudio.o
/sbin/modprobe ip_masq_user.o
/sbin/modprobe ip_masq_vdolive.o

Take a look in /lib/modules/your_kernel_version/ipv4/
and point to everything there. What is actually there will depend
on how your kernel is setup. The ones that are commented above go 
away if you compile the masquerading stuff into the kernel.


I am 99% sure thats all I did. Tho I did recompile the kernel 
to suit me better so if this dosent work, let me know and 
I'll look up the relevant stuff for the kernel.

Setting up the windows machines:

1: Right click on "Network Neighbourhood"
2: Choose "properties"
3: Double click TCPIP=>ethernet (or just TCPIP
 if there is only one option ie no dialup adaptor)
4: Under the IP Address Tab give your machine an 
appropriate IP and Netmask (eg 192.168.1.2 255.255.255.0)
5: Ignore the WINS Tab
6: Under the Gateway tab put the IP of your Linux box
(eg 192.168.1.1)
7: Under the DNS Tab
Enable DNS
Enter machine name (eg: buttercup)
Enter the DNS your Linux box uses (probably that of 
your ISP - in my case 61.8.0.2)
Enter the search domain your linux box uses (probably 
that of your ISP - in my case zip.com.au)
8: click ok to everything
9: feed it the disks it wants
10: restart it
11: you're set!


NOTES:
Forget diald to start with
Get a link up on your linux box and make sure 
the windows boxes can see the world ok.
Get this stuff working THEN start with diald 
cos there will be another set of glitches to 
deal with then. And I DONT understand 
diald at all yet.

 > > Finally I have diald working on the local box. What do I need to configure to
 > > get remote machines to initiate the dial up connection? I have 1 win98 box and 1
 > > other Linux  box connected in a small home network. Any help would be
 > > apprecited.
> 
> Thanks again for your reply. Just a little background. I have been using a little
> script for masquerading that I found at http://www.nerdherd.org/ipchains. All I did
> was put it in  /usr/sbin and after my ppp connection comes up I enter on the command
> line "masquerade" and it sets everything up. I don't think it makes any permanent
> changes to the rc.local file, nonoe that I see any way. I'm wondering if there is way
> to use this in tandem with diald.
> kernel ver:2.2.5-15 (ipchains installed)
> distro: RH6.0
> Something with diald is now strange. It keeps coming up and down on it's own. I
> appreciate all of your assistance, perhaps I can return the favour in the future.

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to