I can't register cause the captcha is not being displayed. Is it the right URL ?dynek - Seems like you will need to open new ticket. I did test with all of these windows opened on Winbox but still did not manage to reproduce problem.
Click on each download link. There is no more torrent.and your point is ?
Please tell us more about that. Which fields are used? What netflow collector understands them?*) trafflow: add natted addrs/ports to ipv4 flow info;
template fields added are postNATSourceIPv4Address, postNATDestinationIPv4Address, postNAPTSourceTransportPort and postNAPTDestinationTransportPort - they should be recognized by any NetFlow v9 collectorWhat format and for what collector are the NAT events anyway, do they correspond to any standard or a generally used format? (I guess that the format of ipt_netflow will be compatible, but I want to be sure).
[admin@rb2011] > /system resource print
uptime: 5d1h22m46s
version: 6.29
build-time: May/27/2015 11:19:36
write-sect-since-reboot: 3422
board-name: RB2011UiAS-2HnD
Do you really need all four architectures immediately? Do you really upgrade MIPS-LE and PPC devices also? It is actually one file per architecture, and unless you are some sort of collector, you usually need only one.Personally I don't 'need it now'.
I am not affected by the bugs resolved in 6.29.1 anyway.
What I am saying is that for whatever reason everyone has, the .torrent files are really useful. More useful than downloading 20 files manually from the download page.
Yeah I used Winbox3RC10 closed everything and checked from command line (ssh) and sector writes is still going higher.dynek - Seems like you will need to open new ticket. I did test with all of these windows opened on Winbox but still did not manage to reproduce problem.
I already described the mechanism above (see http://forum.mikrotik.com/viewtopic.php ... ve#p484196).According to previous topics many clients did respond that sector writes issue was solved for them (when Firewall menu was opened in Winbox). We also did see that fix is working in out lab. If you still notice sector writes counter rising without apparent reason, then please write to. Tell us what do you do at the moment when it is happening. For example, if it is happening while Winbox is opened, then name what kind of windows are you using while it is happening.
I tested it on RB411AH with 6.29.1 and I see 4 sector writes after just opening an existing firewall rule (a new empty accept rule in forward chain). A new line appears in Log each time I open the rule (double click on the rule) with this text:Excessive flash writings are not solved.
Tried on Omnitik for the first time, freshly updated from 6.28 to 6.29 via direct update. Opening the rule in firewall (just double click, no change, no save) adds two writes to the flash each time.
Sometimes just opening makes "filter rule moved by user" in the log.
What the hell? Having only one fake rule to check what it does when I open it, and it does these things??? Even when the rule is disabled! Of course the only one rule cannot be moved anywhere!
How difficult could be to correct these errors?
I recently exported from a major v6 ROS to another but after reviewing the terminal found a number of command syntax's had changed on importation of the export. One of the changes was - set time-zone-autodetect=no time-zone-name=Australia/Brisbane which caused the timezone not to be applied. I can't recall the other 2. If this type of thing is happening between versions stability of configurations will be effected.As a matter of fact Mikrotik staff may have accidentally acknowledged this by suggesting to export the config, netinstall and then import the config back - all because the NTP client wouldn't work after an upgrade(!)
I don't see any other official explanation for the tons of bug (or not) reports on each new version.
Take every thread for each new version (especially after v6.x). It will be 6-10pages of which most posts will be about reporting bugs or problems after the upgrade and how downgrading back to whatever previous version, resolves it.
The pattern is quite clear I am afraid.
no, you must upload older files, and run command "/system package downgrade".Can someone confirm if downgrading is just a matter of putting previous version files in place and reboot the device just like an upgrade ?
Thank you !
.1 adresses an issue with CRS where you could not connect to themWhat's the different of the V6.29.1 with this?
Confirmed by Mikrotik to be bug, hopefully it will be corrected in some subsequent winbox.I already described the mechanism above (see http://forum.mikrotik.com/viewtopic.php ... ve#p484196).According to previous topics many clients did respond that sector writes issue was solved for them (when Firewall menu was opened in Winbox). We also did see that fix is working in out lab. If you still notice sector writes counter rising without apparent reason, then please write to. Tell us what do you do at the moment when it is happening. For example, if it is happening while Winbox is opened, then name what kind of windows are you using while it is happening.
I have to add that I am not logging to internal flash at all but to usb flashdisks and to remote syslog.
Used windows are resources, interface list, firewall, route list, profiler, wireless tables and log. Used Winbox3rc10.
[Ticket#2015060366000163] created.
Hi all
Does anybody having problem using IP Hotspot after upgrading to 6.29.1 from 6.27 ?
My clients are obtain dhcp, but after requesting http traffic(before login), the client doesn't appear at /ip hotspot host and it seems the packet is not forwarded normally and caused my client is not redirected to my external login page.
Thank you
Anderson
HelloHello
I upgraded my RB433 from 3.30 to 4.17>5.26>6.29
All went fine.
But i noticed one problem.
ETHER1 is making traffic (around 15mbs) all the time even if device connected to it is not making any traffic at all.
When i disable it its OK then i enable and its OK until i try to ping something on that interface than again 15mbs of fake traffic and CPU goes to 90%
Emmm nothing its classic router tplink connected to that ether1 but noone is using it at that moment but still there is 15/5 mbs usage.And what is the traffic?
+1 also experiencing this on our ccr1036. Upgraded from 6.22 to 6.29, only tx bandwidth flow being sent from an interface. Had to enable traffic flow on our edge router which is still sitting on 6.22.this update appears to have broken NetFlow it is no longer sending ingress and egress flow data for the same interface. only appears to be exporting Egress flows. per interface.
Report this to support@mikrotik.comHi,
I think this is a bug or something can't say cleary.
Problem is when change SIM card for RB922 or RB912 with RouterOS v6.29.1.
Have 2 SIM card with different ISP. Another have PIN code other not have PIN code. When first card witch have PIN code everything works wine, but when i change card to no PIN code one and remove that PIN code area in RouterOS then it can't connect. I need to make FULL reset for router and configure all things again without touch that PIN code area and then SIM works.
Any fix for this?
Very very close to my caseInstalled 6.29.1 on my RB750UP that runs my office. Watchdog timer reboot the router every 5 minutes.
...
Edit: Now that I'm not in a pinch, RB750UP, 6.20, NTP and DNS, couple of GRE links, tried 6.29.1, seemed okay, enabled Fasttrack, worked beautifully, CPU was like 16% while I was pushing it. Love it.
Then it reboot.
Then it reboot again.
...
Have you read my post???Serious bug with ethernet on SXT G-5HPacD and v6.29.1 - messed up a lot of time and cpe-s.
In bridged mode, cannot access the device from ethernet side. After ~a day of working eth starts blinking 1 per second, reboot does not help.
Downgrading to the 6.28 solved the problem
I noticed same bug on my RB 433. Anybody else?this update appears to have broken NetFlow it is no longer sending ingress and egress flow data for the same interface. only appears to be exporting Egress flows. per interface.
I noticed same bug on my RB 433. Anybody else?this update appears to have broken NetFlow it is no longer sending ingress and egress flow data for the same interface. only appears to be exporting Egress flows. per interface.
Hi, same issue here. Version 6.27 works perfect. Version 6.29.1 fails to route traffic through the tunnel other than its own openvpn subnet. I can ping the openvpn interface on the Routerboard though, so the tunnel is up.Hi,
since 6.29 (and 6.29.1) OpenVPN seems broken :
If I connect to openvpn from the internet the connection succeeds. But no network traffic is possible (ping, http,dns ...). In the WebUI i can see the connection is alive but no packets are going through.
If I connect to openvpn from inside (intranet) the connection is established and everything (ping, http, dns, ...) is working.
Any ideas about this ?
Meitonga
I noticed same bug on my RB 433. Anybody else?this update appears to have broken NetFlow it is no longer sending ingress and egress flow data for the same interface. only appears to be exporting Egress flows. per interface.
Hello! Yes, i have similar bug with 6.29.1. Traffic flow does not work correctly.
Dear Sir, Hi, I am also facing the same problem, NTP client is not responding, and the time is not correct, I got more than 10 mikrotiks, ALL of them got that problem, the version are 6.28, 6.29, even 6.30 (19), any one else got the same problem?I recently exported from a major v6 ROS to another but after reviewing the terminal found a number of command syntax's had changed on importation of the export. One of the changes was - set time-zone-autodetect=no time-zone-name=Australia/Brisbane which caused the timezone not to be applied. I can't recall the other 2. If this type of thing is happening between versions stability of configurations will be effected.As a matter of fact Mikrotik staff may have accidentally acknowledged this by suggesting to export the config, netinstall and then import the config back - all because the NTP client wouldn't work after an upgrade(!)
I don't see any other official explanation for the tons of bug (or not) reports on each new version.
Take every thread for each new version (especially after v6.x). It will be 6-10pages of which most posts will be about reporting bugs or problems after the upgrade and how downgrading back to whatever previous version, resolves it.
The pattern is quite clear I am afraid.
received decline with id 0 from 0.0.0.0
/system resource print
version: 6.29.1
architecture-name: powerpc
board-name: RB1100AHx2
chain=input disabled=yes action=drop connection-state=invalid log=no log-prefix=""
chain=input disabled=yes action=accept connection-state=related log=no log-prefix=""
chain=input disabled=yes action=accept connection-state=established log=no log-prefix=""
Same problem here (two independent RB1100AHx2).As I understand the current processing of IPSec encrypted traffic, the traffic passes the firewall input chain, is then decrypted and the decrypted traffic is then again handled by the firewall e.g. the forward chain.
When the firewall processes the decrypted traffic it will be shown as coming from the original interface the encrypted IPSec traffic has been received on. As such there it is not possible to determine if the decrypted traffic is coming from an IPSec tunnel.
Up until RouterOS 6.27 it was possible to overcome this shortcoming by marking incoming IPSec packets using the firewalls mangle functionality. The packet mark would remain on the decrypted traffic (e.g. also on the forward chain) and could therefore be used in the firewall for filtering purposes.
Since RouterOS 6.28 the packet marks do not exist on the decrypted traffic anymore. Has this been changed / fixed in RouterOS 6.29?
Thanks
seems like it won't be possible anymore, but another solution is coming:After upgrade from 6.24 to 6.29.1, ipsec packet mark in mangle-prerouting chain does not work, or it's not catched by filter-forward chain.
p.s. Normis, sed s/wheather/whether/What's new in 6.30rc19 (2015-Jun-12 11:45):
*) firewall - added ipsec-policy matcher to check wheather packet was/will be ipsec processed or not;
/system resource print
uptime: 2h50m33s
version: 6.29.1
build-time: Jun/01/2015 13:30:35
free-memory: 42.1MiB
total-memory: 64.0MiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 400MHz
cpu-load: 5%
free-hdd-space: 4084.0KiB
total-hdd-space: 16.0MiB
write-sect-since-reboot: 707
write-sect-total: 119714
bad-blocks: 0%
architecture-name: mipsbe
board-name: mAP
platform: MikroTik
because it's not a releaseSorry, I know this is not the 6.30rc topic, but there is no one official.
please write to support@mikrotik.comThere is a problem with the scheduler on v6.30rc22.
Some RCs have their owns topics.because it's not a releaseSorry, I know this is not the 6.30rc topic, but there is no one official.
please write to support@mikrotik.comThere is a problem with the scheduler on v6.30rc22.
Where can I download 6.28?@Infused
I roll 6.28 release on 90% of our company routers and its by far most stable version, but to be honest, i didnt had problems with 6.27 either.
Copy the old URL and adjust it like -
Where can I download 6.28?
Thanks!
in fact specifically happened the day before yesterday and yesterday 21:00CCR1009-8G-1S-1S + with packages v6.29.1 crash after several hours
on average througtput 100MiB Running
ospf+vlan+PPPoE-Server+simple queues
Thanks!Copy the old URL and adjust it like -
Where can I download 6.28?
Thanks!
http://download2.mikrotik.com/routeros/ ... e-6.28.npk
checked with 6.29 - no problem when adding ARP entry if dynamic entry for this IP already existsI can't make any of arp static due to "Couldn't add new ARP, Already have such ARP!" error.
It would be awesome if there was a command for that too. making static is only possible on gui (I know with some scripts it is possible. I mean something like "/ip arp set x static=yes")
After series of tests, I found the source of this issue: it's just the fact, that if you set physical interface (ether11 in my case) as Target for simple queue and there are VRRP interfaces on this physical interface, then the traffic that goes through those VRRP interfaces are not included in this simple queue (even if this VRRP interfaces "sit" on the ether11 port). More precisely, outgoing traffic is handled, incoming not (as you can see on screenshots). There is src-nat (firewall - NAT) rule to handle the address translation from LAN to WAN - is it possible that it affects this situation?Upgraded two RB1100AHx2 (powerpc) from 6.24 to 6.29.1 and since then I have problem with Simple Queues respectively... half of it:
Simple example from wiki - limit LAN traffic (identified by IP address range) to WAN (identified by interface eth11 to ISP; there is src-nat to public IP address on VRRP interface assigned to eth11). Upload queue works as expected, but download one does not... with the same configuration as before upgrade.
I've upgraded also few other 2011UAS-2HnD (mipsbe) boxes in the same way, but all of them works normally as expected, but it might be also configuration related...
Just a guess... VRRP problem?
I'm also having the same issues, Time is not being updated via NTP, I set the NTP server IP address.Dear Sir, Hi, I am also facing the same problem, NTP client is not responding, and the time is not correct, I got more than 10 mikrotiks, ALL of them got that problem, the version are 6.28, 6.29, even 6.30 (19), any one else got the same problem?I recently exported from a major v6 ROS to another but after reviewing the terminal found a number of command syntax's had changed on importation of the export. One of the changes was - set time-zone-autodetect=no time-zone-name=Australia/Brisbane which caused the timezone not to be applied. I can't recall the other 2. If this type of thing is happening between versions stability of configurations will be effected.As a matter of fact Mikrotik staff may have accidentally acknowledged this by suggesting to export the config, netinstall and then import the config back - all because the NTP client wouldn't work after an upgrade(!)
I don't see any other official explanation for the tons of bug (or not) reports on each new version.
Take every thread for each new version (especially after v6.x). It will be 6-10pages of which most posts will be about reporting bugs or problems after the upgrade and how downgrading back to whatever previous version, resolves it.
The pattern is quite clear I am afraid.