wich are the files i must configure to have full acess to the internet (this includes icq and irc) from my other computer that runs windows. I'm connected by lan NE2000 , and i run SuSe 6.1 in my main computer.
Who is Participating?
rwenzlaConnect With a Mentor Commented:
I don't know what kernel options are standard on Suse but what you want to do is IP masquerading.  For that you'll need:

A kernel with the following options ON:

IP Firewall
IP Masquerading
IP Always Defragment
(There may be a few others, They are labled in the config

You can tell if Masquerading options are on if



You will need the package ipchains.

You very likely will need /usr/doc/HOWTO/IP-Masquerading-HOWTO.

You will need the autodial daemon, diald, or kernel 2.2.0 or greater where demand dialing is supported.  I'm assuming you have on demand pppd working on your main machine, and the ethernet working on both.

Phew . . .
1) Verify that you have the ip_masqerading kernel options on.  If not, you'll have to do a kernel re-compile, or install a pre-compiled one with them on.

2) you need to issue the following commands at boot (I have them in /etc/rc.d/rc.local):

/sbin/ipchains -F
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -i ppp0 -j MASQ
echo "1" > /proc/sys/net/ipv4/ip_forward

/sbin/depmod -a
/sbin/modprobe ip_masq_ftp
/sbin/modprobe ip_masq_quake
/sbin/modprobe ip_masq_irc
/sbin/modprobe ip_masq_cuseeme
.. . .

(These ip_masq_xxxx modules are only needed for the 'tricky' protocols, they are located in /lib/modules/2.2.x/ip4v on RedHat. Probably similar on SuSe.  Add all you need.  The echo "1". . . should work on any distrib. that follows SysVInit)

Next.  On your server, use the route command to add an entry for your local net if you havent done so already. And be sure the ppp0 routes to your ISP are correct and your ISP's host IP address (ip.ip.ip.ip) is listed as the default gateway.

/sbin/route add -net netmask -dev eth0

/sbin/route add default gateway ip.ip.ip.ip -dev ppp0

Finally, on your Win9x client.  In NetworkNeigh. -> Properties, assign a local net IP address (usually 192.168.1.n), a netmask for your local net (usually, add the IP, host, and DNS info of your
ISP to the appropriate sections, and Finally, add the local IP address of your server (usually as the default gateway.

As a shortcut, you can add names of the boxen to the /etc/hosts file on your linux box, and to \windows\system\hosts.txt on your Win9x box (though it doesn't seem to do much on the Win boxes.)

Now, I think I'll go to bed.

There are a lot, and they may depend on your distro :)

check the linux documentation project at:

The Network Administration Guide should have all the info (and/or pointers to it) you need.

I've been playing with RedHat 6.0 and Mandrake 6.1; you'll probably need to change the etc/sysconfig/network file only.

Another useful one is /etc/hosts (I use this one because I'm lazy, so I can avoid typing whole addresses for some machines I use often)

Of course, now you don't even need to know the files :) use netcfg, linuxconf, or whatever nice interface your distro gives you for that :)
Cy HDesktop Support AnalystCommented:
Depending on your distro:

-the IP address for a domain nameserver(dns)
-the telephone number to dial
-your login and password
-an IP address for your machine if the network you are connecting to isn't going to provide you a dynamic one
-whether or not you ISP usus an authentication method as PAP, CHAP or MS-CHAP. If so, you will need a secret to enable authentication. The secret will be a wrod or sequence of charaters.

Just some of the things you might need. Check system configuration of your distro version for any additional help.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.