Re: Trouble with IP forwarding
Your answer can be found in the Mini-Howto, IP-Masquerade.
The network address 192.168.0.0 has been designated by the internet gods as
a non-routable network, this allows companies (and you and me) to use it for
internal use accomplishing two things. (1) We don't unnecessarly take up a
whole class-c for a few systems we wish to connect to the internet and (2)
since it is non-routable, a would-be attacker will have a dang hard time
getting inside your net.
The solution??? IP-Masquerading. The system acting as the gateway between
your client and your ISP will do some IP packet header substitution so the
ISP thinks all the traffic is comming from your gateway. Response packets
have the origial header restored when it hits your gateway so it can be
moved on to the proper system.
Good luck.
-Lane
-----Original Message-----
From: Michael B. Taylor <mtaylor@mapleloop.rmt.utk.edu>
To: debian-user@lists.debian.org <debian-user@lists.debian.org>
Date: Thursday, August 20, 1998 6:58 PM
Subject: Trouble with IP forwarding
>I am trying to get ip forwarding working between a hamm box and a
>Win95 box. Both machines have permanent ip addresses recognized by the
>campus name server.
>
>I compiled a custom kernel with the Debinized 2.0.34 source, with ip
>forwarding enabled. I installed a second net card in the hamm box and
>configured eth1 as 192.168.1.1. I established a route to the W95 box
>through eth1. I can get traffic between eth1 and the W95 box, but I cant
>get the hamm box to route traffic from the W95 box to the outside world
>through eth0. I have tried configuring the W95 box's gateway as
>192.168.1.1, and also the public (eth0) address of the hamm box.
>
>Obviously I am missing something here. Any deposits to my clue bag
>greatly appreciated.
>
>Mike
>
>
>--
>Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org <
/dev/null
>
Reply to: