6.3 Released

[elgrandiegote]

@Rivera

*) pptp, l2tp, sstp - allow to specify server via dns name;
Please add OpenVPN to that list. Seriously, that’s just unfair for users.
pptp - insecure.
sstp - supported only in windows.
l2tp - requires ipsec+l2tp combo, hard to configure by user.

+1

[npero]

@elgrandiegote

@Rivera

*) pptp, l2tp, sstp - allow to specify server via dns name;
Please add OpenVPN to that list. Seriously, that’s just unfair for users.
pptp - insecure.
sstp - supported only in windows.
l2tp - requires ipsec+l2tp combo, hard to configure by user.

+1

+1

[ayufan]

@Rivera

Ubuntu/Mint
NM in ubuntu lacks L2TP/IPsec support.

https://launchpad.net/~seriy-pr/+archive/network-manager-l2tp

[boen_robot]

@aleprolit

manager: command /tool user-manager user create-and-activate-profile not work with argument “user”,and work only with argument “numbers”. For example in script:

 
   $addRequest = new Request('/tool user-manager user create-and-activate-profile');
    $addRequest->setArgument('customer','gsm');
//-->    $addRequest->setArgument('user',$from);
    $addRequest->setArgument('numbers',$userId);
    $addRequest->setArgument('profile',$profile);
    $client->sendSync($addRequest);

Has it also been renamed from terminal (I haven’t upgraded just yet myself…)? If so, the API behavior is to be expected, and the rename itself - typical, kind’a (sadly). But look at it from the bright side - the rename to “numbers” suggests that you can now target multiple users, whereas you could previously target just one user.

If terminal still shows it as “” - yeah, that’s a ROS bug all right.

[richardtrip]

@normis

l2tp - hard to configure by user.

You mean OpenVPN is easier to configure by user? Personally, I strongly disagree.

For sure it is easier to import one config file on android/ios/Windows/Mac. But we all know the problems with the mikrotik implementation (no udp/lzo).

Sent from my A500 using Tapatalk 4

[ddejager]

After upgrading from 6.0 to 6.2 all my INPUT firewall rules disappeared. Is this fixed in 6.3?

Also after upgrading from 6.0 to 6.2 clicking on quickset caused winbox to close immediately. Is this fixed in 6.3?

My hardware is RB2011UAS-2HnD.

[roneyeduardo]

*) ppp, hotspot - added ability to specify where to insert rate limiting queue,
it’s parent and type;

Can we do that via Radius attributes? How?

[theprism]

@normis

IPsec is working in v6.1 and v6.2, what did you mean by this?

In v6.1 the following IPSEC problem existed:
Windows 7 ← L2TP/IPSEC → Mikrotik 6.1 stopped working.
L2TP was passing OK but when reached IPSEC portion it compains in logs about payload and triming.

Was this fixed?

Thanks,
the_prism

[Sandor1k]

I have a problem with the creation of backups. When you click backup of the entire disk space scores.

[TerAnYu]

igmp-proxy, the image breaks down at the incoming stream over 10Mbps.
PIM is not possible to use it to check.

[MrYan]

@ddejager

After upgrading from 6.0 to 6.2 all my INPUT firewall rules disappeared. Is this fixed in 6.3?

I had this also (from 6.1 to 6.2). When I upgraded to 6.3 the rules remained in place.


Matt.

[infused]

Finally upgraded my core CCR from RC13 to 6.3. Runs much smoother. Cpu seems to be better too.

I don’t run BGP or IPSec, but use most other features.

Mikrotik: Is there a layout of what services/features use what cpus?

[infused]

Actually winbox bug in 6.3 on ccr.

Use safe mode and turn it off. I go to exit winbox and it says im in safe mode, if I quit, changes will be undone.

[pcunite]

@infused

Mikrotik: Is there a layout of what services/features use what cpus?

Tools / Profile

[infused]

@pcunite

@infused

Mikrotik: Is there a layout of what services/features use what cpus?

Tools / Profile

Doesn’t show you what cpus each service is working across though.

[theprism]

@theprism

@normis

IPsec is working in v6.1 and v6.2, what did you mean by this?

In v6.1 the following IPSEC problem existed:
Windows 7 ← L2TP/IPSEC → Mikrotik 6.1 stopped working.
L2TP was passing OK but when reached IPSEC portion it compains in logs about payload and triming.

Was this fixed?

Thanks,
the_prism

Normis, can you confirm that this was fixed and Windows 7 ← L2TP/IPSEC → Mikrotik 6.1 works fine?

Thanks,

T.P.

[normis]

@theprism

@theprism

@normis

IPsec is working in v6.1 and v6.2, what did you mean by this?

In v6.1 the following IPSEC problem existed:
Windows 7 ← L2TP/IPSEC → Mikrotik 6.1 stopped working.
L2TP was passing OK but when reached IPSEC portion it compains in logs about payload and triming.

Was this fixed?

Thanks,
the_prism

Normis, can you confirm that this was fixed and Windows 7 ← L2TP/IPSEC → Mikrotik 6.1 works fine?

Thanks,

T.P.

Please tell me your Mikrotik Support ticket number, and I will check status.

[Supportkavos]

After upgrade to 6.3 cannot connect with openvpn to 6.2. Tls error. Mtk to mtk.

[guilhermeramires]

You need to set SRC-ADDRESS if you want to reach the same result.

@CStrauch

I found a problem with the new traceroute tool. My backbone provider uses an MPLS network with private addresses and this means I can’t ‘see’ the network from another router other than the border router. The new ‘mtr’ behaviour is stopping the tracing after 3 lost hops.

Thanks in advance!

Carlos Strauch

[guilhermeramires]

ARP=reply-only is not working on CCRs.

X86, MIPSBE and PPC is working fine.