Re: bridging

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Phillip Windell (_at_.)
Date: 07/20/04 

Date: Tue, 20 Jul 2004 13:30:51 -0500

"Greg Brewer" <greg-spam@brewer.net> wrote in message
news:40fd565d$0$449$be864849@news.hal-mli.net...
> I'm not sure where my vocabulary is failing

No problem..... :-)

I just have to make extra sure I know what someone is really talking about
before I suggest changes to their stuff that might get them in trouble if it
doesn't work.

> ---------------------------------------------------------------
> Internet -- <T1 modem[1]> -- <Cisco PIX 501[1]> -- <Web Server>
>
> Internet -- <T1 modem[2]> -- <Cisco PIX 501[2]> -- <switch>
> -- <mail server, file server, workstations>
>
> ---------------------------------------------------------------

Ok. I understand now. We have something like that here. We have a Video
Server that downloads "content" that we broadcast over the air. It requires
a lot of Internet bandwidth for recieving, so rather than run it over our
already busy T1, we run it out a separate Internet connection all by itself.

Now I am going to assume that the T1 and PIX[1] is to be dedicated only for
the Web Server,...So....

The easiest way to deal with this:

[Option #1] - If each of the PIXs use same subnet on the Internal
Interface.....
Connect the Webserver's NIC into the switch right along with all the other
machines. Do the same for *both* PIXs. Just make them one big happy family
together. Then you want the Webserver's Network Settings to be statically
assigned and you would change it's Default Gateway to the PIX[1] that you
wanted it to use to get to the Internet. All other machines stay the way
they are and will use the PIX[2] to get to the Internet.

<Internet>-- PIX[1]--
                                   \
                                      - [Switch]--<all machines and
Webserver>
                                   /
<Internet>--PIX[2]--

[Option #2] - If PIXs have different subnets on the Internal
Interface........
Connect the Webserver's NIC into the switch right along with all the other
machines, but *not* the PIX[1] in this case. Just make them one big happy
family together. Then you add a second NIC to the Webserver and set it up
with the right network settings to talk to the PIX[1] and make the PIX[1]
the Default Gateway for the Web Server. The NIC on the Webserver that faces
the LAN requires a *blank* Default Gateway. Do *not* enable "routing" on the
webserver, it is not a router. As long as your LAN does not have multiple
subnets that the Webserver needs to "talk" to there isn't anything else to
do, but if there are other subnets then Static Routes must be added to the
Webserver's Routing Table to overcome the fact that the Gateway is blank.

<To Internet>---PIX[1]----<Webserver>
                                                     |
<To Internet>---PIX[2]-------[Switch]----<all machines> 

-- 
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Relevant Pages

  • Re: 2 Nics and 2 subnets traffic configuration
    ... 192.168.2.x network won't that disable internet access on the 192.168.0.x ... Would it work better if I use the server as the gateway? ... >> 2 locations w/ different subnets, this first location has a 192.168.0.x ...
    (microsoft.public.windows.server.networking)
  • Where to put my IIS WebServer ?
    ... I need advice on proper placement of my webserver. ... the proper gateway on the internal NIC config...that this gateway will become ... becomse un reachable from the internet ...
    (microsoft.public.inetserver.iis.security)
  • Re: home lan (three pcs, two eth in gw, no external router)
    ... >i understand i must do something so that the two subnets talk to each other, ... If B can access the internet then evidently you have routing enabled. ... For any further testing make sure firewall is deactivated. ... it the default gateway of the firewall's eth1. ...
    (comp.os.linux.networking)
  • Re: Apache behind/in front of gateway
    ... Inside clients or outside ... > Outside clients will be accessing the webserver, ... With in front of the gateway I mean that the webserver is ... > the corporate network but still accessible by Internet clients. ...
    (comp.unix.bsd.openbsd.misc)
  • Re: Client Internet old chestnut
    ... I have never used the same ranges, i know they should be different subnets ... > gateway on everything. ... >> getting out to the internet beyond is obviously a problem. ... >> that I can ping the external subnet but not the router. ...
    (microsoft.public.windows.server.sbs)