Guy we have big problems. The second week we are steel not able to make work our RB532 routers .Porblem that Omnidirectional antenna not working in one kilometer.I tryed to direct routers each other with directional antenna in one kilometer. The Result is terrible .Please take a moment and look at the ping times. Somebody must know what is happening.

From directional client router I tryed to ping directional main router.


tx/rx signal strength is -89 -92

antenna b mode
changed to: short mode

192.168.10.1 64 byte ping: ttl=64 time=76 ms
192.168.10.1 64 byte ping: ttl=64 time=59 ms
192.168.10.1 64 byte ping: ttl=64 time=109 ms
192.168.10.1 64 byte ping: ttl=64 time=3 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=73 ms
192.168.10.1 64 byte ping: ttl=64 time=7 ms
192.168.10.1 64 byte ping: ttl=64 time=69 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=3 ms
192.168.10.1 64 byte ping: ttl=64 time=77 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=8 ms
192.168.10.1 64 byte ping: ttl=64 time=67 ms
192.168.10.1 64 byte ping: ttl=64 time=3 ms
192.168.10.1 64 byte ping: ttl=64 time=12 ms
192.168.10.1 64 byte ping: ttl=64 time=54 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=65 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=116 ms
192.168.10.1 64 byte ping: ttl=64 time=60 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=55 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=47 ms


antenna b mode
changed to: long mode

192.168.10.1 64 byte ping: ttl=64 time=50 ms
192.168.10.1 64 byte ping: ttl=64 time=6 ms
192.168.10.1 64 byte ping: ttl=64 time=21 ms
192.168.10.1 64 byte ping: ttl=64 time=46 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=68 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=33 ms
192.168.10.1 64 byte ping: ttl=64 time=112 ms
192.168.10.1 64 byte ping: ttl=64 time=158 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=9 ms
192.168.10.1 64 byte ping: ttl=64 time=208 ms
192.168.10.1 64 byte ping: ttl=64 time=7 ms
192.168.10.1 64 byte ping: ttl=64 time=282 ms
192.168.10.1 64 byte ping: ttl=64 time=288 ms
192.168.10.1 64 byte ping: ttl=64 time=64 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=6 ms
192.168.10.1 64 byte ping: ttl=64 time=86 ms
192.168.10.1 64 byte ping: ttl=64 time=6 ms


antenna b mode
changed: both mode

192.168.10.1 64 byte ping: ttl=64 time=56 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=69 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=545 ms
192.168.10.1 64 byte ping: ttl=64 time=3 ms
192.168.10.1 64 byte ping: ttl=64 time=3 ms
192.168.10.1 64 byte ping: ttl=64 time=54 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=66 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=7 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=48 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms


both mode
default rates

192.168.10.1 64 byte ping: ttl=64 time=63 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=126 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=3 ms
192.168.10.1 64 byte ping: ttl=64 time=72 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=66 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=143 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=55 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=52 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=400 ms
192.168.10.1 64 byte ping: ttl=64 time=6 ms
192.168.10.1 64 byte ping: ttl=64 time=11 ms
192.168.10.1 64 byte ping: ttl=64 time=56 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping


Checked all support rates not more than 12 mbps


192.168.10.1 64 byte ping: ttl=64 time=233 ms
192.168.10.1 64 byte ping: ttl=64 time=97 ms
192.168.10.1 64 byte ping: ttl=64 time=234 ms
192.168.10.1 64 byte ping: ttl=64 time=54 ms
192.168.10.1 64 byte ping: ttl=64 time=67 ms
192.168.10.1 64 byte ping: ttl=64 time=222 ms
192.168.10.1 64 byte ping: ttl=64 time=75 ms
192.168.10.1 64 byte ping: ttl=64 time=63 ms
192.168.10.1 64 byte ping: ttl=64 time=157 ms
192.168.10.1 64 byte ping: ttl=64 time=181 ms
192.168.10.1 64 byte ping: ttl=64 time=64 ms
192.168.10.1 64 byte ping: ttl=64 time=98 ms
192.168.10.1 64 byte ping: ttl=64 time=189 ms
192.168.10.1 64 byte ping: ttl=64 time=200 ms
192.168.10.1 64 byte ping: ttl=64 time=55 ms
192.168.10.1 64 byte ping: ttl=64 time=84 ms
192.168.10.1 64 byte ping: ttl=64 time=99 ms
192.168.10.1 64 byte ping: ttl=64 time=263 ms
192.168.10.1 64 byte ping: ttl=64 time=68 ms
192.168.10.1 64 byte ping: ttl=64 time=225 ms
192.168.10.1 64 byte ping: ttl=64 time=195 ms
192.168.10.1 64 byte ping: ttl=64 time=81 ms
192.168.10.1 64 byte ping: ttl=64 time=66 ms
192.168.10.1 64 byte ping: ttl=64 time=66 ms
192.168.10.1 64 byte ping: ttl=64 time=201 ms
192.168.10.1 64 byte ping: ttl=64 time=178 ms
192.168.10.1 64 byte ping: ttl=64 time=57 ms
192.168.10.1 64 byte ping: ttl=64 time=247 ms


