Thank you very much for the report about Intel cards. We have found the issue, it will be fixed in the next RouterOS version.
VDR, what do you use for testing? bandwidth test?
Please provide us with full details of testing method.
Still can’t see SD card in RB593G with PXE config on it… i hope this post wont be deleted as my previous one was. You really need to use gloves when writing to Mikrotik.
keema,
Please make sure your SD card works (try another disk), try to format disk and then make support output file (send it to support).
Perhaps post was deleted, as it was not related to 6.23 release!
After upgrade one of my SXT lite 5 had CPU to 100% caused by ipsec and wireless rate jumping like crazy from one to another (2 or 3 changes per second).
I solved downgrading to 6.15 and disabling security packege.
ibm do you have any IPSec configuration on your SXT?
Have you tried to disable security package at 6.23?
Next time it would be great to get support output file from 6.23, when your router has problems.
I haven’t any ipsec configuration but I didn’t try to disable security package in 6.23 beacuse I thought that a downgrade would solve the problem.
I had 4 labs:
-
Linux server ---------------- (CCR1036) -------FTP Cat 6.E (0,3m) -------- (CCR1036) --------- FTP Cat 6.E (0,3m) ----------- Linux server.
Tested with iperf. -
CCR1006 -------------------- (CCR1036) -------FTP Cat 6.E (0,3m) -------- (CCR1036-2)
--------FTP Cat 6.E (0,3m) --------- Linux server
Tested with BT-TEST from CCR1006 to CCR1036-2. -
(CCR1036) -------FTP Cat 6.E (0,3m) -------- (CCR1036) --------- FTP Cat 6.E (0,3m) ----------- Linux server
Tested with BT-TEST from CCR1036 to CCR1036-2 -
(CCR1036) -------FTP Cat 6.E (0,3m) -------- (CCR1036) --------- FTP Cat 6.E (0,3m) ----------- Linux server (real traffic about 500 / 500 Mbit/s)
RouterOS v6.12:
— 10.200.0.1 ping statistics —
20000 packets transmitted, 20000 received, 0% packet loss, time 64966ms
rtt min/avg/max/mdev = 2.784/2.828/12.616/0.084 ms, pipe 2, ipg/ewma 3.248/2.855 ms
RouterOS v6.22:
— 10.200.0.1 ping statistics —
20000 packets transmitted, 19860 received, 0% packet loss, time 67536ms
rtt min/avg/max/mdev = 2.689/2.873/5.706/0.139 ms, ipg/ewma 3.377/2.825 ms
Packet loss occurs equally and according Router OS versions.
- The SD card is working with SD adapter in PC.
- My post was deleted because I said you should do the test yourselves instead of outsourcing test labs to users with no pay I may add.
keema, have you tried to format your disk and make support output file?
Currently this is a separate package and not included in the RouterOS bundle package. Currently it is working stable. If you are planning to develop a new CAPsMAN system I would suggest to use v2. Before deploying it check if the configuration is working ok. If you see some problems please email to support@mikrotik.com
Sergej
Is there any chance to fix problems with proxy cache … like discribed here :
http://forum.mikrotik.com/t/cache-hits-problem-on-6-x/78362/1
looks that proxy didnt mark cached files as dscp=4 ?
We have tested same kind of ping between two CCR devices in our lab and 20000 packets were exchanged without any problems.
In version 6.15 ethernet hardware queue was reduced and this might cause dropped packets while ping is not the only traffic going through device.
When you send icmp packets with size 65000, then 44 fragments are being sent to destination address and if one of them is lost then whole packet is being dropped.
Also when you send ping reply to source address and if there is no place in queue for 44 reply fragments, then packet will be dropped.
Hi dear Mikrotik team ,
When you are implement custom channel width on AC products ?
With this response, I can not satisfy. If I use the ping size of 45000, so the result is exactly the same !!!
Other test:
Ping from my linux server ---- 0,3 m CAT6 ----- CCR 1036 (NAT) -----0,3 m CAT6 -------- CCR 1036 (BGP) --------fiber ------- GW Linux.
Command:
ping -i 0,1 -s 45000 XXX.XXX.47.129 -c 1000
Traffic through CCR router:
rx-packets-per-second: 31 359
rx-bits-per-second: 314.9Mbps
tx-bits-per-second: 35.1Mbps
Result:
— XXX.XXX.47.129 ping statistics —
1000 packets transmitted, 957 received, 4% packet loss, time 6321ms
rtt min/avg/max/mdev = 4.994/5.668/17.363/0.817 ms, pipe 2, ipg/ewma 6.327/5.651 ms
Bill, nostradamus.
To solve the issue with Intel cards, please install the version from the link on your router,
http://www.mikrotik.com/download/share/routeros-x86-6.23.1.npk
Let us know about the results.
bax,
Thank you very much for the report!
We will try to fix the cache-hit DSCP issue in the next RouterOS version 6.24!
Liked 
Can you also check this ? http://forum.mikrotik.com/t/userman-https/83553/1
Broadcom NetXtreme II BCM5708S Gigabit Ethernet didn’t work in RouterOS 6.23. But in RouterOS 6.22 works fine. Why?
lemosh,
we are sorry for the incovenience caused by the following problem.
Please install MikroTik RouterOS 6.23.1 on your router,
http://forum.mikrotik.com/t/routeros-v6-23-1-special-release/83580/1
Let us know about the results!
maybe because it’s actually still NOT working as it should in 6.23 (and 6.23.1). I opened ticket 2014120966000348:
I’ve configured VRRP IPv6 on 2 routers in my lab on same ipv6 network with a global scope address on VRRP interface and it works in the first place but then after some interface down / up or disable / enable I get both VRRP nodes in MASTER and some log messages like this:
Router1# vrrp,warning vrrp1 received packet from fe80::d6ca:6dff:fe0e:9ae4 misconfigured IP addresses 2a00:f8c0:1000:9::190, fe80::200:5eff:fe00:202, fe80::200:5eff:fe00:202 != 2a00:f8c0:1000:9::190, fe80::200:5eff:fe00:202
Router2# vrrp,warning vrrp1 received packet from fe80::4e5e:cff:fe4e:684 misconfigured IP addresses 2a00:f8c0:1000:9::190, fe80::200:5eff:fe00:202 != 2a00:f8c0:1000:9::190, fe80::200:5eff:fe00:202, fe80::200:5eff:fe00:202
Also this “misconfigured IP addresses” message is then displayed on the VRRP interface in winbox and there is no way to clear this error, even disable / enable of the interface does not clear it and the interfaces stay in MASTER or sometimes the “backup” router is flapping between BACKUP and MASTER. only deleting the VRRP interface or rebooting both routers clears the error.
Looks like there is something totally wrong with link local address handling in VRRP as the link local is 2 times or even 3 times in the announcement, as far I can tell from that log message. or maybe it’s still some keepalive issue and the “misconfigured IP addresses” is only a side effect.
really, they said it’s fixed in 6.23 and I mean it’s somehow working slightly better, but still totally unusable. I really wonder if they tested this at all after “fixing” it. 