Page 1 of 1

v5.18 released

Posted: Fri Jun 22, 2012 11:00 am
by normis
What's new in 5.18 (2012-Jun-21 17:20):

*) fixed upgrade problem when it failed with error "disk is too small" while
there was plenty of space left;
*) fix health and poe access reliability on OmniTIK UPA and RB750UP boards;
*) sstp - improve initial handshake to better handle many new connections;
*) wireless - do not use bridge and WDS mode on AP-AP links, causes loops;
*) dhcp ipv6 pd client - fixed ipv6 pool creation after reboot;
*) dhcp ipv6 pd client - added option add-default-route;
*) sstp - fixed connection idle time reporting;
*) fix bad block count not to increase on Samsung K9F1208U0C nand;
*) snmp - fix dhcp lease table, snmp reported an incorrect information
when a static lease had configured different address than current active address,
this should also solve problem with dude polling same leases over and over again;
*) fix RB1100 crash on interface disable/l2mtu change/reboot;
*) dns could not resolve some domain names, was ignoring replies with DNAME RRs;
*) fix firewall log action - sometimes was not logging mac addr;

Download: http://www.mikrotik.com/download

Re: v5.18 released

Posted: Fri Jun 22, 2012 11:45 am
by nickshore
Seems to be a bug in IPv6 dhcp PD client.

It was ok immediately after reboot, but shortly after I see:
/ipv6 dhcp-client print detail 
Flags: D - dynamic, X - disabled, I - invalid 
 0    interface=aaisp pool-name="aapool" pool-prefix-length=64 status=bound prefix=2001:XXX:YYY:1::/64 expires-after=4885w2d21h50m9s 
      duid="00030001000c42e18a17" add-default-route=no 
The pool has disappeared.

This means my IPv6 address which is assigned from the pool goes invalid.

If I renew the dhcpv6 then the expiry is more usual:
/ipv6 dhcp-client print detail 
Flags: D - dynamic, X - disabled, I - invalid 
 0    interface=aaisp pool-name="aapool" pool-prefix-length=64 status=bound prefix=2001:XXX:YYY:1::/64 expires-after=59m13s 
      duid="00030001000c42e18a17" add-default-route=no 
But still no pool.

If I release the dhcpv6 then the pool appears.

I also notice that winbox is showing a different expires time compared wiith the command line on /ipv6 dhcp-client print detail

Nick.

Re: v5.18 released

Posted: Fri Jun 22, 2012 12:21 pm
by mrz
You are right about winbox not showing correct Expire time. We will fix it in the next version.

I cannot repeat other problem. Can you post /ipv6 pool print poutput?

Re: v5.18 released

Posted: Fri Jun 22, 2012 12:27 pm
by nickshore
When it wasn't working there was no pool at all
/ipv6 pool print detail 
Flags: D - dynamic 
Currently (after I Released) it shows
/ipv6 pool print detail 
Flags: D - dynamic 
 0 D name="aapool" prefix=2001:XXX:YYY:1::/64 prefix-length=64 expire-time=48m16s
I'll reboot it again and see what happens

Nick.

Re: v5.18 released

Posted: Fri Jun 22, 2012 12:34 pm
by nickshore
It takes about 20 seconds after boot to go from having a pool to the pool disappearing:
[nicks@rb751.shore.me.uk] > /ipv6 pool print detail 
Flags: D - dynamic 
 0 D name="aapool" prefix=2001:XXX:YYY:1::/64 prefix-length=64 expire-time=59m51s 
[nicks@rb751.shore.me.uk] > 
[nicks@rb751.shore.me.uk] > /ipv6 pool print detail       
Flags: D - dynamic 
 0 D name="aapool" prefix=2001:XXX:YYY:1::/64 prefix-length=64 expire-time=0s 
[nicks@rb751.shore.me.uk] > /ipv6 pool print detail 
Flags: D - dynamic 
 0 D name="aapool" prefix=2001:XXX:YYY:1::/64 prefix-length=64 expire-time=0s 
[nicks@rb751.shore.me.uk] > /ipv6 pool print detail 
Flags: D - dynamic 
 0 D name="aapool" prefix=2001:XXX:YYY:1::/64 prefix-length=64 expire-time=0s 
[nicks@rb751.shore.me.uk] > /ipv6 pool print detail 
Flags: D - dynamic 
I wonder if it happens as the sntp client starts ?

Nick.

Re: v5.18 released

Posted: Fri Jun 22, 2012 1:46 pm
by WirelessRudy
What's new in 5.18 (2012-Jun-21 17:20):


*) wireless - do not use bridge and WDS mode on AP-AP links, causes loops;
I'm a bit confused here...; is this a problem in previous version that now is solved? Or is the bridge and WDS funcion on AP-AP links causing loops and in 5.18 is therefore not recommend to use?

I suppose it is a problem solved. But than again, never knew it had an issue. I use it in same situations in versions up to 5.16 and have seen no problems so far.....

Re: v5.18 released

Posted: Fri Jun 22, 2012 1:48 pm
by WirelessRudy
And what about the wireless disconnection problems in some units that evolved in 5.17?
I have made some support tickets for these with many examples but still not seeing any solution?

Re: v5.18 released

Posted: Fri Jun 22, 2012 2:00 pm
by karlos
*) wireless - do not use bridge and WDS mode on AP-AP links, causes loops;

I'm a bit confused here...; is this a problem in previous version that now is solved? Or is the bridge and WDS funcion on AP-AP links causing loops and in 5.18 is therefore not recommend to use?

I suppose it is a problem solved. But than again, never knew it had an issue. I use it in same situations in versions up to 5.16 and have seen no problems so far.....
We had this problems on our network. Previous owner of a part of our network was using using it. After upgrading from some 5.0rcXX to 5.7 we foung huge packet rates (like 15000p/s) on some interfaces going from no IP to no IP. Everything was solved just moving from AP-AP WDS mode to AP-client mode. It was impossible for use to fing what is the problem, (switch, RB, rOS or something else) but after changing the topology it was solved, so nevermind what it was.

Re: v5.18 released

Posted: Fri Jun 22, 2012 2:03 pm
by honzam
And what about the wireless disconnection problems in some units that evolved in 5.17?
I have made some support tickets for these with many examples but still not seeing any solution?
I do the same. Still disconnect in 5.18

Re: v5.18 released

Posted: Fri Jun 22, 2012 2:21 pm
by uldis
What's new in 5.18 (2012-Jun-21 17:20):


*) wireless - do not use bridge and WDS mode on AP-AP links, causes loops;
I'm a bit confused here...; is this a problem in previous version that now is solved? Or is the bridge and WDS funcion on AP-AP links causing loops and in 5.18 is therefore not recommend to use?

I suppose it is a problem solved. But than again, never knew it had an issue. I use it in same situations in versions up to 5.16 and have seen no problems so far.....
That changelog line means that there were a problem between WDS-WDS link that instead using just wds mode it also used the bridge mode which then created a loop. This problem if fixed now and WDS to WDS links will work fine.