AGAIN DEFAULT RATES

192.168.10.1 64 byte ping: ttl=64 time=68 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=318 ms
192.168.10.1 64 byte ping: ttl=64 time=147 ms
192.168.10.1 64 byte ping: ttl=64 time=73 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=21 ms
192.168.10.1 64 byte ping: ttl=64 time=64 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=71 ms
192.168.10.1 64 byte ping: ttl=64 time=33 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=21 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=62 ms
192.168.10.1 64 byte ping: ttl=64 time=310 ms
192.168.10.1 64 byte ping: ttl=64 time=54 ms
192.168.10.1 64 byte ping: ttl=64 time=57 ms
192.168.10.1 64 byte ping: ttl=


RX TX SIGNAL STREWNGH -92 - 91

CHANNEL 1 ( 2412)

192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=425 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=23 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=118 ms
192.168.10.1 64 byte ping: ttl=64 time=140 ms
192.168.10.1 64 byte ping: ttl=64 time=30 ms
192.168.10.1 64 byte ping: ttl=64 time=102 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=50 ms
192.168.10.1 64 byte ping: ttl=64 time=11 ms
192.168.10.1 64 byte ping: ttl=64 time=71 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms




CHANNEL 2 ( 2417)


192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=148 ms
192.168.10.1 64 byte ping: ttl=64 time=43 ms
192.168.10.1 64 byte ping: ttl=64 time=74 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=452 ms
192.168.10.1 64 byte ping: ttl=64 time=57 ms
192.168.10.1 64 byte ping: ttl=64 time=189 ms
192.168.10.1 64 byte ping: ttl=64 time=5 ms
192.168.10.1 64 byte ping: ttl=64 time=14 ms
192.168.10.1 64 byte ping: ttl=64 time=43 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=61 ms
192.168.10.1 64 byte ping: ttl=64 time=73 ms
192.168.10.1 64 byte ping: ttl=64 time=6 ms
192.168.10.1 64 byte ping: ttl=64 time=6 ms
192.168.10.1 64 byte ping: ttl=64 time=57 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=325 ms
192.168.10.1 64 byte ping: ttl=64 time=14 ms
192.168.10.1 64 byte ping: ttl=64 time=14 ms
192.168.10.1 64 byte ping: ttl=64 time=41 MS




CHANNLE 3 ( 2422)

192.168.10.1 64 byte ping: ttl=64 time=219 ms
192.168.10.1 64 byte ping: ttl=64 time=60 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=70 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=6 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=76 ms
192.168.10.1 64 byte ping: ttl=64 time=366 ms
192.168.10.1 64 byte ping: ttl=64 time=62 ms
192.168.10.1 64 byte ping: ttl=64 time=9 ms
192.168.10.1 64 byte ping: ttl=64 time=73 ms
192.168.10.1 64 byte ping: ttl=64 time=61 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=60 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=71 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=51 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=472 ms



CHANNLE 6 (2437)



