?????| os2-wireless_users@2rosenthals.com ?????????????? ????? #2126 |
????? |
|
|---|
Interesting solution! Haven't thought about this myself. So I tried itPitty! I really think that this switch should be transparent to TCPBEUI, as the NetBEUI client should not be aware at all of the underlying TCP/IP stuff. But OTOH you never know what the TCPBEUI stack does in order to make the protocol conversion work...
out (loop back interface as lan2, other subnet, TCPBEUI only bound to
this interface, ipgate on) with the following result:
Using lan0 (wired) it does work (domain logon, TCPBEUI access to
shares). Using lan1 (WLAN) it does not work completely (NO domain logon,
but TCBEUI access to shares).
(Have I told you already, that I still cannot figure out how this
TCPBEUI implementation works?)
So I switched back to the "two interfaces configured in the same subnet
configuration".
But I really think that this is the correctI doubt that the xwlan script should be run before the WLAN interface is configured. The purpose of the script is to run additional commands depending on the _configured_ WLAN interface, for this the WLAN interface must already be configured. The only thing that I could think of is to redesign the script interface and add two more events. SO it would not only be
sequence: Because it is possible to start a process then which strikes
when the interface is fully configured by XWLAN. But it's a bit hard to
code to step back in time when xwlan.cmd is started after configuring
the interface. ;-)
|
???????: ????,
??????,
??????. ????????? ??? ???????? |