On Saturday 21 April 2001 22:11, Mani Murugesan wrote:
> I am running Linux (RH7) on a IBM i series Notebook. Works Great!
>
> I still have this problem which I had already addressed to this list and
> have not solved yet: When I connect to the internet from my notebook and
> am on my LAN, I want internet access for the other boxes on the LAN. (proxy
> serving). I have a win partition on my notebook and if I can make proxy
Here's a mail I had written on PLUG. I'm posting it here for you. There's
another mail that someone else had sent for a similar query, but it said
almost the same thing... If things are still unclear, let me know offline and
I'll see if i can drag it out from my PLUG mailbox...
--------------------------------------------------
Client side config:
-------------------
1. On the windoze m/cs, from TCP/IP properties, set up the default g/w to
point to the linux box.
2. Add the Linux box in the DNS tab as well.
Server side config:
-------------------
If you want the slickest setup, you'll need SQUID as well as NAT.
1. Setup squid. (Read the dox to see how.. plenty of them available on the
net)
2. In your /etc/rc.d/rc.local file, add the following:
modprobe <mod_name1>
modprobe <mod_name2>
..
..
..
(You get the module names using 'modprobe -l | grep masq' - use just the
module names u find there.. This adds protocol based masquerading. These
little helper proggies are needed to allow the named protocols to work
properly... for instance, with ths ip_masq_ftp module loaded, the client m/cs
can do active ftp.)
3. Setup ipchains to allow masquerading for the local network.
# ipchains -A forward -s <localnet>/<net-bits> -j MASQ
# /etc/rc.d/init.d/ipchains save
(the ipchains save ensures that the masq rules are saved and will be restored
at boot up each time.. This is presuming u have a Redhat derived m/c.
<localnet>/<netbits> would normally look like 192.168.0.0/24
Also ensure that you have ipchains enabled at startup for your default
runlevel. [ Maybe with 'ntsysv' ] )
4. Set up a caching nameserver on the linux box. Again read the dox.
(The next step is optional, but makes sure that all web requests out of the
network get cached. Good practice if you're on a relatively large network. No
one can bypass squid then...)
5a. Edit /etc/squid.conf and do this:
httpd_accel_host virtual
httpd_accel_port 80
httpd_accel_with_proxy on
httpd_accel_has_host_header on
5b. # ipchains -A input -s <localnet>/<net-bits> -p tcp \
--destination-port 80 -j REDIRECT <port-squid-runs-on>
(Again save ipchains rules if required)
-----------------------------------------------------------------------
Voila! You should be done.
I'm assuming that you're using a stock 2.2 kernel...
With 2.4 kernels it's different - the masq part atleast...
HTH
-Faisal.
--
-====----====----====----====----====----====----====---
____
/ \
"@'| '..` |`@" L I N U X
/__| \__/ |__\ May the source be with you
\__U_/
--------------------------------------------------------
DON'T PANIC!
-The Hitchhiker's Guide To The Galaxy.
-====----====----====----====----====----====----====---
----------------------------------------------
The mailing list archives are available at
http://lists.linux-india.org/cgi-bin/wilma/linux-india-help
