Re: Multiple OS/2 PEERLAN help please

On 08/30/08 04:28 am Mike Luther wrote:

Earlier posted in OS/2 networking but no answer .. maybe here?

For the first time I'm contemplating a workstation on a substantial size
OS2 PEERLAN local network which I wish to connect to the Internet
individually but not to introduce IP interface to the whole LAN.

This means, as best I see it, there need to be two NIC cards in this
single box. The box I propose this on is an Intel 915GAVL motherboard
with the Intel 10/100 NIC chipset MCP2 latest everything. It works
beautifully now by swapping the TCP/IP LOCAL setup between LAN0 as
either a DHCP connection when connected physically to the supplied ADSL
modem, or .. when reset to a fixed address setup and plugged into the
local LAN. Of course a reboot is required for that methodology to work.

Now I want to use LAN interfaces, one on DCHP for the Internet. The
other one for only the PEERLAN connection. Or at least that is what I
think should be done.

Per what I understand about OS/2 LAN work, only one NIC can have DHCP
addressing. And obviously the 'standard' 127.0.0.1 private address will
remain. I contemplate using the current Intel on motherboard chip for
that DHCP connection as LAN0. As far as I know, I should maintain both
IBM's OS/2 NETBIOS and IBM TCP/IP protocols as normal for this chip
operation.

Next to maintain a common interface hardware scenario, I choose to use a
Kingston KTC-120 PCI slot second NIC card. I already have one installed
on the to be tested box. The normal OS/2 driver for it works fine. But,
as I think I should do, in this case I only ought to use the IBMOS/2
NETBIOS on this NIC interface, since it's only purpose is to connect to
the local PEERLAN operation.

My question next is what should the settings in the TCP/IP configuration
be here for the ROUTE setup?

Also I know from what I have seen so far, that a discrete ROUTE setup
ought to go in the SETUP.CFG operation for MPTN which ties this to the
expected LAN1 interface enable work for the KTC120 card.

Also, from memory long ago at this, for just fixed addressing, how goes
this? Can there be two different routers here, one for the ADSL
operation; the other for the local LAN? Even if only the interface to
the IP side handles DHCP and so on? How do we get around the conflict
that if there are two routers, both may be focused on 192.168.1.1 setup
addresses? Or is this some kind of a maybe more than dumbo switch game
and not just a router? On which side of the fence?

Many years back, when I first got an always-on high-speed Internet connection, I used an old 486 machine running InJoy as a firewall. Then I realized that my connections speeds were far, far slower than other customers of the same ISP were reporting.

I bought a LinkSys router/switch, connection speeds went way up, and the LinkSys took up far less space and used far less power.

Perce

.

Relevant Pages

  • Re: Help on Cisco ASA 5510 VPN IPsec
    ... Inbound TCP connection denied from 10.100.7.245/22 to 10.100.5.10/1953 flags SYN ACK on interface lan ... mtu wan 1500 ...
    (comp.dcom.sys.cisco)
  • Multiple NIC OS/2 PEERLAN help please
    ... For the first time I'm contemplating a workstation on a substantial size OS2 PEERLAN local network which I wish to connect to the Internet individually but not to introduce IP interface to the whole LAN. ... It works beautifully now by swapping the TCP/IP LOCAL setup between LAN0 as either a DHCP connection when connected physically to the supplied ADSL modem, ...
    (comp.os.os2.networking.misc)
  • NATD and Address Redirection
    ... interface and a private "LAN" address on the 2nd interface serving a ... group of windows machines on the LAN with private IPS. ... a test running VNC server on the ... It seems that the connection works ...
    (freebsd-hackers)
  • Re: Multiple OS/2 PEERLAN help please
    ... not to introduce IP interface to the whole LAN. ... address setup and plugged into the local LAN. ... The two NICs will be on different networks so routing *ought* to sort ...
    (comp.os.os2.misc)
  • Multiple OS/2 PEERLAN help please
    ... For the first time I'm contemplating a workstation on a substantial size OS2 PEERLAN local network which I wish to connect to the Internet individually but not to introduce IP interface to the whole LAN. ... It works beautifully now by swapping the TCP/IP LOCAL setup between LAN0 as either a DHCP connection when connected physically to the supplied ADSL modem, ... Per what I understand about OS/2 LAN work, only one NIC can have DHCP addressing. ...
    (comp.os.os2.misc)