http://www.mikrotik.com/download/router ... 22.torrentsergejs
Where I can download "ROS for all Devices" as it was before ?
The link "all stable files" at the download page
Caci99,The link "all stable files" at the download page
Where did you find this link ?
Caci99,The link "all stable files" at the download page
Where did you find this link ?
at the "Useful tools and utilities" section, below the normal download packages section
*) PoE firmware version 2.1What's new in 5.22 (2012-Nov-23 09:28):
*) userman - fix PayPal "bad HTTP response";
*) kvm - fixed possible ROS guest incomplete package installation;
*) l2tp server - added keepalive-timeout setting;
*) wireless - fixed RADIUS mac-caching;
*) wireless - fixed rare nv2 link stall;
*) metarouter - fixed system occasional lockup for 12s on RB4xx and RB7xx;
*) metarouter - fixed crash when FPU exception was raised in one of powerpc metarouters;
*) quickset - added HomeAP mode;
*) fixed "export compact" in "ip proxy";
http://www.mikrotik.com/download
From this thread:*) PoE firmware version 2.1What's new in 5.22 (2012-Nov-23 09:28):
*) userman - fix PayPal "bad HTTP response";
*) kvm - fixed possible ROS guest incomplete package installation;
*) l2tp server - added keepalive-timeout setting;
*) wireless - fixed RADIUS mac-caching;
*) wireless - fixed rare nv2 link stall;
*) metarouter - fixed system occasional lockup for 12s on RB4xx and RB7xx;
*) metarouter - fixed crash when FPU exception was raised in one of powerpc metarouters;
*) quickset - added HomeAP mode;
*) fixed "export compact" in "ip proxy";
http://www.mikrotik.com/download
why not mentioned, and what was fixed? One RB750UP upgraded from 5.21 (PoE firmware 2.0) so far, not bricked yet.
My latest update from support:
new changed poe-controller firmware will be included into RouterOS 5.22. It will
address "crazy lights" when in auto-on mode, weirdness with ether5 port. However
it will not address issues with forced-on mode.
So, how serious is this? Every links goes down now and than. Should I now upgrade or not? (I just finished upgrading to 5.21...)What's new in 5.22 (2012-Nov-23 09:28):
*) wireless - fixed rare nv2 link stall;
Has anyone considered that having so many different torrent files means far less effective seeding? Someone who downloads the mipsle torrent, can only peer with someone else who downloaded the mipsle torrent--in particular, they cannot peer with somebody who downloaded the "all files" torrent. And vice-versa. For each of the platforms. Rather than all ROS torrent downloaders sharing files in one group, there are now five disjoint sub-groups. Bad Idea™!The link "all stable files" at the download page still points at ROS 5.21. Need to correct the link manually.
Very BAD, so mikrotik dont write FULL changelog*) PoE firmware version 2.1What's new in 5.22 (2012-Nov-23 09:28):
*) userman - fix PayPal "bad HTTP response";
*) kvm - fixed possible ROS guest incomplete package installation;
*) l2tp server - added keepalive-timeout setting;
*) wireless - fixed RADIUS mac-caching;
*) wireless - fixed rare nv2 link stall;
*) metarouter - fixed system occasional lockup for 12s on RB4xx and RB7xx;
*) metarouter - fixed crash when FPU exception was raised in one of powerpc metarouters;
*) quickset - added HomeAP mode;
*) fixed "export compact" in "ip proxy";
http://www.mikrotik.com/download
why not mentioned, and what was fixed? One RB750UP upgraded from 5.21 (PoE firmware 2.0) so far, not bricked yet.
What problems were you having before?My RB1200 normal again with ROS 5.22,thanks
So, how serious is this? Every links goes down now and than. Should I now upgrade or not? (I just finished upgrading to 5.21...)What's new in 5.22 (2012-Nov-23 09:28):
*) wireless - fixed rare nv2 link stall;
Did the links stall under certain conditions? Or in general.
In the first case I would like to know what these conditions/configs where.... In the second case I probably need to update again soon.... (after not too many issues are being reported here...)
Several of us would like to see more info on this anyway.... MT?Glad to see the nv2 stalling bug reported as fixed, need to ask if it depends on only bridge/AP side, or also stations need upgrade?
In either 5.21 or 5.22 my iPad1 works great. That's weird. I'm on a 433ahSame bug in v5.22 and 5.21 (on v5.19 didn't met such problem):
can't log in through web-interface (more often from Safari browser, iPhone), there is a following message: "Internal server error".
As I read changelog, similar problem has already been solved in version 5.7, but now it seems to appear again in 5.21 and 5.22
Please fix this problem.
how often does it happen?Same bug in v5.22 and 5.21 (on v5.19 didn't met such problem):
can't log in through web-interface (more often from Safari browser, iPhone), there is a following message: "Internal server error".
As I read changelog, similar problem has already been solved in version 5.7, but now it seems to appear again in 5.21 and 5.22
Please fix this problem.
correctFor everyone that says there is no options in Advanced tab it was already discussed in another topic.
The options that are shown are the only relevant for the currently selected wireless mode. For example there is no ack setting in nstreme. That is why it is not shown in Advanced. Switch to a protocol that uses the option and you will see it.
again error:napismizpravu, what do you see at /tool profiler?
It happens almost every time I try to log in throuh web-interface (Safari) on iPhone. What do you mean by asking "What happens if you manually open the IP address of the hotspot router- does it allow to login?"? In address bar of Safari I enter IP-address of my RB750G, on logon screen I enter password (user "admin" automatically filled in) and press logon - after a few seconds I see the same logon screen with message "Internal Server Error" below password field.how often does it happen?Same bug in v5.22 and 5.21 (on v5.19 didn't met such problem):
can't log in through web-interface (more often from Safari browser, iPhone), there is a following message: "Internal server error".
As I read changelog, similar problem has already been solved in version 5.7, but now it seems to appear again in 5.21 and 5.22
Please fix this problem.
What happens if you manually open the IP address of the hotspot router - does it allow to login?
Please make a support output file right after you see that error message and send it to support@mikrotik.com
Nov 30 08:47:56 33Comm LAN-DHCP deassigned 192.168.151.244 from aa:aa:aa:aa:aa:aa
Nov 30 08:47:56 33Comm LAN-DHCP assigned 192.168.151.244 to aa:aa:aa:aa:aa:aa
Nov 30 08:48:00 33Comm LAN-DHCP deassigned 192.168.151.247 from dd:dd:dd:dd:dd:dd
Nov 30 08:48:00 33Comm LAN-DHCP assigned 192.168.151.247 to dd:dd:dd:dd:dd:dd
Nov 30 08:48:00 33Comm LAN-DHCP deassigned 192.168.151.245 from bb:bb:bb:bb:bb:bb
Nov 30 08:48:00 33Comm LAN-DHCP assigned 192.168.151.245 to bb:bb:bb:bb:bb:bb
Nov 30 08:48:00 33Comm LAN-DHCP deassigned 192.168.151.246 from cc:cc:cc:cc:cc:cc
Nov 30 08:48:00 33Comm LAN-DHCP assigned 192.168.151.246 to cc:cc:cc:cc:cc:cc
...
Nov 30 12:48:56 33Comm LAN-DHCP deassigned 192.168.151.244 from aa:aa:aa:aa:aa:aa
Nov 30 12:48:56 33Comm LAN-DHCP assigned 192.168.151.244 to aa:aa:aa:aa:aa:aa
Nov 30 12:49:00 33Comm LAN-DHCP deassigned 192.168.151.246 from cc:cc:cc:cc:cc:cc
Nov 30 12:49:00 33Comm LAN-DHCP assigned 192.168.151.246 to cc:cc:cc:cc:cc:cc
Nov 30 12:49:00 33Comm LAN-DHCP deassigned 192.168.151.247 from dd:dd:dd:dd:dd:dd
Nov 30 12:49:00 33Comm LAN-DHCP assigned 192.168.151.247 to dd:dd:dd:dd:dd:dd
Nov 30 12:49:01 33Comm LAN-DHCP deassigned 192.168.151.245 from bb:bb:bb:bb:bb:bb
Nov 30 12:49:01 33Comm LAN-DHCP assigned 192.168.151.245 to bb:bb:bb:bb:bb:bb
/ip pool
add name=LAN-pool ranges=192.168.150.100-192.168.151.249
/ip dhcp-server
add add-arp=yes address-pool=LAN-pool authoritative=yes disabled=no interface=\
ether1-LAN name=LAN-DHCP
/ip dhcp-server network
add address=192.168.150.0/23 dns-server=192.168.150.1 gateway=192.168.150.1 \
netmask=23 ntp-server=10.0.1.13
/ip dhcp-server lease
add address=192.168.151.244 client-id=1:c0:3f:e:10:21:7b mac-address=aa:aa:aa:aa:aa:aa server=LAN-DHCP
add address=192.168.151.245 client-id=1:0:e:8:d9:a9:11 mac-address=bb:bb:bb:bb:bb:bb server=LAN-DHCP
add address=192.168.151.246 client-id=1:0:e:8:d7:60:34 mac-address=cc:cc:cc:cc:cc:cc server=LAN-DHCP
add address=192.168.151.247 client-id=1:0:e:8:d8:4c:fb mac-address=dd:dd:dd:dd:dd:dd server=LAN-DHCP
Do u still have this problem with 5.22 because I have this problem with previous versionThe scenario is Sextant AP ----> Sextant station bridge (protocol nv2) ... after 1 day trafic stoping. Enable disable wireless interface traffic comes. When ptotocol is nstream no problem. Downgrade to 5.18 NO problem too.
So here's how it looks from terminal:I came across memory usage reporting error using v.5.22 with web proxy enabled caching to RAM. "System -> Resources" claim to have 4GiB free memory on my RB450G, while graphs say for example "Max: 345.17MiB (137.4%); Average: 124.61MiB (49.6%); Current: 66.73MiB (26.5%);". When I clean out the proxy cache stored in RAM all goes back to normal. I've 50% of RAM allocated for proxy cache.
do you have 5.22 on both sides?The scenario is Sextant AP ----> Sextant station bridge (protocol nv2) ... after 1 day trafic stoping. Enable disable wireless interface traffic comes. When ptotocol is nstream no problem. Downgrade to 5.18 NO problem too.
most likely you are configuring the Nv2 station end. For Nv2 station you only need to check if you willl use security or not as all the other Nv2 settings are sent and configured by AP.Am I missing something in 5.22 but in Winbox, wireless settings, NV2 Tab a heap of settings missing, TDMA Period Cell radius etc only field there now is the security check box and entry..
Only accessible by terminal now ?
Maybe you have the default ssid=MikroTik?There's an issue with 'export compact' feature
It does not include the SSID if the radio is in NV2 mode AP/bridge
This is from a 711GA-5HnD
/interface wireless
set 0 band=5ghz-a/n country=ireland default-forwarding=no disabled=no \
frequency=5660 ht-rxchains=0,1 ht-txchains=0,1 l2mtu=2290 mode=ap-bridge \
nv2-preshared-key=xxxxxxxxxxxxxxxxxxxx nv2-security=enabled \
security-profile=CPE wireless-protocol=nv2
we need support output file from that situation so we could understand what is causing that.Hello Folks!
PROBLEM!!
Suddenly one by one our CPE:s stop working, no traffic on eth1 at all, DHCP offer we see only, nothing more.
Known affected devices so far RB411
Rollback to 5.20 solved the problem.
please make a support output file from that router and send to support@mikrotik.comROS: 5.22
00:00:13 system,error,critical System rebooted because of kernel failure
00:00:16 system,error,critical router was rebooted without proper shutdown
00:00:19 interface,info ether1 link up (speed 100M, full duplex)
RB433AH
After few hours again "rebooted because of kernel failure" and CPU 100% and 100MHz !!!
ROS 5.22 looks like early beta...
Installed Chrome browser on iPhone - no problem with log in (tried several times - every time successfully). But with v5.19 and earlier versions - I have never met such problem with Safari browser on iOS.Segir, have you tried to install a Chrome on IOS device, does it work with it?
With RouterOS v5.20 you didn't have such problem?
Am I the only one with this problem?When removing an UPS, or changing the serial port of an UPS, the previous serial port is still assigned to the UPS and unable to be reused by any other process.
what do you mean by "changing the port"? how many serial ports does your device have, and why are you changing them?Am I the only one with this problem?When removing an UPS, or changing the serial port of an UPS, the previous serial port is still assigned to the UPS and unable to be reused by any other process.
RB1100AH.what do you mean by "changing the port"? how many serial ports does your device have, and why are you changing them?Am I the only one with this problem?When removing an UPS, or changing the serial port of an UPS, the previous serial port is still assigned to the UPS and unable to be reused by any other process.
I now have also problems with creating backup on 5.22. Backup file gets partially created and the router logs:So here's how it looks from terminal:I came across memory usage reporting error using v.5.22 with web proxy enabled caching to RAM. "System -> Resources" claim to have 4GiB free memory on my RB450G, while graphs say for example "Max: 345.17MiB (137.4%); Average: 124.61MiB (49.6%); Current: 66.73MiB (26.5%);". When I clean out the proxy cache stored in RAM all goes back to normal. I've 50% of RAM allocated for proxy cache.
> /system resource print
uptime: 1w13h59m17s
version: 5.22
free-memory: 4294958956KiB
total-memory: 257108KiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 680MHz
cpu-load: 0%
free-hdd-space: 435532KiB
total-hdd-space: 520192KiB
write-sect-since-reboot: 1117527
write-sect-total: 47863782
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB450G
platform: MikroTik
and screenshot from winbox:
Dec 8 10:11:27 router error creating backup file: could not read all configuration files
/export file=filename
I confirm this problem still occur.Do u still have this problem with 5.22 because I have this problem with previous versionThe scenario is Sextant AP ----> Sextant station bridge (protocol nv2) ... after 1 day trafic stoping. Enable disable wireless interface traffic comes. When ptotocol is nstream no problem. Downgrade to 5.18 NO problem too.
but now 2-3 days with 5.22 seam fine
I have this problem after 5.18 version. With 5.18 no problem. (upgraded new versions (5.19-5.20-5.21-5.22 on both sides but same problems)I confirm this problem still occur.Do u still have this problem with 5.22 because I have this problem with previous versionThe scenario is Sextant AP ----> Sextant station bridge (protocol nv2) ... after 1 day trafic stoping. Enable disable wireless interface traffic comes. When ptotocol is nstream no problem. Downgrade to 5.18 NO problem too.
but now 2-3 days with 5.22 seam fine
what do you mean by "changing the port"? how many serial ports does your device have, and why are you changing them?Am I the only one with this problem?When removing an UPS, or changing the serial port of an UPS, the previous serial port is still assigned to the UPS and unable to be reused by any other process.
This helps me as well. So, it's dude or snmp issue?Read in another post about someone who had a similar problem so i changed my dude settings on the specific device and unchecked the Router OS checkbox in the general tab in the dude. It seems to have solved the problem.
Definitely not. These are configured sites upgraded to 5.22 where we see thisMaybe you have the default ssid=MikroTik?
The same probem. Configuration is AP BRIDGE with nv2. No trafic, no ping. Reboot solved problem.The scenario is Sextant AP ----> Sextant station bridge (protocol nv2) ... after 1 day trafic stoping. Enable disable wireless interface traffic comes. When ptotocol is nstream no problem. Downgrade to 5.18 NO problem too.
Anyone else came across faulty memory usage reporting and broken configuration backup?I now have also problems with creating backup on 5.22. Backup file gets partially created and the router logs:So here's how it looks from terminal:I came across memory usage reporting error using v.5.22 with web proxy enabled caching to RAM. "System -> Resources" claim to have 4GiB free memory on my RB450G, while graphs say for example "Max: 345.17MiB (137.4%); Average: 124.61MiB (49.6%); Current: 66.73MiB (26.5%);". When I clean out the proxy cache stored in RAM all goes back to normal. I've 50% of RAM allocated for proxy cache.
> /system resource print
uptime: 1w13h59m17s
version: 5.22
free-memory: 4294958956KiB
total-memory: 257108KiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 680MHz
cpu-load: 0%
free-hdd-space: 435532KiB
total-hdd-space: 520192KiB
write-sect-since-reboot: 1117527
write-sect-total: 47863782
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB450G
platform: MikroTik
and screenshot from winbox:I can doCode: Select allDec 8 10:11:27 router error creating backup file: could not read all configuration files
though with no problems.Code: Select all/export file=filename
NO COMMENT on dhcp-server deassigning and reassigning leases at odd times?! This isn't happening to anyone else?Beginning on Nov 12, several devices on our network are having their (static) DHCP addresses deassigned and immediately reassigned every few hours, intermittently, despite the standard 3-day lease length... At the same time that this occurs, current connections (e.g., VoIP, Skype) on these devices drop... I am not sure if this is caused by the dhcp-server system (e.g., changes made for 5.21) or something else; Hopefully, this will help someone track down the problem. If anyone has any insight into this, or this issue has been seen before, please let me know!
EDIT: This is on a RB750UP, currently running ROS 5.22. Upon further perusal of the logs, this deassign-reassign pattern goes back years--but this is the first time I have noticed it happening with static leases, and with devices for which it causes the user a real inconvenience.
Jan 9 11:24:05 33Comm LAN2-DHCP deassigned 192.168.152.20 from [hh:hh:hh:hh:hh:hh]
Jan 9 11:24:06 33Comm LAN2-DHCP assigned 192.168.152.20 to [hh:hh:hh:hh:hh:hh]
...
Jan 9 16:04:14 33Comm LAN2-DHCP deassigned 192.168.152.20 from [hh:hh:hh:hh:hh:hh]
Jan 9 16:04:15 33Comm LAN2-DHCP assigned 192.168.152.20 to [hh:hh:hh:hh:hh:hh]
Config:
/ip pool
add name=LAN2-Pool ranges=192.168.152.10-192.168.152.250
/ip dhcp-server
add add-arp=yes address-pool=LAN2-Pool authoritative=yes disabled=no interface=ether2-LAN lease-time=3d name=LAN2-DHCP
/ip dhcp-server network
add address=192.168.152.0/24 dhcp-option="" dns-server=192.168.152.1 gateway=192.168.152.1 ntp-server=10.0.1.13 wins-server=""
This is probably normal behaviour. A DHCP client should renew its IP adress at half leasetime. Most clients do it more often in my expreience.At the very least, I would expect these events to occur three days apart; i.e., the duration of the lease. And I certainly would not expect a DHCP renewal to cause connections to drop. Insights, anyone?
Renewing the lease might be normal behavior, but not dropping connections as a result! I found these deassign/reassign events because they coincide with the client reporting that an application's remote database connection closed unexpectedly. It has been happening several times a day. Not all of them trace back to one of these DHCP events, but the fact that two of them do makes me suspicious.This is probably normal behaviour. A DHCP client should renew its IP adress at half leasetime. Most clients do it more often in my expreience.At the very least, I would expect these events to occur three days apart; i.e., the duration of the lease. And I certainly would not expect a DHCP renewal to cause connections to drop. Insights, anyone?
I have the same problem with many customers on 5.22 and DHCP leases, Yes there is something wrong with 5.22 DHCPThis cannot be normal dhcp-server behavior, nor can this many different clients (owned by various individuals working in different organizations) be misconfigured in the same way. This isn't even the complete list for one day, just the more egregious examples:
DHCP deassigns/reassigns the same IP to the same MAC three times within fifteen seconds:Assigned, then 7 minutes later (de)assigned 4 times over the course of ~6 minutes:
- Jan 10 10:12:48 33Comm Hotspot-DHCP deassigned 10.1.150.82 from [mac1]
Jan 10 10:12:48 33Comm Hotspot-DHCP assigned 10.1.150.82 to [mac1]
Jan 10 10:12:57 33Comm Hotspot-DHCP deassigned 10.1.150.82 from [mac1]
Jan 10 10:12:57 33Comm Hotspot-DHCP assigned 10.1.150.82 to [mac1]
Jan 10 10:13:01 33Comm Hotspot-DHCP deassigned 10.1.150.82 from [mac1]
Jan 10 10:13:02 33Comm Hotspot-DHCP assigned 10.1.150.82 to [mac1](de)assigned only 30 seconds after the initial assignment:
- Jan 10 14:23:06 33Comm Hotspot-DHCP assigned 10.1.150.60 to [mac2]
Jan 10 14:30:38 33Comm Hotspot-DHCP deassigned 10.1.150.60 from [mac2]
Jan 10 14:30:38 33Comm Hotspot-DHCP assigned 10.1.150.60 to [mac2]
Jan 10 14:32:23 33Comm Hotspot-DHCP deassigned 10.1.150.60 from [mac2]
Jan 10 14:32:23 33Comm Hotspot-DHCP assigned 10.1.150.60 to [mac2]
Jan 10 14:33:15 33Comm Hotspot-DHCP deassigned 10.1.150.60 from [mac2]
Jan 10 14:33:15 33Comm Hotspot-DHCP assigned 10.1.150.60 to [mac2]
Jan 10 14:37:00 33Comm Hotspot-DHCP deassigned 10.1.150.60 from [mac2]
Jan 10 14:37:00 33Comm Hotspot-DHCP assigned 10.1.150.60 to [mac2]...and then half an hour later, most disturbingly, the same device is deassigned, and then reassigned a different IP:
- Jan 10 16:29:32 33Comm Hotspot-DHCP assigned 10.1.150.86 to [mac3]
Jan 10 16:30:04 33Comm Hotspot-DHCP deassigned 10.1.150.86 from [mac3]
Jan 10 16:30:05 33Comm Hotspot-DHCP assigned 10.1.150.86 to [mac3]When would that ever be desired behavior?!
- Jan 10 17:02:27 33Comm Hotspot-DHCP deassigned 10.1.150.86 from [mac3]
Jan 10 17:02:30 33Comm Hotspot-DHCP assigned 10.1.150.66 to [mac3]
Assigned and deassigned twice over the course of one second--and left deassigned?!Interestingly, in this last case, the log file on the board itself shows this (de)assignment happening seven times in one second, and leaves it assigned. The above is taken from its remote log. On the board, the log file reads:
- Jan 10 23:40:46 33Comm Hotspot-DHCP assigned 10.1.150.46 to [mac4]
Jan 10 23:40:46 33Comm Hotspot-DHCP deassigned 10.1.150.46 from [mac4]
Jan 10 23:40:46 33Comm Hotspot-DHCP assigned 10.1.150.46 to [mac4]
Jan 10 23:40:46 33Comm Hotspot-DHCP deassigned 10.1.150.46 from [mac4]Clearly something is broken!
- jan/10 23:40:46 dhcp,info Hotspot-DHCP assigned 10.1.150.46 to [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP deassigned 10.1.150.46 from [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP assigned 10.1.150.46 to [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP deassigned 10.1.150.46 from [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP assigned 10.1.150.46 to [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP deassigned 10.1.150.46 from [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP assigned 10.1.150.46 to [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP deassigned 10.1.150.46 from [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP assigned 10.1.150.46 to [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP deassigned 10.1.150.46 from [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP assigned 10.1.150.46 to [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP deassigned 10.1.150.46 from [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP assigned 10.1.150.46 to [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP deassigned 10.1.150.46 from [mac4]
jan/10 23:40:46 dhcp,info Hotspot-DHCP assigned 10.1.150.46 to [mac4]
I'm glad to know it isn't just me or something flaky about our configuration. Are you also experiencing the breaking of persistent connections (VoIP, RDP) when this happens? Do you suppose downgrading to 5.21 might improve the situation?I have the same problem with many customers on 5.22 and DHCP leases, Yes there is something wrong with 5.22 DHCPThis cannot be normal dhcp-server behavior, nor can this many different clients (owned by various individuals working in different organizations) be misconfigured in the same way... Clearly something is broken!
I have downgraded some CPE's to 5.20 because the logs on cpe's running that version did not have dhcp issues and i needed a quick if temporary fix for this, on the AP's and a lot of cpe's which are still 5.22 until i downgrade is to remove any IP Services not being used for me i use only Winbox + Telnet the rest API,ftp,ssh,www-ssh and especially www are not used so i disabled not sure it will help.I'm glad to know it isn't just me or something flaky about our configuration. Are you also experiencing the breaking of persistent connections (VoIP, RDP) when this happens? Do you suppose downgrading to 5.21 might improve the situation?
@Sergis I have the same issue and will follow your instructions, in response to question about local network works fine and there is no problem with wireless disconnects, bad switch, etc.Hotz1
we are interested in your problem about DHCP-server leases reassignments.
1) Please run /tool sniffer on DHCP-server interface, during assignment/deassigment;
2) Make support output file after clicking stop on /tool sniffer;
3) Send both files for us, we will research where could be the problem (I assume local network works fine and there is no problem with wireless disconnects, bad switch, etc.).
Jan/08/2013 18:59:43 dhcp,info dhcp1 deassigned 192.168.1.198 from 8C:FA:BA:5D:39:97
Jan/08/2013 18:59:45 dhcp,info dhcp1 assigned 192.168.1.198 to 8C:FA:BA:5D:39:97
Jan/08/2013 19:11:47 dhcp,info dhcp1 deassigned 192.168.1.96 from 04:0C:CE:4C:95:2A
Jan/08/2013 19:11:49 dhcp,info dhcp1 assigned 192.168.1.96 to 04:0C:CE:4C:95:2A
Jan/08/2013 20:06:08 dhcp,info dhcp1 deassigned 192.168.1.198 from 8C:FA:BA:5D:39:97
Jan/08/2013 20:06:09 dhcp,info dhcp1 assigned 192.168.1.198 to 8C:FA:BA:5D:39:97
Jan/08/2013 21:54:51 dhcp,info dhcp1 assigned 192.168.1.33 to 60:67:20:AB:E8:4C
Jan/09/2013 11:33:58 dhcp,info dhcp1 deassigned 192.168.1.29 from 00:1B:B1:8B:2E:40
Jan/09/2013 18:18:40 dhcp,info dhcp1 deassigned 192.168.1.96 from 04:0C:CE:4C:95:2A
Jan/09/2013 18:18:42 dhcp,info dhcp1 assigned 192.168.1.96 to 04:0C:CE:4C:95:2A
Jan/09/2013 18:26:31 dhcp,info dhcp1 deassigned 192.168.1.198 from 8C:FA:BA:5D:39:97
Jan/09/2013 18:26:32 dhcp,info dhcp1 assigned 192.168.1.198 to 8C:FA:BA:5D:39:97
Jan/09/2013 21:32:10 interface,info ether1 link down
Jan/09/2013 21:32:34 interface,info ether1 link up (speed 100M, full duplex)
Jan/09/2013 21:32:43 interface,info ether1 link down
Jan/09/2013 21:32:44 interface,info ether1 link up (speed 100M, full duplex)
Jan/09/2013 21:32:51 interface,info ether1 link down
Jan/09/2013 21:32:53 dhcp,info dhcp1 deassigned 192.168.1.93 from 00:19:FB:24:BA:11
Jan/09/2013 21:32:53 dhcp,info dhcp1 assigned 192.168.1.93 to 00:19:FB:24:BA:11
Jan/09/2013 21:32:53 interface,info ether1 link up (speed 100M, full duplex)
Jan/10/2013 18:59:43 dhcp,info dhcp1 deassigned 192.168.1.198 from 8C:FA:BA:5D:39:97
Jan/10/2013 19:00:02 dhcp,info dhcp1 assigned 192.168.1.198 to 8C:FA:BA:5D:39:97
Jan/10/2013 19:01:30 dhcp,info dhcp1 deassigned 192.168.1.96 from 04:0C:CE:4C:95:2A
Jan/10/2013 19:01:31 dhcp,info dhcp1 assigned 192.168.1.96 to 04:0C:CE:4C:95:2A
Jan/10/2013 20:03:38 dhcp,info dhcp1 deassigned 192.168.1.33 from 60:67:20:AB:E8:4C
Jan/10/2013 20:03:39 dhcp,info dhcp1 assigned 192.168.1.33 to 60:67:20:AB:E8:4C
Jan/10/2013 20:44:25 dhcp,info dhcp1 deassigned 192.168.1.35 from 00:0C:43:CE:19:D6
Jan/10/2013 20:44:34 dhcp,info dhcp1 assigned 192.168.1.35 to 00:0C:43:CE:19:D6
Jan/10/2013 21:02:28 interface,info ether1 link down
Jan/10/2013 21:02:48 interface,info ether1 link up (speed 100M, full duplex)
Jan/10/2013 21:02:57 interface,info ether1 link down
Jan/10/2013 21:02:59 interface,info ether1 link up (speed 100M, full duplex)
Jan/10/2013 21:03:05 interface,info ether1 link down
Jan/10/2013 21:03:06 dhcp,info dhcp1 deassigned 192.168.1.93 from 00:19:FB:24:BA:11
Jan/10/2013 21:03:07 interface,info ether1 link up (speed 100M, full duplex)
Jan/10/2013 21:03:12 dhcp,info dhcp1 deassigned 192.168.1.198 from 8C:FA:BA:5D:39:97
Jan/10/2013 21:03:12 dhcp,info dhcp1 assigned 192.168.1.93 to 00:19:FB:24:BA:11
Jan/10/2013 21:03:13 dhcp,info dhcp1 assigned 192.168.1.198 to 8C:FA:BA:5D:39:97
Jan/11/2013 15:39:32 dhcp,info dhcp1 deassigned 192.168.1.96 from 04:0C:CE:4C:95:2A
Jan/11/2013 15:39:34 dhcp,info dhcp1 assigned 192.168.1.96 to 04:0C:CE:4C:95:2A
Jan/11/2013 21:13:11 dhcp,info dhcp1 deassigned 192.168.1.96 from 04:0C:CE:4C:95:2A
Jan/11/2013 21:13:13 dhcp,info dhcp1 assigned 192.168.1.96 to 04:0C:CE:4C:95:2A
Jan/12/2013 17:59:17 dhcp,info dhcp1 deassigned 192.168.1.198 from 8C:FA:BA:5D:39:97
Jan/12/2013 17:59:19 dhcp,info dhcp1 assigned 192.168.1.198 to 8C:FA:BA:5D:39:97
Jan/12/2013 18:11:42 dhcp,info dhcp1 deassigned 192.168.1.96 from 04:0C:CE:4C:95:2A
Jan/12/2013 18:11:46 dhcp,info dhcp1 assigned 192.168.1.96 to 04:0C:CE:4C:95:2A
Jan/12/2013 18:32:50 dhcp,info dhcp1 deassigned 192.168.1.37 from 00:0C:E7:01:62:4C
Jan/12/2013 18:33:24 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/12/2013 18:35:24 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/12/2013 18:35:41 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/12/2013 19:39:11 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/12/2013 19:39:15 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/13/2013 13:23:27 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/13/2013 13:23:30 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/13/2013 13:24:38 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/13/2013 13:30:25 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/13/2013 13:30:31 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/13/2013 13:30:36 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/13/2013 13:42:46 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/13/2013 13:42:46 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/13/2013 17:32:01 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/13/2013 17:32:52 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/14/2013 13:50:11 dhcp,info dhcp1 deassigned 192.168.1.30 from 08:60:6E:27:07:C9
Jan/14/2013 13:50:11 dhcp,info dhcp1 assigned 192.168.1.30 to 08:60:6E:27:07:C9
Jan/14/2013 19:45:31 dhcp,info dhcp1 deassigned 192.168.1.198 from 8C:FA:BA:5D:39:97
Jan/14/2013 19:45:38 dhcp,info dhcp1 assigned 192.168.1.198 to 8C:FA:BA:5D:39:97
Jan/14/2013 20:40:25 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/14/2013 20:40:42 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/14/2013 21:37:38 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/14/2013 21:37:50 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/14/2013 21:38:19 dhcp,info dhcp1 deassigned 192.168.1.31 from 00:0C:E7:01:62:4C
Jan/14/2013 21:38:29 dhcp,info dhcp1 assigned 192.168.1.31 to 00:0C:E7:01:62:4C
Jan/14/2013 23:16:31 dhcp,info dhcp1 deassigned 192.168.1.30 from 08:60:6E:27:07:C9
Jan/14/2013 23:16:31 dhcp,info dhcp1 assigned 192.168.1.30 to 08:60:6E:27:07:C9
Jan/14/2013 23:18:32 dhcp,info dhcp1 deassigned 192.168.1.30 from 08:60:6E:27:07:C9
Jan/14/2013 23:18:32 dhcp,info dhcp1 assigned 192.168.1.30 to 08:60:6E:27:07:C9
Jan/14/2013 23:20:09 dhcp,info dhcp1 deassigned 192.168.1.30 from 08:60:6E:27:07:C9
Jan/14/2013 23:20:09 dhcp,info dhcp1 assigned 192.168.1.30 to 08:60:6E:27:07:C9
Did you ever get a resolution to this? Couldn't see anything acknowledging the bug in the v5 changelogs so guessing it's still an issue with v5.26?RB1100AH.
I had an issue with an UPS that doesnt want to be recognized after a reboot. I tried to assign the UPS to the second port, but the first serial port is still show in used by the UPS. Even after removing all UPS from the setup, I can't even use the terminal to serial as I get an error that the port is still assigned to the UPS even when there is no more UPS in the setup.
So, how serious is this? Every links goes down now and than. Should I now upgrade or not? (I just finished upgrading to 5.21...)What's new in 5.22 (2012-Nov-23 09:28):
*) wireless - fixed rare nv2 link stall;
Did the links stall under certain conditions? Or in general.
In the first case I would like to know what these conditions/configs where.... In the second case I probably need to update again soon.... (after not too many issues are being reported here...)
I'd like some additional information on this as well. I've noticed a problem where some NV2 configured access points would just stop sending/receiving data and would not start again until the interface was disabled and then re-enabled.
Does this fix that issue? Is there a detailed bug report we can see?