Re: v5.18 released

Posted: Fri Jun 22, 2012 3:30 pm
by angboontiong
What's new in 5.18 (2012-Jun-21 17:20):


*) wireless - do not use bridge and WDS mode on AP-AP links, causes loops;
I'm a bit confused here...; is this a problem in previous version that now is solved? Or is the bridge and WDS funcion on AP-AP links causing loops and in 5.18 is therefore not recommend to use?

I suppose it is a problem solved. But than again, never knew it had an issue. I use it in same situations in versions up to 5.16 and have seen no problems so far.....
what does it mean "AP-AP links causing loops"???

Re: v5.18 released

Posted: Fri Jun 22, 2012 3:38 pm
by aldreytg
*) dhcp ipv6 pd client - added option add-default-route;


I can't find this option....

Re: v5.18 released

Posted: Fri Jun 22, 2012 3:46 pm
by mrz
It is not in winbox yet.

Set it from terminal
/ipv6 dhcp-client set x add-default-route=yes

Re: v5.18 released

Posted: Fri Jun 22, 2012 4:43 pm
by engineertote
What's new in 5.18 (2012-Jun-21 17:20):


*) wireless - do not use bridge and WDS mode on AP-AP links, causes loops;
I'm a bit confused here...; is this a problem in previous version that now is solved? Or is the bridge and WDS funcion on AP-AP links causing loops and in 5.18 is therefore not recommend to use?

I suppose it is a problem solved. But than again, never knew it had an issue. I use it in same situations in versions up to 5.16 and have seen no problems so far.....
That changelog line means that there were a problem between WDS-WDS link that instead using just wds mode it also used the bridge mode which then created a loop. This problem if fixed now and WDS to WDS links will work fine.
can you pls post sample of config, i think it will make sense as its bit confused

Re: v5.18 released

Posted: Fri Jun 22, 2012 5:35 pm
by ditonet
WebFig: URL direct links to disabled sub-menu pages still works :(
[Ticket#2012061366000346]

Regards,

Re: v5.18 released

Posted: Fri Jun 22, 2012 5:48 pm
by jhheider
RB751U-2Hn is still spinning out with 100% flash on wifi => bridge => masq => internet traffic. Rendering DNS and telnet/ssh unusable. Sigh. These models have taken so long and still not working.

Re: v5.18 released

Posted: Fri Jun 22, 2012 6:04 pm
by nickshore
RB751U-2Hn is still spinning out with 100% flash on wifi => bridge => masq => internet traffic. Rendering DNS and telnet/ssh unusable. Sigh. These models have taken so long and still not working.

This doesn't happen for me, Have you tried going back to an empty config and starting again ?

Nick.

Re: v5.18 released

Posted: Fri Jun 22, 2012 8:10 pm
by MrYan
What's new in 5.18 (2012-Jun-21 17:20):
*) dhcp ipv6 pd client - fixed ipv6 pool creation after reboot;
Was the change meant to fix this?

Flags: X - disabled
# NAME VERSION SCHEDULED
0 system 5.18


17:50:57 dhcp,error creating ippool6 failed: prefix of two pools cannot overlap! (6)



Matt.

Re: v5.18 released

Posted: Sat Jun 23, 2012 1:02 am
by jhheider
RB751U-2Hn is still spinning out with 100% flash on wifi => bridge => masq => internet traffic. Rendering DNS and telnet/ssh unusable. Sigh. These models have taken so long and still not working.

This doesn't happen for me, Have you tried going back to an empty config and starting again ?

Nick.
Yup. Done from a netinstall. Done reset-default on the wireless configuration. *Was* getting the watchdog reboots before 5.17, and going back and forth on a ticket for that since December, but that, at least, has dropped in frequency to a manageable level. But heavy traffic, particularly upstream, causes the router to just spin out of control. /tool profile stops updating, on an already opened telnet session. Reproducible within about 15 seconds.

Re: v5.18 released

Posted: Sat Jun 23, 2012 2:10 am
by chojrak11
When adding DHCPv6 Binding, no matter GUI or command line, it is being marked as dynamic and disappears after router reboot.
[admin@router] /ipv6 dhcp-server binding> add duid=00010001157dbdeadbeefc0de777 iaid=24xxxxx92 address=2001:xxxx:xxxx:xxxx::10 life-time=1:00:00 server=all disabled=no
[admin@router] /ipv6 dhcp-server binding> print
Flags: X - disabled, D - dynamic 
 #   ADDRESS                                                DUID                 IAID SERVER           STATUS 
 0 D 2001:xxxx:xxxx:xxxx::10/128                            00010001157...  24xxxxx92 dhcp_ipv6        waiting
Notice the "D". I can make it static with "make-static", but this needs fixing I think. There are some more problems, like when I do
set [ find ] server=my_server_name
it doesn't show in GUI.

I cannot make my Windows 7 machine to get this specific binding address... After turning on debug logging, no matter how I set ND or DHCPv6, it displays:
Handling only prefix delegation, discarding..

Re: v5.18 released

Posted: Sun Jun 24, 2012 12:12 am
by docmarius
For me, the ipv6 PD pool being unavailable after reboot has been solved.

Thank you.

Re: v5.18 released

Posted: Mon Jun 25, 2012 2:05 am
by Ivoshiee
Does the superchannel work for anyone on v5.18?

It seems not to work between SXT 5HnD and RB411AR running R52nM. I'll get no radiolink if I put in any arbitrary frequency, but I get radiolink as soon as I put in any default link frequency value. Either AP side is not sending anything out or client side is unable to transmit/receive in arbitrary frequencies (by it's status it is not scanning every available frequency).

Note: Both sides are running v5.18, country code is set "no_country_set" and both ends are set to the same frequency.

What I am doing wrong?

Re: v5.18 released

Posted: Mon Jun 25, 2012 2:09 am
by napismizpravu
traffic 2-3Mb/s 3-4 hours >> RB433UAH (power 24V 2A) >>problem not responding routerboard (stop traffic, no winbox,no telnet,..) >> power off-on = OK functional again

Re: v5.18 released

Posted: Mon Jun 25, 2012 12:13 pm
by angboontiong
traffic 2-3Mb/s 3-4 hours >> RB433UAH (power 24V 2A) >>problem not responding routerboard (stop traffic, no winbox,no telnet,..) >> power off-on = OK functional again

will it be due to the ethernet halt?
or you talking about via wireless?

Re: v5.18 released

Posted: Mon Jun 25, 2012 12:21 pm
by dinoex
I still see the same on RB435G with R52HN, running for 1 to 3 days,
then no traffic, no Winbox, no ssh, no ping, no arp telnet.

Board is still visible in Neighbor Discovery on Ethernet,
power off-on = OK functional again.

Re: v5.18 released