168.10.1 64 byte ping: ttl=64 time=64 ms
192.168.10.1 64 byte ping: ttl=64 time=150 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=55 ms
192.168.10.1 64 byte ping: ttl=64 time=70 ms
192.168.10.1 64 byte ping: ttl=64 time=64 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=119 ms
192.168.10.1 64 byte ping: ttl=64 time=63 ms
192.168.10.1 64 byte ping: ttl=64 time=63 ms
192.168.10.1 64 byte ping: ttl=64 time=72 ms
192.168.10.1 64 byte ping: ttl=64 time=62 ms
192.168.10.1 64 byte ping: ttl=64 time=147 ms
192.168.10.1 64 byte ping: ttl=64 time=65 ms
192.168.10.1 64 byte ping: ttl=64 time=54 ms
192.168.10.1 64 byte ping: ttl=64 time=64 ms
192.168.10.1 64 byte ping: ttl=64 time=154 ms
192.168.10.1 64 byte ping: ttl=64 time=3 ms
192.168.10.1 64 byte ping: ttl=64 time=77 ms
192.168.10.1 64 byte ping: ttl=64 time=67 ms
192.168.10.1 64 byte ping: ttl=64 time=115 ms
192.168.10.1 64 byte ping: ttl=64 time=77 ms
192.168.10.1 64 byte ping: ttl=64 time=52 ms
192.168.10.1 64 byte ping: ttl=64 time=114 ms
192.168.10.1 64 byte ping: ttl=64 time=4 ms
192.168.10.1 64 byte ping: ttl=64 time=64 ms


PLEASE HELP !!!!!!!!!!!!!!!!!!!!!!!

tx/rx signal strength is -89 -92 is very week you need beter signal to work, check cable, antena, card. You can try to change data rate use a fixed data rate. Select posible 9Mbps or 12Mbps or lower try it work beter but for 1km signal is very week.
I have link 2km with signal -72 /-72 fixed data rate to 36Mbps very low ping and transfer rate TCP 16Mbps in bandwitch test.

I already tryed to lower data rates to 12 mbps. But It is not affected.
What is rong with this routers I don't know ?

Why omnidirectional antenna not working ? Where is our mistake ?
Even with directional antenna we got very high ping times .

By the way which cable you mean ?

Cable between miniPCI card and antena.
You can try to change antena a or antena b and watch the signal.
Please write what equipment your are using cable, antena, board. Then someone on forum can help you.

I suggest, don't change settings, that you don't understand.
Use default-settings for wireless interface configuration.
-Run '/system reset',
-Enable wireless interface,
-set ssid, band frequency.
Connect antenna to the correct wireless card connector.
Than everything should work fine.

You need to tell us more about your setup if we are going to be able to help you..... just posting ping times and yelling help doesn't accomplice much.

Start by giving you hardware setup, start at one card and described every single part that is in the path until we reach the next card... including the cards themself

Also, have you done a link path budget? That is the FIRST thing to do when you are going to set up a new link.... even before ordering the gear!

Best regards

/Jörgen

hi, friend

waoooooo
my Apple slow slow connection......cos too many PINGING REPORT

nothing way to make help, [maybe your RouterOS and Wireless Confuse], better you can start from begining by reseting your routerOS and make sure after reset, IP address, SSID, Band, Frequency [AP and Client must be same SSID, Band, Freq]. Don't make change if your are not understand, leave everything config as default is better. here our wireless without LOS around 4,5km work fine.

regards,
BalimoreDOTcom
--------------------

You may be to high with the omni. It could be shooting over your customers.
But, then again if you can't get it with two directional antennas I would say that you need to try changing the channels and if thats a bust then try the 5 and 10 mhz channels. (Only if you are using Mikrotik at both ends.)
Try the first link to see if you are in line with the other antennas your trying to hit.

http://www.wisp-router.com/calculators/downtilt.php
http://www.wisp-router.com/calculators/fresnel.php
http://www.wisp-router.com/calculators/simple_som.php

There are other calculators but I have to plug Eje any chance I get. LOL

Please answer some of these questions so we can try to help you the best that we can.

