Good to see ospf issue to be resolved. Also wireguard is a much awaited feature. Thanks!RouterOS version 7.1beta2 has been released in public "development" channel!
What's new in 7.1beta2 (2020-Aug-21 12:29):
!) added "bgp-network" output filter flag;
!) added bonding interface support for Layer3 hardware offloading;
!) added IPv6 nexthop support for IPv4 routes;
!) added Layer3 hardware offloading support for CRS309-1G-8S+IN, CRS312-4C+8XG-RM, CRS326-24S+2Q+RM and CRS354-48G-4S+2Q+RM;
!) added WireGuard support;
*) disk - improved external disk read/write speeds;
*) ospf - fixed point to point routes becoming inactive;
*) route - fixed source address selection of outgoing packets;
*) other minor fixes and improvements;
All released RouterOS v7 changelogs are available here:
https://mikrotik.com/download/changelog ... lease-tree
How to report RouterOS v7 bugs:
viewtopic.php?f=1&t=152006
It does routing at wirespeed, in all ports. There are several constraints, and a limit of 4096 connections, if I'm not wrong. But in some use cases it will be a killing feature.This level 3 offloading looks very interesting. Do we have any numbers to show what it can mean as this has the potential to put emphasis on the R in CRS :-)
Use NetInstall to flash hAP Mini.any hint on how to flash this on a HAP MINI?
thanks in advance
It's Wireguard v1.0.0 proper (as shipped with v5.6).WireGuard implementation was done like MikroTik did to OpenVPN or kept as is in Linux 5.6?
Thank you.
Gave it a try on a hEX (RB750Gr3) and it worked out of the box!!) added WireGuard support;
@PaternotIt does routing at wirespeed, in all ports. There are several constraints, and a limit of 4096 connections, if I'm not wrong. But in some use cases it will be a killing feature.This level 3 offloading looks very interesting. Do we have any numbers to show what it can mean as this has the potential to put emphasis on the R in CRS :-)
https://i.mt.lv/cdn/product_files/CRS32 ... 200149.png@Paternot
I 4 1 do NOT believe that It will do routing at wire-speed ... why I do not believe that .... because for L3 wire-speed requires an ASIC and non of the hardware specs I see have that L3 ASIC in the gear. Yes there will be an improvement in performance but nowhere near wire-speed.
I 4 1 do NOT believe that It will do routing at wire-speed ... why I do not believe that .... because for L3 wire-speed requires an ASIC and non of the hardware specs I see have that L3 ASIC in the gear. Yes there will be an improvement in performance but nowhere near wire-speed.
@macgaiverhttps://i.mt.lv/cdn/product_files/CRS32 ... 200149.png
Are you sure that mention switchip doesn't have that feature?
not able to put device in netboot mode in any way tried... short, direct cable from pc eth to eth2, i add this command:Use NetInstall to flash hAP Mini.any hint on how to flash this on a HAP MINI?
thanks in advance
in comments above is said to use cli for now, probably winbox is not yet updated to include gui for wireguardThe second one is about wireguard. Why I can't specify the port number for peer? Is it intended or a bug as well?
Yeah, it works via cli, thanks.in comments above is said to use cli for now, probably winbox is not yet updated to include gui for wireguardThe second one is about wireguard. Why I can't specify the port number for peer? Is it intended or a bug as well?
L3 offloading happens on the switch chip.So in terms of MikroTik and RouterOS I do not see ANY functionality that mimics or deals with wire-speed Routing at the switch level.
@mrsharknot able to put device in netboot mode in any way tried... short, direct cable from pc eth to eth2
@Cha0sThe switch chips used in those RB models (which are ASICs basically) do support L3 routing at wirespeed as per Marvell's datasheet.
The hardware support was already there, but MikroTik just started supporting it on ROS.
OK thanks .... I found the following that looks very interesting and exciting for MikroTik users :-)I don't have it at hand, but I remember someone had posted it in the forum a while ago.
Well, the switch chipset has the circuitry. If they will implement it all they way is another question. But the hardware is already there.@PaternotIt does routing at wirespeed, in all ports. There are several constraints, and a limit of 4096 connections, if I'm not wrong. But in some use cases it will be a killing feature.This level 3 offloading looks very interesting. Do we have any numbers to show what it can mean as this has the potential to put emphasis on the R in CRS :-)
I 4 1 do NOT believe that It will do routing at wire-speed ... why I do not believe that .... because for L3 wire-speed requires an ASIC and non of the hardware specs I see have that L3 ASIC in the gear. Yes there will be an improvement in performance but nowhere near wire-speed.
Still waiting for something?Any update in wireless?
Configuring wireguard is pretty straight forward. Just look at the options available.Wireguard support cool thing, but where is an instruction how to use it?
They still have to implement MPLS - I think that is the one major feature still missing from the current beta. Otherwise, there are probably many small fixes needed here and there.Any time frame to move off development phase and make it ready for production / stable?
Do a search on this forum and you find many answer. Netinstall is one way. You can also downgrade to an older version that is much smaller, like some 6.44.x version, then upgrade to latest.any hint on how to flash this on a HAP MINI? On previous beta, it said internal storage is not enough to upgrade... it's a brand new model, factory
Totally agree! I will love to see MPLS implementedThey still have to implement MPLS - I think that is the one major feature still missing from the current beta. Otherwise, there are probably many small fixes needed here and there.Any time frame to move off development phase and make it ready for production / stable?
This level 3 offloading looks very interesting. Do we have any numbers to show what it can mean as this has the potential to put emphasis on the R in CRS :-)
We are waiting for the usual stuff:Still waiting for something?Any update in wireless?
3Com 4800G switch from 2009 is my bread and butter switch: IS-IS, BGP, OSPF, VRF; PIM-SSM all running with full IPv4 and IPv6 support.There is no need to question the possibility of doing L3 routing on a switch, there have been competing switches from other companies that do wirespeed routing for a long time.
For sure we'll get those features on ROS just wait till WiFi 7 gets announced xDWe are waiting for the usual stuff:Still waiting for something?Any update in wireless?
1. airtime fairness improvvements (http://blog.cerowrt.org/post/real_results/, https://forum.openwrt.org/t/aql-and-the ... vely/59002)
2. MU-MIMO
3. 802.11 k/v/r
...
This level 3 offloading looks very interesting. Do we have any numbers to show what it can mean as this has the potential to put emphasis on the R in CRS :-)
You'd be a fool to reimplement it yourself. Have a look at the Wireguard site and code and see for yourself how carefully it's been developed. Mikrotik would/might have only done some interface changes to make it work the ROS way.WireGuard implementation was done like MikroTik did to OpenVPN or kept as is in Linux 5.6?
Thank you.
/interface macsec
add cak=4cb39ed149d0e0dbea5fad4b91e5456f ckn=f98446584e49ad9e2cd99b2aff00adb73e0b4109eb916b8d5bbe208dda274abb \
disabled=no interface=ether5 name=macsec1 profile=default
[admin@under desk] /interface/macsec> print
Flags: I - inactive, X - disabled, R - running
0 name="macsec1" interface=ether5 status="negotiating" cak=4cb39ed149d0e0dbea5fad4b91e5456f
ckn=f98446584e49ad9e2cd99b2aff00adb73e0b4109eb916b8d5bbe208dda274abb profile=default
[admin@under desk] /interface/macsec>
Can't add key in wireguard via cli with "=" at the end. But can add it later via edit and can add it via gui.
[admin@MikroTik] /interface/wireguard> add private-key="EMjwk8mpDylWKGU0c/z9TR1e5u1D75OUz2jsv3lZu3k="
[admin@MikroTik] /interface/wireguard> peers/
[admin@MikroTik] /interface/wireguard/peers> add allowed-address=10.20.30.40 public-key="ObVREVOUlpRvqPxshivdYGiirVhb/U/dt1T7rQE2WFk=" interface=wireguard1
[admin@MikroTik] /interface/wireguard/peers> export
# aug/22/2020 09:10:46 by RouterOS 7.1beta2
/interface wireguard peers
add allowed-address=10.20.30.40/32 interface=wireguard1 public-key="ObVREVOUlpRvqPxshivdYGiirVhb/U/dt1T7rQE2WFk="
Flags: I - INACTIVE, U - UNREACHABLE, A - ACTIVE; c - CONNECT, o - OSPF, d - DHCP, l - LDP-MAPPING
Columns: DST-ADDRESS, GATEWAY, DISTANCE, SCOPE, TARGET-SCOPE, IMMEDIATE-GW
DST-ADDRESS GATEWAY DIS SC TA IMMEDIATE-GW
Ad 0.0.0.0/0 10.0.0.1 1 30 10 10.0.0.1%ether1
Io 10.0.0.0/23 110 20 10
Ao 10.0.0.0/23 sstp-odesskaya 110 20 10 sstp-odesskaya
Ac 10.0.0.0/24 ether1 0 10 ether1
Io 10.52.56.0/24 110 20 10
Ao 10.52.56.0/24 sstp-odesskaya 110 20 10 sstp-odesskaya
Io 100.64.0.0 110 20 10
Ao 100.64.0.0 sstp-odesskaya 110 20 10 sstp-odesskaya
Io 100.64.0.1 110 20 10
Ao 100.64.0.1 sstp-odesskaya 110 20 10 sstp-odesskaya
Io 100.64.0.2 110 20 10
Ao 100.64.0.2 sstp-odesskaya 110 20 10 sstp-odesskaya
Io 100.64.0.3 110 20 10
o 100.64.0.3 sstp-odesskaya 110 20 10 sstp-odesskaya
Ac 100.64.0.3 sstp-odesskaya 0 10 sstp-odesskaya
Io 100.64.0.4 110 20 10
Ao 100.64.0.4 sstp-odesskaya 110 20 10 sstp-odesskaya
Io 100.64.0.5 110 20 10
Ao 100.64.0.5 sstp-odesskaya 110 20 10 sstp-odesskaya
Io 100.64.0.6 110 20 10
Io 100.64.1.0/24 110 20 10
Ao 100.64.1.0/24 sstp-odesskaya 110 20 10 sstp-odesskaya
Io 100.64.3.0/24 110 20 10
Ao 100.64.3.0/24 sstp-odesskaya 110 20 10 sstp-odesskaya
Io 100.64.6.0/24 110 20 10
Ao 100.64.6.0/24 sstp-odesskaya 110 20 10 sstp-odesskaya
/routing ospf instance
add name=ospf_v2 router-id=100.64.0.7 version=2
/routing ospf area
add area-id=0.0.0.0 instance=ospf_v2 name=backbone_v2
/routing ospf interface
add area=backbone_v2 network=sstp-odesskaya network-type=point-to-point
When you don't like that, just don't turn the knobs!Wireguard is working well, except for that minor winbox issue with the endpoint port. With how easy it was to setup, I totally get the Wireguard hype now. IPSEC has a frustrating amount of knobs to turn.
[admin@MikroTik] /interface/wireguard> export
# aug/22/2020 21:33:34 by RouterOS 7.1beta2
# software id = xxxx-xxxx
#
# model = RouterBOARD 952Ui-5ac2nD
# serial number = xxxxxxxxxxxxx
/interface wireguard
add listen-port=53 mtu=1420 name=wireguard private-key=\
"private_key"
/interface wireguard peers
add allowed-address=0.0.0.0/0 endpoint=185.253.xx.x:53 interface=wireguard \
preshared-key="preshared key" public-key=\
"pub_key"
WOW, fantastic job, RouterOS getting better and better, thanks, we just need letsencrypt integrated to RouterOS.RouterOS version 7.1beta2 has been released in public "development" channel!
What's new in 7.1beta2 (2020-Aug-21 12:29):
!) added "bgp-network" output filter flag;
!) added bonding interface support for Layer3 hardware offloading;
!) added IPv6 nexthop support for IPv4 routes;
!) added Layer3 hardware offloading support for CRS309-1G-8S+IN, CRS312-4C+8XG-RM, CRS326-24S+2Q+RM and CRS354-48G-4S+2Q+RM;
!) added WireGuard support;
*) disk - improved external disk read/write speeds;
*) ospf - fixed point to point routes becoming inactive;
*) route - fixed source address selection of outgoing packets;
*) other minor fixes and improvements;
All released RouterOS v7 changelogs are available here:
https://mikrotik.com/download/changelog ... lease-tree
How to report RouterOS v7 bugs:
viewtopic.php?f=1&t=152006
i absolutely disagree with you @pe1chlBut as more and more features are added (e.g. multiple different encryption methods, as in IPsec), it becomes more complicated over time.
See how it went with OpenVPN, that was also simple at first but got more complicated on the way, especially because there was little forethought on how to accomodate future flexibility in the initial protocol.
IMHO the same will happen with wireguard.
I have the same issue, I think firewall rules are not setup correctly (although I accept traffic on the listening port and forward to/from the interface), it doesn't seem to flow. The tunnel sets up correctly and the client routes to the WG server, but I can't figure out how to correctly set it up so that traffic is routed back correctly. Does anyone have a complete example including firewall rules where how to connect a roaming client to the WG server such that all (internet) traffic is routed through the MikroTik WG system?hi
please help about wg config
i setup peer and wg interface but cant get any traffic throw the tunnel
Code: Select all[admin@MikroTik] /interface/wireguard> export # aug/22/2020 21:33:34 by RouterOS 7.1beta2 # software id = xxxx-xxxx # # model = RouterBOARD 952Ui-5ac2nD # serial number = xxxxxxxxxxxxx /interface wireguard add listen-port=53 mtu=1420 name=wireguard private-key=\ "private_key" /interface wireguard peers add allowed-address=0.0.0.0/0 endpoint=185.253.xx.x:53 interface=wireguard \ preshared-key="preshared key" public-key=\ "pub_key"
When you restrict yourself to site-to-site tunnels between equipment running the same software, IPsec is not complicated either. E.g. a GRE/IPsec tunnel using pre-shared keys between two MikroTik routers can be configured with a couple of mouseclicks.“ WireGuard securely encapsulates IP packets over UDP. You add a WireGuard interface, configure it with your private key and your peers' public keys, and then you send packets across it. All issues of key distribution and pushed configurations are out of scope of WireGuard; these are issues much better left for other layers, lest we end up with the bloat of IKE or OpenVPN. In contrast, it more mimics the model of SSH and Mosh; both parties have each other's public keys, and then they're simply able to begin exchanging packets through the interface.”
/ip route
add distance=1 dst-address=172.28.248.0/24 gateway=ipip-tunnel-z3 pref-src=\
192.168.69.1
add distance=1 dst-address=192.168.134.0/24 gateway=ipip-tunnel-z3 pref-src=\
192.168.69.1
add distance=1 dst-address=192.168.135.0/24 gateway=ipip-tunnel-z3 pref-src=\
192.168.69.1
add distance=1 dst-address=192.168.136.0/24 gateway=ipip-tunnel-z3 pref-src=\
192.168.69.1
add distance=1 dst-address=192.168.248.0/24 gateway=ipip-tunnel-z3 pref-src=\
192.168.69.1
/ip route
add dst-address=172.28.248.0/24 gateway="" pref-src=1.69.168.192
add dst-address=192.168.134.0/24 gateway="" pref-src=1.69.168.192
add dst-address=192.168.135.0/24 gateway="" pref-src=1.69.168.192
add dst-address=192.168.136.0/24 gateway="" pref-src=1.69.168.192
add dst-address=192.168.248.0/24 gateway="" pref-src=1.69.168.192
I like to add and ask others (if they are seeing the same) that I am seeing a similar issue with the LTE modem disappearing after a Router boot or USB Modem unplugging and pluggingBoth Sierra MC7430 and Quectel EC25 work great in MBIM mode in ROS7. Big difference with 6.47.x, as the MC7430 was only supported in PPP mode and the EC25 was supported in PPP and ECM modes. I do notice the amount of information the cards report is different. The MC7430 only reports RSSI, whereas the Quectel cards report RSSI, RSRP, SINR and RSRQ.
EC25AU.PNG
MC7430.PNG
I also notice the lte1 interface of the device with the EC25 card sometimes disappears after a reboot.
For now I'd assume that conversion from older versions does not work yet (for those features that drastically changed, like routing) and setup everything from scratch.I've upgraded from 6.46.6 to 7.1beta2 directly (I know, bad) ...and this happend with my static routes.
There is a difference between hashing (as SHA1) and encryption (as AES...) and just because someone is able to generate 2 different PDF files that produce same SHA1 hash does not mean he could reversely generate private keys used in VPN ...OpenVPN realization in Mikrotik is still useless due to lack of SHA256/SHA512 support (SHA-1 deprecated https://shattered.io/)
When SHA512 will be supported in Mikrotik?
/queue simple
add max-limit=30M/30M name=All_30Mbit queue=pcq-upload-default/pcq-download-default target=192.168.0.0/24
Number two was already mentioned in this thread. Number four is cosmetic and on re-entering the route window they are displayed as disabled.ROS: 7.1beta2
2) Unable to set peer Endpoint port in winbox. CLI works
4) IPv4 routes are deleted immediately after disabling (winbox)
CRS326-24G-2S+ has an older switch chip, for which L3 offloading is not supported yet. Here is the list of supported devices:So announcement says CRS309-1G-8S+IN, CRS312-4C+8XG-RM, CRS326-24S+2Q+RM and CRS354-48G-4S+2Q+RM for L3 offload but CRS317 mentioned above as working.
I have CRS326-24G-2S+ (arm). Will it take advantage of L3 offloading? If so, what else will?
/ interface gre unset timeout [ find ]
Are you sure about timeout? there is no such optionYou have to unset the timeout for GRE interfaces:
Code: Select all/ interface gre unset timeout [ find ]
/ interface gre unset keepalive [ find ]
!!!!! this fixed my IPIP tunnel too. lol (unsetting keepalive for ipip that is).Ah, stupid me... Of course it's keepalive.
Code: Select all/ interface gre unset keepalive [ find ]
[admin@gw-viper-rds] /interface/ipip> print
Flags: R - RUNNING
Columns: NAME, MTU, ACTUAL-MTU, LOCAL-ADDRESS, REMOTE-ADDRESS, DSCP
# NAME MTU ACTU LOCAL-ADDRESS REMOTE-ADDRE DSCP
0 R ipip-tunnel-z3 auto 1402 172.28.252.69 172.28.252.1 inherit
I still consider 7.x as a pre-Beta as it just reboots you touch someting that is untouchable. You only will know it was untouchable because, after the reboot the change was lost.Upgraded my RB3011 this morning to 7.1beta 2.
I reset the router before upgrading and only configured it with a WAN connection to upgrade to Beta2.
Upgrade seemed to go okay so I set about configuring it correctly.
First issue was renaming an interface (ether1 renamed to WAN) would result in a reboot as soon as I clicked OK or Apply.
Second issue was a deal breaker and that was all 10 interfaces were limited to 10Mb only. I tried manually setting them to 1Gb full duplex but to no avail.
I reverted back to 6.47.2 so unfortunately I can't generate a supout but just wondering if anyone has seen anything similar? Surely there are other RB3011 users out there that have upgraded?
/ip/firewall/raw> print stats
Flags: X - DISABLED, I - INVALID
Columns: CHAIN, ACTION, BYTES, PACKETS
# CHAIN ACTION BYTES PACKETS
0 prerouting drop 7 182 164 577 801 072 9 367 141 933 521 187 617
1 X prerouting drop 0 0
2 X prerouting notrack 9 890 406 038 755 190 484 15 743 512 066 554 732 580
3 X prerouting passthrough 3 821 585 153 310 984 802 6 668 097 643 014 512
Ok@npeca75 & @tpedko - Is it possible for You to send supout.rif files to support@mikrotik.com, referencing this forum thread, so we can troubleshoot this further?
Yeah. I wasn't expecting too much but I found the RB3011 much more unstable than the CHR and two CRS125s I have it running on.I still consider 7.x as a pre-Beta as it just reboots you touch someting that is untouchable. You only will know it was untouchable because, after the reboot the change was lost.
I went back to a stable Beta within minutes after walking into reboot walls.
Yes, this is a must! Is so easy to do, since almost all the needed code is already there.Is there a plan for resolving DNS peer names in WireGuard properties?
or we are doomed to script/resolve/set wireguard peer endpoint?
+1 on that request. Using a domain would make things much easier indeed.Yes, this is a must! Is so easy to do, since almost all the needed code is already there.Is there a plan for resolving DNS peer names in WireGuard properties?
or we are doomed to script/resolve/set wireguard peer endpoint?
Yes, it is. Just like the rest:Also, I can't seem to find a way to enable logging for wireguard. Is this not yet implemented in this latest beta?
[Interface]
PrivateKey = 123456=
Address = 172.16.0.12/32
Address =111:222:aaa/128
DNS = 8.8.8.8
[Peer]
PublicKey = 456789=
AllowedIPs = 0.0.0.0/0
AllowedIPs = ::/0
Endpoint = aaa.bbb.com:2255
Here you will find the RoS 7.1beta download link. It shows each supported architecture.What I tried to find out if the ROS 7 betas can run on anything else than ARM based devices? For example can it work on the CCRs?
Maybe a bit of clarification on the supported hardware would be nice as I cant find anything about that except for a single entry by Normis from 2019 (only ARM for now).
I am not running the MikroTik implementation so I have no idea if in its current state of RouterOS 7.1beta2 how may peers can be run .... and yes under ubnt EdgeRouter I have multiple Peers running in client sites.Does anyone have more than one simultaneous wireguard interface working?
I have one little test, with 3 CHRs. I named them after their IP, so we have 115, 116 and 118 machines.Looks like only one wireguard interface is working at a time, whatever is started first. Only the first shows as "running".
Does anyone have more than one simultaneous wireguard interface working?
Thanks both for your input. I have found the problem: using WebFig the listen-port always defaults to 12321. Although I was not using the port, it would conflict with the other interface. Setting one of the listen-port to something else worked fine.Looks like only one wireguard interface is working at a time, whatever is started first. Only the first shows as "running".
Does anyone have more than one simultaneous wireguard interface working?
Same issuewinbox 3.24 64bit on win7, rb450gx4. Open interfaces, add Virtual ethernet. Winbox closed.
I'm having similar problems on my rb4011igs+5hacq2hnd-in. Also did a reset to defaults with minor adjustments (ssid, wpa2 psk etc).Does anyone have some issues with wifi? On my hap ac^2 from time to time wifi clients can't get ip addresses from dhcp. I have tried to reset wifi settings to default, reset router itself, configure wifi via quick setup web page. Nothing works for me. I have downgraded routeros back to the stable version and everything works just fine again. Only strange thing in logs that I saw was something like "disconnected, group exchange timeout".
Are you sure you have imported the entire chain from the root, and not only the server certificate?I have a small issue with DNS over HTTPS. It works perfectly in 6.47.2, but now mikrotik can't verify certificate. I tried to re-import it, but nothing helps.
Yes I'm, and it was validated succesfully on stable branchAre you sure you have imported the entire chain from the root, and not only the server certificate?I have a small issue with DNS over HTTPS. It works perfectly in 6.47.2, but now mikrotik can't verify certificate. I tried to re-import it, but nothing helps.
You might be interested this howto : https://rickfreyconsulting.com/wireguard/ , but how to route one client without marking I don't know, unfortunately.Hi,
Let's say I have this in my wireguard configuration file, how would I deploy it in my mikrotik router?
Also, how would I route traffic from client 192.168.0.44 only, through this tunnel?
Any help would be greatly appreciated
Thanks!
Code: Select all[Interface] PrivateKey = 123456= Address = 172.16.0.12/32 Address =111:222:aaa/128 DNS = 8.8.8.8 [Peer] PublicKey = 456789= AllowedIPs = 0.0.0.0/0 AllowedIPs = ::/0 Endpoint = aaa.bbb.com:2255
Hi,You might be interested this howto : https://rickfreyconsulting.com/wireguard/ , but how to route one client without marking I don't know, unfortunately.Hi,
Let's say I have this in my wireguard configuration file, how would I deploy it in my mikrotik router?
Also, how would I route traffic from client 192.168.0.44 only, through this tunnel?
Any help would be greatly appreciated
Thanks!
Code: Select all[Interface] PrivateKey = 123456= Address = 172.16.0.12/32 Address =111:222:aaa/128 DNS = 8.8.8.8 [Peer] PublicKey = 456789= AllowedIPs = 0.0.0.0/0 AllowedIPs = ::/0 Endpoint = aaa.bbb.com:2255
Thank you for the tricky way with marking. I did it, pings between server and mikrotik is good, DNS is working on well, but internet on the client is incredibly slow, trying to troubleshoot it
10. Finally add a new route in the terminal, like this, /ip route add dst-address=0.0.0.0/0 gateway=[your wireguard interface]@main routing-table=VPNProvider
That's it, your specified clients should now be routed through your vpn connection
Yes, I noticed that too. I can max out my 500/100 internet connection with ROS 6.47.2, fasttrack enabled, but with ROS 7.1b2, I'm getting only about 100+/100, even with fasttrack enabled (using a mikrotik hex).
Thank you for the tricky way with marking. I did it, pings between server and mikrotik is good, DNS is working on well, but internet on the client is incredibly slow, trying to troubleshoot it
For some modem types, the DHCP client is dynamically created and cannot be modified (nor prevented from being dynamically generated and created manually), so this advice is not applicable. For the dynamically created DHCP client, the setting in question (plus other ones) is (in theory) inherited from the apn profile.You need to turn it off in the DHCP client!
Ok, but it can be clearly seen above that "Use peer DNS" is OFF in the LTE profile and it is ON in the DHCP client. So that is a bug?For some modem types, the DHCP client is dynamically created and cannot be modified (nor prevented from being dynamically generated and created manually), so this advice is not applicable. For the dynamically created DHCP client, the setting in question (plus other ones) is (in theory) inherited from the apn profile.You need to turn it off in the DHCP client!
Yes it requires a license. You can get a trial as usual.Do beta releases require licence for testing ?
In other words can I install it f.e. on x86 for tests without any additional licence ?
Hi, disabling fasttrack seems to solve this problemThank you for the tricky way with marking. I did it, pings between server and mikrotik is good, DNS is working on well, but internet on the client is incredibly slow, trying to troubleshoot it
Have you tried changing the speed/duplex etc via the CLI instead of via the web ui?A brand New CCR2004, with an Optical GPON ONU SFP recognized as brand "ODI"
The ONU is fully functionnal under v6.47.2, seems to let change the AUto Negotiation Speed to more than 1000M Full, but allways limited to 1000M.
According to https://www.dslreports.com/forum/r32230 ... 57810S-NIC SGMII linux patches can let SFP sticks run at more that 1000M, so I give a try to v7.1beta2.
I upgraded the fimrware, go to the sfp-sfpplus interface, doble clic, and yes, it's still recognized, but this time eligible speeds are not pre checked. So I check 2.5G Full, and instant reboot.
No way to change the neciable speed. Everytime I try to change it, it reboots. Unfortunately, It seems limited to 1000M.
Capture1.PNG
- I give a try with another stick of this kind, and I come back. I do have several sticks of this kind.
- When I do exactly the same procedure with another SFP ONU Stick (CarllitoxxPro), it reboots.
This bug, about SFP speed negociation, seems generic, including with Mikrotik Interfaces.
- It's exactly the same reboot changing the negociated speed of a S+RJ10 Mikrotik Interface
I can make you more explicit capture CLI, most of all for the first ONU stick of course, If you can let it run 2.5Gbps patching this bug, I would be gracefull.
Hope this helps. Feel free to contact me by email.
Thanks for the advice. I try it.
Have you tried changing the speed/duplex etc via the CLI instead of via the web ui?
I had a similar issue forcing a 10gbit interface to be 1gbit on a CRS 317 running 7.1beta2. Via winbox would cause the router to crash, via CLI worked fine.
Wireguard endpoints are set and updated automatically on handshake.
No, only one endpoint (at a time). The other side has to initiate the handshake.Huh. Are you sure that both of endpoint can be updated automatically?Wireguard endpoints are set and updated automatically on handshake.
Nevertheless, I can't find any example of routeros setup with one of the peers is with endpoint (e.g. "client") and other is without ("server"). May be I'm on wrong path...
I don't have a single Wireguard interface with one peer as server and one as client. But I do have two Wireguard interfaces, where one is a server (listening) and has two peers. On these, the peer endpoints update automatically as already mentioned. My other Wireguard interface is a client with one peer. The CLI is needed to set the endpoint port for this one.Huh. Are you sure that both of endpoint can be updated automatically?
Nevertheless, I can't find any example of routeros setup with one of the peers is with endpoint (e.g. "client") and other is without ("server"). May be I'm on wrong path...
In my case, even with user-peer-dns off both in lte1 and the dynamic dhcp-client, ip dns is showing it in the "dynamic-servers" and there is no way to get rid of them once installed, no matter what I do.lte1 receives DNS via DHCP (from the modem) with the checkbox off in LTE APN - Use Peer DNS. I can't turn off the use of DNS from the router side.
Mikr_DNS.png
That's hardly an "in depth tutorial". And don't get me started on the quality of the screenshots, missing accompanied selectable text for whatever goods are or aren't in them, or the discrepancies between the screenshots and the settings export provided. Or the missing proper explanation of allowed address fields with proper examples.This gentlemen wrote an in-depth tutorial for MikroTik site to site VPN:
https://rickfreyconsulting.com/wireguar ... n-example/
@ Znevna ....It's not rocket science to build up a Wireguard tunnel and route something over it.This gentlemen wrote an in-depth tutorial for MikroTik site to site VPN:
https://rickfreyconsulting.com/wireguar ... n-example/
Do you guys get a cut for traffic generated to his site or out of how many "clients" that guy "gets" thanks to you?:)
Ofc you'd say that, you're in the same business model. I also hope he gets as many clients as he deserves.@ Znevna ....It's not rocket science to build up a Wireguard tunnel and route something over it.This gentlemen wrote an in-depth tutorial for MikroTik site to site VPN:
https://rickfreyconsulting.com/wireguar ... n-example/
Do you guys get a cut for traffic generated to his site or out of how many "clients" that guy "gets" thanks to you?:)
IMO Rick Frey provides an excellent tutorial on using WireGuard and MikroTik and I hope that he gets as many clients as he deserves.
I fully agree with you, and also I think he is mainly a wireguard fanboi and makes false claims about the alternative methods (especially on RouterOS)....
Such a posting would actually be useful when it included relevant details of what you were experiencing.I have an issue here with the 7.1 beta 2 on 3 hAp ac^2 devices. Had te return to the stable branch for wireless to become stable again.
On all devices i had serious stability issues.
He told that the same I am seeing: devices get stuck but otherwise connected on both interfaces.I have an issue here with the 7.1 beta 2 on 3 hAp ac^2 devices. Had te return to the stable branch for wireless to become stable again.
On all devices i had serious stability issues.
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk group-key-update=1h mode=dynamic-keys supplicant-identity=MikroTik
/interface wireless
set [ find default-name=wlan1 ] adaptive-noise-immunity=ap-and-client-mode antenna-gain=4 band=2ghz-onlyn channel-width=\
20/40mhz-Ce country=spain disabled=no frequency=auto installation=indoor mode=ap-bridge ssid=MT \
wireless-protocol=802.11 wmm-support=enabled
set [ find default-name=wlan2 ] adaptive-noise-immunity=ap-and-client-mode antenna-gain=5 band=5ghz-onlyac basic-rates-a/g=12Mbps \
channel-width=20/40/80mhz-XXXX country=spain disabled=no frequency=auto installation=indoor mode=ap-bridge rate-set=configured \
ssid=MT vht-supported-mcs=mcs0-9,mcs0-9,none wireless-protocol=802.11 wmm-support=enabled
I know and i'm sorry for that but i had to revert to a stable situation because of work i had to do. But still i thought it might be usefull to report.Such a posting would actually be useful when it included relevant details of what you were experiencing.I have an issue here with the 7.1 beta 2 on 3 hAp ac^2 devices. Had te return to the stable branch for wireless to become stable again.
On all devices i had serious stability issues.
sep/06/2020 20:14:55 system,error,critical router rebooted because some critical program crashed
Thanks! Is this just a bug in the beta that the drop down list is not visible?You can write the interface name manually and it will work even if there's no list from which you could easily select it.
I saw it again. The message was "NETWORK_SELECTION_DISABLED_DHCP_FAILURE=2 " (It was 1 last time I saw it. It recovers with disable/enable in wlan2 , disable/enable wlan1 in the router.. Failing devices are mostly android, but also a windows and a linux laptop occasionally. I have set wireless debug in one of the phones and saw a message like NETWORK_UNAVAILABLE DHCP NOT RESPONDING=1 (I'm inventing the message but it was the idea).
What is a "white IP"?Wireguard does not connect from Mikrotik behind NAT to a Linux server with a white IP.
"White IP" is used in the post-soviet area instead of "public IP". "Grey" means "private". No idea what's the origin of this.What is a "white IP"?
Without using NAT. Without port forwarding, the interface address is not in the private or gray IP range.What is a "white IP"?
Share a secret )But Wireguard with Mikrotik behind NAT is not a problem for me.
I'm sorry, but there's no secret... Just works for me.Share a secret )But Wireguard with Mikrotik behind NAT is not a problem for me.
/interface/wireguard/export hide-sensitive
# model = 960PGS
# serial number = CB540BCF02D3
/interface wireguard
add listen-port=8526 mtu=1420 name=3001
/interface wireguard peers
add allowed-address=192.168.160.0/24 endpoint=XX.181.201.XXX:61830 interface=3001 public-key=\
"Fp9D00OEAHH9zotl3pw6cMTmwICL/OkZEj7KBo4ZWns="
I have a similar issue like this on my RB750Gr3.Upgraded my RB3011 this morning to 7.1beta 2.
I reset the router before upgrading and only configured it with a WAN connection to upgrade to Beta2.
Upgrade seemed to go okay so I set about configuring it correctly.
First issue was renaming an interface (ether1 renamed to WAN) would result in a reboot as soon as I clicked OK or Apply.
Second issue was a deal breaker and that was all 10 interfaces were limited to 10Mb only. I tried manually setting them to 1Gb full duplex but to no avail.
I reverted back to 6.47.2 so unfortunately I can't generate a supout but just wondering if anyone has seen anything similar? Surely there are other RB3011 users out there that have upgraded?
[admin@MikroTik] >> /interface/ethernet/export
# sep/09/2020 08:38:45 by RouterOS 7.1beta2
# software id = VQDT-J37Q
#
# model = RouterBOARD 750G r3
# serial number = 8AFF080AF8C6
/interface ethernet
set [ find default-name=ether1 ] advertise=10M-half,10M-full
set [ find default-name=ether5 ] advertise=10M-half,10M-full
/interface ethernet unset [ find default-name=ether1 ] value-name=advertise
What is the correct way to unset this advertise command ?
/interface ethernet
set [ find default-name=ether1 ] advertise=10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full
I've tried to connect like this to a dozen of a servers and everything worked well enough for me.Wireguard does not connect from Mikrotik behind NAT to a Linux server with a white IP.
The Packet Sniffer on Mikrotik itself does not see any attempts to communicate with the server at all, filters by IP or port do not catch any packets in the direction of the server when the Wireguard interface is turned on and off.I've tried to connect like this to a dozen of a servers and everything worked well enough for me.
I've been wondering is it possible to generate keys on mikrotik for wireguard peers?
You can make a second wireguard interface, and copy the private and public key out of it.I've been wondering is it possible to generate keys on mikrotik for wireguard peers?
Follow the manual until you arrive to configure netbooting. Then ignore what the image days (192.168.88.3) and set instead 192.168.88.1.Ive asked in the forums before updating to V7. One of the supports said it wont harm your device. I did it and it bricked my device. Thanks and sadly i will need to buy another retarded mikrotik device because its my only option. Plus LDF-5 doesnt work in net install mode my computer doesnt recognize it. Sad...
[me@chr-7-1] > interface/wireguard/print
0 name="wg-0" mtu=1500 listen-port=5555 private-key="CE8v6Js/u5gw4qyIvVbY0idQ7fu4dArDK2dwDz4q33c=" public-key="Mrm8SbfGOmEnIUfmWrI+YBRV8fClymdgaceY+EjHqhY="
[me@chr-7-1] > interface/wireguard/set [find name=wg-0] name=wg-1
[me@chr-7-1] > interface/wireguard/print
0 name="wg-1" mtu=1420 listen-port=5555 private-key="CE8v6Js/u5gw4qyIvVbY0idQ7fu4dArDK2dwDz4q33c=" public-key="Mrm8SbfGOmEnIUfmWrI+YBRV8fClymdgaceY+EjHqhY="
The device was launched with 7.X out of the box, you can't go lower than thatdowngrade V7.1 beta2 impossible to downgrade Mikrotik chateau LTE12 stable version 6.47.3 no working Need help
thankThe device was launched with 7.X out of the box, you can't go lower than thatdowngrade V7.1 beta2 impossible to downgrade Mikrotik chateau LTE12 stable version 6.47.3 no working Need help
Can confirm the DHCP issue on RB4011iGS+5HacQ2HnD-IN, though I've only had it happen with one laptop (AC 9560, Arch Linux: linux 5.8.7.arch1-1 networkmanager 1.26.2-1). I was initially reluctant to blame RouterOS since I do tinker with a lot of experimental stuff (and the network card allegedly sometimes has issues with BT, got a new BT mouse recently, etc.), and all other devices seemed to operate normally, but after finally spending a few hours troubleshooting this I have to assume it's the router. RouterOS log only shows the client connecting and disconnecting. Linux/networkmanager log shows a DHCP timeout, which will (by default) make it disconnect after 45s and try reconnecting again. I noticed a DHCP lease does exist for the MAC address.He told that the same I am seeing: devices get stuck but otherwise connected on both interfaces.I have an issue here with the 7.1 beta 2 on 3 hAp ac^2 devices. Had te return to the stable branch for wireless to become stable again.
On all devices i had serious stability issues.
Some time after last disable/enable cycle or reboot, any of the devices stop flowing through the wireless connection. If they are "clever" they migrate to the other, say wlan2. I often find after a few hours that all devices except one are in, say wlan1 and only one is in registration table at wlan2, but not working. disable/enable makes it work again, until it failed
It was not happening in 7.1beta1, it takes a few hours to happen, seems to be related with noise and distance, as it got better to me by:
* increasing the antenna gain in both interfaces (which also made for better signal overall and less warm router, BTW).
* changing a few other wireless settings.
Currently I have:and it happens less than with the default settings. Failing devices are mostly android, but also a windows and a linux laptop occassionally. I have set wireless debug in one of the phones and saw a message like NETWORK_UNAVAILABLE DHCP NOT RESPONDING=1 (I'm inventing the message but it was the idea). The router thought that the phone was happily connected, BTW, but it disappeared from registration table when I switched wifi off / on in the phone, only to return to the same when I forced to reconnect. After disable/enable of the wlanN interface everything works again... for a few hours.Code: Select all/interface wireless security-profiles set [ find default=yes ] authentication-types=wpa2-psk group-key-update=1h mode=dynamic-keys supplicant-identity=MikroTik /interface wireless set [ find default-name=wlan1 ] adaptive-noise-immunity=ap-and-client-mode antenna-gain=4 band=2ghz-onlyn channel-width=\ 20/40mhz-Ce country=spain disabled=no frequency=auto installation=indoor mode=ap-bridge ssid=MT \ wireless-protocol=802.11 wmm-support=enabled set [ find default-name=wlan2 ] adaptive-noise-immunity=ap-and-client-mode antenna-gain=5 band=5ghz-onlyac basic-rates-a/g=12Mbps \ channel-width=20/40/80mhz-XXXX country=spain disabled=no frequency=auto installation=indoor mode=ap-bridge rate-set=configured \ ssid=MT vht-supported-mcs=mcs0-9,mcs0-9,none wireless-protocol=802.11 wmm-support=enabled
/routing/filter/rule/add action=accept chain=bgp_in set-in-nexthop-direct=gateway1
Exactly: viewtopic.php?p=812440#p812440What kind of weirdness? Known issue is that ospf route can appear twice in routing table.
Any details?my router was hacked on this beta version!
Ip of the malware from Hong Kong
They posted a print with one hAP AC2 doing 700 Mbps. Given the CPU used by the RB4011, with also 4 cores and much higher processing power, I'd say yes.Can you get 1Gbps wireguard throughput on any of the mikrotik devices at this time?
I just setup Wireguard on my hAP AC² to replace the IPSEC tunnel I had before and am seeing around ~ 230 Mbit/s with max overclocked CPU on it. Would be nice to squeeze out a little bit more. Here is the CPU load while it's running and I have fasttrack disabled.They posted a print with one hAP AC2 doing 700 Mbps. Given the CPU used by the RB4011, with also 4 cores and much higher processing power, I'd say yes.
For me it works... until it stops working. Then I doI just setup Wireguard on my hAP AC²
(...)
I can also confirm that 2,4 GHZ Wifi is broken and client's don't get dhcp on that one, 5 GHZ seems to work fine.
/interface/wireless { disable wlan1; enable wlan1}
+1 quite unstable WiFi connection. Devices don't get DHCP. Had to force static lease for my Android phone, otherwise it would never connect... Same thing happens with my iPad.For me it works... until it stops working. Then I doI just setup Wireguard on my hAP AC²
(...)
I can also confirm that 2,4 GHZ Wifi is broken and client's don't get dhcp on that one, 5 GHZ seems to work fine.
ant it works again... until it stops working again, in a few hours.Code: Select all/interface/wireless { disable wlan1; enable wlan1}
Can also confirm a DHCP issues on hAP ac2: wireless clients time to time are unable to get IP address and reconnect in a loop.RouterOS version 7.1beta2 has been released in public "development" channel!
There are still so many small issues (and likely some big ones) that it would be foolish to promote it to "stable" anytime soon!Any dates to get the Stable Release? I like to not continue using 6.xx and already push to get 7.xx
All true. But sometimes I start thinking about it. No idea when it will be released, but I hope it will be before june 2021. One can always dream... :DThere are still so many small issues (and likely some big ones) that it would be foolish to promote it to "stable" anytime soon!Any dates to get the Stable Release? I like to not continue using 6.xx and already push to get 7.xx
And of course it would have to go via "testing" anyway.
Wanted to write about this earlier but forgot.!!!!! this fixed my IPIP tunnel too. lol (unsetting keepalive for ipip that is).Ah, stupid me... Of course it's keepalive.
Code: Select all/ interface gre unset keepalive [ find ]
THANKS.
Running! ^^Code: Select all[admin@gw-viper-rds] /interface/ipip> print Flags: R - RUNNING Columns: NAME, MTU, ACTUAL-MTU, LOCAL-ADDRESS, REMOTE-ADDRESS, DSCP # NAME MTU ACTU LOCAL-ADDRESS REMOTE-ADDRE DSCP 0 R ipip-tunnel-z3 auto 1402 172.28.252.69 172.28.252.1 inherit
https://www.marvell.com/content/dam/mar ... 016-12.pdfhttps://i.mt.lv/cdn/product_files/CRS32 ... 200149.png@Paternot
I 4 1 do NOT believe that It will do routing at wire-speed ... why I do not believe that .... because for L3 wire-speed requires an ASIC and non of the hardware specs I see have that L3 ASIC in the gear. Yes there will be an improvement in performance but nowhere near wire-speed.
Are you sure that mention switchip doesn't have that feature?
Update - after around half an hour, it jumped to 100% and finished!I then tried to do a sup-output on the CCR, but that got to 8% and then did nothing more.
:-) That shows how long it is since I've needed to generate one then!That is "normal", also for 6.47 versions. It does not always take half an hour but it can take considerable time, being stuck at 7 or 8%.
When it's ready!When can we expect the next v7 beta release?
But they ARE releasing it on fridays. At least the last 2 or 3 releases where on a friday. Yes, yes. I know: joking and all that. :DFriday is not a good day being the start of the Mikrotik weekend.
Sorry, couldn't resist.
Also lots of users would probably tend to call or file bugreports immediately when it was during the workweek, while in the weekend they know there will be no immediate response and they first study the matter a bit more, and find the solution themselves...Yeah, at least you can evaluate the scale of disaster by Monday, not jumping into every small reported bug right after the release :)
LOLing here. :DGuys, stop telling everybody that they should wait for other people do testing of new release. If you do it long enough, nobody will test new release.
BTW, anybody installing beta version (the thread is about v7.1beta) in any approximation of production environment is living on the cutting edge and deserves whatever hits him/her.
but people with Chateau not have a way to go back to ros v6 bcs mtk give them only Ros7 and no way of installing v6 (except v6.99.x :p ).Guys, stop telling everybody that they should wait for other people do testing of new release. If you do it long enough, nobody will test new release.
BTW, anybody installing beta version (the thread is about v7.1beta) in any approximation of production environment is living on the cutting edge and deserves whatever hits him/her.
Don't expect rc in for long time, they first need to include all functionality and have that tested for some time.Lets hope to see 7.1 b3 or porbably 7.1 rc tomorrow xD
it is already 13 months since first beta was out.Don't expect rc in for long time, they first need to include all functionality and have that tested for some time.Lets hope to see 7.1 b3 or porbably 7.1 rc tomorrow xD
Probably won't see a rc version this year.
I would be surprised to see a stable version 7 next year.
Point being?it is already 13 months since first beta was out.Don't expect rc in for long time, they first need to include all functionality and have that tested for some time.Lets hope to see 7.1 b3 or porbably 7.1 rc tomorrow xD
Probably won't see a rc version this year.
I would be surprised to see a stable version 7 next year.
Can't rush perfection! :) Glad they are taking their time to get it right.Looks like Mikrotik knows how to treat their employees, other companies would have rushed to push V7 into production as soon as possible.
My condolences go to victims of MT ;-)mkxbut people with Chateau not have a way to go back to ros v6 bcs mtk give them only Ros7 and no way of installing v6 (except v6.99.x :p ).BTW, anybody installing beta version (the thread is about v7.1beta) in any approximation of production environment is living on the cutting edge and deserves whatever hits him/her.
Check "Page history". Those changes are one month old :)https://help.mikrotik.com/docs/display/ ... col+Status
seems like beta3 is almost there.
Maybe next week hahaLets hope to see 7.1 b3 or porbably 7.1 rc tomorrow xD
Also confirm DHCP Issue on 3 devices, two hAP ac2 and 962UiGS-5HacT2HnT. Even disabling/enabling wlan1 interface don't work for me. Removing host from DHCP server leases working, but not in whole situations.Can also confirm a DHCP issues on hAP ac2: wireless clients time to time are unable to get IP address and reconnect in a loop.RouterOS version 7.1beta2 has been released in public "development" channel!
WLAN interface disabling/enabling temporary "fix" the problem.
I faced the same issue so reverted back to stable. This is a very basic thing that should be working.Also confirm DHCP Issue on 3 devices, two hAP ac2 and 962UiGS-5HacT2HnT. Even disabling/enabling wlan1 interface don't work for me. Removing host from DHCP server leases working, but not in whole situations. Even if I set dhcp pool like 192.168.20.* i'm receiving from DHCP server ip's from 192.168.88.*, gateway 192.168.88.1. I have to set manually IP from my network, then working ok.Can also confirm a DHCP issues on hAP ac2: wireless clients time to time are unable to get IP address and reconnect in a loop.RouterOS version 7.1beta2 has been released in public "development" channel!
WLAN interface disabling/enabling temporary "fix" the problem.
Additionaly I registered rebooting and not saving settings for ethernet speed settings. I'm trying to disable autonegotiation and set speed manually, after confirm RB reboting and settings doesnt change.
Is someone have this same issue?
regards
What is the problem? It is just efficient and the forum Software shortens the text anyway. Instead of hist post, your post actually has nothing to add to the thread.Do you think that people are unable to follow the thread?
No, Not at all. I am much faster in understanding his point an have no need in ycrolling up and reading the last messages to understand.Don't you think it is unneeded a waste of time?
Right you are. But it is important to shorten the quote to what you actually intend to quote, just as we both did.It is just efficient!
I can't because I had to go to stable in the only machine it had this problem (hAP ac^2). The rest of the machines I have running 7.1betas (no ARM, all one-core MIPSBE) are doing ok, so I guess it is either architecture dependent or dependent on number of cores, configuration, history of installs/configuration, or a mixture of those.(...) nostromog (...) please write to support@mikrotik.com or contact us via our support portal https://help.mikrotik.com/servicedesk In support ticket, please describe issue in detail, your network setup and create supout.rif file once issue is present and share it with us. Thank you for reporting the issue.
At least for the past few minutes - after performing a "/interface wireless reset-configuration" for both 2G and 5G, and then setting the channel widths back to 20/40XX and 20/40/80XXXX, things seem to be working. We'll see if it stays that way for a while. Based on some other inconsistencies I'm guessing/hoping there's some issues with upgrading that might not exist in "clean" installs of 7.1b2.Has anyone been able to restore normal/stable wifi operation on this beta? I loaded it on my home router for Wireguard - wifi is now useless. Fortunately I have a secondary wifi AP available.
The Routing Marks it a bummer, basically the only thing holding me back to do some proper testing on OVPN UDPHello!
Just upgraded to v7.1b2 and spotted a few issues:
First and most important is routing marks don't work
The second one is about wireguard. Why I can't specify the port number for peer? Is it intended or a bug as well?
Probably this will help you to set up routing tables:OVPN over UDP works great for me on CHR
I did notice when I try to add a routing mark I cant type any New Routeing Mark , It only have one option and that is to choose main,
-) Winbox does not show all features, use CLI for most functionality
Are you sure they were in /flash folder, not in the root directory that is mounted to RAM?including wiping the file storage...where I had stored a couple backup configs
I have the same problem the C.A falls quicklyHey all,
someone with Chateau 12LTE who was able to get properly working with SIM card?
Modem is very unstable and connection after a while drops.
Long story short:I have the same problem the C.A falls quickly
I am familiar with how CISCO does in on their MLS devices. Typically for wire-speed routing in the Cisco Switch world Cisco requires three entities to implement multilayer switching: the switching engine (SE), the route processor (RP), and the MLS protocol. The SE performs the switching function, the RP performs the routing function, and the MLS protocol provides for communication between these two devices. This aside, there is one very simple concept that makes it all possible: the flow. A flow can be defined as a stream of packets from the same source to the same destination using the same application. As an example, a flow could be an HTTP session between a source browser and a target server. In a Cisco MLS network, the initial packet in a session is routed via the RP, but all subsequent packets in that particular session are switched by the SE. The SE maintains a cache about these flows and can determine whether or not a given packet is part of an established session. If so, the SE rewrites the pertinent packet info as if it had been processed by the router and then switches the packet. This process is commonly referred to as “route once, switch many.” It occurs at switch speed, not at the slower router speed.
So in terms of MikroTik and RouterOS I do not see ANY functionality that mimics or deals with wire-speed Routing at the switch level.
We've got 6.47.6 yesterday. And it wasn't even Friday. I think that's enough for this weekend ;-)Can we expect the next beta version today as it is a Friday and over 2 months since the last beta release?
While of course a router should not crash under these circumstances, this is a setting that you normally should not touch. It does not work like most people think it would!I am not entirely sure, but I think we can provoke it, by changing port speed on an interface ex. to "100 half duplex" and back to "auto negotiate".
Write directly to support@mikrotik.com or create a case by https://help.mikrotik.com/servicedeskHow can I help the developers debug this, in a meaningful way.
Update:
We can replicate this behaviour 100% of the times, when we are changing port speed on an interface.
There is a full example in the doc https://help.mikrotik.com/docs/display/ ... figurationanyone tried configuring BGP in ROS7.1beta2 I would love to see some examples :)
yes me too especially with filters. Also it's been 2 months since last beta release.anyone tried configuring BGP in ROS7.1beta2 I would love to see some examples :)
Thanks just want i needed :)There is a full example in the doc https://help.mikrotik.com/docs/display/ ... figurationanyone tried configuring BGP in ROS7.1beta2 I would love to see some examples :)
We still wait for it bcs ppl have two other big problems:It seems wi-fi issue has been fixed in 7.1beta3. Running it for a week without any issues.
PS: not yet available for everyone.
Beta 3? How did you get it?It seems wi-fi issue has been fixed in 7.1beta3. Running it for a week without any issues.
PS: not yet available for everyone.
[admin@MikroTik] > /user ssh-keys private import user=admin private-key-file=test.key
passphrase: *******
unable to load key file (incorrect passphrase?) !
.Modem is very unstable and connection after a while drops.
And that's why you write here instead of creating new thread, sorry but this is not a place to speak about APN AT Commands and Log's changes in LTE.I'm in contact via Mikrotik support and I'd like to know if someone else is experiencing the same problem.
Here i am! I always use LTE mode only on Chateau LTE12 (and before on WAP LTE and LHG LTE too). It works well with all 3CA combination (provider 3 Italy, now Wind3)Hey,
is there anyone who owns a Chateau LTE12 and is able to use LTE mode only?
Currently I'm able to connect to internet only using 3G mode.
I'm in contact via Mikrotik support and I'd like to know if someone else is experiencing the same problem.
It appears they again went "under water" with the v7 beta. There is mention of a 7.1beta3 that apparently some people have, and which is mentioned in the feature completeness table on the help site, but which has not been released to the public.3 months yet next beta is not yet released! waiting for next release that would mitigate the wifi dhcp lease issue on hap ac2