wap54g to wrt54g

i have a wap54g and a computer connected to a switch. the computer can
ping the wap54g but can't ping the wrt54g.

the wap54g has the ip address of the wrt54g as the gateway and is set as
an access point. both use the same channel and ssid.

why can't the wap54g "see" the wrt54g?

it's driving me nuts! :-(

On Sun, 20 Mar 2005 22:28:33 GMT, bryan <(E-Mail Removed)>
wrote:

>i have a wap54g and a computer connected to a switch. the computer can
>ping the wap54g but can't ping the wrt54g.

What are the IP addresses of the WRT54G and the WAP54G? They should
NOT be the same, but must be in the same class c IP block (i.e.
192.168.1.xxx)

Are you using Linksys firmware, or some alternative firmware?

>the wap54g has the ip address of the wrt54g as the gateway and is set as
>an access point. both use the same channel and ssid.

The WAP54G only uses its IP address for configuration. Everything it
does is by bridging. Setting the gateway in the WAP54G does not
magically make it an IP router.

Are you using WDS?

Is the WAP54G in client mode, bridge, repeater, or access point mode?
It should be in client mode.

Have you setup any MAC address filtering in the WRT54G? If so,
disable this feature for now.

>why can't the wap54g "see" the wrt54g?
>it's driving me nuts! :-(

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558

On Sun, 20 Mar 2005 17:16:13 -0800, Jeff Liebermann wrote:

> On Sun, 20 Mar 2005 22:28:33 GMT, bryan <(E-Mail Removed)>
> wrote:
>
>>i have a wap54g and a computer connected to a switch. the computer can
>>ping the wap54g but can't ping the wrt54g.
>
> What are the IP addresses of the WRT54G and the WAP54G? They should NOT
> be the same, but must be in the same class c IP block (i.e.
> 192.168.1.xxx)

..254 and .245 respectively... see:

http://homepage.ntlworld.com/bryan.stevens1/network.jpg

> Are you using Linksys firmware, or some alternative firmware?

linksys. 1.42.2 on the wrt54g and 2.08 on the wap54g.

>>the wap54g has the ip address of the wrt54g as the gateway and is set as
>>an access point. both use the same channel and ssid.
>
> The WAP54G only uses its IP address for configuration.

o.k.

> Everything it does is by bridging. Setting the gateway in the WAP54G
> does not magically make it an IP router.

:-)

> Are you using WDS?

no... i didn't even know what it stood for until i looked it up! will it
help?

> Is the WAP54G in client mode, bridge, repeater, or access point mode? It
> should be in client mode.

it's in access point mode.

i read the documentation and it states that in client mode, the wap54g
will only communicate with another wap54g. in wireless repeater mode, it
will communicate with another wap54g or a wrt54g.

> Have you setup any MAC address filtering in the WRT54G?

yes.

> If so, disable this feature for now.

done... in fact, i thought that was the problem to begin with because i
forgot to disable it :-)

>>why can't the wap54g "see" the wrt54g? it's driving me nuts! :-(

it's still driving me nuts!

On Mon, 21 Mar 2005 18:02:53 GMT, bryan <(E-Mail Removed)>
wrote:

>.254 and .245 respectively... see:
>http://homepage.ntlworld.com/bryan.stevens1/network.jpg

Nice JPG of your network. It should "should" work as shown.

>linksys. 1.42.2 on the wrt54g and 2.08 on the wap54g.

Ummm... The WRT54G comes in v1.0, v1.1, v2.0, v2.2, and v3.0 hardware.
I can't guess which version. Assuming the latest V3.0 hardware,
you're way out of date. Current version is 3.03.6.
http://www.linksys.com/download/firmware.asp?fwid=233
Please verify your hardware version before upgrading.

>> Are you using WDS?
>no... i didn't even know what it stood for until i looked it up! will it
>help?

No. WDS is strictly for communicating between two access points (or
wireless routers). If you had a pair of WRT54G boxes, it could be use
to create a link in place of the WAP54G.

>> Is the WAP54G in client mode, bridge, repeater, or access point mode? It
>> should be in client mode.
>
>it's in access point mode.

WRONG! Go to client mode, do not pass go, send me the $200 you
collect. The WAP54G does not do WDS so you can't use it to connect to
a WRT54G router in WDS mode. It will only talk to the WRT54G in
client mode.

>i read the documentation and it states that in client mode, the wap54g
>will only communicate with another wap54g. in wireless repeater mode, it
>will communicate with another wap54g or a wrt54g.

I never read the docs so such things never bother me much. That may
have been true at one time, but not this week (with updated firmware).
I know of two systems using a WAP54G in client mode talking to a
variety of access points. However, I don't know if they're using the
stock Linksys firmware or some alternative (i.e. HyperWRT or
Sveasoft).

>> Have you setup any MAC address filtering in the WRT54G?
>yes.
>> If so, disable this feature for now.
>done... in fact, i thought that was the problem to begin with because i
>forgot to disable it :-)
>
>>>why can't the wap54g "see" the wrt54g? it's driving me nuts! :-(
>
>it's still driving me nuts!

1. Upgrade the firmware or install an alternative firmware.
2. Turn off MAC address filtering for testing. Same with IP
filtering.
3. Switch the WAP54G to client mode. Do the site survey thing.
4. Send me the $200.


--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558

On Mon, 21 Mar 2005 11:55:28 -0800, Jeff Liebermann
<(E-Mail Removed)> wrote:


>>linksys. 1.42.2 on the wrt54g and 2.08 on the wap54g.
>
>Ummm... The WRT54G comes in v1.0, v1.1, v2.0, v2.2, and v3.0 hardware.
>I can't guess which version. Assuming the latest V3.0 hardware,
>you're way out of date. Current version is 3.03.6.
> http://www.linksys.com/download/firmware.asp?fwid=233
>Please verify your hardware version before upgrading.

Your WAP54G is also slightly out of date. Version 2.08 firmware is
available.


--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558

On Mon, 21 Mar 2005 11:58:46 -0800, Jeff Liebermann
<(E-Mail Removed)> wrote:

>On Mon, 21 Mar 2005 11:55:28 -0800, Jeff Liebermann
><(E-Mail Removed)> wrote:
>
>
>>>linksys. 1.42.2 on the wrt54g and 2.08 on the wap54g.
>>
>>Ummm... The WRT54G comes in v1.0, v1.1, v2.0, v2.2, and v3.0 hardware.
>>I can't guess which version. Assuming the latest V3.0 hardware,
>>you're way out of date. Current version is 3.03.6.
>> http://www.linksys.com/download/firmware.asp?fwid=233
>>Please verify your hardware version before upgrading.
>
>Your WAP54G is also slightly out of date. Version 2.08 firmware is
>available.

Sorry. Ignore that. Got mixed up with another version issue. Too
many windows open on my desktop and too many Monday morning phone
calls.


--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558

On Mon, 21 Mar 2005 11:55:28 -0800, Jeff Liebermann wrote:

> On Mon, 21 Mar 2005 18:02:53 GMT, bryan <(E-Mail Removed)>
> wrote:
>
>>.254 and .245 respectively... see:
>>http://homepage.ntlworld.com/bryan.stevens1/network.jpg
>
> Nice JPG of your network.

thank you... most images are the property of linksys and i shamelessly
stole them to create the graphic.

i know they won't mind because i am a loyal customer :-)

> It should "should" work as shown.

it does work... when you remember to disable mac address filtering, set
the wap54g into client mode and wait for about half a dozen pings to "wake
up" the solaris box!

thanks a lot! :-)

shame on cisco/linksys though... this is not mentioned on their website,
the documentation that comes with the hardware or the help files on the
hardware's web interface.

>>linksys. 1.42.2 on the wrt54g and 2.08 on the wap54g.
>
> Ummm... The WRT54G comes in v1.0, v1.1, v2.0, v2.2, and v3.0 hardware. I
> can't guess which version.

1.1 hardware. the wap54g is, according to what i read on some web page, an
"older version" because it has 7 leds on the front panel.

> Assuming the latest V3.0 hardware, you're way out of date. Current
> version is 3.03.6.
> http://www.linksys.com/download/firmware.asp?fwid=233
> Please verify your hardware version before upgrading.

please verify which country i'm in from before offering me american
versions of firmware! :-)

------ 8< snip ------

> 1. Upgrade the firmware or install an alternative firmware. 2. Turn
> off MAC address filtering for testing. Same with IP filtering. 3.
> Switch the WAP54G to client mode. Do the site survey thing. 4. Send me
> the $200.

sure... here you go.

http://homepage.ntlworld.com/bryan.stevens1/200.jpg

:-)

and thanks again.

On Mon, 21 Mar 2005 22:24:58 GMT, bryan <(E-Mail Removed)>
wrote:

>it does work... when you remember to disable mac address filtering, set
>the wap54g into client mode and wait for about half a dozen pings to "wake
>up" the solaris box!

I'm not so sure its Solaris that's snoozing. I have several client
radios that like to go into "power save" mode if left alone for too
long. It drives my MRTG traffic and ping probe graphs nuts. The
DWL-900AP+ likes to snooze after about 3 minutes, and my SNMP probes
hit every 5 minutes. The result is that the first 2-4 pings are lost
while it wakes up. Seems to be a problem only with client radios, not
access points. I had to rescribble my Perl scripts to ignore the
first few pings.

