I'm using the MNWAPB to allow me to access my linksys NSLU2 via the linksys WGA54G. The problem is that I can only get access to the nslu2 when the MNWAPB is set to station-adhoc (as opposed to standard AP, the first option in the dialog box).
When I set it to this and ping my nslu2 I lose almost every 10th packet.
WAP was not enabled but I was using the mac address access list. When I turned this off I wasn't losing each 10th packet but I was not only getting a maximum transfer rate of about 40KB/s and massive ping times. If this was a wired network i'd say that the speed settings were wrong but as this is wireless I don't know where to start.
My config :
LAN gateway- smoothwall machine connected to adsl.
MNWAPB - station-adhoc. No WEP. No dhcp server running.
WGA54G - adhoc mode. Static IP.
NSLU2 - static IP address.
Distance between the AP and the WGA is ~ 10 meters between which is just plasterboard and wood framed walls.
I've tried having the AP set to "AP" and the WGA54 set to infrastructure but it won't connect to it.
Any idea how I can troubleshoot this situation?
Full Version: MNWAPB to linksys WGA54g
Minitar Forums > Discontinued Products > Minitar 802.11B MNWAPB Wireless Access Point Issues & Firmware
Hi there.
How do you have things wired up. Do you have your NSLU2 wired to the WGA54G and the MNWAPB wired to your LAN gateway or the other way around ?
The WGA54G is built as a client device so I would assume you have it wired to the NSLU2. Then you would need to have the WGA54G configured in Infrastructure mode and the MNWAPB in AP mode. I would disable WEP and MAC filtering to start with to get everything running.
Regards,
S.
How do you have things wired up. Do you have your NSLU2 wired to the WGA54G and the MNWAPB wired to your LAN gateway or the other way around ?
The WGA54G is built as a client device so I would assume you have it wired to the NSLU2. Then you would need to have the WGA54G configured in Infrastructure mode and the MNWAPB in AP mode. I would disable WEP and MAC filtering to start with to get everything running.
Regards,
S.
serialmonkey: Its setup in the order that I listed them in the first post.
This is it exactly.
nslu2 -> ethernet -> wga54g -> thru the air -> MNWAPB -> ethernet -> 100MB switch -> ethernet -> smoothwall -> ethernet(from 2nd smoothwall interface) -> adsl modem.
Setup of each. (all netmasks are 255.255.255.0)
nslu2 - Static ip. 192.168.0.77 gateway 192.168.0.1 100MB full duplex.
wga54g - Static ip. 192.168.0.22 gateway 192.168.0.1 Switched to infrastructure mode.
MNWAPB - Static ip. 192.168.0.10 gateway 192.168.0.1. No WAP. No MAC filtering. AP mode. No dhcp server.
smoothwall - static ip. 192.168.0.1
Currently I am unable to ping 192.168.0.77 from the smoothwall machine.
MNWAPB settings screen caps
I do realise that the WGA and MNWAPB should be in infrastructure and AP modes respectively. The weird thing is that if I play around and put the MNWAPB into "Station-Adhoc" mode I am able to ping the end device (nslu2). However the speeds are bad and connection is flakey.
Any ideas???
This is it exactly.
nslu2 -> ethernet -> wga54g -> thru the air -> MNWAPB -> ethernet -> 100MB switch -> ethernet -> smoothwall -> ethernet(from 2nd smoothwall interface) -> adsl modem.
Setup of each. (all netmasks are 255.255.255.0)
nslu2 - Static ip. 192.168.0.77 gateway 192.168.0.1 100MB full duplex.
wga54g - Static ip. 192.168.0.22 gateway 192.168.0.1 Switched to infrastructure mode.
MNWAPB - Static ip. 192.168.0.10 gateway 192.168.0.1. No WAP. No MAC filtering. AP mode. No dhcp server.
smoothwall - static ip. 192.168.0.1
Currently I am unable to ping 192.168.0.77 from the smoothwall machine.
MNWAPB settings screen caps
I do realise that the WGA and MNWAPB should be in infrastructure and AP modes respectively. The weird thing is that if I play around and put the MNWAPB into "Station-Adhoc" mode I am able to ping the end device (nslu2). However the speeds are bad and connection is flakey.
CODE
ping -t 192.168.0.7
Pinging 192.168.0.77 with 32 bytes of data:
Reply from 192.168.0.77: bytes=32 time=1223ms TTL=64
Reply from 192.168.0.77: bytes=32 time=25ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=5ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=5ms TTL=64
Reply from 192.168.0.77: bytes=32 time=4ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=328ms TTL=64
Request timed out.
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=10ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=1401ms TTL=64
Request timed out.
Reply from 192.168.0.77: bytes=32 time=18ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=919ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Request timed out.
Reply from 192.168.0.77: bytes=32 time=2774ms TTL=64
Reply from 192.168.0.77: bytes=32 time=10ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=4ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=4ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Request timed out.
Reply from 192.168.0.77: bytes=32 time=907ms TTL=64
Reply from 192.168.0.77: bytes=32 time=7ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Pinging 192.168.0.77 with 32 bytes of data:
Reply from 192.168.0.77: bytes=32 time=1223ms TTL=64
Reply from 192.168.0.77: bytes=32 time=25ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=5ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=5ms TTL=64
Reply from 192.168.0.77: bytes=32 time=4ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=328ms TTL=64
Request timed out.
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=10ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=1401ms TTL=64
Request timed out.
Reply from 192.168.0.77: bytes=32 time=18ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=919ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Request timed out.
Reply from 192.168.0.77: bytes=32 time=2774ms TTL=64
Reply from 192.168.0.77: bytes=32 time=10ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=4ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=4ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=3ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Request timed out.
Reply from 192.168.0.77: bytes=32 time=907ms TTL=64
Reply from 192.168.0.77: bytes=32 time=7ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Reply from 192.168.0.77: bytes=32 time=2ms TTL=64
Any ideas???
Well it appears that the WAG is not associating to the MNWAPB. Does the WAG give you any debug/logging information that might explain why it's failing to associate ?
If it "sorta" works with the MNWAPB in station-adhoc mode that suggests that the WAG is also an Adhoc mode instead of an Infrastructure mode - even know you have it set to Infrastructure which is odd.
Regards,
S.
If it "sorta" works with the MNWAPB in station-adhoc mode that suggests that the WAG is also an Adhoc mode instead of an Infrastructure mode - even know you have it set to Infrastructure which is odd.
Regards,
S.
Thanks. Maybe the switch on the wga it is busted and its stuck in ad hoc mode. The problem is that it doesn't even work reliably in that mode. I can't even telnet into the nslu2 without the connection dropping before I get to the password prompt!
The wga doesn't really give you much at all in the web interface.
You can pretty much set the IP and see what wireless networks it can see. I can see my wireless network but it just won't "connect". It has the ability to manually select the network but when I do it just won't "associate" with it for some reason.
Another quick question. Is there any documentation on the net that says what the different modes actually mean and what the diferences actually are? ie. AP mode vs station-infrastructure mode. [edit] found it in the faq.
Also, what is the purpose of the "WLAN MAC" field in the "station" modes?
[edit]I assume that as its a station you put in the mac address of the machine your being the wireless nic for?
[Update] If I put the AP into "Station Ad-Hoc" mode then click "Select site survey" then select the one thing that pops up there I get a working but very slow connection (24.44KB/s). I don't get the packet drops every 10th or so packet like before however I do get very slow speeds and bad pings while doing anything ie. ftp transfers. It really surprises me that this actually works at all!
In ad-hoc modes do you need to manually select what network you want to connect to from the MNWAPB interface for the connection to happen?
[edit] Just found the FAQ's
The wga doesn't really give you much at all in the web interface.
You can pretty much set the IP and see what wireless networks it can see. I can see my wireless network but it just won't "connect". It has the ability to manually select the network but when I do it just won't "associate" with it for some reason.
Another quick question. Is there any documentation on the net that says what the different modes actually mean and what the diferences actually are? ie. AP mode vs station-infrastructure mode. [edit] found it in the faq.
Also, what is the purpose of the "WLAN MAC" field in the "station" modes?
[edit]I assume that as its a station you put in the mac address of the machine your being the wireless nic for?
[Update] If I put the AP into "Station Ad-Hoc" mode then click "Select site survey" then select the one thing that pops up there I get a working but very slow connection (24.44KB/s). I don't get the packet drops every 10th or so packet like before however I do get very slow speeds and bad pings while doing anything ie. ftp transfers. It really surprises me that this actually works at all!
CODE
Reply from 192.168.0.77: bytes=32 time=434ms TTL=64
Reply from 192.168.0.77: bytes=32 time=515ms TTL=64
Reply from 192.168.0.77: bytes=32 time=457ms TTL=64
Reply from 192.168.0.77: bytes=32 time=391ms TTL=64
Reply from 192.168.0.77: bytes=32 time=560ms TTL=64
Reply from 192.168.0.77: bytes=32 time=331ms TTL=64
Reply from 192.168.0.77: bytes=32 time=365ms TTL=64
Reply from 192.168.0.77: bytes=32 time=521ms TTL=64
Reply from 192.168.0.77: bytes=32 time=626ms TTL=64
Reply from 192.168.0.77: bytes=32 time=245ms TTL=64
Reply from 192.168.0.77: bytes=32 time=255ms TTL=64
Reply from 192.168.0.77: bytes=32 time=414ms TTL=64
Reply from 192.168.0.77: bytes=32 time=448ms TTL=64
Reply from 192.168.0.77: bytes=32 time=223ms TTL=64
Reply from 192.168.0.77: bytes=32 time=398ms TTL=64
Reply from 192.168.0.77: bytes=32 time=435ms TTL=64
Reply from 192.168.0.77: bytes=32 time=435ms TTL=64
Reply from 192.168.0.77: bytes=32 time=625ms TTL=64
Reply from 192.168.0.77: bytes=32 time=296ms TTL=64
Reply from 192.168.0.77: bytes=32 time=515ms TTL=64
Reply from 192.168.0.77: bytes=32 time=457ms TTL=64
Reply from 192.168.0.77: bytes=32 time=391ms TTL=64
Reply from 192.168.0.77: bytes=32 time=560ms TTL=64
Reply from 192.168.0.77: bytes=32 time=331ms TTL=64
Reply from 192.168.0.77: bytes=32 time=365ms TTL=64
Reply from 192.168.0.77: bytes=32 time=521ms TTL=64
Reply from 192.168.0.77: bytes=32 time=626ms TTL=64
Reply from 192.168.0.77: bytes=32 time=245ms TTL=64
Reply from 192.168.0.77: bytes=32 time=255ms TTL=64
Reply from 192.168.0.77: bytes=32 time=414ms TTL=64
Reply from 192.168.0.77: bytes=32 time=448ms TTL=64
Reply from 192.168.0.77: bytes=32 time=223ms TTL=64
Reply from 192.168.0.77: bytes=32 time=398ms TTL=64
Reply from 192.168.0.77: bytes=32 time=435ms TTL=64
Reply from 192.168.0.77: bytes=32 time=435ms TTL=64
Reply from 192.168.0.77: bytes=32 time=625ms TTL=64
Reply from 192.168.0.77: bytes=32 time=296ms TTL=64
In ad-hoc modes do you need to manually select what network you want to connect to from the MNWAPB interface for the connection to happen?
[edit] Just found the FAQ's
CODE
[Wireless PC]--------[WGA54G].........[Minitar]
|
|
[Router]--[switch]--[Wired PC's]
|
|
[Router]--[switch]--[Wired PC's]
Hi there,
Sounds like your WAG is stuck in adhoc mode. Adhoc definatly isn't going to be the most stable. I suggest you return your WAG and see if you can get it into infrastructure mode.
Regards,
S.
Sounds like your WAG is stuck in adhoc mode. Adhoc definatly isn't going to be the most stable. I suggest you return your WAG and see if you can get it into infrastructure mode.
Regards,
S.
DOH! Might see if I can get ahold of a different AP first and see if that make any difference.
Let us know how you go.
S.
S.
Hi
I too have been having issues with my MNWAPB when in ADHOC mode.
I have posted in "802.11B Minitar Wireless Access Point Modifications" probably should have posted to this forum..
Absolutely get things out of ADHOC and into AP/Infrastructure that has been my simple fix.
Best of luck
Ross
PS: I would also ensure that MAC address filtering is on as well - I'm amazed at how many APs my grid-parabola can see!
I too have been having issues with my MNWAPB when in ADHOC mode.
I have posted in "802.11B Minitar Wireless Access Point Modifications" probably should have posted to this forum..
Absolutely get things out of ADHOC and into AP/Infrastructure that has been my simple fix.
Best of luck
Ross
PS: I would also ensure that MAC address filtering is on as well - I'm amazed at how many APs my grid-parabola can see!
The issue is he can't get his other device out of adhoc mode so infrastructure isn't an option that is available at this time.
I've posted in your other thread regarding your adhoc problems.
S.
I've posted in your other thread regarding your adhoc problems.
S.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.