Can you tell us what antennas you are using, omni and directional(dbi, brand, model# )?

What miniPCI radios are you using in the AP and CPE?

How high is the AP antenna?

How high is the CPE antenna?

Do you have full line of sight?

Is there anything blocking the line of sight?

Have you ran the Frequency Usage tester in MT to see if there are cleaner channels to use?

to sergejs:

I did it almost one hundred times.It didn't help us.



Sorry guys I can't unswer all of you.But I ll try to describe everything as I can.
And thank you for your support.


I am going to write everything again detailly.
We have four RB532 Wireless routers.Two of them is directional router other two is omnidirectional router.

All antennas are in dbi mode.

wireless card R52
FCC ID:TVR52


2.4 (18 dbi mode)

there is no any obstacle between routers.

the last test has been between directional and omnidirectional routers in 50 meters.
From the Two main routers we got the same signal level.Also from the client side we took both directional routers for test .But the
same signal level.Everything terrible .It is my first Wireless MAN project.
But I didn't expected everything will be so terrible.

The same signal level we got from directional antennas in distance 600 meters.Unfortunatelly in such distance we can't get signal
from omnidirectional antenna.


Please look at the website provided bellow for locatiot one the main routers and signal levels:

http://mecdun.s5.com


Regards

Configuration of Main router

Flags: X - disabled, R - running
0 name="wlan1" mtu=1500 mac-address=00:0C:42:05:2E:56 arp=enabled
disable-running-check=no interface-type=Atheros AR5413
radio-name="000C42052E56" mode=ap-bridge ssid="test" area=""
frequency-mode=manual-txpower country=no_country_set antenna-gain=0
frequency=2412 band=2.4ghz-b scan-list=default rate-set=default
supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps basic-rates-b=1Mbps
basic-rates-a/g=6Mbps max-station-count=2007 ack-timeout=dynamic
tx-power-mode=default noise-floor-threshold=default
periodic-calibration=default periodic-calibration-interval=60
burst-time=disabled dfs-mode=none antenna-mode=ant-b wds-mode=disabled
wds-default-bridge=none wds-default-cost=100 wds-cost-range=50-150
wds-ignore-ssid=no update-stats-interval=disabled
default-authentication=yes default-forwarding=yes default-ap-tx-limit=0
default-client-tx-limit=0 hide-ssid=no security-profile=default
disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both
compression=no allow-sharedkey=no



from client side configuration by defaul.

I guess you have R52 wireless card (You have to connect pigtail to 'outside' secondary connector of the card).

Try to use another frequency for the AP (use 'snooper' to find another possibly less overloaded channel).

Signal level is very low, check cable from antena to router and check antena. Check every connector.
Try to change antena a or antena b and check signal.
On picture signal is very very week. Your problem is signal you must have better signal and then everthing work.

to sergejs;

I tired every time to change inside motherboard pigtail place (main and aux) .I also cganged from configruration mode antenna mode to B and to A.

And also it is not so simple just to direct dicectional router to omnidirectional router and to get signal.Sometimes we can't get signal .

to npero;

What you mean when you saing ,check the cable. What must I do ? I think everyting ok.

to Jober;

Our director not allowed to use 5 or 10 ghz .In our country this frequency licenzed and most compnies using it.

Rauf,
once again don't change configuration you don't understand.
For 'antenna-mode=ant-b' use aux connector.
Are you able to get normal signal, when routers are placed near to each other ?

Our director not allowed to use 5 or 10 ghz .In our country this frequency licenzed and most compnies using it.

He didn't write to use 5 or 10 Ghz frequencies, but 5 or 10 MHz channel bandwidth!

Best regards,
Christian Meis

to cmit ; You are right !



to sergejs;

Router each other working ; - 64 - 68 signal strengh

But when I again got router a way for 50 meters signal level a gain was
-90 -96 range.

I also removed extention cabel from Antenna.I connect it without it.

I again want to note on our area there area some d-link routers for indoor. Ther area also visble outdoor. Is it possible that interference to Mikrotik routers.

Please some suggestion.

It is not possible that you don't a have suggestion.

Guys where area you all ?

King Regards

1) First check that you use correct antenna connector (if you get bad signal over 50 m, it means annena connected to the wrong connector).
for antenna-mode=ant-b aux (secondary).

2) Check previous posts above, I said try to change a channel (snooper feature will show network load over all channels on used band).

2.4ghz u need signal better than -70, and -50 is ideal
this is different from 5ghz signal strength -50 up to -80 still okay to pass through 6mbps data

As mentioned before, try a different channel.

2.4 (18 dbi mode)

Is this the omni gain? If so, as mentioned, if the elevation of the 2 links is different, this may be your problem (flat signal).

You have to wonder if the recievers in the radios are fried if you tested these links so close together with high gain antennas. Not sure if you can cook them that quick tho...?

i have the solution for you Switch to a new Radio card. You have a broken antenna switch in the R52 card.
I have now in 2 months have sent back 35 pcs of the r52 card with broken antenna switch on.