>please verify which country i'm in from before offering me american
>versions of firmware! :-)

It's difficult enough to guess the hardware mutation. Now, I'm
suppose to guess the country? Well, since you're obviously a Red
Dwarf fan, methinks thou art in the UK.

>http://homepage.ntlworld.com/bryan.stevens1/200.jpg

Well, thanks for the effort but I have enough play money for my
Monopoly set. How about change for one of these?
http://www.joelscoins.com/millions.htm


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice http://www.LearnByDestroying.com
# (E-Mail Removed)
# (E-Mail Removed) AE6KS

On Mon, 21 Mar 2005 23:18:25 +0000, Jeff Liebermann wrote:

> On Mon, 21 Mar 2005 22:24:58 GMT, bryan <(E-Mail Removed)>
> wrote:
>
>>it does work... when you remember to disable mac address filtering, set
>>the wap54g into client mode and wait for about half a dozen pings to
>>"wake up" the solaris box!
>
> I'm not so sure its Solaris that's snoozing.

------ 8< snip ------

you're right again, jeff :-)

the solaris box is switched off so i tried pinging the wap54g with the
following results:

[root@rimmer ~]# ping 192.168.1.245
PING 192.168.1.245 (192.168.1.245) 56(84) bytes of data.
From 192.168.1.102 icmp_seq=1 Destination Host Unreachable
From 192.168.1.102 icmp_seq=2 Destination Host Unreachable
From 192.168.1.102 icmp_seq=3 Destination Host Unreachable
64 bytes from 192.168.1.245: icmp_seq=4 ttl=64 time=7.50 ms
64 bytes from 192.168.1.245: icmp_seq=5 ttl=64 time=1.91 ms
64 bytes from 192.168.1.245: icmp_seq=6 ttl=64 time=1.85 ms

>>please verify which country i'm in from before offering me american
>>versions of firmware! :-)
>
> It's difficult enough to guess the hardware mutation. Now, I'm suppose
> to guess the country? Well, since you're obviously a Red Dwarf fan,
> methinks thou art in the UK.

thou art correct!

seriously though, if less experienced users are coming here for help,
maybe the more experienced users should come up with some sort of
"questionnaire" the newbs have to complete before they get help.

if i had downloaded that firmware and flashed the ap, the results could
have been disastrous. is there an faq for this ng?

>>http://homepage.ntlworld.com/bryan.stevens1/200.jpg
>
> Well, thanks for the effort but I have enough play money for my Monopoly
> set. How about change for one of these?
> http://www.joelscoins.com/millions.htm

superb... i want one! :-)

On Mon, 21 Mar 2005 23:51:18 GMT, bryan <(E-Mail Removed)>
wrote:

>[root@rimmer ~]# ping 192.168.1.245
>PING 192.168.1.245 (192.168.1.245) 56(84) bytes of data.
>From 192.168.1.102 icmp_seq=1 Destination Host Unreachable
>From 192.168.1.102 icmp_seq=2 Destination Host Unreachable
>From 192.168.1.102 icmp_seq=3 Destination Host Unreachable
>64 bytes from 192.168.1.245: icmp_seq=4 ttl=64 time=7.50 ms
>64 bytes from 192.168.1.245: icmp_seq=5 ttl=64 time=1.91 ms
>64 bytes from 192.168.1.245: icmp_seq=6 ttl=64 time=1.85 ms

Yep. It takes a while to wake up the WAP54G in client mode.

>seriously though, if less experienced users are coming here for help,
>maybe the more experienced users should come up with some sort of
>"questionnaire" the newbs have to complete before they get help.

Nobody would read it. I've tried that in other newsgroups. I would
be elated if people would disclose:
1. What problem they are trying to solve.
2. What they have to work with.
3. Numbers not prose.
It's amazingly difficult to get people to supply simple things like
model numbers and versions.

>if i had downloaded that firmware and flashed the ap, the results could
>have been disastrous. is there an faq for this ng?

No FAQ. With the way wireless is changing daily, the FAQ would need
to be rescribbled daily. There are recovery proceedures for a failed
WRT54G firmware upgrade. Here's one:
http://voidmain.is-a-geek.net/redhat...g_revival.html

>> http://www.joelscoins.com/millions.htm
>superb... i want one! :-)

Watch out for the inflation rate. It's down to $1million dollars for
$1 via paypal. The Euro is doing a bit better at $1million Euro's for
$19:
http://www.milliondollarbill.com/euros01.html


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice http://www.LearnByDestroying.com
# (E-Mail Removed)
# (E-Mail Removed) AE6KS