Jesus, I apologize for not catching the multiple default gateways.  A
host on a IP network can have no more than one default gateway.  In
the case of multihomed machines, the machine is able to communicate
with hosts on both networks because they are locally connected.  If
you were to ever do anything unusual, like put a router on your
private side, and add another subnet, you would have to either add a
static route or use a routing protocol.  But, anyone doing something
so unusual is going to already know that...
-Erik

On 4/18/05, Craig White <craigwhite@azapple.com> wrote:
> On Mon, 2005-04-18 at 15:31 -0700, Jesus E Zepeda wrote:
> > Hi, Erik:
> >
> > Yes, you are right that is a private network behind a firewall and
> > 10.100.1.245 is the firewall's interface to the 10.100.0.0/16 network.
> > At this network I have Windows machines accessing the Internet. But my
> > computer is the only instance that has two NICs.
> >
> > Craig, provided me with a pice of information that resulted an excellent
> > progress. I can ping on both sides of my computer and get on the
> > Internet now. He recommended adding at /etc/sysconfig/network these two
> > lines:
> >
> > GATEWAYDEV=eth0
> > GATEWAY=10.100.1.145
> >
> > Because at this moment I am not at the site where my computer is, I
> > setup a test environment at my office but I am lacking of a router. So,
> > if having 2 gateways is a nono and my computer is standing between these
> > two Gateway interfaces: The firewall and the internal router, I wonder
> > whether I will be able to access the other side of the private router as
> > well?
> >
> > I will check on this early tomorrow, but if you guys see what my problem
> > is (My Computer is in between two routers and has to access both sides),
> > what would be the best way to attain it?
> ----
> static route
> 
> man route
> 
> say for example, eth1 is 192.168.1.204 and you have a router that has an
> ip address of 192.168.1.1 and your internal lan has an ip network
> address scheme of 192.168.0.0/24
> 
> Then (assuming your router will permit this - you might want to be
> 'restrictive' on exactly which ports are forwarded through the router
> from your Linux box to the internal LAN as your Linux box is in
> untrusted waters)...
> 
> route add -net 192.168.0.0 netmask 255.255.255.0 dev eth1
> 
> (I think - this of course is untested).
> 
> plink around with this manually and once you get it to work...you could
> add this command to /etc/rc.d/rc.local like...
> 
> route add -net 192.168.0.0 netmask 255.255.255.0 dev eth1 &
> 
> so it is created every restart
> 
> Craig
> 
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change  you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change  you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss