On Sun, Jul 14, 2002 at 04:15:15AM -0400, Mike Burger wrote:
> On Sat, 13 Jul 2002, Anthony E. Greene wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 13-Jul-2002/15:39 -0400, Mike Burger <[EMAIL PROTECTED]> wrote:
> > >You don't set them to use 192.168.1.126 as the gate
On Sat, 13 Jul 2002, Anthony E. Greene wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 13-Jul-2002/15:39 -0400, Mike Burger <[EMAIL PROTECTED]> wrote:
> >You don't set them to use 192.168.1.126 as the gateway...you have them
> >use 10.10.10.1 as the gateway...it's the interface,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13-Jul-2002/15:39 -0400, Mike Burger <[EMAIL PROTECTED]> wrote:
>You don't set them to use 192.168.1.126 as the gateway...you have them
>use 10.10.10.1 as the gateway...it's the interface, on the router, that
>they can see, by virtue of their net
BTW...as for how to tell them, that will depend on the OS on the other
systems, and whether or not you're using DHCP or static IPs.
If you're doing DHCP, you can simply tell the DHCP server that the gateway
is 10.10.10.1, and it will give it to the clients at lease renewal.
For the ISC dhcpd,
You don't set them to use 192.168.1.126 as the gateway...you have them
use 10.10.10.1 as the gateway...it's the interface, on the router, that
they can see, by virtue of their network address.
You then set up ip_forwarding (set FORWARD_IPV4=yes" in
/etc/sysconfig/network), so that the firewall
Going to do something I've never tried before... building a Linux based
router/firewall. Currently the box is running Redhat 7.3 and will also be
doing DNS services. Both NICs are already installed... eth0 is
192.168.1.126 for the time being, and eth1 is 10.10.10.1. Eth1 is connected
to a hub w