Routerboard r52hn manual


















Need that low signal kick script. Afridi just joined. Kindly let me know because i was going to purchase Units but through the forum i found with it the unusual issues. If mikrotik fixed that issue then please let me know thanks.

These dishes are 7 years old working like new still. I have had ping -t running for almost 24 hours and not missed a packet. In fact I have watch dog turned on waiting for a missed packet and it has not restarted.

I am going on vacation on friday for a week so I need it solid or to where it can restart to fix itself while i am gone. So I may not do anymore testing for speed increase untill i return. As far as i can tell, I am very happy with unit even though lack of people helping in forums. Most of the info I have learned was trial and error. Keep i mind there is access to so many settings in routeros that it can be easy to mess it up. I would sugest not to use opera web browser for web login. I had a box brick using opera browser over the wireless.

I am still waiting on what to set to kick clients when signal goes lower then what I need because it causes unit to hang data. The ping window is of the client. Connection time is correct, I rebooted today at around 12pm, before that it was 10hrs or so no loss.

I yesterday I connected connection 2 and had both connections streaming video, I then noticed very high ping and low data, including connects and disconnects. So I did a lot of reading and found the issue. Legacy B 1,2,5,11 using mixed mode was causing a lot of problems. This is not a mikrotik, router os, driver, or chipset issue Basically N knows when N is talking and tells others to wait till ready.

G also knows when N is talking and N knows when G is talking. But when B is talking on a N and G connections are alive it cant hear both because B clients do not know when other N and G clients are talking because they can not hear them and B does not tell them N or G is busy. So if your mixing bgn then it will cause issues if all are using data. Here is the testing settings for this.

Keep unit in BGN mode. In advanced mode, Data Rates tab, rate selection: advanced rate: configured supported rates B, none checked. HT tab ht tx chains: checked ht rx chains: checked ht amsdu limit: ht amsdu threshold: ht guard: any ht ampdu priorities: ALL CHECKED Now all these settings are applied to my unit, I can connect with client with others connected and I see very little change in pings to others connected.

No more data loss during new client connection to already connected clients. Hope this helps. I will post with any new updates. This increased some speed and slightly better ping! I prefer the sector as the antennas. I would always check CCQ during installation and always try to avoid places that will create interference. I changed all advanced settings to mikrotik default values and everything went well until put under pressure of a speedtest for long period of time.

After several minutes I lost data to almost nothing and had disconnects and reconnects. I changed everything back to my settings and everything was back to normal. I would suggest for the default mikrotik settings in firmware to be changed to help new customers make connections with less issues.

Everything seems to work properly tiil now with the default configuration. Still waiting to see if any other issues will occur with more connected clients the next days. Same issues with an upgrade to 6. This was very frustrating until I discovered someone on the site using some older off brand 2GHz outdoor wireless cameras about m from the device.

With the devices turned off the connections became stable and speed increased to what was expected for the available bandwidth. I was able to diagnose the interference using the Dude software on a laptop which was plugged directly into the PoE. It seems to me that the cameras were making a non-stop signal "drowning" out my other Metals with Omni's running WDS network. I also increased the disconnect timeout to 10s from the default 5s.

I am still on 5. B only does not work or has very bad data loss. N Only does not put out faster data. This morning I had a metal radio lock up. I went to the log and it says client connected then had data loss and disconnected. Nothing I do seems to fix that problem. Although, I have noticed that the G only mode works a lot better and faster then my old branded unit.

I need to know if upgrading to version 6 firmware will help with issues? Upgraded to 6. I have noticed that the Portal to the Mesh that is the only device connected via cat-5e to the main router which is connected to the "internet".

Anyways, this device will stop "working" with the wireless like it does not show on the list SSID but still responds to winbox shows in the winbox This has always been fixed by a power cycle, which it comes right back.

I have also noticed when the wireless doesn't seem to be working showing on the SSID list on client it's actually busy using the wlan device to scan or snoop or some other tool or once I had set it to "wds slave" mode for the wireless mode and it was scanning for available WDS devices so it wasn't showing on the SSID list. This is my first time using RouterOS devices and I am a somewhat experienced wireless wi-fi installer.

I have just used off the shelf Belkin or Linksys devices up till now. I was rather worried about my first experiences with these Metal devices but now it seems maybe all my issues were caused by either interference of outside RF at the site, or bad configuration.

The watch dog will ping an ip address on the wireless and when it stops pinging it will reboot the device for you and record the log if needed. This is saving me from unplugging. I tried 4 hour in the setting and it was to long. The only down fall of the reboot is the metal stops all my other wifi devices on other channels while it reboots, and this can cause the other devices to reboot as well since it causes no ping for the watch dog.

But at least they are close to being is sync with the hour. WirelessRudy Forum Guru. With default power setting signals into 's on the other end! Set radios now to dBm to get signals in to - 60dBm range. Station-bridge on one end, bridge mode on the other. So a bridged link running over them. Both running v6. Its usually the client that needs a reboot to get it back working again. I have been playin now for over a week to get the link stable but without success Tried to swap AP-station, same results but now the other units needs the reboots Tried to use nstreme but don't seem to get any reasonable traffic over the link.

