Is there any way available on ROS to route IPv4 traffic over IPv6 tunnels? i.e. EoIPv6??With latest beta versions I don't see any problems routing IPv6 traffic over ppp tunnels. If you have any problems please describe in details.
Can Mikrotik do this?no bgp enforce-first-as
no bgp enforce-first-as
Guess that was misquoted...I don't know what you can do...I also migrated from 3.6 --> 4.0 beta...
Can I turn off those resources of IP175D to make it equal to IP175C through this menu?*) added support for ethernet switch configuration in WinBox;
Lets hope they think the same./system hardware set this-crazy-feature-enabled=no
*) fixed problem - SFQ queues did not work on interfaces (wireless) if none
of simple or tree queues were added;
YES, this happen for ages, very randomly and very often./system scheduler
add comment="" disabled=no interval=1d name=backup on-event=backup start-date=jan/01/1970 start-time=00:00:00
Ive seen it occasionally too...We have witnessed address-list entries that are ignored completely until you simply disable / enable them.
I see absolutely no problem too, with ROS 3.14rc1 while NOT using pppoe server.What is this? I'm testing 3.14rc1 in 3 routers (x86 and RB's) and no problem until now.
"/ip firewall mangle disable 0 "
*worship to MT**) console - added login parameters, passed as part of login name, after '+';
can be used to disable colors (+c) and terminal autodetection (+t), e.g.
"admin+ct";
And this mean 600+ pppoe sessions running ROS 3.0rc13? IF so, guess you could post details about hardware, etc of this pppoe yours?We didn't have this kind of problems with high load setups: 600+ pppoe
Just problem with packet loss for traffic going through this pppoe router.
Yes, MT ROS 2.9.x does not recognize the onboard lan adapter on that GZIS motherboard, but ROS 3.0 do.Do you maybe have integrated motherboard lan card enabled on this pppoe machine which mikrotik 2.9.x doesn't see?
Oh, how sad... Cannot implement a dynamic QoS script based on clients latency in a wireless AP. Too bad.only thing that matters is - does it fail or not.
Whats the red string about?Don't use rc12 because of upgrade of x86 only.
/interface wireless set wlan1 default-authentication=no
*cheers*well there is nothing special mentioned. most of the stuff is corrected in v3 and the winbox finding can be solved by using a tunnel. of course we will improve these things
I second that also... thxCan you provide a bit of a description as to what the "Hardware Retries" feature does? I have a few devices that hopefully will benefit from this fix, and I would just like to understand a bit more about what is actually happening with it.