Mailing List os2-wireless_users@2rosenthals.com Archived Message #6324 | back to list |
|
---|
I understand.
Thus, the E100B driver is bound to lan0 and the IBM Prism driver is
bound to lan1.
Confirmed.
Please ensure that you have *no* entries for lan1 in your TCP/IP
configuration notebook.
XWLAN should manage this entirely on its own.Agreed.
Could you please follow-up with a copy of \MPTN\BIN\SETUP.CMD as well\MPTN\BIN\SETUP.CMD:
as \MPTN\ETC\DHCPCD.CFG ?
Thank you again for your help!
This is surely an odd one. The IBM prism driver is quite old, too,
though I don't really suspect that that's the cause of this. If it
were just an XWLAN thing, then I might lean in that direction (some
lack of proper functionality for XWLAN to adequately see the device),
but at the command line, it should behave. The dhcpmon -t command
kills the DHCP client daemon, allowing it to switch to a different
interface via the -i parameter.
Subscribe: Feed,
Digest,
Index. Unsubscribe Mail to ListMaster |