sobriquet <dohduhdah@yahoo.com> hath wroth:
>On 23 dec, 06:50, Jeff Liebermann <je...@cruzio.com> wrote:
>> sobriquet <dohduh...@yahoo.com> hath wroth:
>>
>> >On a home network, I'm using a LinkIt hub with various computers
>> >plugged in and they all access the web via a main computer that has 2
>> >network cards and runs ezproxy to share the network connection.
>>
>> I couldn't find much on the "Linkit Hub". *It appears to be UK only.
>> Got a URL?
>
>Can't find a link. There is no model number on the device.
>But it's just a simple hub with 8 ports from the brand "linkit".
Sorry, I misread your question. I thought the Linkit Hub was where
Ezproxy was running. No need for details on the hub.
>> >I've plugged a Linksys WAP54G Wireless-G Access Point into the hub
>>
>> What hardware version of the WAP54G? *Look on the serial number tag
>> for the version number. *Extra credit for supplying the firmware
>> version.
What hardware versions WAP54G?
What firmware version are you running?
Have you checked the Linksys web site for the latest firmware?
>> >with a laptop I'm able to connect wirelessly *via the Linksys device
>> >and browse the internet.
>>
>> Huh. *Did you goof and use Linksys instead of Linkit in the above
>> sentence?
>
>No. The Linkit device is not wireless. The Linksys device is wireless
>but there is still a cable coming out one end that plugs into the
>linkit hub.
OK. Could I trouble you to explain how you're able to connect via
wireless to the WAP54G and browse the internet, but not be able to
configure the device? It's apparently working as expected. The only
thing that doesn't work is the CD, which isn't really necessary. Just
point your browser to 192.168.1.1 or 192.168.1.254 and you should be
able to manage the WAP54.
However, there's a catch. If your Ezproxy is delivering DHCP IP
addresses to your laptop, the delivered IP address might not be in the
same Class C IP block as the WAP54G. See if the 3rd digit in the IP
address on your laptop is a "1" as in 192.168.1.254. If not, then
temporarily assign a static IP address to your laptop such as
192.168.1.11 so that you can talk to the WAP54G. Then try connecting
to the management web interface at 192.168.1.254. If successful,
change the 3rd digit of the WAP54 IP address to be the same as the
rest of your network. Also change the WAP54 to either get its IP
address via DHCP (not recommended), or a static IP that is NOT already
being used on your network.
One more possible catch. If your network is on 192.168.1.xxx, and
your Ezroute is running its server at 192.168.1.1, and you have an
ancient version of the WAP54G, then you run a chance of having a
duplicate IP address at 192.168.1.1. There's also a small chance that
your unspecified broadband connecting device uses 192.168.1.254 (such
as 2wire). Look for duplicated IP's.
>> >However, when I try to use the CD that comes
>> >with the Linksys device, it can't establish a connection to the device
>> >to configure the settings.
>>
>> That's easy. *Don't use the CD. *You don't need it. *Plug a PC into
>> the WAP54G. *You may need a crossover ethernet cable. *Check if the
>> lights come on normallyl on both the WAP54G and the computah. *Point
>> your web browser to whatever is the deafult IP address for the WAP54G.
>> It's either 192.168.1.245 or 192.168.1.1 depending on WAP54G version.
>> Do the setup thing. *When done, move the cable to the Linkit thing.
>> Done. *
>Somehow I can't reach those addresses.
>The local computers all have IP addresses assigned in the range
>192.168.0.[0..255] and they work via a proxy 192.168.0.1.
>With subnet mask 255.255.255.0.
Bingo. See paragraph above starting with "However, there's a
catch...". You'll need to temporarily juggle IP's on your laptop so
that you can configure the WAP54G and change its IP address. No big
deal if you've done it once or twice. Pain in the posterior if this
is the first time.
>> Oh, you might have to power cycle everything to deal with any changes
>> in connected MAC addresses caused by juggling the hardware around.
>>
>> >For instance, I want to specify a WEP security key.
>>
>> WEP sucks. *If that's all that's offered, you're using an ancient
>> hardware and/or firmware version. *Use WPA-PSK (WPA-personal). *If you
>> must use WEP, use the hex key instead of the ASCII. *There's a stupid
>> bug in the way many devices convert an ASCII 5 or 13 character key,
>> into a 10 or 26 Hex character WEP key.
>Well, any key is better than no key. But I'll try WPA-PSK if I can
>manage to configure the linksys device.
There are those that will argue that a false sense of security is
worse than no security. Current hacking software can break WEP keys
in about 2-3 minutes.
>Hopefully I've been able to provide some more details.
Nope. You've supplied all that's necessary. It was the IP addresses
that were missing. Incidentally, you can sorta cheat and setup
EZproxy for a
netmask = 255.255.0.0
That will allow 192.168.0.xxx and 192.168.1.xxx networks to coexist
simultaneously. However, many routers and some software don't allow
this because it requires more address table space. I would just move
the WAP54 IP address and be done with it. (Also, label the IP on the
router or you will forget the IP address. I've been there).
> Here is a picture:
> http://www.ibbu.nl/~nsprakel/IMG_5228.JPG
Yech, speckle and noise. EXIF shows you have a Canon PowerShot S3 IS.
It took the photo at F2.7 and 1/13 sec without a flash. At 3PM you
should have had more light to work with, or used the flash.
Incidentally, I have an Canon S5 IS, which I really like.
--
Jeff Liebermann
jeffl@cruzio.com
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558