You will not see transmissions from WAPs which have hidden SSIDs. inSSIDer will find those too.

Netgear is on channel 11 and Buffalo on channel 6
Is it worth changing them to see if signal improves?

What dB would you think is good?

Thanks
Neil

They are far enough apart that if there is nothing else in those ranges then it won't make any difference. Leave them as they are and only change if you think you are getting signal issues.

Hi

Well all seemed well to start with, did speedtest and was getting results averaging 6.0Mbps on Iphone, Ipad and Acer laptop all connected to Netgear with a ping of around 49ms. It suddenley slowed down on all of the above to about 0.2Mbps, ping still the same and Uplload is still consistent at 0.82Mbps(this hasn't changed at any point)
Looking at Inssider the signal remained the same at all times(well within a couple) -39.

I have tried changing security and even disabling it, but no difference.

Have you any ideas what may be causing this.

Thanks
Neil

PS Have now just tried speedtest at 6.20AM and without doing anything ping is 47ms, download 12.28Mbps and upload 0.81Mbps.

Edited by deleted (Sat 31-Dec-11 06:24:50)

Just to let you know what is happening:

Was monitoring signal on Inssider 2 and when the the connection slowed down to a halt, noticed that suddenly a lot of BT signals and a plus net signal were all being picked up all on chammel 10, so i changed the Netgear channel to 1 and speed was back, so monitoring now to see if it continues.

Neil

Glad you sorted it. In the end it is a matter of monitoring the channels to see which are best in your area.

The default Buffalo address range is 192.168.11.x

If you set the Netgear to a static IP of 192.168.11.99, the OP should set the router address range to 192.168.11.1 - 192.168.11.98.

Mysterious slow-downs commonly happen in a router-as-AP configuration due to conflict. Disconnect the cable between router and AP, powercycle them both, then switch them both on. After a few minutes, only then connect the cable. Works every time, unlike any other order or procedure. Do the same if ever you reboot or switch any device off/on or remove the cable.

InsSSider does not detect hidden SSIDs. In addition, unmodulated and non-WiFi interference, and the fact that the SNR you get depends not on the transmit beacon power of other networks, but on the amount of traffic, means looking at the channel graph is a poor way of selecting a channel. Cycling through channels one by one and observing the RSSI and its steadiness is the best way to use inSSider to select a channel.

If you select "non-overlapping" channels this does not mean the 2 devices are free from interference from each other around the house. The 802.11 transmit mask does not demand a steep roll-off after +/- 11Mhz. Multi-path causes constructive and destructive effects to signal strength, and moving closer to one device obviously causes a further imbalance to signal strength. Therefore very real decreases in SNR can be seen with consequent reductions in MCS values and throughput. If you stay connected to the closer AP however, this is not too much of a problem in practice.

In reply to a post by vimto_girl:

InsSSider does not detect hidden SSIDs.

Says here it does http://www.howtogeek.com/howto/28653/debunking-myths...

In reply to a post by BatBoy:

In reply to a post by vimto_girl:

InsSSider does not detect hidden SSIDs.

Says here it does http://www.howtogeek.com/howto/28653/debunking-myths...

Who is he? Why should I care what he says?

If an SSID is not broadcast in the beacon from an AP, then inSSider will NOT be able to retrieve it. The information is simply not transmitted from the AP - you can consult the IEEE 802.11 standard if you don't believe me. When this is the case, some STA drivers will not even report the AP to the operating system if it is not associated with it, so there will be no network at all in inSSider. Most actually do report it, but in inSSIDer the SSID name will either be blank or say unknown. Try it yourself, version 1, version 2, it doesn't matter.

And the important point, if transmit beacons are disabled altogether from a closed-network enterprise AP, then inSSIDer will not show the network whatsoever, regardless of the STA or driver or OS used.

Edited by deleted (Wed 04-Jan-12 20:14:14)

In reply to a post by vimto_girl:

In reply to a post by BatBoy:

In reply to a post by vimto_girl:

InsSSider does not detect hidden SSIDs.

Says here it does http://www.howtogeek.com/howto/28653/debunking-myths...

Who is he? Why should I care what he says?

Because it contradicts what you're saying. Why not post a link to a 3rd party page corroborating your story?