//Rickard

i have the solution for you Switch to a new Radio card. You have a broken antenna switch in the R52 card.
I have now in 2 months have sent back 35 pcs of the r52 card with broken antenna switch on.

//Rickard

Inside the router case on the back side of motherboard I found externall antenna not connected. But there is one question Haw it worked with opnidirectional antenna even in 5 meters with out this?
I connected it to aux from back side and from the front side also I connected it to aux, in any way signal was bad - 75 db in 3 meter.

Tomorrow I am going to test it again . I'll post the results.

guys I want a gain to note that it is not working . We can't get signal .
Today we again tested .Signal was 85 -89 in 10 meters .

Omidirestional router we used as an APBRIDGE .
Directional router used as a station.

to sergejs;

You are working for Mikrotik company and you must give us some suggestion .(or you can write to my e-mail address)

this project is very big and important. Can you tell me the router model which is don't hase any such kind of problems.

to rickard;

Is it possible that four RB532 router's card broken ?

RB532 have MiniPCI slot there insert wireless card router board is work and it's ok.
Please call someone with little more expertise in wireless, posible is problem miniPCI wireless card, connector, cable, replace everthing and reset router to default configuration. Then enable wireless interface and setup only mode (ap-bridge, client or somethin else).
10m you must have signal lower -50.
You need someone with practical experience in wireless.
If you closed north Serbia I can help you.

this project is very big and important. Can you tell me the router model which is don't hase any such kind of problems.

Yup - I agree... I think you need to call in the professionals!

Important projects can be ruined by wasting time figuring things out and quite likely doing something wrong.

Mikrotik is not for beginners...

guys I want a gain to note that it is not working . We can't get signal .

to rickard;

Is it possible that four RB532 router's card broken ?


:?

Yes is possible , we had a towet that blow away all 5 radio cards in sector antennas,

//Rickard

Guys experience for childrens. Are you joking ?

In my opinion problem with RB52 wireless cards.I have four routers as I told before .And I don't have a any other wireless card or pigtails or antennas to change . Only thing what I can do is to change routers wireless cards to each other and their place in mother board.Ofcourse I resetted routers conf many times. But I think problem here on the Physical Layer.

to npero;

Thank you for your help .


to GWISA;

Beginners for me is 12 ,13 years old man .


to all;

I suposed somebody knows exactly where is problem that is why I post problem here.


regards

to rickard;

I think it is only way. I should agree with you.

Guys experience for childrens. Are you joking ?

no joking. i really suggest you to hire a consultant, and attend our MUM if you can.

http://www.mikrotik.com/consultants.html
http://mum.mikrotik.com/

I suggest, don't change settings, that you don't understand.
Use default-settings for wireless interface configuration.
-Run '/system reset',
-Enable wireless interface,
-set ssid, band frequency.
Connect antenna to the correct wireless card connector.
Than everything should work fine.

---------------
Hi friend and Sergejs

is possible to that command?

1. we don't have factory-default.backup
2. reload backup file by creates first

from two days ago our wireless almost every 20s disconnect and reconnect.... we have around 4,5km normaly work fine with bad signal[-79 ] 2,4ghz, only from now is problem, than for temporary all client move to other ap [not mikrotik].

thanks all
regards
BalimoreDOTcom
----------------

I suggest, don't change settings, that you don't understand.
Use default-settings for wireless interface configuration.
-Run '/system reset',
-Enable wireless interface,
-set ssid, band frequency.
Connect antenna to the correct wireless card connector.
Than everything should work fine.

---------------
Hi friend and Sergejs

is possible to that command?

1. we don't have factory-default.backup
2. reload backup file by creates first

from two days ago our wireless almost every 20s disconnect and reconnect.... we have around 4,5km normaly work fine with bad signal[-79 ] 2,4ghz, only from now is problem, than for temporary all client move to other ap [not mikrotik].

thanks all
regards
BalimoreDOTcom
----------------

---------------------------------------
Hai, all

we had close my problem, and running like before, our ap with omni 15dbi to make connect station with plat antenna 19dbi all with RB, around 4,5km and 2,5km. just make single band is 2.4ghz-b and now very nice timeout.
regards
BalimoreDOTcom
--------------------------------------