Re: [TCLUG:10339] Possible solution

["Brian J. Ackermann" <brianj@subrad.com>]

Ok, but what about the 205.218.57.[16-31] addresses?

I definately agree with you about yanking all info from the scripts and
starting over, its something I've been thinking about for some time now.

Thanks,
Brian

> Be sure that for each interface, gateway, netmask and perhaps broadcast
> are specified explicitly -- don't let the system fill in its defaults, we
> don't trust it. This is what you want:
>
> 1. Traffic to the internal network (192.168.6.0) has the internal network
>    interface (eth0, 192.168.6.48) as its gw.
> 2. Traffic to the Internet (0.0.0.0) has gw.bbros.com as its gateway.
> 3. /etc/hosts and/or DNS are properly configured so that using a name
>    (gw.bbros.com) in your routing table will work. Alternatively, you can
>    use gw.bbros.com's IP address in your table.
> 4. IPv4 Forwarding is enabled in your kernel, so that traffic from the
>    internal network (whose nodes have your eth0/192.168.6.48 listed as
>    their gateway) destined for the Internet will find its way out.
>
> Read the ifconfig(8) and route(8) man pages closely, to get an idea of how
> ifconfig(8) shapes the routing table, and to learn how you can poke the
> routing table by hand if required.
>
> I hope this helps. If anyone can find any flaws in my reasoning or factual
> errors in my explanation, please correct them.
>
> --
>   Christopher Reid Palmer : http://www.innerfireworks.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> For additional commands, e-mail: tclug-list-help@mn-linux.org
>
>