As client do from captive portal side but from cli. Useful for scripting too if you want start counting login star time since x.*) hotspot - added option to login user manually from cli;
Can someone explain this please
CCR1036 OK!Does anyone tested on CCR1009 ?
Had problems with wireless part mine was not dead. Try netinstall... It worked for meHave attempted an update on two mibsbe devices, an RB450G and RB2011UAS-RM, both are now broken. Haven't been able to revert or recover them yet. Any one else have troubles?
Just tested this on CCR1009 and CCR1036 and it works great. Thanks MikroTik!!We have released 6.34 version.
*) mpls - forwarding of VRF over TE tunnel stopped working after BGP peer reset;
MikroTik 6.34rc36 (testing)
NOC Router Login:
Rebooting...
Stopping services...
verified routeros-mipsbe-6.34rc39.npk
installed routeros-mipsbe-6.34rc39
Restarting system.
RouterBOOT booter 3.24
RouterBoard 2011UAS
CPU frequency: 600 MHz
Memory speed: 200 MHz
Memory size: 128 MiB
NAND size: 64 MiB
Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Starting...
Starting services...
info failed: std failure: timeout (13)
There are archive on the top of download page.6.34 was made current, but "bugfix only" is stil 6.32.x
now it is not possible to update 6.33.5 to 6.33.6 from within the router.
or am I overlooking some possibility? I don't see the option to select a specific version anywhere, only the release channels.
and when I go to download on http://www.mikrotik.com there appears to be no way to download a specific version either, except by guessing its name.
ok I have found the archive section now, thanks.There are archive on the top of download page.
I think version need to finish more extensive testing before it is released in the bugfix channel, so it might be the reason for delay.
Also, switching version on all channels at the same time is not good idea, you need to leave at least some version to go back to in case of emargency.
Can you be more specific? What exactly isn't working?
I've upgraded 3-4 devices to 6.34 so far and I haven't got any issues with SNMP (or anything else for that matter) using Cacti, Observium, Dude and custom scripts.
I have got just the same issue. IPSEC between Mikrotiks only work if they all have 6.34 version. Android cannot connect via L2TP+IPSEC after RouterOS upgrade.L2TP / IPsec VPN from Android is not working since I upgraded to 6.34 Reverted back to 6.33.5 and it works again. Mikrotik to Mikrotik works providing they are all 6.34 But log doesnt even give errors on 6.34 with Android VPN connection attempts.
Please read the release notes!I have got just the same issue. IPSEC between Mikrotiks only work if they all have 6.34 version. Android cannot connect via L2TP+IPSEC after RouterOS upgrade.L2TP / IPsec VPN from Android is not working since I upgraded to 6.34 Reverted back to 6.33.5 and it works again. Mikrotik to Mikrotik works providing they are all 6.34 But log doesnt even give errors on 6.34 with Android VPN connection attempts.
And same problem as RB3011, no Switch menu too.No Ip --> Cloud in hap Lite with Winbox 3.1
We also opened ticket [Ticket#2016013166000402] as we have exactly the same thing, SNMP is reporting about 1/10 of real actual traffic passing through.Can you be more specific? What exactly isn't working?
I've upgraded 3-4 devices to 6.34 so far and I haven't got any issues with SNMP (or anything else for that matter) using Cacti, Observium, Dude and custom scripts.
We are seeing the numbers on the interfaces way lower than the actual interfaces are showing...
6.34 was the section between the two vertical bars... Stats drop off to 1/10? normal
I can confirm that on my routers the bandwidth usage displayed in graphs is much lower than the real.We also are seeing traffic graph issues with the release. rc41 was fine. After upgrade to the release the graph shows lower values than the interfaces do.The only lines in the graph that look to be proper size are ones that were drawn while refreshing the graph page.
So the first two graph lines at 9am local time show traffic to be around 1Gbps which is correct. After leaving and coming back 10 minutes later I refresh and the very next line shows less than 200Mbps.
Just a thought - how hard would it be to add a tick box for "show-incomplete" in /ip arp ? This may make it easier for some users to understand ?About ARP entries - they are completely normal. They have been there forever. Incomplete entries simply were no shown. Now we just do not hide them any more.
Well, because of many static entries in my dhcp-server-leases-list, I thought dynamic entriess are gone.There is something wrong in 6.33.6 and 6.34 relating secondary column sorting in WinBox, both 3.0 and 3.1. See the screenshot from 6.33.5 and previous versions - I use the sorting where ascending Address is primary and descending Expires secondary column.I can not set that in newer RouterOS. (I have just tried my home RB2011UiAS, nothing else)
I have the same identical problem and i opened a ticket this morning.Can you be more specific? What exactly isn't working?
I've upgraded 3-4 devices to 6.34 so far and I haven't got any issues with SNMP (or anything else for that matter) using Cacti, Observium, Dude and custom scripts.
We are seeing the numbers on the interfaces way lower than the actual interfaces are showing...
6.34 was the section between the two vertical bars... Stats drop off to 1/10? normal
Hi!Hello,
link to download all? torrent?
thank you
You are right, the problem is about not empty Address:What is the actual problem with sorting? We fixed Winbox and DHCP leases. Big part of information was not shown for static entries. Now you can see it. Please send to support@mikrotik.com screen shots where we could see correct and incorrect behaviour.
I suppose the old behaviour is fixed in mind, so all dynamic entries where on the top of the list regardless of any sorting.What is the actual problem with sorting? We fixed Winbox and DHCP leases. Big part of information was not shown for static entries. Now you can see it. Please send to support@mikrotik.com screen shots where we could see correct and incorrect behaviour.
I noticed that too, but didn't have the adjusted command, thanks.just for everyone's info.. this version broke our firewall I got an error that said expecting : in this line
add chain=ICMP protocol=icmp icmp-options=0:0-255 limit=5,5 action=accept comment="0:0 and limit for 5pac/s" disabled=no
I figured out what the change was by export the firewall which was already loaded that would no no longer load..
it wants this
add chain=ICMP protocol=icmp icmp-options=0:0-255 limit=5,5:packet action=accept comment="0:0 and limit for 5pac/s" disabled=no
so there is a new option on the limit command.. that specifies packets or bits apparently .... no sure what it does.
I was thinking about that too. It would not be the same - it would just list dynamic hosts first, sorted by IP. But I would like to see most fresh dynamic hosts first and, after them all the static sorted by IP - exactly as it was until now. Many of my routers have hundreds of dynamic host in wireless subnet and tens of static host for each other subnets. The old behaviour was perfect to see actual status.but I think a additional sort criteria with "D" for dynamic will be fine to give the look as before.
I've seen another problem with the DHCPv6-Client in 6.34 and Prefix Delegation. The "prefix-hint" doesn't appear to be functioning correctly.There seems to be an issue with the DHCPv6-Client.
...
This issue occurs in 6.34 for the first time. Until 6.33.5 there are no problems. 6.33.6 not tested.
Regarding the two posts before about IPV6, Dualstack with Carrier "T-Online/Deutsche Telekom" is running fine here.Hi!
After i upgrade from 6.30.4 to 6.34 i discover ipv6 was not working anymore. The issue seams to be the ipv6 dhcp client stuck in "Status: searching...". After i click the "Release" button the status is switching to "Status: bound" and then ipv6 is working fine. I'm using RouterOS in a KVM virtual machine and before the update i made a snaphot. If i revert to snapsot (version 6.30.4) everything is working fine. I try to reconfigure from scatch the version 6.34 to see if the issue is present and it was.
My connection type is pppoe with dhpd-pd
Marius.
My configuration is very similar. Vigor 130 in PPPoE Pass Through Mode, RB751G, ISP is "1und1" but carrier is also "Deutsche Telekom". The issue can be reproduced at 100%. After a downgrade it works again flawless.
Regarding the two posts before about IPV6, Dualstack with Carrier "T-Online/Deutsche Telekom" is running fine here.
No Problems, so I can´t confirm it . Hardware used is RB2011UiAS-2HnD with Vigor 130 in modem-mode.
Regards.......Detlef
Unfortunately, it is not a bug, it is the new feature We should use filter "Dynamic - is - yes" and then reorder (cca 7 clicks all together) or change to "no" and reorder again.In previous versions, the Address was empty for dynamic hosts, so I could get it right as in screeenshot, dynamic hosts first, sorted by Expires column and then static hosts:
1. click on Expires column, sorting is by this column ascending;
2. click on Expires column again, sorting is by this column descending;
3. click on Address column, sorting is by Address - the rows without any Address are listed first, sorted by Expires column.
It is not possible to set the same sorting in newer RouterOS, because dynamic hosts have the Addresses not empty.
Thx, we are waiting impatientlyThank you all for the report about SNMP values. Fix is on the way.
Probably graph counters show less traffic because the code that hides traffic generated by the new backdoor includes also normal packets... (just kidding).After several months and after a lot of rc release of new major version is full of basic errors. (GRAPH, SNMP, etc.)
I noticed when upgrading a CCR1036 with V6.34. snmp with cacti shows incorrect data. The Cacti will flatline on a read of 80mbps or whichever for about an hour or so and then update correctly again. When you log into the unit the SNMP data updates correctly immediately.Can you be more specific? What exactly isn't working?
I've upgraded 3-4 devices to 6.34 so far and I haven't got any issues with SNMP (or anything else for that matter) using Cacti, Observium, Dude and custom scripts.
It is the normal behaviour, isn't it?6.34 WebFig Torch malfunction, showing two lines of incomplete data (after clicking on start it works):
Is it too much asking for a v6.34.1 with the fix? Using an RC in production environment sounds a bit scary...Graphing and SNMP related issues are fixed in 6.35rc3 version:
*) interface - show stats properly in bits not bytes;
I also experience the same problem here, with pppoe +dhcpv6-pd. Reverting to 6.33.5 and everything works again.Hi!
After i upgrade from 6.30.4 to 6.34 i discover ipv6 was not working anymore. The issue seams to be the ipv6 dhcp client stuck in "Status: searching...". After i click the "Release" button the status is switching to "Status: bound" and then ipv6 is working fine. I'm using RouterOS in a KVM virtual machine and before the update i made a snaphot. If i revert to snapsot (version 6.30.4) everything is working fine. I try to reconfigure from scatch the version 6.34 to see if the issue is present and it was.
My connection type is pppoe with dhpd-pd
Marius.
/ip ipsec peers display problem for enc-algorithm. Peers configured with enc-algorithm=aes-128 are shown with enc-algorithm=aes-256We have released 6.34 version.
What's new in 6.34 (2016-Jan-29 10:25):
*) ipsec - allow my-id address specification in main mode;
*) ipsec - prioritize proposals;
*) ipsec - support multiple DH groups for phase 1;
Wonderful! Good job Mikrotik!What's new in 6.34.1 (2016-Feb-02 14:08):
*) interface - fixed stats that were 8x smaller;
*) traffic-monitor - fixed stats that were 8x smaller;
*) smips - properly detect smips boards for winbox & webfig.
It is cosmetic problem. Console shows aes-256 instead of aes-128. Winbox/webfig shows correct value. Will be fixed in one of the next rc builds/ip ipsec peers display problem for enc-algorithm. Peers configured with enc-algorithm=aes-128 are shown with enc-algorithm=aes-256We have released 6.34 version.
What's new in 6.34 (2016-Jan-29 10:25):
*) ipsec - allow my-id address specification in main mode;
*) ipsec - prioritize proposals;
*) ipsec - support multiple DH groups for phase 1;