[ale] network question

Mel Burslan mel.burslan at s1.com
Mon Aug 13 11:34:37 EDT 2001


Together with not being a networking expert, lately, due to a big site
move, I have been involved/forced to be involved in networking. As an
answer to your question, something on this hub must be talking to both
of the networks that you are telling about. Hub itself (or switch in the
same train of thought unless it is a Cisco with switch routing module or
equivalent) can not provide the routing functionality.

Assuming this hub/switch of yours is not an advanced (read as expensive)
unit, your topology should look something like this :

+---+
|   | ---A-------172.16.255.x
|   |
|   | ---B-------172.16.255.x
| H |   .
|   |   .
|   |   .
| U |   .
|   | --X--------172.16.255.x
|   |
| B | --Y--------172.16.200.x
|   |
|   |
|   |
|   |
|   |            Same machine with 2 physical interfaces  
|   | ----GW-------> 172.16.255.220---172.16.200.220 <--------+
|   |                                                         |
|   | --------GW----------------------------------------------+
|   |
|   |
|   |
+---+

Where Machines A thru X are on one subnet Machine Y is on the other
subnet whereas your GW machine having at least 2 separate network
interfaces, each talking to one of the two subnets and this machine
knowing how to route packet from one to the other subnet. (i.e. your
basic router configuration.

Hope it helps..

--Mel
+-------------------------------------------+
| DUMB = Disasters Usually Motivate Backups |
+-------------------------------------------+


Wandered Inn wrote:
> 
> Mel Burslan wrote:
> >
> > The answer is yes to both hub and switch. If you are using a plain old
> > dumb hub, you are the one calling the shots which devices can talk to
> > which other device(s) on any given IP address range/subnet. If you are
> > using a switch, the situation may get more complicated if there are
> > "virtual lan"s to get into the action. In which case, switch ports which
> > are going to be on the same subnet must be assigned to the same VLANs.
> 
> Okay, so a couple of folks say this is possible.  Question is, I'm not
> sure how this works.  For example, say I have a hub that contains
> 172.16.255.0, but I want to stick another machine on that hub with the
> ip of 172.16.200.15.  So how's the routing work?  I've tried this and
> this machine can't see any of the others.  The gw on this hub is
> 172.16.255.220, but I can't get the 172.16.200.15 machine to 'see' the
> gw.
> 
> --
> Until later: Geoffrey           esoteric at denali.atlnet.com
> 
> "Great spirits have always found violent opposition from mediocre minds.
> The latter cannot understand it when a man does not thoughtlessly submit
> to hereditary prejudices but honestly and courageously uses his
> intelligence." - Albert Einstein
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.





More information about the Ale mailing list