| ????????? #4913 ?????? ?????? ???????? os2-wireless_users@2rosenthals.com |
????????? ? ?????? |
|
|---|
New Question:That is because the WLAN monitor works around a problem with the DHCP client: it kills the DHCP client daemon before issuing another dhcp request. If you don't do this, the dhcp client just does nothing...
If you are switching back and forth using a 'wired' and 'wireless' cmd files such as those that Neil wrote. How should the new widget be configured for the card? A. No radio and DHCP?
B. Radio on and don't configure?
C. Radio on and DHCP?
D. Radio on and Manually configure?
'Cause, I had it manually configured and the script didn't work. I changed it to 'Don't Configure' and the script worked but the unit didn't get an IP address but did work when I changed it to DHCP AFTER running the script.....
And what is the default netmask? 225.225.225.225 or 225.225.225.0 ?I coded that according to my TCP/IP reference:
|
???????????: ?????????,
????????,
?????????. ?????????? ???????? ?????????????? ?????? ???????? |