It doesn’t seem right to be running docker images on a router. It seems like this is getting away from what I would consider a professional router and more so a home type router. All of these additions are just adding more things that could cause security issues or stability issues. Why aren’t these add-on packages? Will there be RouterOS 7.x without all of these additional addons? If not, I may look elsewhere for future router deployments or upgrades to current sites.
In case someone still doesn’t understand the problem. I won’t bother with downgrading to 6.x for some nice copy/paste comparison, so you’ll just need to trust me on the fact, that this will work perfectly on 6.x - but you (mikrotik) yourself confirmed, that you’ve repeated the problem on your side, and you’ve fixed this in one of 6.49 betas so are you not fixing this on purpose in ROS7 or what gives?
> /system/routerboard/print
routerboard: yes
model: RB4011iGS+
revision: r2
serial-number: [redacted]
firmware-type: al2
factory-firmware: 6.45.9
current-firmware: 7.1rc3
upgrade-firmware: 7.1rc3
> /ip address/print
Columns: ADDRESS, NETWORK, INTERFACE
# ADDRESS NETWORK INTERFACE
0 10.248.1.82/30 10.248.1.80 sfp-sfpplus1
> /interface/ethernet/print detail
(...)
10 R name="sfp-sfpplus1" default-name="sfp-sfpplus1" mtu=1500 l2mtu=1500 mac-address=[redacted] orig-mac-address=[redacted] arp=enabled arp-timeout=auto loop-protect=default loop-protect-status=off loop-protect-send-interval=5s
loop-protect-disable-time=5m auto-negotiation=no advertise="" full-duplex=yes tx-flow-control=off rx-flow-control=off speed=1Gbps bandwidth=unlimited/unlimited sfp-rate-select=high fec-mode=auto sfp-shutdown-temperature=95C
> /ping 10.248.1.81 size=1500 do-not-fragment
SEQ HOST SIZE TTL TIME STATUS
0 10.248.1.81 1500 64 155us
1 10.248.1.81 1500 64 153us
sent=2 received=2 packet-loss=0% min-rtt=153us avg-rtt=154us max-rtt=155us
> /ping 10.248.1.81 size=1501 do-not-fragment
SEQ HOST SIZE TTL TIME STATUS
0 packet too large and cannot be fragmented
1 packet too large and cannot be fragmented
> /interface/ethernet/set sfp-sfpplus1 l2mtu=4090 mtu=4000
> /ping 10.248.1.81 size=1500 do-not-fragment
SEQ HOST SIZE TTL TIME STATUS
0 10.248.1.81 1500 64 157us
1 10.248.1.81 1500 64 152us
sent=2 received=2 packet-loss=0% min-rtt=152us avg-rtt=154us max-rtt=157us
/ip/address> /ping 10.248.1.81 size=1501 do-not-fragment
SEQ HOST SIZE TTL TIME STATUS
0 10.248.1.81 timeout
1 10.248.1.81 timeout
sent=2 received=0 packet-loss=100%
It nice all those outboard motors however I agree that the priority should be just have a working v7. Till now every version of v7 was not usable for me and even caused huge problems and causing stress.
A fallback to v6 was also blocked due to that backup being broken and you are thinking is all worth.
I’m fully aware of this, and I have scripts running on RB4011s that workaround this bug on each reboot. I even reported it here: http://forum.mikrotik.com/t/rb4011-l2mtu-bug/141030/1 and to support. I probably might’ve had something to do with this finally getting fixed in 6.49 beta, but who cares about the credit – I just want this bug GONE.
The only actions they have right now are masquerade, dst-nat, and redirect. Those are useful but what most people want to be able to Network Prefix Translation, which means using netmap, since the main NPT support in Linux does not support connection tracking, and netmap does basically the same thing but does support connection tracking.
Hey MikroTik, how to use the cake-autorate-ingress flag of cake? cake qdisc defaults to egress according to linux docs. No way to tell it, that it is ingress instead. So if you set cake-bandwidth to 50mbit and enable autoingress: it works for some minutes to finally reduce to 1mbit approx. I assume it is due to the missing possibility to set ingress/egress. Cake wont autorate on egress and finally autorates something very low.