I think that someone else got the problem with Mangle - connection mark.I have not encountered the Mangle bug even.
You and TKIT are two people that have seen it so farI think that someone else got the problem with Mangle - connection mark.I have not encountered the Mangle bug even.
Please, do not make such imprecise posts anymore, i got my coffee cold while jumping to check all the routers. So far all my connection marks for routing marks and packet marks are working fine, i will keep looking, but, looks to me ether it is configuration error, or specific complex situation is necessary to repeat the problem.Mangle & QT from ver 4.11 aren't working on 5.0 rc1
Could you be more specific?1. found some bug with RPS - recomended to disable RPS in this version
2.And RC1 still has bug with torch on intel ethernet.
Anybody check if stability of 802.11n wireless is better?
RB433AH on Ver 4.11 everything works fine. On 5.0 RC1 mangle don't "catch" traffic. Traffic on WAN interface goes 100%, so I'm checking QT and there's no treffic there. I've limits for clients in forward(4 mangle entries, & 2 QT entries for each user) and QoS in prerouting. I didn't make new config. I've just upgraded from 4.11. I checked mark names in console, and everything seemed to be ok. Do I have to make new config for 5.0RC1 or post mangle & QT listenings here? I go back to 4.11 and everything is OK.Can you give us all the details?Mangle & QT from ver 4.11 aren't working on 5.0 rc1
It closes the login, and shows blank webfig page.weconfig to choose to cancel at the time of login page is in a loop.
I upgraded one 450G as well. It works. I have L3 on 1, 2 and 5 and 3 &4 are switch slaves to 2. It has OpenVPN that is working as well. Mangle connection marking as well. This and that...upgraded a rb450g and can now only get ethernet link on port1, not on rest of the ports.
Do you run latest BIOS?here is my test result:
Server: HP DL360 G6
CPU: Intel Xeon E5620 2.40 GHz Quad core
Traffic: 250Mb/s IN / 250Mb/s OUT
Anybody check if stability of 802.11n wireless is better?
How many queue should be?And another bug - on x86 multicore cpu and intel ethernet with many queue when run "profile" - router reboot. Already send supout
how did u checked how many harware queues where been in use?its not a shaper queue, i mean ethernet hardware queue on intel chip 82576 or 82575
Shaper queue (simple queue or queue tree) works fine on v5RC1, tested on 1300 simple queue and queue tree
He wrote:how did u checked how many harware queues where been in use?
Not hardware buffer queues.Shaper queue (simple queue or queue tree) works fine on v5RC1, tested on 1300 simple queue and queue tree
??? i don't have dst-limit sirFor everybody that has problems with firewall in RC1, try to disable all rules that have dst-limit setting
On a rb711 as 801.11 client connected (wireless) to a rb333 running v4.11 these data are to be seen in winbox of the rb711.is the ccq and tx signal strenth suppose to be missing in winbox
Yes, I observed this too. It's keeping me from testing nv2 as I can't get a sense of CCQ and TX power relative to normal nstreme.ccq and tx-signal isn't showinf currently for Nv2 links.
and currently Nv2 doesn't support short guard interval and that is why the max data-rate is 270Mbps
:if ([/ping 172.17.255.2 count=4]>1) do={:foreach i in=[/ppp secret find disabled=no comment="NET47 Export"] do={/ppp secret disable $i}} else={:foreach j in=[/ppp secret find disabled=yes comment="NET47 Export"] do={/ppp secret enable $j}}
bummer... OK well at least i know its not just me!Ports 11, 12 and 13 on RB1100s were giving me all kinds of grief even on 4.11 so I pretty much stopped using them completely.
For everybody that has problems with firewall in RC1, try to disable all rules that have dst-limit setting
on what arch this happens, my test ppc router took "ssh test+c160w@hs -i id_dsa" command happilyWould like to report a bug with ssh.
Since the update was made to disable ssh password auth to accounts with ssh-keys, I am now unable to use those ssh keys
to login with extended console params added to username as in : admin+c160w@<router-ip>.
I can live with the password disabling feature, but this method greatly simplifies parsing the output in our external scripting.
Please consider looking into this?
Thanks,
ReenignE
This is happening on mipsbe: RB433.on what arch this happens, my test ppc router took "ssh test+c160w@hs -i id_dsa" command happilyWould like to report a bug with ssh.
Since the update was made to disable ssh password auth to accounts with ssh-keys, I am now unable to use those ssh keys
to login with extended console params added to username as in : admin+c160w@<router-ip>.
I can live with the password disabling feature, but this method greatly simplifies parsing the output in our external scripting.
Please consider looking into this?
Thanks,
ReenignE
Sorry, I just realized these were at beta6 and not rc1. When I upgraded the ssh issue went away. Thanks for checking, though.This is happening on mipsbe: RB433.on what arch this happens, my test ppc router took "ssh test+c160w@hs -i id_dsa" command happilyWould like to report a bug with ssh.
Since the update was made to disable ssh password auth to accounts with ssh-keys, I am now unable to use those ssh keys
to login with extended console params added to username as in : admin+c160w@<router-ip>.
I can live with the password disabling feature, but this method greatly simplifies parsing the output in our external scripting.
Please consider looking into this?
Thanks,
ReenignE
/system resource print output is:
uptime: 1d3h36m51s
version: "5.0beta6"
free-memory: 50332KiB
total-memory: 62252KiB
cpu: "MIPS 24Kc V7.4"
cpu-count: 1
cpu-frequency: 300MHz
cpu-load: 42%
free-hdd-space: 30888KiB
total-hdd-space: 61440KiB
write-sect-since-reboot: 62896
write-sect-total: 6841782
bad-blocks: 0%
architecture-name: "mipsbe"
board-name: "RB433"
platform: "MikroTik"
Thanks,
ReenignE
Sorry for the late reply -- it was a Motorola DOCSIS 3.0 Cable modem. Can't remember the model off hand. I was using ether13 as the WAN port for the router.wildbill442, what device is connected to ether13 when these problems occur?