upgrading from v5

RouterOS General
1

can anyone point me where can i find a complete list what is critically changed from v5 to v6? because i’ve just found out v6 drastic change on simple queue where i have to re-organize the queues now :frowning:

what i do notice, something like:

/queue simple target-addresses=192.168.0.2/24 interface=ether1>>local queue=default-small/default-small limit-at=0/0 max-limit=256k/512k

is automatically transformed into:

/queue simple target=192.168.0.2/24,ether1 queue=default-small/default-small limit-at=0/0 max-limit=256k/512k

now, this cause a massive problem, because the new one now not only queueing a target(192.168.0.2), instead, it queues everything on ether2.

i also have just found out that:

/ip address address=192.168.0.253/24 interface=ether1
/ip firewall mangle chain=prerouting src-address=192.168.0.0/24 new-routing-mark=internet1 passthrough=no

on routerOS v5, this rule is OK when ping to 192.168.0.253, but on v6, it is RTO because the icmp is probably routed by force to the marked route even if the addressed ping is local ip.

2

There is a page on the wiki that lists all of the 5.x->6.x changes.

http://wiki.mikrotik.com/wiki/Manual:What's_New_In_v6

There were changes to the packet flow as well that you may be hitting.

http://wiki.mikrotik.com/wiki/Manual:Packet_Flow#Changes_in_RouterOS_v6
http://wiki.mikrotik.com/wiki/Manual:Packet_Flow_v6

3

help.

90    name="NEW PC-01 Games" target=192.168.0.181/32 parent=none packet-marks=games priority=8/8 queue=default/default limit-at=384k/384k max-limit=512k/512k burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s 

91    name="NEW PC-02 Games" target=192.168.0.182/32 parent=none packet-marks=games priority=8/8 queue=default/default limit-at=384k/384k max-limit=512k/512k burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s

why is it only 1 work? shouldn’t both working because they have different target? it is used to be working on v5 :frowning:

4

I assume its rule 90 that works and 91 doesn’t?

Did you look at how the packet flows change with v6? Queues now happen after source-nat. Do you do any NAT with these addresses? Also are you setting up a list of /32s to divide up bandwidth? Have you looked into PCQ?

5

it works now, but i still fear some are still messed :frowning:
so, i’m assuming:

/queue simple target-addresses=192.168.0.2/32 interface=ether1>>local queue=default-small/default-small limit-at=0/0 max-limit=256k/512k

can be replaced on v6 with:

/queue simple target="ether1>>local" name="ethernet1"
/queue simple target=192.168.0.2/32 name="queue1" queue=default-small/default-small limit-at=0/0 max-limit=256k/512k parent="ethernet1"

because that’s what i did on rules 90-91 and many others.

i already open the wiki you gave, i’m still trying to chew on it. i’m confused, does that mean, i have to switch my prerouting mangle into postrouting mangle for mark-packet action?

6

Prerouting is still in the same place. Just post routing is different.

I haven’t used simple queues that much and I have really only ever used an interface as a target with packet marking. I have yet to target an interface+IP range.

If your setting up individual queues for customer classes you should look into PCQ it will simplify your config greatly.

7

i have used PCQ before, it is great, but it takes time to figure out which client is already on full queue. on simple and single queue for every client, i can easily view which client is full by seeing the queue list