said:
>>Dani says, if I read her correctly, "I preferred to set up y WL330g with
>>a static, non-conflicting address from the private IP range
>>172.16.0.0/20."
>And she chose 172.16.21.20 not 172.16.21.1. Try it that way.
I have read and reread Dani's configuration instructions, and I see no
reference to 172.16.21.20. Dani Says:
"The default IP address for configuration page is set to 192.168.1.1. As
many DSL routers use the same address, problems may occur. Hence the
WL330g can be assigned an IP address via DHCP, or may be configured to a
different static address. To use the device in client mode--where no DHCP
server is available!--I preferred to set up my WL330g with a static,
non-conflicting address from the private IP address range 172.16.0.0/20
(e.g.: 172.19.20.21); any similar address range would be suitable. The PC
or Laptop that accesses the configuration web server must have an address
in the same address range, of course (e.g.: 172.19.20.1). This IP address
can be joined with an IP Alias to the same LAN port in addition to the
regular IP address used for the normal network traffic (e.g.: 192.168.1.x,
assigned by DHCP). To provide this I modified the OS/2 TCP/IP setup batch
file \MPTN\BIN\SETUP.CMD as follows:
---- SETUP.CMD --------
route -fh
arp -f
ifconfig lo 127.0.0.1
dhcpstrt -i lan0 <---- regular IP
Address for lan0 by DHCP ifconfig lan0 172.19.20.1 netmask 255.255.255.0
alias <---- static Alias IP Address for lan0 ---- SETUP.CMD --------
Anyhow, I changed the IP address from 172.19.20.1 to 172.16.21.20. I can
still access the internet, but I still am unable to use the browser to
access the WL330g. I also tried using 172.19.21.20. Also, I am unable to
connect to any of those addresses using PING (in ethernet mode -- I didn't
try it in access mode).
>>>>Also, using a browser, like Dani suggests, I cannot access the pocket AP
>>>>by typing http://172.19.20.1 or anything else, either in ethernet mode or
>>>>in AP mode.
>Note that she accesses the ap via 172.16.21.20.
I can't see where she says that.
>Note that the 172.19.20.1 address in setup command is just another IP
>address for your system. That's what the word alias means. As Dani
>explains in the article, you need this address because the AP will only
>respond to IP addresses on the 172.19.20 network. This is a security
>measure to prevent remote devices from adjusting the APs configuration
>for you.
Thanks very much for the explanation. I did not understand about setup.cmd
and about host -- your explanation is very helpful.
Sandy
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
>> Next Message >>
Return to [ 06 |
October |
2005 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
