HP3000-L Archives

May 2002, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tom Emerson <[log in to unmask]>
Reply To:
Tom Emerson <[log in to unmask]>
Date:
Thu, 9 May 2002 14:43:21 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (62 lines)
Simple answer: no can do without a router of some sort

Reason: subnet masks are a mask of /consecutive '1' bits/ starting from the
MSB of the 4-octet IP address.  The first '0' bit indicates the break
between "network" and "machine" (host)

> -----Original Message-----
> From: [log in to unmask]

> Basically, ... I want ... two devices to connect to each other.
>
> The first device has IP address 10.175.139.134, subnet mask
> 255.255.255.0.
> The second has 192.168.0.1, subnet 255.255.255.0. So, to

Technically, the first address (10.175.139.134) is a "class A" address,
however you have applied a "class C" mask to that address and have
effectively "subnetted" your "10..." network into a network ID of
"10.175.139".

> Is it correct reasoning; will these two addresses with this
> subnet mask be able to connect

No, since 10.175.139 <> 192.168.0, these two networks cannot "talk" without
a router device of some sort.  [aside: also 'technically', neither of these
"networks" is allowed to "route" over the "internet"]

> To provide more background: I have a Compaq wireless USB adapter
> to provide network connectivity to another wireless device, via
> the W2K Pro workstation to which the USB adapter connects.

So if I understand this, the USB adapter is configured on the 192.168.0
"network" and the "other wireless device" is on the 10.175.139 "network".

> other wireless device should be able to see the workstation,
> and everything else the workstation sees. 192 addresses are allowed
> on this network, and routing issues should be resolvable.

I gather from this that the win2k's only connection to "the network" is via
the wireless adapter (i.e., it doesn't have a real NIC).  If that is the
case, then the win2k box is a red herring -- what you're talking about is
connecting the "other wireless device" into your "wireless network" [which,
for obvious reasons, shouldn't rely on the presence of a particular PC being
connected and/or powered at any given time]  The ONLY way you will be able
to do this is to congire the "other wireless device" to have a 192.168.0
"network" address [which may not be possible if you already have 250+
devices on 192.168.0...]

OTOH: if the w2k box DOES have a real "hardwired" connection, then your w2k
box IS your "router" -- the wireless adapter needs to be configured on the
10.175.139 "network" so that it matches the "other wireless device".  Your
w2k box will have TWO network addresses and should have "routing" enabled.
In this case, the "other wireless device" needs to have the IP address of
the w2k's wireless adapter configured as it's "gateway"; and the w2k box
[may] need a static route to the 10.175.139 "network" [or other devices on
the network may or may not need that "static route" configured.  Basically,
you would use the w2k's "192.168.0.1" address as the gateway to the
10.175.139 "network"]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2