Posted: Mon Jun 25, 2012 1:16 pm
by mrz
When adding DHCPv6 Binding, no matter GUI or command line, it is being marked as dynamic and disappears after router reboot.
Thank you for the report, problem will be fixed.

Re: v5.18 released

Posted: Mon Jun 25, 2012 2:42 pm
by spacemind
Hey,


I got my OpenVpn connections freezing after a while with 5.17 and now with 5.18.

If restart of ovpn client it will work for a few more hours.

I have rb751-2hnd as openvpn client, linux server. with other mk versions i have a stable openvpn connection.



thanks

Re: v5.18 released

Posted: Mon Jun 25, 2012 3:34 pm
by napismizpravu
traffic 2-3Mb/s 3-4 hours >> RB433UAH (power 24V 2A) >>problem not responding routerboard (stop traffic, no winbox,no telnet,..) >> power off-on = OK functional again

will it be due to the ethernet halt?
or you talking about via wireless?
The dead RouteOS (etherX,Wi-Fi + no graf statistic memory,CPU...all)

Re: v5.18 released

Posted: Mon Jun 25, 2012 6:26 pm
by k3dt
---

Re: v5.18 released

Posted: Mon Jun 25, 2012 9:15 pm
by jhheider
RB751U-2Hn is still spinning out with 100% flash on wifi => bridge => masq => internet traffic. Rendering DNS and telnet/ssh unusable. Sigh. These models have taken so long and still not working.

This doesn't happen for me, Have you tried going back to an empty config and starting again ?

Nick.
Yup. Done from a netinstall. Done reset-default on the wireless configuration. *Was* getting the watchdog reboots before 5.17, and going back and forth on a ticket for that since December, but that, at least, has dropped in frequency to a manageable level. But heavy traffic, particularly upstream, causes the router to just spin out of control. /tool profile stops updating, on an already opened telnet session. Reproducible within about 15 seconds.
Responding to myself, it's worth noting that an RB951-2n with identical configuration, running 5.18, never gets above 2% flash utilization under the same circumstances, and remains completely responsive throughout, even when snmpwalking the entire tree multiple times.

The only issue, so far, with the *951* is this:


[jacob@RB951-2n] > /sys rout pr
routerboard: yes
model: 951-2n
serial-number: ****
current-firmware: 2.39
upgrade-firmware: 2.40
[jacob@RB951-2n] > /sys rout up
Do you really want to upgrade firmware? [y/n]
y
firmware upgrade failed

But, I'll live with that to have a functioning AP.

Re: v5.18 released

Posted: Mon Jun 25, 2012 10:21 pm
by elikxir
ppoe connection ok , no internet after upgrade.
reboot,disable-enable connection => no internet .
ipv6 - lost pool