Tried with fixed conn. Tried to lower power step by step. Problem persist with result that powers lower than 21dBm units wont talk to eachother no more while the are still connected with dBm and dBm conn. Tried units by day, but also by night and in the rain. Same results so temp.

When idle the links stays running for days. But everybit more traffic than say 5Mb above, station drops and need a reboot. Sometimes also the AP wireless crashes Scan stays empty. After reading all these post here and hearing some other similar stories from a friend of mind I am thinking MT should actually stop selling these units or solve the problem.

The problem itself is imho the radio's. The are not stable and under significant load just collapse. I think these units have to go RMA OH, by the way. The link runs over a town with therefore several hundreds of wifi signals to be picked up. Some with strengths upto ! Hence I use channel I am the only one there But since the channel 40Mhz wide I am basically covering the whole 2,4Ghz band.

So yes, interference can be the issue. But if the metal is not able to handle this it is not even worth putting it on the market! For empty 2,4Ghz spectrum you have to fly to the moon! And probably still picking up signals from us Show your appreciation of this post by giving me Karma! Rudy R. It could be software, could be hardware, but email that file to support first. I even set watchdog to produce one if the ping to the other end of the link fails.. Basically it means the unit really crashes, isn't it?

If the supout. Re: Metal 2 shpn Problem in WIFI Wed Aug 28, am we need the support output file which is made before reboot - when the problem is happening. Re: Metal 2 shpn Problem in WIFI Wed Aug 28, pm we need the support output file which is made before reboot - when the problem is happening. Not because Metal 2 obviously has issues but because support mikrotik. I have very similar issues with a few Metal 2 devices I have bought that are loosing client registrations until rebooted and managed to capture the supout files before reboot while in a frozen state.

Sent them to the email address above and haven't received an answer at all for 10 full days now. Is there maybe some other support email that IS working? For me, the workaround is to schedule a nightly reboot of the device Thanks, Ivan. So I'll wait until I got something back and try again I just got 5units metals 2.

MikroUser just joined. Thermal sensor in metal is stupid. Lets see what they come back with Considering the Metal's case as the heatsink i think it could resolve the problem. There's also from the same manufacturer a 6. If I can find where to get some I'll post the results. CPU doesn't need a heatsink, since it doesn't get very hot, and since the case works as a heatsink from the other side of the PCB.

The issues you are seeing are probably related to something else. We are replacing them for Grooves as soon as they stop working. Sometimes the problem can be minimized with an scheduled reboot every few hours but is just a temporal fix.

We are not installing them by now waiting for a proper solution. If at least they failed from the begining we could RMA them before installing but the problem doesn't appear until they are on a production enviroment. I have the same problem.

I was changed my metal 2 to a new one yesterday, but the problem is the same. After about few hours the clients are disconnected until i reboot the metal. It's amazing, all metal and I will send you back to sue for damages. I did what, I found Metal as a competitive model to Bullet M2, even with better resources The problem: When we have 5 clients connected at 6 a.

No Internet. Because we are a small company and we are not able to test out product before selling it Is this your problem??? Iam not happy with you I want my money back or your product changed for a working ONE What should I do?

All three the 2. We have replaced it with boards and radios. Lansman just joined. I am an old hand radio guy. I have done radio for more than 50 years. I should be able to help you do some design modifications to help keep the internal devices cooler. Instruction manual : Connect the power adapter to turn on the device. Open Abra Avatud Avaa Mode d'emploi : Connectez l'adaptateur d'alimentation pour allumer l'appareil.

Ouvrez Aprire Handleiding : Sluit voedingsadapter aan op het apparaat in te schakelen. Deschide Odprite Otvorte User manuals. Child pages. Wireless for home and office. Browse pages. A t tachments 9 Page History. Pages User Manuals Wireless for home and office. Jira links. Connecting Please follow these quick steps to set up your device: Choose your powering solution, please see the P owering section for possibilities.

Connect your internet provider Ethernet cable to the ETH1 port. Connect your other local computers to the any of other Ethernet ports. The device will boot up, front led indicator will light in solid blue, and Wireless network will be available for connecting. Open network connections on your PC, mobile phone, or other device and search for MikroTik wireless network and connect to it.

We recommend clicking the "Check for updates" button and updating your RouterOS software to the latest version to ensure the best performance and stability. Choose your country, to apply country regulation settings, and set up your password on the screen that loads.

Powering The device accepts powering from either the power jack or from the LAN1 Ethernet port: Direct-input power jack 5. Eth1 port accepts V DC input at the board; higher voltage needed to compensate for power loss on long cables from non-standard passive Power over Ethernet injectors.

The board does not work with IEEE Maximum power consumption 11 W. We have sent a verification link to to complete your registration. Log In Sign Up. Forgot password? Enter your email address and check your inbox. Please check your email for further instructions. Enter a new password. We recommend you to set up a password to secure your device, follow these steps Connecting 1. Connect your Internet cable to port 1, and local network PCs to ports 2. Log into your router and configure a the Wireless password and router password to secure your wireless network and access to the router 4.

The username is admin and there is no password 5. Powering The board accepts powering from the power jack or from the first Ethernet port Passive PoE : direct-input power jack 5.

You can only view or download manuals with. Sign Up and get 5 for free. Upload your files to the site. You get 1 for each file you add. Get 1 for every time someone downloads your manual.



0コメント

  • 1000 / 1000