This change was in RC for some time already!.*) partitions - fixed crash on repartition when there is not enough free space;
Well - that would explain my bricked 2011 when I tried to repartition to remove a DD-WRT image that I wasn't using.....
If only I'd waited two more days to mess with it.
/ping thangorodrim.benesovi.eu
invalid value for argument address:
invalid value of mac-address, mac address required
invalid value for argument ipv6-address
failure: dns name exists, but no appropriate record
/interface eoip> add remote-address=2a00:1028:8386:8c5e::1 tunnel-id=0
failure: 2a00:1028:8386:8c5e::1 is not a valid dns name
same hereHello,
I have three issues with 6.36 and 6.36.2
1) Winbox disconnects after a random interval
2) Can't ping hostname with aaaa record, for example:3) Can't add EoIP tunnel with IPv6 remote endpoint:Code: Select all/ping thangorodrim.benesovi.eu invalid value for argument address: invalid value of mac-address, mac address required invalid value for argument ipv6-address failure: dns name exists, but no appropriate record
This works on 6.34.6Code: Select all/interface eoip> add remote-address=2a00:1028:8386:8c5e::1 tunnel-id=0 failure: 2a00:1028:8386:8c5e::1 is not a valid dns name
[admin@MikroTik-Amir] > ping ipv6.mikrotikfa.com
invalid value for argument address:
invalid value of mac-address, mac address required
invalid value for argument ipv6-address
failure: dns name exists, but no appropriate record
What sense does it have?Yes, .1 release was released only for 9 minutes.
Hum, the issue seems to have resolved itself. An old empty address-list from several months ago started showing up in the drop downs. It disappeared right after I generated a supout.rif. Oh well, it's ok now.proximus - Please write to support@mikrotik.com and report this issue. I am not being able to reproduce issue like this right away.
.
Hi,benesm1 - Winbox disconnects will be fixed in upcoming Winbox versions.
105547111 - Please write to support@mikrotik.com and report this issue. Tell us exactly how did you perform an upgrade step-by-step.
jarda, micromaxi - We were preparing 6.36.1 for release, had some more fixes already, added them to version, tested and released 6.36.2. 6.36.1 was released only to save it in archive.
proximus - Please write to support@mikrotik.com and report this issue. I am not being able to reproduce issue like this right away.
benesm1, irghost, ZeroByte - Ping issue is reported to our developers. However it is not related to 6.36.2 RouterOS version.
as it was said, just add eoipv6 tunnel, not eoip:and what about the IPv6 EoIP?
[admin@TestPlace] /interface eoipv6> add remote-address=2a00:1028:8386:8c5e::1 tunnel-id=0
I am not the only one with OCD!6.36.1 was released only to save it in archive.
Ha!as it was said, just add eoipv6 tunnel, not eoip:and what about the IPv6 EoIP?Code: Select all[admin@TestPlace] /interface eoipv6> add remote-address=2a00:1028:8386:8c5e::1 tunnel-id=0
Hi Strods - Donebenesm1 - Winbox disconnects will be fixed in upcoming Winbox versions.
105547111 - Please write to support@mikrotik.com and report this issue. Tell us exactly how did you perform an upgrade step-by-step.
jarda, micromaxi - We were preparing 6.36.1 for release, had some more fixes already, added them to version, tested and released 6.36.2. 6.36.1 was released only to save it in archive.
proximus - Please write to support@mikrotik.com and report this issue. I am not being able to reproduce issue like this right away.
benesm1, irghost, ZeroByte - Ping issue is reported to our developers. However it is not related to 6.36.2 RouterOS version.
/sys pack up up
This will occur if :RouterOS X86: Show R before interface name of interface list but this interface not connected with any device, why?
Does it work when you disable fastpath/fasttrack?Prerouting mangle broken in 6.36 is still broken for me.
RouterOS X86: Show R before interface name of interface list but this interface not connected with any device, why?
/interface ethernet set etherX disable-running-check=no
Well, it works that way. But CPU usage has grown significantly.Does it work when you disable fastpath/fasttrack?Prerouting mangle broken in 6.36 is still broken for me.
This interface is not a Master port and I have not configure it as a bridge interface (it is unused interface), I think maybe it is a bug for x86, so pl check it thoroughly.This will occur if :RouterOS X86: Show R before interface name of interface list but this interface not connected with any device, why?
1. the interface is a "Master Port" for another interface that is connected to a device,
Or
2. If the interface is a Bridge Interface
Sounds reasonable, because I have Dual WAN setup and mangles belong to second WAN interface.Mangle will not work if FastTrack is enabled. It also means that policy routing will not work. Maybe in past you had FastTrack and everything was working correctly if some interface did not support FastTrack on older version. If we add support to, for example, PPPoE and you upgrade device ,then FastTrack will start to work and firewall will not.
Was this all working fine before you upgraded? Have you tried to downgrade and check if it works again after that? Which version is it working on?I'm not sure if this was fixed in this release, but here is a (potential) bug I found in 6.36
I've noticed a problem with the RB2011 series routers. I offer a hosted VoIP solution to my customers.
All my customers have a Mikrotik router and cisco phones in their LAN
I vlan and prioritize all phones and voip protocols. All my customers are setup the same way, the only difference is the model mikrotik I install for them.
I've already had 3 customers with the same exact problem. Phones would drop connections to the VoIP server, reconnect and drop again.
I checked everything, dropped packets, TCP timeouts, UDP Timeouts, jitter, latency, server logs, error logs…. everything checked out fine….
I noticed the only customers that were having this problem were customers with an RB2011 on ver 6.36 (yes I made sure the routerboard version was also up to date)
How did I fix the problem?? I changed out their mikrotik rb2011 with a mikrotik RB951Ui-2HnD or Mikrotik RB750r2, anything other than the 2011 worked immediately after installing it. The phones have been rock solid and working flawlessly, like all my other customers.
I saw there is a Mikrotik update today, one of the fixes is IPV6 connection tracking, All my customers are on ipv4.
Any thoughts?
You should maybe move that wiki page to "Manual:Fasttrack" instead, the multiple instances of the word "wiki" looks silly. Or maybe "Manual:Firewall/Fasttrack" would be better?
Hm, that's quiet annoying. It was stable before... Is there any workaround?benesm1 - Winbox disconnects will be fixed in upcoming Winbox versions.
have you read my answer? http://forum.mikrotik.com/viewtopic.php ... 40#p554440This interface is not a Master port and I have not configure it as a bridge interface (it is unused interface), I think maybe it is a bug for x86, so pl check it thoroughly.
Please not I have not find this problem in router board with same ROS v6.36.2
I think this is a cosmetic issue./routing ospf interface
add network-type=broadcast passive=yes
Thank you Sir, your command is working, I have apply your command to all interface of my routerhave you read my answer? http://forum.mikrotik.com/viewtopic.php ... 40#p554440This interface is not a Master port and I have not configure it as a bridge interface (it is unused interface), I think maybe it is a bug for x86, so pl check it thoroughly.
Please not I have not find this problem in router board with same ROS v6.36.2
on routerboards this parameter does not exist and works as it is set to 'no'
Hey Normis,Not sure how that happened, it was a mistake. Now it will be here:
http://wiki.mikrotik.com/wiki/Manual:IP/Fasttrack
If there are specific IPv6 related interfaces to be created, why are there no tabs on the interface window for these IPv6 tunnels?Ha!as it was said, just add eoipv6 tunnel, not eoip:and what about the IPv6 EoIP?Code: Select all[admin@TestPlace] /interface eoipv6> add remote-address=2a00:1028:8386:8c5e::1 tunnel-id=0
thank you, overlooked that. Works like a charm now.
v6.36.2 /wireless access-list - mac blocking not working. please resolve issue ty
well, this part should be fixed somehow you may write to support@ with this inconsistencyIf there are specific IPv6 related interfaces to be created, why are there no tabs on the interface window for these IPv6 tunnels?
If you would go the EoIP tunnel tab on the interfaces window, you could only add 'normal' IPv4 tunnels, no IPv6. The only way to add such IPv6 tunnel is via the main interface tab