WBS210 usable as a normal AP with 2 omni antennas?
Hey guys,
got yesterday a new WBS210.
Connected 2 5dbi TP Link omni antennas to it.
All settings are very untouched, only set the channel width to 20mhz.
2 Laptops are connected -> Windows shows 144MBit/s, distances are about 5 meters.
Copying a file (CIFS) with around 9MBytes/s. But its slower than my old WR841ND V10 with latest Openwrt (both antennas are oriented vertical).
During this operation has the 2nd laptop extreme ping drops and the times are rising to 2000 - 3000ms.
Network operations are impossible :(
So the question is, are this devices not designed for such scenarios, means acting as a normal 'Home AP'?
Thank you and best regards
Eduard
Additional information: I havn't tried to change the antenna orientation, means both are just vertical.
Is this maybe the problem, so one antenna should be vertical and the other horizontal?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@McLovin Whereas I can't see any reason why this shouldn't work as a home AP, I personally would advise against this from people uninitiated to FWA in general. There's many reasons for this but primarily my advise has to do with the Tx power you're introducing in-house which must be kept at low levels at all times to safeguard against health & safety concerns.
As for the issues you're having you should probably try lowering the transmit power from within the UI to start with and add the antenna gain parameters that reflect the product you've installed.
- Copy Link
- Report Inappropriate Content
FWA - 'Frankfurter Wasser- und Abwassergesellschaft mbH'? :)
Anyway, then please advice, where my problem is.
As I already said, most of the wireless settings are stock and look similar to this (this is from the emulator page, as I dont have access to the device right now):
I know the WBS210 can provide till 27dBm, but i would like to use TX Power as less as possible, means in my case 5dBi antenna + maximum 15 dBm amplifier.
Tried also with 0dBm, but without improving the results.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Ya, thats correct, its from the emulator page.
QOS is deactivated.
Will have access to the device in one hour.
Will enable QOS and report back.
Thank you for your help mate ;)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
This are my test settings:
Tried with QOS and Short GI, but still during copy operation from a NAS to an android phone on the laptops heavy ping drops:
Reply from 192.168.1.1: bytes=32 time=34ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms TTL=64
Reply from 192.168.1.1: bytes=32 time=107ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=30ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=28ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1450ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=124ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2799ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2877ms TTL=64
Reply from 192.168.1.1: bytes=32 time=80ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1575ms TTL=64
Reply from 192.168.1.1: bytes=32 time=72ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1339ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1703ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1945ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=34ms TTL=64
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=49ms TTL=64
Reply from 192.168.1.1: bytes=32 time=75ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 615, Received = 566, Lost = 49 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2877ms, Average = 99ms
Control-C
^C
C:\Users\Administrator>
During it getting also 'Failed to get data' message:
This is my noise at the moment:
In the middle (channel 6) is my old WR841ND, so the WBS210 is choosing channel 1.
And this is my test environment (unfortunately there is not enough space to put the antennas into a vertical position) lol:
- Copy Link
- Report Inappropriate Content
Let's try disabling 'auto' in distance settings and set it manually to something along the lines of either 0, or 0.01 - you be the judge as at the moment it's automatically set to 400m and at the same time lower your Tx power to 1dBm...
with regards to antenna orientation the polarization when 2 streams are used (on 20Mhz that'd be on MCS8+) it is indeed horizontal and vertical so I'd assume you're better off setting one perpendicular to the other on that plane. Haven't really ever tried this on a WBS210 indoors so I'm guessing here..
If everything else fails try hard setting MCS to 7 (72.2mbps) so that only 1 stream is used and repeat your tests.
- Copy Link
- Report Inappropriate Content
Set the value to 0.01 -> no improvements.
1 antenna vertical, the other one horizontal -> same behavior, no improvements.
Both antennes vertical, TX rate set to MCS7 -> no improvements, sorry:
- Copy Link
- Report Inappropriate Content
@McLovin weird...perhaps if you chose a different channel then? I'm also seeing the Tx still @15dBm, did you try lowering it all the way down to 1dBm?
- Copy Link
- Report Inappropriate Content
ya, have tried with 0, 5, 10, 15 and maximum 27dBm.
Clients see just a stronger signal, but the behavior is always the same, while a filetransfer from NAS to the Android phone have other 2 laptops instanly ping timeouts.
Tried also on 1, 6 and 11 channels.
Then switched the WBS210 off and the WR841ND on.
No ping timeouts, fast filetransfers, no problems at all.
At the end of the house, its about 7m from AP away and one level higher than the AP, with WBS210 (15dBm) I see on the Android phone 81dBm and with WR841ND 71dBm.
Also in this scenario is the filetransfer faster with WR841ND.
They both have the same 5 dBi omni TP-Link antennas.
Really strange.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 7249
Replies: 24
Voters 0
No one has voted for it yet.