Poštni seznam arhiviranih sporo?il Prejšnje sporo?ilo naslednje sporo?ilo Nazaj na seznam

Od: Lewis G Rosenthal <os2-wireless_users@2rosenthals.com> Glava
Izvorno E-sporo?ilo
Pošiljalec: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Zadeva: OS/2 Wireless Users List: MPTS and wireless NIC
Datum: Sun, 13 Apr 2003 00:59:50 est5edt
Za: os2-wireless_users@2rosenthals.com

Briefly (income tax season in the US - no time!):

OS/2 will not allow you to enable the DHCP client on more than one adapter simultaneously. This has been true as far as I can remember, going back to Warp 3 Connect (and before, probably). The only way to get DHCP working for both adapters is the slight of hand which Mark points out below, i.e., Alt-F1 at the boot blob, then select an alternate CONFIG.SYS.

Now, for the alternate CONFIG.SYS to work, you also - as Mark has pointed out - need an alternate PROTOCOL.INI, etc. On my systems, which routinely switch from wired to wireless, I have the following:

   * CONFIG.W for wireless use (press W at the alternate config menu).
   * CONFIG.W changes the macs path from C:\IBMCOM to
     C:\IBMCOM\WIRELESS, the structure & contents of which look like so:

Directory of C:\IBMCOM\WIRELESS

4-07-03   8:26a     <DIR>           0  .

4-13-03  12:05a     <DIR>           0  ..

4-07-03   8:32a      1732           0  LANTRAN.LOG

11-08-02   9:55p     <DIR>           0  MACS

11-08-02   9:55p     <DIR>           0  PROTOCOL

2-04-03   9:29p      2100          35  PROTOCOL.INI

1-11-03   2:11p         0           0  RFCCACHE.LST

       7 file(s)       3832 bytes used

Directory of C:\IBMCOM\WIRELESS\MACS

11-08-02   9:55p     <DIR>           0  .

4-07-03   8:26a     <DIR>           0  ..

7-24-00   1:31p      7559           0  AIRO340.OS2

1-31-02  10:16a     50688           0  switch.os2

       4 file(s)      58247 bytes used

Directory of C:\IBMCOM\WIRELESS\PROTOCOL

11-08-02   9:55p     <DIR>           0  .

4-07-03   8:26a     <DIR>           0  ..

4-14-00  10:04a     18918           0  kdbnet.sys

4-14-00  10:08a    115524           0  landd.os2

2-11-00   9:17a       512           0  landll.exe

2-11-00   9:17a     30592           0  landlldd.os2

4-14-00  10:09a      2198           0  lanpdd.os2

4-14-00  10:09a     38197           0  lanvdd.os2

4-14-00  10:09a      4222           0  lanvmem.sys

4-14-00  10:09a     42085           0  nbtcp.exe

4-14-00  10:03a     69812           0  netbeui.os2

4-14-00  10:03a     16948           0  netbios.os2

4-14-00  10:07a     18996           0  odi2ndi.os2

4-14-00  10:09a    103780           0  tcpbeui.os2

1-23-02  12:34p       167           0  vproto.nif

      15 file(s)     461951 bytes used

Total files listed:

      26 file(s)        524030 bytes used

   * I have an alternate PROTOCOL.INI, which replaces references to
     IBMFEEO2.NIF with AIRO340_NIF.
   * Any references to \IBMCOM\PROTOCOL or \IBMCOM\MACS in CONFIG.SYS
     are changed accordingly in CONFIG.W to \IBMCOM\WIRELESS\PROTOCOL
     and \IBMCOM\WIRELESS\MACS.
   * Drivers and protocols referenced in PROTOCOL.INI will be loaded
     from the MACS directory underneath the location of PROTOCOL.INI,
     hence the need for the subdirectory structure.

Now, there's probably a more elegant way of handling the duplication of the directory structure underneath \IBMCOM\WIRELESS, most notably, TVFS could probably handle the PROTOCOL and MACS directories with symlinks to the actual \IBMCOM\PROTOCOL and \IBMCOM\MACS directories.

Note also that while I have the vswitch driver for VPC in there, it still does not support wireless NICs, as a result (IIRC) of the way in which the MAC address on the wireless NIC must be used to maintain connectivity with the access point. Spoofing it will break the connection (again, it's been awhile since I kicked this around with our friends at Innotek, so forgive me if I misspeak), however, I was told that they were working on a solution for the problem. So, meanwhile, I copied the vswitch driver over along with everything else, but it's definitely NOT needed (or functional with this setup).

Anyway, while the setup is a bit easier under W2K (or even Linux), it does work consistently. Also, for my wife's machine, as she's mainly wireless and only occasionally wired (well, _she's_ more than occasionally "wired," but her ThinkPad isn't!!), I have reversed the CONFIG.SYS and CONFIG.W setups, so that "W" refers to "wired" vis-ŕ-vis "wireless".

Whew! And I tried to be brief!

madodel@ptdprolog.net wrote:

In <200304121457.h3CEvmjM057418@mail.cruzio.com>, on 04/12/03 at 10:55 AM,
  "Neil Waldhauer" <neil@blondeguy.com> said:

 

Now that I have the wireless NIC working, I'm going to have to get both
the built-in NIC and the wireless NIC to work together.
   


 

For my first test, I just changed the built-in Intel NIC driver to the
AmbiCom Prism driver, and all went well. Should I configure the wireless
NIC as a second NIC?
   


 

I want to use DHCP on whichever NIC gets a network. How can I configure
that?
   



If you figure it out please let us all know.  I tried for a year to get a
ired and wireless Nics to coexist and finally gave up and now only use
wireless in my laptops.  Perhaps with DHCP and using the same router, DHCP
server it might work.  TCP/IP only allows a single default route for all
connections, so I could never get access to the other one (this was with
the now ancient IBM Wireless LAN).  I couldn't get NetBIOS to work with
two Nics either.  Though I have two wired Nics in server which runs Injoy
firewall, without problem.

What others have done is use the Alt-F1 boot menu to select which
configuration to run on boot.  There was an article on how to do multiple
boot configurations a long time ago by Dan Casey in the VOICE Newsletter. It swaps config.sys with the appropriate driver and you have to swap
protocol.ini files also. http://www.os2voice.org/VNL/past_issues/VNL0898H/vnewsf2.htm


Mark

 


--
Lewis
---------------------------------------------------------------------
Lewis G Rosenthal, CNA
Rosenthal & Rosenthal            :  Accountants / Network Consultants
New York / Northern Virginia     :                www.2rosenthals.com
Novell Users International       :                 www.whytheylie.com
OS/2's new face is eComStation   :                www.ecomstation.com
--------------------------------------------------------------------- This OS/2 system (Apollo) uptime is 0 days 04:18 hours and 15 seconds


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Naro?iti: Poro?ilo (Feed), Izvle?ek (Digest), Indeks.
Odjava
E-pošta za mojstra za sezname