Text 114, 63 rader
Skriven 2006-08-03 19:57:17 av mark lewis (1:3634/12.0)
    Kommentar till text 113 av Mike Luther (1:117/3001.0)
Ärende: Help on multiple NIC's
==============================
 ML> But in this case, I want to use just this one new box for a dual
 ML> purpose.  I want to use it for DCHP connection via a router to the
 ML> Internet, but connect it to the local LAN and *NOT* allow the
 ML> exposure to the local LAN to the Internet.  I visualize that can be
 ML> done by choosing to leave my WAN connectivity via TCP/IP on only
 ML> the on-board LAN0 Intel 10/100 chipset. 

that should work but i believe a/the key may be in the routing tab in the
tcp/ip setup (ie: IP Forwarding)...

 ML> And then I propose to use the second NIC in the PCI slot to 
 ML> communicate with the local LAN via 'standard' OS/2 NETBIOS.   And 
 ML> no, *NOT* as NETBIOS over TCP/IP, grin!

the only time you would have a problem with that is if you allow the netbios
ports to be open to the WAN... i run everything over here as netbios on tcp/ip
and specifically block the netbios ports at the firewall to prevent them from
getting out... i have to run netbios this way due to interfacing with linux
samba stuffs which doesn't do netbios without tcp/ip...

 ML> So I go in and remove the NETBIOS protocol in the MPTS setup from
 ML> the LAN0 Intel 10/100 setup.

STOP! reboot the box before going any further... make sure this setup works...
then shutdown again and...

 ML> I then add the second NIC, the Kingston KT-120 unit as LAN1 and 
 ML> set it up only for NETBIOS there. 

STOP! reboot the box before going any further...

 ML> Looking at the NETBIOS setup parameters in that part of the MPTS
 ML> configuration, I see that we are still set up this way for the
 ML> proper NETBIOS host name and so on.  Of course we reboot to get
 ML> things going in CONFIG.SYS.

ah, ok... so maybe you only want/need to do the first reboot ;)

 ML> Then I go in to the TCP/IP LOCAL setup via the desktop, the TCP/IP
 ML> folder and so on.  In it I leave the DHCP operation for the LAN0
 ML> interface enabled.  In OS/2 it is only LAN0 which can use DHCP so I
 ML> am taught.  And, when booted, the box on TCP/IP only on that LAN0
 ML> is still working fine with a Linksys WRT-54GL router connected to
 ML> my cable service through DCHP for temporary test and research
 ML> addressing.

i'm not aware of this eth0/lan0 restriction for dhcp... it is my understanding
that one can dhcp several/all cards in a box... the key is that they must be on
different wired networks...

 ML> Then I go into the LAN1 interface and enable it.  I arbitrarily
 ML> assign this interface a non-used 192.168.1.## address with a net
 ML> mask of 255.255.255.0 as 'normal'.  I reboot.

however, i've also found that i seem to get the best of life when i do choose
my own nic addresses wherever i go ;)

i think you may be missing the reboot to verify the modified setup is working
before adding the second card and setting it up...

)\/(ark

 * Origin:  (1:3634/12)