SSTP: sstp-client for linux not working properly?sstp - supported only in windows.
SSTP: sstp-client for linux not working properly?sstp - supported only in windows.
IPSec/L2TP is fairly easy to configure. You have built-in (or easily installable) support for all the platforms (ex. Windows Phone). We have users using: OSX, Windows 7 and 8, Ubuntu/Mint, Android and iOS. All of them can use graphical tools to connect to VPN server.4) Easy to configure. Not IPSec/L2TP, because installing strong/openswan and writing all configs... doh.
Plain policy-based IPsec. With all the recently added features to support road-warrior configurations this is now my #1 choice to be used with Mikrotik.If you so strong against OpenVPN, please provide me with protocol that will be:
IPsec is working in v6.1 and v6.2, what did you mean by this?Yes, but IPSEC was not working well in 6.1 and 6.2. Were all issues with it fixed in 6.3?
Is it working?
Thanks,
T.P.
It was working just fine for me in 6.2, and works fine in 6.3 now. The only problem is that SA expiration time is misreported in WinBox and WebFig (see 2 posts above), but that is definitely not a show-stopper.Yes, but IPSEC was not working well in 6.1 and 6.2. Were all issues with it fixed in 6.3?
Is it working?
This will be fixed in v6.4The problem with both WinBox and WebFig misreporting the IPsec SA expiration time is not fixed yet in 6.3. The reported value is a) incorrect and b) counts up (but should count down). Everything is fine on console, the "/ip ipsec installed-sa print" command reports correct value.
Original report is here: http://forum.mikrotik.com/viewtopic.php ... 50#p381561
+1*) 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*) 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.
https://launchpad.net/~seriy-pr/+archiv ... nager-l2tp> Ubuntu/Mint
NM in ubuntu lacks L2TP/IPsec support.
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.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:Code: Select all$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);
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).You mean OpenVPN is easier to configure by user? Personally, I strongly disagree.l2tp - hard to configure by user.
Can we do that via Radius attributes? How?*) ppp, hotspot - added ability to specify where to insert rate limiting queue,
it's parent and type;
In v6.1 the following IPSEC problem existed:IPsec is working in v6.1 and v6.2, what did you mean by this?
I had this also (from 6.1 to 6.2). When I upgraded to 6.3 the rules remained in place.After upgrading from 6.0 to 6.2 all my INPUT firewall rules disappeared. Is this fixed in 6.3?
Tools / ProfileMikrotik: Is there a layout of what services/features use what cpus?
Doesn't show you what cpus each service is working across though.Tools / ProfileMikrotik: Is there a layout of what services/features use what cpus?
Normis, can you confirm that this was fixed and Windows 7 <- L2TP/IPSEC -> Mikrotik 6.1 works fine?In v6.1 the following IPSEC problem existed:IPsec is working in v6.1 and v6.2, what did you mean by this?
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
Please tell me your Mikrotik Support ticket number, and I will check status.Normis, can you confirm that this was fixed and Windows 7 <- L2TP/IPSEC -> Mikrotik 6.1 works fine?In v6.1 the following IPSEC problem existed:IPsec is working in v6.1 and v6.2, what did you mean by this?
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
Thanks,
T.P.
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
/file remove email
/system backup save name=email
/tool e-mail send server=173.194.70.16 port=587 user=me@gmail.com password=mypass start-tls=yes to=me@gmail.com from=Router subject=Backup body="copy config router" file=email.backup
I don't have any ticket number.Please tell me your Mikrotik Support ticket number, and I will check status.Normis, can you confirm that this was fixed and Windows 7 <- L2TP/IPSEC -> Mikrotik 6.1 works fine?
Thanks,
T.P.
This is a community forum. Community members can't and don't fix bugs. If you wish a problem to be addressed, you Must contact support. Posting here doesn't guarantee that a member of MikroTik support will read the post.I don't have any ticket number.Please tell me your Mikrotik Support ticket number, and I will check status.Normis, can you confirm that this was fixed and Windows 7 <- L2TP/IPSEC -> Mikrotik 6.1 works fine?
Thanks,
T.P.
I mentioned about this here http://forum.mikrotik.com/viewtopic.php ... 50#p373740 and here http://forum.mikrotik.com/viewtopic.php ... 50#p373772
Broken multiple Paste comands in v6.3 CCR (in v6.2 all works fine)
...
Paste in terminal and get the error....Code: Select all[admin@Mikrotik] > /interface vlan add arp=reply-only interface=ether3 name=TEST vlan-id=3000 [admin@Mikrotik] > /ip address add address=10.250.255.1/24 interface=TEST [admin@Mikrotik] > /ip pool add name=pool_TEST ranges=10.250.255.2-10.250.255.254 [admin@Mikrotik] > /ip dhcp-server add add-arp=yes address-pool=pool_TEST disabled=no interface=TEST lease-time=1h name=DHCP_TEST input does not match any value of interface
These problems are related.Hi.
I upgrade 951G-2HnD to 6.3.
Function "Reset Configuration" is broken.
Default configuration not apply after reboot.
In 6.2 it work.
/interface {
set ether6 name=ether6-master-local;
set ether7 name=ether7-slave-local;
set ether8 name=ether8-slave-local;
set ether9 name=ether9-slave-local;
set ether10 name=ether10-slave-local;
}
/interface ethernet {
set ether7-slave-local master-port=ether6-master-local;
set ether8-slave-local master-port=ether6-master-local;
set ether9-slave-local master-port=ether6-master-local;
set ether10-slave-local master-port=ether6-master-local;
}
input does not match any value of master-port
There are still menu bugs but I confirm this in performance 6.3 run much much betterFinally 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?
Well, this is a bug that wasn't present in previous versions. It appeared starting with v6.1 and since I never got any answers if it was fixed or no in v6.2, and now v6.3, I keep asking. No time to upgrade and test and revert back if the problem persists.This is a community forum. Community members can't and don't fix bugs. If you wish a problem to be addressed, you Must contact support. Posting here doesn't guarantee that a member of MikroTik support will read the post.I don't have any ticket number.
I mentioned about this here http://forum.mikrotik.com/viewtopic.php ... 50#p373740 and here http://forum.mikrotik.com/viewtopic.php ... 50#p373772
I've noticed something similar in API. (not sure if issue was on 5.25 as I never used so many commands on ROS5)None of my scripts work anymore, it's almost as if MikroTik invented asynchronous command execution where the second command is executed before the result from the first one is commited.
Have you tried to simply get the response from one "add" command before doing the next?I've noticed something similar in API. (not sure if issue was on 5.25 as I never used so many commands on ROS5)None of my scripts work anymore, it's almost as if MikroTik invented asynchronous command execution where the second command is executed before the result from the first one is commited.
If I send to many API commands directly after the other, over same API connection, some commands are just dropped. E.g. making groups of 8 simple queues, with a parent, if I pump them to fast, then sometimes up to 3 of some of the group's 8 would be 'lost'/not there. If I put in a 40ms delay between commands, it runs reliably, but painfully slow for a few thousand entries.
Regards
Ekkas
I actually wait for !done after each command. I must also say it's my first multi-core router, don't know if that could be related but it's not a big issue. I am updating my app to be more intelligent in what to update, so less updates with proper pauses will be workable. Sometimes it will run thousands without problem, so it's not like it a consistent issue, but I cannot take a chance so I'll rather run slower and know all scripts are applied correctly.Then again, this may make the app slower due to the multiple remote calls... so I guess if you simply "fragment" your receives - make it send,send,send,receive, then again send,send,send,receive, etc. you might get best results.
Just for Beeline.All other (i.e. NORMAL) ISPs use PPPoE or IPoE.*) pptp, l2tp, sstp - allow to specify server via dns name;
This is very very important small feature for my region- lets say goodbye to some significant scripting