unplugged , plugged in => everything seems ok .
ipv6 - i didnt try again (i'm afraid , maybe bites) :)

so, resolving any prob = unplug-plug in .

Re: v5.18 released

Posted: Tue Jun 26, 2012 1:46 am
by Ivoshiee
It seems the new v5.18 did bring a new firmware as well. What is changed in it?

Re: v5.18 released

Posted: Tue Jun 26, 2012 3:26 am
by WirelessRudy
It seems the new v5.18 did bring a new firmware as well. What is changed in it?
How's that? mipsbe runs 2.39 as did 5.17 mipsbe...

Re: v5.18 released

Posted: Tue Jun 26, 2012 5:12 am
by dison4linux
RouterBOOT 2.39 is new to me too... No information in the official Change Log.
http://wiki.mikrotik.com/wiki/RouterBOOT_changelog

v5.18 released

Posted: Tue Jun 26, 2012 6:13 am
by jhheider
The only issue, so far, with the *951* is this:


[jacob@RB951-2n] > /sys rout pr
routerboard: yes
model: 951-2n
serial-number: ****
current-firmware: 2.39
upgrade-firmware: 2.40
[jacob@RB951-2n] > /sys rout up
Do you really want to upgrade firmware? [y/n]
y
firmware upgrade failed

But, I'll live with that to have a functioning AP.
Spoke too soon, I guess. Look like the wireless just disappears every few hours on the 951. Doesn't even show up on a scanner, much less as a joinable network. /int wire en 0 fixes it, even though the interface is enabled. Doing more testing, will open a ticket tomorrow.

Re: v5.18 released

Posted: Tue Jun 26, 2012 11:39 am
by chadd
I upgraded an RB1100 AH X2 to 5.18 tonight and it kept rebooting due to kernel failure. Sent a few support files in and downgraded back to 5.14.

Chadd

Re: v5.18 released

Posted: Tue Jun 26, 2012 12:18 pm
by wehrhard
I upgraded an RB1100 AH X2 to 5.18 tonight and it kept rebooting due to kernel failure. Sent a few support files in and downgraded back to 5.14.

Chadd
I have the same error and already a ticket at MT. But I get a crash when I switch in Bridge from RSTP to None. And I do not get a suppout. Do you have "no crash problems" in ROS 5.14?

If yes, I would downgrade as well. I want to go on holidays and do not need a crash router in my network.

Re: v5.18 released

Posted: Tue Jun 26, 2012 12:54 pm
by uldis
The only issue, so far, with the *951* is this:


[jacob@RB951-2n] > /sys rout pr
routerboard: yes
model: 951-2n
serial-number: ****
current-firmware: 2.39
upgrade-firmware: 2.40
[jacob@RB951-2n] > /sys rout up
Do you really want to upgrade firmware? [y/n]
y
firmware upgrade failed

But, I'll live with that to have a functioning AP.
Spoke too soon, I guess. Look like the wireless just disappears every few hours on the 951. Doesn't even show up on a scanner, much less as a joinable network. /int wire en 0 fixes it, even though the interface is enabled. Doing more testing, will open a ticket tomorrow.
About the firmware upgrade failure - this will be fixed in v5.19.

About the wireless problem - the AP didn't show up on the Scan (no SSID seen)? What RouterOS version you are using? Were you doing a high speed download through the wireless interface? Could you make a support output file next time when this happens (before doing enable on wireless interface)?
We will make a test to see if we could reproduce this problem.

Re: v5.18 released

Posted: Tue Jun 26, 2012 1:00 pm
by normis
I upgraded an RB1100 AH X2 to 5.18 tonight and it kept rebooting due to kernel failure. Sent a few support files in and downgraded back to 5.14.

Chadd
I have the same error and already a ticket at MT. But I get a crash when I switch in Bridge from RSTP to None. And I do not get a suppout. Do you have "no crash problems" in ROS 5.14?

If yes, I would downgrade as well. I want to go on holidays and do not need a crash router in my network.
Chadd, thanks for the files.

wehrhard, please also send us your supout.rif file so we can see what caused the crash

Re: v5.18 released

Posted: Tue Jun 26, 2012 1:10 pm
by wehrhard
I upgraded an RB1100 AH X2 to 5.18 tonight and it kept rebooting due to kernel failure. Sent a few support files in and downgraded back to 5.14.

Chadd
I have the same error and already a ticket at MT. But I get a crash when I switch in Bridge from RSTP to None. And I do not get a suppout. Do you have "no crash problems" in ROS 5.14?

If yes, I would downgrade as well. I want to go on holidays and do not need a crash router in my network.
Chadd, thanks for the files.

wehrhard, please also send us your supout.rif file so we can see what caused the crash
Hello, I already wrote you. After the crash I must power cycle manuell the router and there is no suppout in the file section. The ticketnumber is Ticket#2012061266000651. I received from you the ROS 5.18 rc1. There was the error solved if I switch "Bridge use Firewall on/off". With 5.17 the kernel error reboots automaticly and produces a suppout which you have already. FYI, It is a RB1100 AH only but I want to use the RB1100AHx2. Can I use the RB1100AHx2 with 4.17 as well? Is the ROS 5.14 stable concerning the RSTP and Bridge switching?

Re: v5.18 released

Posted: Tue Jun 26, 2012 1:13 pm
by normis
You only tested the pre-release RC version. This topic is about release version. It has some changes. It would be great if you also could try the released version.

Re: v5.18 released

Posted: Tue Jun 26, 2012 6:31 pm
by chadd
Well unfortunately the RB1100 AH X2 is now crashing with 5.14 also. This router was running 5.14 for a very long time with no crashes so I am not sure if 5.18 caused some sort of config change that is causing the issues or what. If I don't figure something out soon I am going to have to pull the router from the network.
I upgraded an RB1100 AH X2 to 5.18 tonight and it kept rebooting due to kernel failure. Sent a few support files in and downgraded back to 5.14.

Chadd
I have the same error and already a ticket at MT. But I get a crash when I switch in Bridge from RSTP to None. And I do not get a suppout. Do you have "no crash problems" in ROS 5.14?

If yes, I would downgrade as well. I want to go on holidays and do not need a crash router in my network.

Re: v5.18 released

Posted: Tue Jun 26, 2012 9:10 pm
by chadd
I downgraded all the way to 5.11 and put the older firmware 2.38 on it and haven't had any reboots for over 2 hrs now.
Well unfortunately the RB1100 AH X2 is now crashing with 5.14 also. This router was running 5.14 for a very long time with no crashes so I am not sure if 5.18 caused some sort of config change that is causing the issues or what. If I don't figure something out soon I am going to have to pull the router from the network.
I upgraded an RB1100 AH X2 to 5.18 tonight and it kept rebooting due to kernel failure. Sent a few support files in and downgraded back to 5.14.

Chadd
I have the same error and already a ticket at MT. But I get a crash when I switch in Bridge from RSTP to None. And I do not get a suppout. Do you have "no crash problems" in ROS 5.14?

If yes, I would downgrade as well. I want to go on holidays and do not need a crash router in my network.

Re: v5.18 released

Posted: Wed Jun 27, 2012 4:12 am
by chadd
Ok just had another kernel failure with 4.11 2.38 FW.. Not sure what the deal is but this router ran for months before installing 5.18 with no crashes.
I downgraded all the way to 5.11 and put the older firmware 2.38 on it and haven't had any reboots for over 2 hrs now.
Well unfortunately the RB1100 AH X2 is now crashing with 5.14 also. This router was running 5.14 for a very long time with no crashes so I am not sure if 5.18 caused some sort of config change that is causing the issues or what. If I don't figure something out soon I am going to have to pull the router from the network.



I have the same error and already a ticket at MT. But I get a crash when I switch in Bridge from RSTP to None. And I do not get a suppout. Do you have "no crash problems" in ROS 5.14?

If yes, I would downgrade as well. I want to go on holidays and do not need a crash router in my network.
[/quote]

Re: v5.18 released

Posted: Wed Jun 27, 2012 6:07 am
by Hotz1
can you pls post sample of config, i think it will make sense as its bit confused
See this thread for details.

Re: v5.18 released

Posted: Wed Jun 27, 2012 6:50 am
by Hotz1
Now that 5.18 is available and addresses the AP-AP WDS issue, I have a bunch of Routerboards to downgrade from 6.0rc2. Unfortunately, when I copy in the npk and use "/ system package downgrade" (or the Winbox equivalent), certain routerboards appear to hang, and upon cycling power, still have 6.0rc2 loaded. Thereafter, simply rebooting (as opposed to explicitly downgrading) also causes the device to stop responding until power is cycled.

Our RB711s, 435s, 532s and SXTs have downgraded with no problem. The problem seems to be limited to OmniTiks and RB750UPs. Of course neither of these models has a serial port, so I can't confirm that it is failing while (or prior to) validating the 5.18 npk, or report whatever error message might have been displayed.

I have no reason to think netinstall won't work; However, an on-site visit to each device just isn't the most convenient way to change versions. If there is in fact a bug in the downgrade process, I hope MT will be able to solve it.

v5.18 released

Posted: Wed Jun 27, 2012 6:50 am
by jhheider
Spoke too soon, I guess. Look like the wireless just disappears every few hours on the 951. Doesn't even show up on a scanner, much less as a joinable network. /int wire en 0 fixes it, even though the interface is enabled. Doing more testing, will open a ticket tomorrow.
About the firmware upgrade failure - this will be fixed in v5.19.

About the wireless problem - the AP didn't show up on the Scan (no SSID seen)? What RouterOS version you are using? Were you doing a high speed download through the wireless interface? Could you make a support output file next time when this happens (before doing enable on wireless interface)?
We will make a test to see if we could reproduce this problem.
Ticket#2012062766000132. Let me know how else I can help. I'd love for rb951 to work better than the 751s.

Re: v5.18 released

Posted: Wed Jun 27, 2012 7:15 am
by docmarius
Hi,

With the new 5.18 i experience some faulty behavior for L2TP tunnels.

After working for a few days, the tunnel just refuses to connect and cycles like dialing/disconnected.
Disabling/enabling the interface does not change that behavior.
Everything returns to normal after router reboot.

HW is a RB450G.

Tnx,
Marius

Re: v5.18 released

Posted: Wed Jun 27, 2012 10:03 am
by omidkosari
[Ticket#2012033166000201] remote-ipv6-prefix-pool problem with pppoe
Long time bug ?

Re: v5.18 released

Posted: Thu Jun 28, 2012 11:49 am
by napismizpravu
just happened:
PC start > ethernet (NAT DHCP)> RB433UAH (24V 2A) >>> routerboard rebooted watchdog off, log: kernel failure

Re: v5.18 released

Posted: Fri Jun 29, 2012 12:03 am
by chadd
Normis,

Any word on this ticket #201206266600026 ? I have sent in numerous support output files now and haven't heard a word back. The router is still crashing with kernel failures. I need some help here or I am going to have to pull this router and find something else to replace it.
I upgraded an RB1100 AH X2 to 5.18 tonight and it kept rebooting due to kernel failure. Sent a few support files in and downgraded back to 5.14.

Chadd
I have the same error and already a ticket at MT. But I get a crash when I switch in Bridge from RSTP to None. And I do not get a suppout. Do you have "no crash problems" in ROS 5.14?

If yes, I would downgrade as well. I want to go on holidays and do not need a crash router in my network.
Chadd, thanks for the files.

wehrhard, please also send us your supout.rif file so we can see what caused the crash

Re: v5.18 released

Posted: Fri Jun 29, 2012 2:53 am
by mindragon
Minor detail -- the NetInstall on the download page links to the 5.17 not the 5.18 net install.

Re: v5.18 released

Posted: Fri Jun 29, 2012 5:00 am
by jandafields

Spoke too soon, I guess. Look like the wireless just disappears every few hours on the 951. Doesn't even show up on a scanner, much less as a joinable network. /int wire en 0 fixes it, even though the interface is enabled. Doing more testing, will open a ticket tomorrow.

SAME EXACT PROBLEM! I can't use the RB-951 because it keeps disappearing! PLEASE PLEASE fix this!!!

Re: v5.18 released

Posted: Fri Jun 29, 2012 3:42 pm
by Lakis
Now that 5.18 is available and addresses the AP-AP WDS issue, I have a bunch of Routerboards to downgrade from 6.0rc2. Unfortunately, when I copy in the npk and use "/ system package downgrade" (or the Winbox equivalent), certain routerboards appear to hang, and upon cycling power, still have 6.0rc2 loaded. Thereafter, simply rebooting (as opposed to explicitly downgrading) also causes the device to stop responding until power is cycled.

Our RB711s, 435s, 532s and SXTs have downgraded with no problem. The problem seems to be limited to OmniTiks and RB750UPs. Of course neither of these models has a serial port, so I can't confirm that it is failing while (or prior to) validating the 5.18 npk, or report whatever error message might have been displayed.

I have no reason to think netinstall won't work; However, an on-site visit to each device just isn't the most convenient way to change versions. If there is in fact a bug in the downgrade process, I hope MT will be able to solve it.
Simple try
Downgrade to 5.17 than upgrade to 5.18
with OmniTik it works

Re: v5.18 released

Posted: Fri Jun 29, 2012 7:09 pm
by chadd
Well for others having problems with the RB1100 rebooting due to kernel faults, I received an update from Support on the issue.

Apparently there is an issue with the RB1100 and the use-ip-firewall setting that causes kernel failures. It was recommended that I disable use-ip-firewall to get rid of the kernel faults, this is kind of hard to do on this device because it is being used as a transparent traffic shaper. It was indicated that they are not going to be able to fix it until V6 is released.

Pretty inconvenient not be able to use a $500 router because of a bug like this.
Normis,

Any word on this ticket #201206266600026 ? I have sent in numerous support output files now and haven't heard a word back. The router is still crashing with kernel failures. I need some help here or I am going to have to pull this router and find something else to replace it.

Re: v5.18 released

Posted: Fri Jun 29, 2012 7:39 pm
by jandafields
Do you remember several years ago when their products and software were simply STABLE? The v2 mikrotik software was awesome! Back then, there was lots of talk of "this will kill cisco, etc". Now, it seems that there is something major wrong in every single release, that has to be fixed in the next release... which then introduces yet another problem.

I've got some very old Mikrotik v2 stuff running 24/7 that hasn't been touched in years... and still going strong... uptime in the hundreds (or thousands) of days.

Now days, with their new software and hardware, there is always something wrong. The RB2011ahx2 limited storage, the RB1100 crashing, the RB751 wireless performance, the RB951 wireless disappearing, OVPN problems, SSTP stability issues......

Re: v5.18 released

Posted: Fri Jun 29, 2012 8:10 pm
by WirelessRudy
Well for others having problems with the RB1100 rebooting due to kernel faults, I received an update from Support on the issue.

Apparently there is an issue with the RB1100 and the use-ip-firewall setting that causes kernel failures. It was recommended that I disable use-ip-firewall to get rid of the kernel faults, this is kind of hard to do on this device because it is being used as a transparent traffic shaper. It was indicated that they are not going to be able to fix it until V6 is released.

Pretty inconvenient not be able to use a $500 router because of a bug like this.
Can't agree more on that!

What struck me lately in the last upgrades is that nowadays it seems any update is immediately called "stable" where within weeks the successor upgrade is there because it was not so stable after all....

In the v3.x and v4.x families the stable versions where always some versions behind the latest upgrades.... (not that that makes a lot of sense, being "stable" and been succeeded by upgrades is sometimes a bit of a contradiction...)

I think new upgrades should only be called "stable" if they run stable on the majority of hardware-software configurations for at least some weeks without any serious issues being mentioned by an relevant group of regular forum users (these can be considered as 'alfa'(?), ''beta'(?), no better, "charlie" testers :o

I fully agree with you that an mayor router as the rb1100, which will be used by many for the network traffic management, in lots of cases in transparent mode, is now not able to run a software version that is published on the download page as "stable". Ridiculous!

5.16, 5,17 and now 5.18 are succeeded in a fast schedule which in my opinion shows not a lot of serious testing is done before release.

I can't yet pass to 5.17 or higher because I have several wireless units starting to disconnect with these version and MT, yet again, don't seem to be able to put their finger on what is happening here but instead just bring new version out without solving the problems existing in older ones... :?

Re: v5.18 released

Posted: Fri Jun 29, 2012 9:58 pm
by dzieva
Well for others having problems with the RB1100 rebooting due to kernel faults, I received an update from Support on the issue.

Apparently there is an issue with the RB1100 and the use-ip-firewall setting that causes kernel failures. It was recommended that I disable use-ip-firewall to get rid of the kernel faults, this is kind of hard to do on this device because it is being used as a transparent traffic shaper. It was indicated that they are not going to be able to fix it until V6 is released.

Pretty inconvenient not be able to use a $500 router because of a bug like this.
Can't agree more on that!

What struck me lately in the last upgrades is that nowadays it seems any update is immediately called "stable" where within weeks the successor upgrade is there because it was not so stable after all....

In the v3.x and v4.x families the stable versions where always some versions behind the latest upgrades.... (not that that makes a lot of sense, being "stable" and been succeeded by upgrades is sometimes a bit of a contradiction...)

I think new upgrades should only be called "stable" if they run stable on the majority of hardware-software configurations for at least some weeks without any serious issues being mentioned by an relevant group of regular forum users (these can be considered as 'alfa'(?), ''beta'(?), no better, "charlie" testers :o

I fully agree with you that an mayor router as the rb1100, which will be used by many for the network traffic management, in lots of cases in transparent mode, is now not able to run a software version that is published on the download page as "stable". Ridiculous!

5.16, 5,17 and now 5.18 are succeeded in a fast schedule which in my opinion shows not a lot of serious testing is done before release.

I can't yet pass to 5.17 or higher because I have several wireless units starting to disconnect with these version and MT, yet again, don't seem to be able to put their finger on what is happening here but instead just bring new version out without solving the problems existing in older ones... :?
I fully agree with you.

Re: v5.18 released

Posted: Fri Jun 29, 2012 10:16 pm
by dzieva
I do not believe that MikroTik will solve the problem of disconnection in NV2.
I'm changing my whole wireless network for 802.11 with dual ospf because I'm tired of waiting for a solution.

Dzieva.
excuse me for my english.

Re: v5.18 released

Posted: Fri Jun 29, 2012 10:36 pm
by EarthStation
After the bad experience we had with 5.15, we are still running 5.16. Over 80 devices, 2011, 800's, 433's 433AH, 411, 411Ar's, Grooves, 750's 751's etc, all very stable in both 2 and 5 Ghz bands. Now we read the forum and watch what happens to the new versions. Just thought I'd mention this might be a good fallback position.

Re: v5.18 released

Posted: Fri Jun 29, 2012 11:51 pm
by Keron
After the bad experience we had with 5.15, we are still running 5.16. Over 80 devices, 2011, 800's, 433's 433AH, 411, 411Ar's, Grooves, 750's 751's etc, all very stable in both 2 and 5 Ghz bands. Now we read the forum and watch what happens to the new versions. Just thought I'd mention this might be a good fallback position.
can u upload anywhere that 5.16 ??
i need version for rb400, npk packages (mipsbe)

thanks in advance

v5.18 released

Posted: Sat Jun 30, 2012 12:47 am
by TheWiFiGuy
Unless you need wds in which case improvements in 5.18 really make a difference.

Re: v5.18 released

Posted: Sat Jun 30, 2012 1:57 am
by WirelessRudy
well, I changed some 15% of my network to 5.17, basically talking 3 AP's with their clients, into 5.17.
On these I have some 2% that are now disconnecting, the rest is rock solid.
Disconnecting units are mainly 133C3' but now also 2 groove's and one rb411.

I am playing a bit with these in setting these back to 5.16, or upgrade to 5.18 and set some other wireless parameters.
So far can't really distill what is making the difference. Next thing I want to do is to set the AP back to 5.14 to see if that improves things...

Actually, the improvement in 5.17, the improved ping times, is noted a bit (not a lot though) in these networks. I am only wondering if that improvement is actually achieved by upgrading the AP or the CPE or do both have to be upgraded?
MT is not really giving an answer to this....

We'll see, I am used to be my own tester on MT stuff.....

tuning routerboard

Posted: Sat Jun 30, 2012 11:46 am
by napismizpravu
tuning routerboard RB433UAH ??? :shock: :lol:
:-D USB speed samba max 21,5Mb/s write 19,2Mb/s read 5.19rc1 fw.2.41 (v.5.18 fw.2.39 max 6-10Mb/s) - RB433UAH

torrent client + tracker, DLNA, support USB DVB-T tuner it will be in the version of 5.xx for RB433UAH???

Re: v5.18 released

Posted: Sun Jul 01, 2012 9:09 pm
by kilos
Minor problem - typo consumtion should be consumption
Winbox & Webfig

HW RB435G
Image

Terminal - no typos
/system health> print
fan-mode: auto
use-fan: main
active-fan: none
voltage: 22.9V
current: 92mA
temperature: 16C
power-consumption: 2.1W

Re: v5.18 released

Posted: Sun Jul 01, 2012 9:47 pm
by Lakis
I do not believe that MikroTik will solve the problem of disconnection in NV2.
I'm changing my whole wireless network for 802.11 with dual ospf because I'm tired of waiting for a solution.

Dzieva.
excuse me for my english.

Also don't forget problem of disconnection with Nstreme

Re: v5.18 released

Posted: Mon Jul 02, 2012 4:21 am
by angboontiong
Well for others having problems with the RB1100 rebooting due to kernel faults, I received an update from Support on the issue.

Apparently there is an issue with the RB1100 and the use-ip-firewall setting that causes kernel failures. It was recommended that I disable use-ip-firewall to get rid of the kernel faults, this is kind of hard to do on this device because it is being used as a transparent traffic shaper. It was indicated that they are not going to be able to fix it until V6 is released.

Pretty inconvenient not be able to use a $500 router because of a bug like this.
Can't agree more on that!

What struck me lately in the last upgrades is that nowadays it seems any update is immediately called "stable" where within weeks the successor upgrade is there because it was not so stable after all....

In the v3.x and v4.x families the stable versions where always some versions behind the latest upgrades.... (not that that makes a lot of sense, being "stable" and been succeeded by upgrades is sometimes a bit of a contradiction...)

I think new upgrades should only be called "stable" if they run stable on the majority of hardware-software configurations for at least some weeks without any serious issues being mentioned by an relevant group of regular forum users (these can be considered as 'alfa'(?), ''beta'(?), no better, "charlie" testers :o

I fully agree with you that an mayor router as the rb1100, which will be used by many for the network traffic management, in lots of cases in transparent mode, is now not able to run a software version that is published on the download page as "stable". Ridiculous!

5.16, 5,17 and now 5.18 are succeeded in a fast schedule which in my opinion shows not a lot of serious testing is done before release.

I can't yet pass to 5.17 or higher because I have several wireless units starting to disconnect with these version and MT, yet again, don't seem to be able to put their finger on what is happening here but instead just bring new version out without solving the problems existing in older ones... :?
I fully agree with you.
I believe that mikrotik not able to test it properly then only push it out due to they have no such network like what all of us having now...

they should consider hire us as they outdoor tester... ^_^

Re: v5.18 released

Posted: Mon Jul 02, 2012 11:28 am
by WirelessRudy
I'll guess this way works out cheaper for them.... let the users be the free beta testers...
But in the long term it might works out dear, they will loose clients this way that probably will never come back......

Re: v5.18 released

Posted: Tue Jul 03, 2012 10:20 pm
by tomekmak
Do you remember several years ago when their products and software were simply STABLE? The v2 mikrotik software was awesome! Back then, there was lots of talk of "this will kill cisco, etc". Now, it seems that there is something major wrong in every single release, that has to be fixed in the next release... which then introduces yet another problem.

I've got some very old Mikrotik v2 stuff running 24/7 that hasn't been touched in years... and still going strong... uptime in the hundreds (or thousands) of days.

Now days, with their new software and hardware, there is always something wrong. The RB2011ahx2 limited storage, the RB1100 crashing, the RB751 wireless performance, the RB951 wireless disappearing, OVPN problems, SSTP stability issues......
Agree 100%.

Since 4.xx i switched to antoher wireless product. And IT JUST WORKING. MT wake up....

Re: v5.18 released

Posted: Wed Jul 04, 2012 12:20 am
by karina
After the bad experience we had with 5.15, we are still running 5.16. Over 80 devices, 2011, 800's, 433's 433AH, 411, 411Ar's, Grooves, 750's 751's etc, all very stable in both 2 and 5 Ghz bands. Now we read the forum and watch what happens to the new versions. Just thought I'd mention this might be a good fallback position.
I second that. I have stayed with 5.16 many hundreds of devices no problems. Rb1200. 1000 433 411 433 sxt omnitik all stable on 5.16

Re: v5.18 released

Posted: Wed Jul 04, 2012 1:04 am
by n21roadie
Do you remember several years ago when their products and software were simply STABLE? The v2 mikrotik software was awesome! Back then, there was lots of talk of "this will kill cisco, etc". Now, it seems that there is something major wrong in every single release, that has to be fixed in the next release... which then introduces yet another problem.

I've got some very old Mikrotik v2 stuff running 24/7 that hasn't been touched in years... and still going strong... uptime in the hundreds (or thousands) of days.

Now days, with their new software and hardware, there is always something wrong. The RB2011ahx2 limited storage, the RB1100 crashing, the RB751 wireless performance, the RB951 wireless disappearing, OVPN problems, SSTP stability issues......
Agree 100%.

Since 4.xx i switched to antoher wireless product. And IT JUST WORKING. MT wake up....
Until Mikrotik produce a hi-spec AP + PTP integrated solution and tweak its proprietary wireless protocol to suit, they can fine tune and develop with specific upgrades for these rather than the present updates trying to fix issue’s on customer’s custom setup’s (Made for Mikrotik) which is very difficult to accomplish. As a WISP I would pay for hi-spec units if they were reliable, good performance, cheap is no good when there is unhappy customers.

Re: v5.18 released

Posted: Wed Jul 04, 2012 1:47 am
by Alessio Garavano
Well for others having problems with the RB1100 rebooting due to kernel faults, I received an update from Support on the issue.

Apparently there is an issue with the RB1100 and the use-ip-firewall setting that causes kernel failures. It was recommended that I disable use-ip-firewall to get rid of the kernel faults, this is kind of hard to do on this device because it is being used as a transparent traffic shaper. It was indicated that they are not going to be able to fix it until V6 is released.

Pretty inconvenient not be able to use a $500 router because of a bug like this.
Normis,

Any word on this ticket #201206266600026 ? I have sent in numerous support output files now and haven't heard a word back. The router is still crashing with kernel failures. I need some help here or I am going to have to pull this router and find something else to replace it.
Hi Chadd, i am having same problem in a RB1100AHx2 which NOT have using "use-ip-firewall" in the bridge...
Recently i send a supout.rif and waiting for an answer... the rare is after each reboot the current firmware in /system routerboard is cleaned...
Then share the ticket answer... Regards!

Re: v5.18 released

Posted: Wed Jul 04, 2012 8:53 am
by chadd
Mine also shows the current FW field blank when it crashes. I temporarily replaced the RB1100 with a 450G running 5.8 and have not had any crashes on it at all. I downgraded the RB1100 to 5.8 on suggestion from Support but haven't put it back on the network yet to test it out.

Hi Chadd, i am having same problem in a RB1100AHx2 which NOT have using "use-ip-firewall" in the bridge...
Recently i send a supout.rif and waiting for an answer... the rare is after each reboot the current firmware in /system routerboard is cleaned...
Then share the ticket answer... Regards!

Re: v5.18 released

Posted: Wed Jul 04, 2012 8:08 pm
by Lakis
I have 4 SXT-SXT p2p link all good signal like from -58 to -65 all have good line of sight low interference signal quality 90-100% all mt 5.18

in nstreme protocol I have good throughput more than 50mbit TCP but can't use due disconnection problem it so often like sometimes 2 times a minute and more
with nv2 performans are degradeting like 50% less throughput bigger ping (due to nv2)

I m writing so long about nstreme problem not fixed yet
If someone have similar problem pls share it..

Re: v5.18 released

Posted: Thu Jul 05, 2012 10:49 pm
by tatianab
I hope this verison solve the wds problem, i couldnt get WDS (AP BRIDGE on all Routerboards) to work with v5.5. the links were stables, good signal and throughput, pings were about 50ms between all the APs but when clients started connecting the links were still stables but no ping response between all the APs and clients couldnt go on internet (network goes down).
Does this happen to anyone?

Re: v5.18 released

Posted: Fri Jul 06, 2012 5:40 am
by Roy
WDS does not support 802.11n?
What's mikrotik's plan?


I test with 7ea(6 hopping) RB800 with Static Mesh
Result is 26Mbps.

When I test with AP-Station,,, up to 100Mbps.

Wish to up to 100Mbps at Static Mesh

Re: v5.18 released

Posted: Fri Jul 06, 2012 3:01 pm
by spire2z
I do not believe that MikroTik will solve the problem of disconnection in NV2.
I'm changing my whole wireless network for 802.11 with dual ospf because I'm tired of waiting for a solution.

Dzieva.
excuse me for my english.
Try to increase your cell radius if you have disconnects.

SSHD server problem?

Posted: Fri Jul 06, 2012 5:00 pm
by crs
Hi.

Recenlty I've upgraded most of my routers to 5.18. I didn't notice any problems except my script that synchronizes configuration between routers stopped working. I've made some investigation and I've noticed that RouterOS commands executed via ssh didn't return any output, but it only happens when my script runs from command line. Strange but it's a fact. I've created script with commands:
/usr/bin/ssh user@192.168.1.14 ":put [ /system identity get name ]"
/usr/bin/ssh user@192.168.1.17 ":put [ /system identity get name ]"
/usr/bin/ssh user@192.168.1.18 ":put [ /system identity get name ]"
Authentication is done via keys. Routers have RouterOS versions appropriate to their last IP octet f.e. 1.14 has version 5.14.

When I run this script from command line every router returns its identity, but when I set cront to run it, only .1.14 and 1.17 return identity. I've made a test downgrading router with 5.18 to 5.17 and it started working.

Any idea?

Re: SSHD server problem?

Posted: Fri Jul 06, 2012 5:04 pm
by chojrak11
Hi.

Recenlty I've upgraded most of my routers to 5.18. I didn't notice any problems except my script that synchronizes configuration between routers stopped working. I've made some investigation and I've noticed that RouterOS commands executed via ssh didn't return any output, but it only happens when my script runs from command line. Strange but it's a fact. I've created script with commands:
/usr/bin/ssh user@192.168.1.14 ":put [ /system identity get name ]"
/usr/bin/ssh user@192.168.1.17 ":put [ /system identity get name ]"
/usr/bin/ssh user@192.168.1.18 ":put [ /system identity get name ]"
Authentication is done via keys. Routers have RouterOS versions appropriate to their last IP octet f.e. 1.14 has version 5.14.

When I run this script from command line every router returns its identity, but when I set cront to run it, only .1.14 and 1.17 return identity. I've made a test downgrading router with 5.18 to 5.17 and it started working.

Any idea?
Yeah on FreeBSD I'm getting randomly:
protocol error: expected control record

Re: v5.18 released

Posted: Fri Jul 06, 2012 8:47 pm
by spire2z
For me nv2 is the best protocol for point to point and apart from having to make the cell radius bigger in some links to eliminate the disconnect problem I have found it really stable even in noisy environments specially when under heavy load.

I think the overall speed is not quite as fast as nstream because the tdma divides the up and down more equally but in terms of stability when the link is under a heavy load my tests show it to be far more stable latebcy wise specially if you have voip users.

I would say the secret with n and nv2 is having a good antenna with very good isolation between the polarity's.

Re: SSHD server problem?

Posted: Mon Jul 09, 2012 10:15 am
by crs
Yeah on FreeBSD I'm getting randomly:
protocol error: expected control record
Can anybody else confirm? I've checked connection from FreeBSD and Ubuntu, and both behave the same way and this indicated that problem is on RouterOS side.

Re: v5.18 released

Posted: Mon Jul 09, 2012 7:56 pm
by Hispeed2U
Summary of what I'm experiencing:
Low signals cause link to stop passing packets across link, but give no errors or disconnects.

Upgraded the AP and my home CPE from 5.14 to 5.18.
AP: RB435G with a XR5 card.
Home: RB711G-5HnD

CPE running single chain 0 as it is hooked up to an old antenna and the AP is only single chain antenna and card as well.

I am shooting through a big oak tree in my yard to a tower about 3 miles away and the signal is kinda crappy, but the status was good enough for me. -117 noise floor -80/-78 signal 77%/88% CCQ.

Before I upgraded to 5.18 I had a rock solid connection and never had a problem. After the upgrade I notice sporadically packets would just stop going across the wireless interface. usually when I had a bunch of traffic coming across the link it would just stop dead. (It may startup back on it's own after a minute or two.)

The CPE still stays connected and I see no error in log, just can't pass traffic at all. To start traffic again quickly I can disable the wireless interface on my CPE and re-enable it and as soon as it linked traffic would start back up.

Anyway I downgraded the CPE only back to 5.14 and am currently having no problems. Just though I would mention it as a possible problem.

With good signals I have not noticed any problems with 5.18 as I have our whole 30 AP and backhaul network upgraded to 5.18 and have had no packet loss through the system over a 48 hour period.

Re: v5.18 released

Posted: Mon Jul 09, 2012 8:15 pm
by n21roadie
For me nv2 is the best protocol for point to point and apart from having to make the cell radius bigger in some links to eliminate the disconnect problem I have found it really stable even in noisy environments specially when under heavy load.

I think the overall speed is not quite as fast as nstream because the tdma divides the up and down more equally but in terms of stability when the link is under a heavy load my tests show it to be far more stable latebcy wise specially if you have voip users.

I would say the secret with n and nv2 is having a good antenna with very good isolation between the polarity's.
....make the cell radius bigger in some links to eliminate the disconnect...


When you say make the cell radius bigger, how much?

Re: v5.18 released

Posted: Mon Jul 09, 2012 9:04 pm
by spire2z
On a 30 km link over sea I had to go to 43km to solve it. For some reason the links over sea seem to need this.

Re: v5.18 released

Posted: Mon Jul 09, 2012 10:58 pm
by n21roadie
On a 30 km link over sea I had to go to 43km to solve it. For some reason the links over sea seem to need this.
I assume freznel zone clearance is OK on the link, also is "ducting" not a issue; http://forum.mikrotik.com/viewtopic.php ... de#p243074
http://forum.mikrotik.com/viewtopic.php ... de#p243074

Re: v5.18 released

Posted: Tue Jul 10, 2012 1:41 am
by spire2z
Frezenel zone is OK. And yeah I would say with nv2 setting the distance longer helps with ducting for some reason.

Re: v5.18 released

Posted: Tue Jul 10, 2012 2:22 am
by n21roadie
Frezenel zone is OK. And yeah I would say with nv2 setting the distance longer helps with ducting for some reason.
Is it only with this link over water you had to increase cell radius and does the same apply to all links, as increasing the cell radius beyond what is required for PTP link could also cause the link to pick up interference from other devices which could be inside this bigger cell radius.

Re: v5.18 released

Posted: Tue Jul 10, 2012 12:46 pm
by spire2z
Difficult to say as the links over the sea are usually the longer ones we do. Have a feeling I may have done that on other links too.

Re: v5.18 released

Posted: Tue Jul 10, 2012 4:25 pm
by r0xmachine
Another "STABLE" version... old problem like wireless disconnection remain....

I have different tower when I try to switch a rock solid and stable AP with routerOS 3.30 with 4.xx or 5.xx and 5.18,
I lose 20% of my clients with the same and known problem (wireless disconnection without any fu**ing reason).
How many stable versions i'm waiting... I'm tired...

Re: v5.18 released

Posted: Tue Jul 10, 2012 4:30 pm
by r0xmachine
Another "STABLE" version... old problem like wireless disconnection remain....

I have different tower when I try to switch a rock solid and stable AP with routerOS 3.30 with 4.xx or 5.xx and 5.18,
I lose 20% of my clients with the same and known problem (wireless disconnection without any fu**ing reason).
How many stable versions i'm waiting... I'm tired...

Re: v5.18 released

Posted: Thu Jul 12, 2012 7:38 pm
by spire2z
increasing the cell radius beyond what is required for PTP link could also cause the link to pick up interference from other devices which could be inside this bigger cell radius.
I don't think it will make any difference to interference. I suspect that it's just the timing window size for the tdma and making it longer helps with any problems. I would say if you have interference it won't make any difference. The noise will still be there regardless of the settings.

Re: v5.18 released

Posted: Wed Jul 18, 2012 6:10 am
by Alessio Garavano
Hello Janis, sorry but, after too many retries waiting an answer or news from your last reply e-mail on July 6th about the [Ticket#2012070466000031] Subject: RB110AHx2 rebooting each 2-3hs [...]

Hello Alessio,
It seems reboots are connected with hotspot. We are still examining supout.rif
file for more details.
Regards,
Janis Kirshteins


Can confirm if the 5.19 build on 16-july have some fix to the hotspot problem which you say to me can see in the supout.rif?

Thanks and regards!

Re: v5.18 released

Posted: Fri Apr 26, 2013 12:14 am
by aquiloni
I hope this verison solve the wds problem, i couldnt get WDS (AP BRIDGE on all Routerboards) to work with v5.5. the links were stables, good signal and throughput, pings were about 50ms between all the APs but when clients started connecting the links were still stables but no ping response between all the APs and clients couldnt go on internet (network goes down).
Does this happen to anyone?
Did this version solved the WDS Problem? I'm running several Grooves A2Hn in AP-AP WDS Bridge mode with version 5.9-5.11 with the same problems (WDS links perfectly active but network goes down no pings to APs)...