Re: Multiple OS/2 PEERLAN help please
- From: "Dave Saville" <dave@xxxxxxxxxxxxxxxxx>
- Date: 02 Sep 2008 08:51:53 GMT
On Mon, 1 Sep 2008 14:22:32 UTC, Mike Luther <mike.luther@xxxxxxxxxx>
wrote:
Thanks VERY much for your time Dave.
Dave Saville wrote:
On Sun, 31 Aug 2008 03:46:16 UTC, Mike Luther <mike.luther@xxxxxxxxxx>
wrote:
Thus do I need only one subnet here? The default one to the WAN side?
If you don't have "ipgate on" on the dual NIC box then anything coming
in from the WAN stops there and anything coming in on the LAN stops
there. The TCP/IP stack will not know what to do with the packets.
OK, I understand this.
Which is *exactly* what you want. But the IP addresses of both NICs
need to be different subnets as you cannot have two NICs on the same
box on the same subnet.
But I'm curious. Looking at the TCP/IP configuration object, if DHCP is in use
for the Lan0, which is to go to the WAN, it looks to me like there is no way to
tell the TCP/IP configuration tool what subnet to use.
<huge snip>
Mike. You seem to be a little confused as to subnet and subnet *mask*.
I see lower down you say you have a Zyxel - If you look in the docs
for that on the CD you will find a very good explanation of this
stuff.
In this case DHCP hands out all the required information on the WAN
side. Now as I understand your setup we have one OS/2 box that at the
moment is connected to *either* a router to the 'net, *or* a local
network that is connected together via a switch. Switches do not have
an address of their own, but it does look as though that LAN is using
192.168.1.* as it's subnet. As you say there is no router involved on
the LAN then they must all be using fixed addresses. We want to leave
that well alone :-)
Now *if*, fairly big if, there are *no* other connections to the
"modem" (Which BTW is actually a router.) then the first thing to
check is that this is indeed the case. Then you need to check what
address the modem/router hands out when they connect using DHCP. If it
is *not* a 192.168.1.* address then all that needs to happen is that
LAN0 needs to be set up for DHCP and LAN1 to fixed - Of course they
need to make sure to connect the ethernet cables to the correct NICs
:-)
If, as is entirely possible, it *does* hand out a 192.168.1.* address
then you need to get into the modem/router and change a couple of
things. Now you may be able to talk them through it or if the
modem/router is set up for WAN support then you could point your
browser to its *external* address and re configure it. The two thing
to be changed are:
1) The address of the modem itself - ie from 192.168.1.1 to, say,
192.168.0.1.
2) The DHCP range of addresses it hands out.
Make both changes and *then* reboot the modem and release/renew the
DHCP lease. You *may* need to restart the browser. Firefox in
particular seems to cache the TCP setup when he starts and does not
see subsequent changes.
Oh, it just struck me - what is connected to that modem when the OS/2
box isn't? If there is anything then it would depend on the other
stuff using DHCP. Otherwise fixed IPs would need to be changed.
HTH.
--
Regards
Dave Saville
NB Remove nospam. for good email address
.
- Follow-Ups:
- Re: Multiple OS/2 PEERLAN help please
- From: Mike Luther
- Re: Multiple OS/2 PEERLAN help please
- References:
- Re: Multiple OS/2 PEERLAN help please
- From: Mike Luther
- Re: Multiple OS/2 PEERLAN help please
- Prev by Date: The Latest FlashPlayer
- Next by Date: Re: Multiple OS/2 PEERLAN help please
- Previous by thread: Re: Multiple OS/2 PEERLAN help please
- Next by thread: Re: Multiple OS/2 PEERLAN help please
- Index(es):
Relevant Pages
|