Also they know that are a problem on dates show on webfig, and I just found that it depends of your browser timezone.Why is a stable version released with a half-hearted implementation of the change in time format?
I think it is a good change in principle, but it seems controversial for scripting (discussion elsewhere) and now we have a mix of formats all over the place.
Would it not be better to make the complete change, or roll back when it cannot be completed, at the point of stable release?
/interface/ethernet/switch/l3hw-settings monitor
/interface/ethernet/switch/l3hw-settings/advanced monitor
What fix are you referring to? This release has several fixes on wifi wave2.Fix for WiFi will be in 7.11 so stay at 7.8
Why is a stable version released with a half-hearted implementation of the change in time format?
What fix are you referring to? This release has several fixes on wifi wave2.Fix for WiFi will be in 7.11 so stay at 7.8
Still waiting to get a response from MT of how this is to be used and why it was implemented............... ?????
*) firewall - added "endpoint-independent-nat" support;
"Endpoint-Independent Mapping" is defined in [BEH-UDP] as follows:
The NAT reuses the port mapping for subsequent packets sent from
the same internal IP address and port (X:x) to any external IP
address and port.
"Endpoint-Independent Filtering" is defined in [BEH-UDP] as follows:
The NAT filters out only packets not destined to the internal
address and port X:x, regardless of the external IP address and
port source (Z:z). The NAT forwards any packets destined to
X:x. In other words, sending packets from the internal side of
the NAT to any external IP address is sufficient to allow any
packets back to the internal endpoint.
A NAT device employing the combination of "Endpoint-Independent
Mapping" and "Endpoint-Independent Filtering" will accept incoming
traffic to a mapped public port from ANY external endpoint on the
public network.
According to*) bridge - fixed HW offloaded STP state on port disable;
*) bridge - fixed HW offloading for vlan-filtered bridge on devices with multiple switches (introduced in v7.8 );
*) bridge - fixed incorrect host moving between ports with enabled FastPath;
setup before upgrade too 7.10 (before is 7.8) STP = none, HW Offload run 1.jpg internet really slow after upgrade too 7.10 before is normal with that setup (7.8)
setup after upgrade enable RSTP and IGMP Snooping, DHCP Snooping, Add DHCP Option 82, HW Offload off, internet back too normal 2.jpg
This on RB750Gr3, i am scratch my head over one hours are this the best setting for 7.10 for now?
Now I did LOL.You read my post? ;)
viewtopic.php?t=197095#p1007949
your right i delete all the firewall filter rule and restore to default config it seem back to normal again, something must be the couse in that ruleAccording to*) bridge - fixed HW offloaded STP state on port disable;
*) bridge - fixed HW offloading for vlan-filtered bridge on devices with multiple switches (introduced in v7.8 );
*) bridge - fixed incorrect host moving between ports with enabled FastPath;
setup before upgrade too 7.10 (before is 7.8) STP = none, HW Offload run 1.jpg internet really slow after upgrade too 7.10 before is normal with that setup (7.8)
setup after upgrade enable RSTP and IGMP Snooping, DHCP Snooping, Add DHCP Option 82, HW Offload off, internet back too normal 2.jpg
This on RB750Gr3, i am scratch my head over one hours are this the best setting for 7.10 for now?
https://help.mikrotik.com/docs/display/ ... +Switching
you should't enable any STP or snooping on your bridge, only if you know exactly why you need these...
Does this actually work for you? I'm not getting any output for that oid when I do an snmpwalk, nor does Observium/LibreNMS get a list of BGP peers.I'm super happy with the BGP addition in SNMP; `bgpPeerTable` (https://oidref.com/1.3.6.1.2.1.15.3)
It would be awesome ifare also added for some NMS-products.
- `bgpLocalAs` (https://oidref.com/1.3.6.1.2.1.15.2) and,
- `bgpIdentifier` (https://oidref.com/1.3.6.1.2.1.15.4),
[xxx@cap-ac] > system/routerboard/print
routerboard: yes
board-name: cAP ac
model: RBcAPGi-5acD2nD
revision: r2
serial-number: B9320BEXXXXX
firmware-type: ipq4000L
factory-firmware: 6.44
current-firmware: 7.9
upgrade-firmware: 7.9
Hello! Please, beware that some of these improvements make Chinese SFP modules (e.g. ONTi Gigabit RJ45 SFP module from Aliexpress) report temperature of 255 degrees which triggers SFP module disabling (for 10 minutes, but it repeats) since the default SFP shutdown temperature is 95 degrees. Thus, you may have problems connecting to your devices after this update if you use such modules.*) sfp - fixed "rate" monitor value for SFP interface on L009UiGS series devices;
*) sfp - fixed combo-ether link monitor for CRS328-4C-20S-4S+ switch;
*) sfp - fixed combo-sfp linking at 1G rate for CRS312 switch;
*) sfp - improved 10G interface stability for 98DX8208, 98DX8212, 98DX8332, 98DX3257, 98DX4310, 98DX8525, 98DX3255, 98PX1012 based switches;
*) sfp - improved module compatibility with bad EEPROM data for RB4011, RB5009, CCR2xxx, CRS312 and CRS518 devices;
*) sfp - improved Q/SFP interface stability for 98DX8208, 98DX8212, 98DX8332, 98DX3257, 98DX4310, 98DX8525, 98DX3255, 98PX1012 switches;
*) sfp - improved SFP interface handling for RB4011, RB5009, CCR2xxx and CRS518 devices;
*) sfp - improved system stability with certain SFP modules for CCR2216 and CRS518 devices;
*) sfp - report EEPROM data even if "auto-init-failed" has occurred;
Here it's working fine for IPv4 only. 99% of my network is ipv6 though.Does this actually work for you? I'm not getting any output for that oid when I do an snmpwalk, nor does Observium/LibreNMS get a list of BGP peers.
The thing is that for me that OID doesn't give any output at all :(Here it's working fine for IPv4 only. 99% of my network is ipv6 though.Does this actually work for you? I'm not getting any output for that oid when I do an snmpwalk, nor does Observium/LibreNMS get a list of BGP peers.
snmpwalk -v 1 -c <community> <router_ip> 1.3.6.1.2.1.15
Amen to that! :)Regarding observium/librenms, that's exactly why he's asking for bgpLocalAs and bgpIdentifier to enable observium's discovery feature.
.Where is /System/LCD settings on RB2011? Is ROS7 stop supporting it?
In rb4011 i have a poll error.RB4011 after update lost ovpn.
Connecting
Established
Disconndcted
<user> detect UNKNOWN
I am not sure how was before
Any ideas?
Fix for what issue?Fix for WiFi will be in 7.11 so stay at 7.8
can you read? read above in this topic....Fix for what issue?Fix for WiFi will be in 7.11 so stay at 7.8
Works fine here!
The thing is that for me that OID doesn't give any output at all :(
Code: Select allsnmpwalk -v 1 -c <community> <router_ip> 1.3.6.1.2.1.15
I got problems with DACs (Direct Attach cables) since the update.Hello! Please, beware that some of these improvements make Chinese SFP modules (e.g. ONTi Gigabit RJ45 SFP module from Aliexpress) report temperature of 255 degrees which triggers SFP module disabling (for 10 minutes, but it repeats) since the default SFP shutdown temperature is 95 degrees. Thus, you may have problems connecting to your devices after this update if you use such modules.*) sfp - fixed "rate" monitor value for SFP interface on L009UiGS series devices;
*) sfp - fixed combo-ether link monitor for CRS328-4C-20S-4S+ switch;
*) sfp - fixed combo-sfp linking at 1G rate for CRS312 switch;
*) sfp - improved 10G interface stability for 98DX8208, 98DX8212, 98DX8332, 98DX3257, 98DX4310, 98DX8525, 98DX3255, 98PX1012 based switches;
*) sfp - improved module compatibility with bad EEPROM data for RB4011, RB5009, CCR2xxx, CRS312 and CRS518 devices;
*) sfp - improved Q/SFP interface stability for 98DX8208, 98DX8212, 98DX8332, 98DX3257, 98DX4310, 98DX8525, 98DX3255, 98PX1012 switches;
*) sfp - improved SFP interface handling for RB4011, RB5009, CCR2xxx and CRS518 devices;
*) sfp - improved system stability with certain SFP modules for CCR2216 and CRS518 devices;
*) sfp - report EEPROM data even if "auto-init-failed" has occurred;
can confirm above is fixed. if you still have issues do these steps:RouterOS version 7.10 has been released in the "v7 stable" channel!
Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.
What's new in 7.10 (2023-Jun-15 08:17):
*) ssh - fixed RouterOS SSH client login when using a key (introduced in v7.9);
Sir, there is a funcionality for this already.<post for topic subscription>
Thank you for the new features, I can confirm that prefix count seems to work fine, but what does "bgp - show address family in advertisements" mean?RouterOS version 7.10 has been released in the "v7 stable" channel!
Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.
What's new in 7.10 (2023-Jun-15 08:17):
!) ipv6 - fixed DNS server processing by IPv6/ND services (CVE-2023-32154);
!) route - added BFD;
*) bgp - allow to filter BGP sessions by AFI;
*) bgp - changed default VPNv4 import distance to iBGP value (200);
*) bgp - do not check route distinguisher on import;
*) bgp - fixed "as-override" and rename to "output.as-override";
*) bgp - fixed "remove-private-as" and rename to "output.remove-private.as";
*) bgp - show address family in advertisements;
*) bgp - show approximate received prefix count by the session;
[admin@CCR1] > /routing/bgp/advertisements/print detail
[admin@CCR1] > /routing/bgp/advertisements/print count-only
0
In docs it says: "Features not yet supported [...] enabling BFD for ip route gateways"!) route - added BFD;
Yes, this has been an issue for me on CCR2004-16G-2S+ since a few releases ago (I think it started with 7.8). Luckily that device has a backup GbE into the network. But for a few releases the DAC has not been working for me anymore. I see RX traffic on it but nothing on the TX side.I got problems with DACs (Direct Attach cables) since the update.
Hello! Please, beware that some of these improvements make Chinese SFP modules (e.g. ONTi Gigabit RJ45 SFP module from Aliexpress) report temperature of 255 degrees which triggers SFP module disabling (for 10 minutes, but it repeats) since the default SFP shutdown temperature is 95 degrees. Thus, you may have problems connecting to your devices after this update if you use such modules.
They don't work anymore, both with auto-negociation and manual transfer rate setting.
One is Ipolex and other is HiFiber. Both don't work anymore. Very annoying ...
Ovpn client log show more info.In rb4011 i have a poll error.RB4011 after update lost ovpn.
Connecting
Established
Disconndcted
<user> detect UNKNOWN
I am not sure how was before
Any ideas?
Everything worked ok in previous version.
I get data in firewall > filter > input
but not in NAT record.
Usr/psw its ok but i get poll error.
What is this error?
I cant find anything for this.
Its the same issue from 7.10rc1:
viewtopic.php?p=1005699#p1005699
That is a very general statement you are stating. There are plenty of reports but not all can be attributed to ROS, many can be misconfiguration. When you say fix will come at 7.11, it is understood that some particular fix will come at 7.11.
What fix are you referring to? This release has several fixes on wifi wave2.
Clients can not connect WiFi only reboot will help. Check forum there is plenty of reports.
and many others*) wifiwave2 - fixed key handshake timeout with re-associating clients;
"Client exception in transport_recv: process_server_push_error: Problem accepting server-pushed peer-id: parse/range issue"
Same problem here...OVPN log:
⏎[Jun 15, 2023, 17:32:18] Client exception in transport_recv: process_server_push_error: Problem accepting server-pushed peer-id: parse/range issue
works well til 7.10
This is logs from stock openvpn client in android 13.1.Ovpn client log show more info.
In rb4011 i have a poll error.
Everything worked ok in previous version.
I get data in firewall > filter > input
but not in NAT record.
Usr/psw its ok but i get poll error.
What is this error?
I cant find anything for this.
Its the same issue from 7.10rc1:
viewtopic.php?p=1005699#p1005699
I have similar ovpn setup and I am back to 7.9.2 working fine again.
[Jun 15, 2023, 21:37:23] OpenVPN core 3.git:: android arm64 64-bit PT_PROXY
[Jun 15, 2023, 21:37:23] ----- OpenVPN Start -----
[Jun 15, 2023, 21:37:23] EVENT: CORE_THREAD_ACTIVE
[Jun 15, 2023, 21:37:23] Frame=512/2048/512 mssfix-ctrl=1250
[Jun 15, 2023, 21:37:23] EVENT: RESOLVE
[Jun 15, 2023, 21:37:26] Contacting .201:1194 via UDP
[Jun 15, 2023, 21:37:26] EVENT: WAIT
[Jun 15, 2023, 21:37:26] Connecting to [.sn.mynetname.net]:1194 (.201) via UDPv4
[Jun 15, 2023, 21:37:26] EVENT: CONNECTING
[Jun 15, 2023, 21:37:26] Tunnel Options:V4,dev-type tun,link-mtu 1601,tun-mtu 1500,proto UDPv4,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-client
[Jun 15, 2023, 21:37:26] Creds: Username/Password
[Jun 15, 2023, 21:37:26] Peer Info:
IV_VER=3.git::
IV_PLAT=android
IV_NCP=2
IV_TCPNL=1
IV_PROTO=30
IV_CIPHERS=AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305:AES-256-CBC
IV_GUI_VER=net.openvpn.connect.android_3.3.4-9290
IV_SSO=webauth,openurl,crtext
[Jun 15, 2023, 21:37:26] VERIFY OK: depth=1, /C=GR/ST=TH/L=T/O=HomeMikrotik/OU=changeme/CN=HomeMikrotikCA/name=changeme/emailAddress=mail@host.domain, signature: RSA-SHA1
[Jun 15, 2023, 21:37:26] VERIFY OK: depth=0, /C=GR/ST=TH/L=T/O=HomeMikrotik/OU=changeme/CN=server/name=changeme/emailAddress=mail@host.domain, signature: RSA-SHA1
[Jun 15, 2023, 21:37:26] SSL Handshake: peer certificate: CN=server, 1024 bit RSA, cipher: ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD
[Jun 15, 2023, 21:37:26] Session is ACTIVE
[Jun 15, 2023, 21:37:26] Sending PUSH_REQUEST to server...
[Jun 15, 2023, 21:37:26] EVENT: WARN info='TLS: received certificate signed with SHA1. Please inform your admin to upgrade to a stronger algorithm. Support for SHA1 signatures will be dropped in the future'
[Jun 15, 2023, 21:37:26] EVENT: GET_CONFIG
[Jun 15, 2023, 21:37:26] OPTIONS:
0 [redirect-gateway]
1 [dhcp-option] [DNS] [192.168.5.36]
2 [ping] [20]
3 [ping-restart] [60]
4 [topology] [subnet]
5 [route-gateway] [192.168.5.39]
6 [ifconfig] [192.168.5.115] [255.255.255.0]
7 [peer-id] [16777215]
[Jun 15, 2023, 21:37:26] Client exception in transport_recv: process_server_push_error: Problem accepting server-pushed peer-id: parse/range issue
[Jun 15, 2023, 21:37:26] Client terminated, restarting in 2000 ms...
[Jun 15, 2023, 21:46:52] ----- OpenVPN Stop -----
[Jun 15, 2023, 21:46:52] EVENT: CORE_THREAD_DONE
There's been some confusion with the naming, actual tx actually shows the value of the remote tx interval. But actual tx is actually picked the highest value as it should. Will be fixed in one of the next versions.BFD is working, but I think desired and actual TX/RX intervals are not working.
For now, all BGPs uptime for 19:10:13 without interruption....Put into production on CCR2116-12G-4S+ with 3 full BGP tables (2 IPv4 only, 1 IPv6 only)
No, I haven't gone crazy, I have multiple RouterBOARDs in HA on the same link...
I have the same problem, also found it in 7.10rc3 and reported it in the thread a few weeks back, bug still in 7.10 in the stable release :(RB4011 after update lost ovpn.
Connecting
Established
Disconndcted
<user> detect UNKNOWN
I am not sure how was before
Any ideas?
Client exception in transport_recv: process_server_push_error: Problem accepting server-pushed peer-id: parse/range issue
referSSH client seems a bit broken.
I use the mikrotik as a client to connect to something like a UniFi - it attempts a connection but it immediately quits. It doesn't get as far as asking for a login or password.
It works in 7.7
Edit: also works ok in 7.10rc1
Same. Downgraded and it works again...RB4011 after update lost ovpn.
Connecting
Established
Disconndcted
<user> detect UNKNOWN
Same here. Also stopped working Passepartout (iOS app) and other Mikrotik OpenVPN clients.OVPN log:
⏎[Jun 15, 2023, 17:32:18] Client exception in transport_recv: process_server_push_error: Problem accepting server-pushed peer-id: parse/range issue
works well til 7.10
Downgraded to 7.9.2 and everything is okSame here. Also stopped working Passepartout (iOS app) and other Mikrotik OpenVPN clients.OVPN log:
⏎[Jun 15, 2023, 17:32:18] Client exception in transport_recv: process_server_push_error: Problem accepting server-pushed peer-id: parse/range issue
works well til 7.10
In my router it seems to be accurate, noting that it includes prefixes discarded by the in-filter in the count (which v6 does not include). Prefixes filtered by the "Input accept NLRI" are not counted."bgp - show approximate received prefix count by the session;"
How much is this "approximate"? Is it a case of "we run a second thread to count this, so may be a little off if something changes during the count" or is it "we will count it one time, when the connection is made, and never again?"
How (in)exact is this number?
@mrz are there any know issues in 7.9 and 7.10 regarding L2TP and IPIP Tunnel + IPSec, which might cause this: viewtopic.php?p=1008075#p1008075There's been some confusion with the naming, actual tx actually shows the value of the remote tx interval. But actual tx is actually picked the highest value as it should. Will be fixed in one of the next versions.BFD is working, but I think desired and actual TX/RX intervals are not working.
what is the issue you are having?After upgrade to v7.10, seeing problems with switches using the 98DX8212 switch chip.
Ticket is SUP-119408
Switch is not detecting anymore an SFP ONT Sercomm FGS202. This use case is common for several users in France of a large ISP (Orange) who have replaced the vendor’s original hardware with MikroTik HW.what is the issue you are having?After upgrade to v7.10, seeing problems with switches using the 98DX8212 switch chip.
Ticket is SUP-119408
Ah, thanks. Looks like the "inaccurate" was just to prevent someone trying to debug something and taking the "count differs by two" seriously.In my router it seems to be accurate, noting that it includes prefixes discarded by the in-filter in the count (which v6 does not include). Prefixes filtered by the "Input accept NLRI" are not counted.
It also is re-calculated at least regularly (maybe everytime you request it?).
7.10 (almost) stable. Just get rid of OVPN and solves a bulk of issues.
I use these values (and I presume most people would) not as an indication if there are 400 or 401 routes via some peer, but to generallyAh, thanks. Looks like the "inaccurate" was just to prevent someone trying to debug something and taking the "count differs by two" seriously.
Or, in other words, "close enough for government work".
I proposed before that instead of these one-line change logs, MikroTik should put all changes in a database that has fields for this single line,I understand stable releases topics are read by people upgrading from stable to stable. in that case single big squashed changelog makes sense
People being in the testing train recevice "incremental" change log ( 1st post of the topic updated). this is also great
We only miss the last step: incremental changelog between last rc and stable. is stable identical to last rc or are there last minute changes ?
indeed. doesnt even show local & remote addresses*) ovpn - improved system stability;
not to sure what u mean by that. On v7.10 ovpn is totally broken
what exactly?ssh client broken , it even works well in 7.10rc serials
It may be stable for 99.9% of all the user. You will never ever find a 100% stable software. Not sure how many times the last 20+ years I have updated stable Cisco software due to bugs, sometimes serious bugs that takes down the network.This is unacceptable for a "stable" update channel
Is the same identical program just with the version number changed....What is the latest version of dude client ( x86 platform) ?
a see 7.10 - https://mikrotik.com/download, download and see inside 7.9....
terminals only understand characters,
Once again: "stable" in the name of the MikroTik releases does not mean the software itself is stable, in that it does not crash and does notIt may be stable for 99.9% of all the user. You will never ever find a 100% stable software.This is unacceptable for a "stable" update channel
Still all up and working without problems. (2d 16:54:56)For now, all BGPs uptime for 19:10:13 without interruption....Put into production on CCR2116-12G-4S+ with 3 full BGP tables (2 IPv4 only, 1 IPv6 only)
No, I haven't gone crazy, I have multiple RouterBOARDs in HA on the same link...
No need to change the changelog structure, In the last "locking post" in RC topic, just add the changelog between last rc and stable or "stable is the same as rxX" and "that's it"I proposed before that instead of these one-line change logs, MikroTik should put all changes in a database that has fields for this single line,I understand stable releases topics are read by people upgrading from stable to stable. in that case single big squashed changelog makes sense
People being in the testing train recevice "incremental" change log ( 1st post of the topic updated). this is also great
We only miss the last step: incremental changelog between last rc and stable. is stable identical to last rc or are there last minute changes ?
for a pointer to relevant documentation (page in the help site), a possible warning related to the change ("date format has changed, you will
need to adapt your scripts when they use the system date"), a longer description of the change when relevant (what exactly has been fixed),
etc. And then there should be a webpage where you can input two different version numbers, and the output will be the change list as we get
now, but "between those two versions"). With clickable items to send you to documentation or more info.
I think it should not be more work than what we get now, but it would be much more usable. And the old style plain text one-line lists can
be automatically generated from this for the changes list displayed by the device itself.
When common sense isn't enough...This forum is not reddit...
By accessing “MikroTik” (hereinafter “we”, “us”, “our”, “MikroTik”, “https://forum.mikrotik.com”), you agree to be legally bound by the following terms. If you do not agree to be legally bound by all of the following terms then please do not access and/or use “MikroTik”. We may change these at any time and we’ll do our utmost in informing you, though it would be prudent to review this regularly yourself as your continued usage of “MikroTik” after changes mean you agree to be legally bound by these terms as they are updated and/or amended. Our forums are powered by phpBB (hereinafter “they”, “them”, “their”, “phpBB software”, “www.phpbb.com”, “phpBB Limited”, “phpBB Teams”) which is a bulletin board solution released under the “GNU General Public License v2” (hereinafter “GPL”) and can be downloaded from www.phpbb.com. The phpBB software only facilitates internet based discussions; phpBB Limited is not responsible for what we allow and/or disallow as permissible content and/or conduct. For further information about phpBB, please see: https://www.phpbb.com/. You agree not to post any abusive, obscene, vulgar, slanderous, hateful, threatening, sexually-orientated or any other material that may violate any laws be it of your country, the country where “MikroTik” is hosted or International Law. Doing so may lead to you being immediately and permanently banned, with notification of your Internet Service Provider if deemed required by us. The IP address of all posts are recorded to aid in enforcing these conditions. You agree that “MikroTik” have the right to remove, edit, move or close any topic at any time should we see fit. As a user you agree to any information you have entered to being stored in a database. While this information will not be disclosed to any third party without your consent, neither “MikroTik” nor phpBB shall be held responsible for any hacking attempt that may lead to the data being compromised.
Fixed it for ya........
You agree not to post any abusive, obscene, vulgar, slanderous, hateful, threatening, sexually-orientated, negative feline comments
or any other material that may violate.......
My proposal also solves the issue where people upgrade from version x.y to x.y+2 in one jump, read the x.y+2 change notes (that are displayed on their screen as part of the upgrade process), but have never seen the x.y+1 change notes and the important information and warnings it contains.
My friend, I'm curious as to why you're opposed to OVPN and actively seeking its removal from RouterOS. However, a simple poll would reveal that a significant number of RouterOS users rely on OVPN. Why, you ask? It's because in areas and countries with high levels of restriction, OVPN is often the last and only solution that works. Additionally, it's highly compatible with a wide range of operating systems and devices, making it a versatile choice for many users.7.10 (almost) stable. Just get rid of OVPN and solves a bulk of issues.
Hi Jax, thanks for taking the time to make a thoughtful reply. I didnt know that was the case ( last hope for VPN in some areas ) and if so, then agree the ongoing lack of focus to fix the issues is more than annoying, its disrespectful.My friend, I'm curious as to why you're opposed to OVPN and actively seeking its removal from RouterOS. However, a simple poll would reveal that a significant number of RouterOS users rely on OVPN. Why, you ask? It's because in areas and countries with high levels of restriction, OVPN is often the last and only solution that works. Additionally, it's highly compatible with a wide range of operating systems and devices, making it a versatile choice for many users.7.10 (almost) stable. Just get rid of OVPN and solves a bulk of issues.
Yes, read the forum... many people reported this bug. It is in 7.9 and 7.10. You should downgrade to 7.8Upgraded both my RB4011 and HAP AX3 using as AP.
RB4011 (Wifi) - stable on 7.9 and 7.10 via LAN and Wifi.
HAP AX3 i upgraded from 7.8 because 7.9 was very unstable with constant Wifi disconnections, random restarts so had to downgrade to 7.8. But even on 7.10 i'm still having the same issue. Downgrading to 7.8 its stable. I have connected Hap Ax3's Ether1 port to ether10 POE port of RB4011 so made my ether1 port of hap ax3 as LAN. DHCP on bridge(ether1, wifi2g, wifi5g). Wifi works for some 30mins then none of my devices are getting connected Mac, iPhone, Homepod, PS5, TV etc until i reboot the ax3.
Is anyone else having the same problem?
Yeah i have downgraded to 7.8 :(Yes, read the forum... many people reported this bug. It is in 7.9 and 7.10. You should downgrade to 7.8Upgraded both my RB4011 and HAP AX3 using as AP.
RB4011 (Wifi) - stable on 7.9 and 7.10 via LAN and Wifi.
HAP AX3 i upgraded from 7.8 because 7.9 was very unstable with constant Wifi disconnections, random restarts so had to downgrade to 7.8. But even on 7.10 i'm still having the same issue. Downgrading to 7.8 its stable. I have connected Hap Ax3's Ether1 port to ether10 POE port of RB4011 so made my ether1 port of hap ax3 as LAN. DHCP on bridge(ether1, wifi2g, wifi5g). Wifi works for some 30mins then none of my devices are getting connected Mac, iPhone, Homepod, PS5, TV etc until i reboot the ax3.
Is anyone else having the same problem?
Far from it. The implementation of OVPN used by Mikrotik is... not great. But the VPN itself is quite good, and have several capabilities that are usefull. One of them is easy of use when dealing with a huge number of clients - since one can force configurations on them, and they can be made by templates. Another is the use of signed certificates - that is another great thing in several situations.I thought ovpn was something cooked up by those using non ipsec routers and using merlin and other after market hack firmwares to emulate VPN. With the advent of wireguard I saw no purpose for a hack job VPN. Wireguard is also cross platform. Are you saying that OVPN is possible where Wireguard is not? I would have thought zerotier a much better solution for such difficult situations?
viewtopic.php?t=196619#p1005390I thought ovpn was something cooked up by those using non ipsec routers and using merlin and other after market hack firmwares to emulate VPN.
[admin@RB4011] > /certificate/enable-ssl-certificate dns-name=my4011.duckdns.org
progress: [error] could not resolve 'my4011.duckdns.org'
[admin@RB4011] > :put [ :resolv my4011.duckdns.org ]
240e:xxxx:xxxx:xxxx::1
same hereAfter the upgrade to v7.10 (stable). The ovpn client will no longer emerge into the the ip/address table. Also there will be a missing entry in the routing table, i.e. there is no gateway. Due to this, the router is no longer able to exchange ip packets between the network and the ovpn client.
wht will be the advantage of this feature. We are planning to use crs 317 for mpls/vpls . Will it benefit in P case scenariompls - added FastPath support;
It does eventually show the IPv6 routes, but I have to wait several minutes for it to work through all the IPv4 routes.Yes that is correct, it seems that the IP->Routes and IPv6->Routes views are just "filters" on a single table with all the routes.
However, there seems to be a problem in your case. In my router I *do* see the IPv6 routes in that window.
(but then it shows "22 items out of 1180" where 1180 is the total number of routes for IPv4 and IPv6)
Doesn't it show the routes after it has finished the counting?
Well, I think not. But at the moment it seems to be how it works.It does eventually show the IPv6 routes, but I have to wait several minutes for it to work through all the IPv4 routes.
Is it supposed to be like that?
This seems to have fixed that problem for me:I also have a problem with my hAP AX3
Wi-Fi disappears and the log gives an error: key handshake timeout
Solved the problem by rolling back to 7.8
.After the upgrade to v7.10 (stable). The ovpn client will no longer emerge into the the ip/address table. Also there will be a missing entry in the routing table, i.e. there is no gateway. Due to this, the router is no longer able to exchange ip packets between the network and the ovpn client.
BFD activated or BFD not in use at the moment?Still all up and working without problems. (2d 16:54:56)
For now, all BGPs uptime for 19:10:13 without interruption....
ospf-1 { version: 2 router-id: 192.168.77.1 } ospf-area-1 { 0.0.0.0 } interface { p2p 172.16.18.1%wireguard3 } neighbor { router-id: 192.168.100.2 state: Full } crypto sequence invalid
It's a general statement for sure. But 7.10 still has some major issue with wifiwave2 at least on the hap ax^[2|3].
That is a very general statement you are stating. There are plenty of reports but not all can be attributed to ROS, many can be misconfiguration. When you say fix will come at 7.11, it is understood that some particular fix will come at 7.11.
Hi..After the upgrade to v7.10 (stable). The ovpn client will no longer emerge into the the ip/address table. Also there will be a missing entry in the routing table, i.e. there is no gateway. Due to this, the router is no longer able to exchange ip packets between the network and the ovpn client.
I *cannot* confirm that ... everything working just fine here with v7.10 as openvpn-client on several (about 30) boxes of different models. And overal, ovpn-client seems pretty stable now, after the v7.8 nightmare has ended.
#sh ipv6 bgp neighbors 1011::15 advertised-routes
There are 174824 routes advertised to neighbor 1011::15
routing-table=peerings nexthop-choice=force-self multihop=yes hold-time=1m30s keepalive-time=30s uptime=20h36m51s880ms last-started=2023-06-19 03:25:31 last-stopped=2023-06-19 03:25:21 prefix-count=4294909605
.What do you mean 'boxes'? Other mikrotik routers?. Do you try ovpn clients on other OSes like Android/Windows/Linux?
I can't confirm this. After upgrading no OpenVPN is coming up on my RouterBoard. All clients are Mikrotik RouterBoards with different V6 FW. This issue occurs also with 6.49.8.I *cannot* confirm that ... everything working just fine here with v7.10 as openvpn-client on several (about 30) boxes of different models. And overal, ovpn-client seems pretty stable now, after the v7.8 nightmare has ended.
Regarding the OVPN issue with "Problem accepting server-pushed peer-id: parse/range issue"! We have managed to reproduce the problem and are working on a fix for it.
We have introduced several improvements regarding the AX stability. It is still a work in progress, but in order to gather more feedback as soon as possible, here is a link to the latest alpha version that contains these fixes. The fixes are mainly targeted at the issue discussed in this thread - the inability of WifiWave2 interfaces to authenticate the clients.
Please treat it with caution. If you experience any wireless-related issues with this alpha build, then let us know at support@mikrotik.com
https://box.mikrotik.com/d/e700b4d034174bce8a22/
I don't know why MikroTik calls it “stable”, when it's really beta, and why they call it beta when it's really alpha.Well...
[admin@MikroTik] /interface/bridge> export
# 2023-06-20 06:33:15 by RouterOS 7.10
# software id = 1839-P0T5
#
# model = CCR2004-16G-2S+
# serial number = HDD085GSQZX
/interface bridge
add ingress-filtering=no name=bridge priority=0 vlan-filtering=yes
[admin@MikroTik] /routing> export
# 2023-06-20 06:38:09 by RouterOS 7.10
# software id = 1839-P0T5
#
# model = CCR2004-16G-2S+
# serial number = HDD085GSQZX
/routing id
add disabled=no id=x.x.x.x name=x.x.x.x select-dynamic-id="" select-from-vrf=main
/routing ospf instance
add disabled=no name=ospf-instance-1 originate-default=never redistribute="" router-id=x.x.x.x routing-table=main
/routing ospf area
add disabled=no instance=ospf-instance-1 name=ospf-area-1
/routing ospf interface-template
add area=ospf-area-1 auth=md5 auth-id=1 auth-key=comm2000 disabled=no interfaces=sfp1.vlan2001
add area=ospf-area-1 disabled=no interfaces=bridge,vlan5,vlan15,vlan30 passive
Ive seen you post this several times that you have 2 RB's in HA. One with v6 and the other on the latest v7. Just curious, how are you doing this? VRRP?Put into production on CCR2116-12G-4S+ with 3 full BGP tables (2 IPv4 only, 1 IPv6 only)
No, I haven't gone crazy, I have multiple RouterBOARDs in HA on the same link...
Only arm and arm64 in that link (probably because those are the wifiwave2 capable platforms).If you read some post up in the thread, there is a download link. Post by wispmikrotik
Has anyone tried this functionality? Counters associated with fast-path in /mpls/settings/ are kept at zero:*) mpls - added FastPath support;
[admin@LSR] > mpls/settings/print
dynamic-label-range: 16-1048575
propagate-ttl: yes
allow-fast-path: yes
mpls-fast-path-packets: 0
mpls-fast-path-bytes: 0
I confirm this is still happening in v7.101) remove any public and private keys
2) downgrad to 7.8
3) import both public and private keys , ssh client is OK
4) upgrade to 7.10
5) ssh client OK
but If remove all key and re-import in 7.10, ssh client broken.
In 7.10. letsencrypt broken again? my duckdns.org dynamic domain name only has a AAAA ipv6 address .
/ip dns static set [find where address-list!=""] address-list=""
I am seeing this too, the dates shown in webfig are one day behind the real date which was totally confusing. Checked via the console and the date and time are correct there. Version 7.10 on 2 different devices.Also they know that are a problem on dates show on webfig, and I just found that it depends of your browser timezone.Why is a stable version released with a half-hearted implementation of the change in time format?
I think it is a good change in principle, but it seems controversial for scripting (discussion elsewhere) and now we have a mix of formats all over the place.
Would it not be better to make the complete change, or roll back when it cannot be completed, at the point of stable release?
[admin@jupiter] > /log/print
[...]
06-20 09:04:34 ssh,info publickey accepted for user: admin
[...]
I can confirm this , if the clients are added to a bridge , from profile , there is no ip entry or route to them. When they are not included in the bridge you can reach them .same hereAfter the upgrade to v7.10 (stable). The ovpn client will no longer emerge into the the ip/address table. Also there will be a missing entry in the routing table, i.e. there is no gateway. Due to this, the router is no longer able to exchange ip packets between the network and the ovpn client.
Hello Anav, I haven't had much experience with Wireguard as it is often blocked by certain ISPs, areas, or countries in the networks I work with. However, there may be some advanced settings that can be adjusted to make it work. Regarding Zerotier, I have heard a lot about it but have not yet had the opportunity to explore it. I am hopeful that MikroTik will add it to their offerings, as more options are always better. With their packages, the possibilities are endless. If the MikroTik team cannot keep up with demand, perhaps it is time to consider going semi or completely open source and allowing the community to build what they need.Hi Jax, thanks for taking the time to make a thoughtful reply. I didnt know that was the case ( last hope for VPN in some areas ) and if so, then agree the ongoing lack of focus to fix the issues is more than annoying, its disrespectful.
My friend, I'm curious as to why you're opposed to OVPN and actively seeking its removal from RouterOS. However, a simple poll would reveal that a significant number of RouterOS users rely on OVPN. Why, you ask? It's because in areas and countries with high levels of restriction, OVPN is often the last and only solution that works. Additionally, it's highly compatible with a wide range of operating systems and devices, making it a versatile choice for many users.
I thought ovpn was something cooked up by those using non ipsec routers and using merlin and other after market hack firmwares to emulate VPN. With the advent of wireguard I saw no purpose for a hack job VPN. Wireguard is also cross platform. Are you saying that OVPN is possible where Wireguard is not? I would have thought zerotier a much better solution for such difficult situations?
In any case, I will no longer mention OVPN in a negative light, and come on Mikrotik FIX IT ALREADY!! Then add zerotrust cloudflare tunnel!!
There is a simple solution to this. Why not use the 21 !!!!! year old standard for time format?I do not think this is expected... Can we have the year in logs, please? (Time only for the current day is ok, but just part of the date is a no-go.)
By the way... Why do the lines start with a space?Code: Select all[admin@jupiter] > /log/print [...] 06-20 09:04:34 ssh,info publickey accepted for user: admin [...]
(because month/day are xxx/xx on previous format, etc.)By the way... Why do the lines start with a space?
However the year should not be stripped.
IMO the whole date-gate disaster should be fixed once and for all.
Hi,Anyone who has upgraded to 7.10 and encounters DNS crashes,
can try using the following code to disable the dns-to-address-list configuration first:
It is known that version 7.10, due to the addition of endpoint-independent-nat, involves major changes to the firewall.Code: Select all/ip dns static set [find where address-list!=""] address-list=""
This causes the dns-to-address-list interaction feature to induce DNS crashes.
Thanks.There are no major changes in firewall.
This DNS issue has nothing to do with the firewall. The issue is caused by static entries with the address-list option enabled. The issue is reproduced and will be resolved as soon as possible.Anyone who has upgraded to 7.10 and encounters DNS crashes,
can try using the following code to disable the dns-to-address-list configuration first:
It is known that version 7.10, due to the addition of endpoint-independent-nat, involves major changes to the firewall.Code: Select all/ip dns static set [find where address-list!=""] address-list=""
This causes the dns-to-address-list interaction feature to induce DNS crashes.
Doesn't seem like it.*) wireguard - fixed IPv6 traffic processing with multiple peers;
These networks do not overlap, no? If they do the behavior is expected.The issue remains if the allowed-address set on the router is an ipv6 /64.
Wait, do the allowed-address ranges of your peers overlap or are they even identical? If so, I would be surprised if it where supported.Doesn't seem like it.*) wireguard - fixed IPv6 traffic processing with multiple peers;
The issue remains if the allowed-address set on the router is an ipv6 /64.
It works but only if that peer is the most recently enabled.
If another peer is enabled, the 1st will stop working on ipv6.
If the allowed-address is a /128 however the bug does seem to disappear. I can disabled/re-enable other peers no problem.
ROS 7.10 seems that Check Gateway = ping/arp/bfd does not work any more. In IP / Route, Check Gateway = ping/arp/bfd will result in Check Gateway Ok. Unchecked and all connections will be routing through main only.
But for sure you do not read.maybe i wrote not clearly:
Well, it probably shouldn't do that. But...you might want to try manually adding the wifiwave2 package from https://download.mikrotik.com/routeros/ ... 1beta2.zip – that will have wifiwave2.npk that you can copy to Files on router and reboot – see if that at least fixes it.Second piece - just taken out of the box, moved routeros-7.10-arm64.npk package to files, system - reboot.
after reboot - lost wifi
Be careful with version mismatches ...Well, it probably shouldn't do that. But...you might want to try manually adding the wifiwave2 package from https://download.mikrotik.com/routeros/ ... 1beta2.zip – that will have wifiwave2.npk that you can copy to Files on router and reboot.
*) upgrade - do not run manual upgrade if some packages are missing;
I guess I thought this release notes was about this very case, perhaps not.*) upgrade - do not run manual upgrade if some packages are missing;
Well...that's fair enough.this was implemented from 7.10, not beforeI guess I thought this release notes was about this very case, perhaps not.
OVPN fixed ???Please rename header on this thread to v7.10.1 [stable] is released! or do as you normally do, post a new thread for a new release.
All previous stable has its own thread.Why?? This is still stable 7.10. Do you want for every small update new thread? That is nonsence
#Software: Microsoft Internet Information Services 7.5
#Version: 1.0
#Date: 2023-06-28 06:57:10
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
2023-06-28 06:57:10 10.1.1.200 GET /*******CA.crl - 80 - *.*.*.* Mikrotik/7.x+Fetch 200 0 0 93
#Software: Microsoft Internet Information Services 7.5
#Version: 1.0
#Date: 2023-06-28 07:57:10
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
2023-06-28 07:57:10 10.1.1.200 GET /*******CA.crl - 80 - *.*.*.* Mikrotik/7.x+Fetch 200 0 0 140
#Software: Microsoft Internet Information Services 7.5
#Version: 1.0
#Date: 2023-06-28 08:57:11
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
2023-06-28 08:57:11 10.1.1.200 GET /*******CA.crl - 80 - *.*.*.* Mikrotik/7.x+Fetch 200 0 0 124
A certificate revocation list (CRL) is a list of digital certificates that have been revoked by the issuing certificate authority (CA) before their actual or assigned expiration date.
Just updated my reply...hope it makes more sense.O.K. maybe i'm wrong, but what means and for what reason there are "Next update" field in crl?
Nope. Anything going out to OVPN interface is marked "invalid" by ROS' firewall. Even if they are properly routed and NAT'ed.OVPN fixed ???
On ROSv7.10, neither method works. Downgraded to ROSv7.9.2 and method 2 works fine.What does link has to do with your problem? Please post config.
#Method 1#
add action=endpoint-independent-nat chain=srcnat out-interface-list=WAN protocol=udp randomise-ports=no src-address=192.168.0.0/24 to-addresses=1.1.1.1
add action=endpoint-independent-nat chain=dstnat dst-address=1.1.1.1 in-interface-list=WAN protocol=udp randomise-ports=no to-addresses=192.168.0.0/24
add action=netmap chain=srcnat ipsec-policy=out,none out-interface-list=WAN src-address=192.168.0.0/24 to-addresses=1.1.1.1
#Method 2#
add action=netmap chain=dstnat in-interface-list=WAN protocol=udp dst-port=1024-65535 dst-address=1.1.1.1 to-addresses=192.168.0.2
add action=netmap chain=srcnat ipsec-policy=out,none out-interface-list=WAN src-address=192.168.0.0/24 to-addresses=1.1.1.1
/interface ovpn-client
add certificate=client_test.crt_0 cipher=aes256-cbc connect-to=xxx.xxx.xxx.xxx mac-address=02:4F:B6:A7:4B:B8 max-mtu=1400 name=ovpn-out1-far \
port=12333 profile=openvpn-test.net protocol=udp user=test
I have the same OVPN-Issue, with 7.10 and 7.10.1.RB4011 after update lost ovpn.
Connecting
Established
Disconndcted
<user> detect UNKNOWN
I am not sure how was before
Any ideas?
WTF isn't that a bit too much for the hap ac 3 hardware?+1
hAP ac^3
OpenVPN (UDP)
over ~ 6000 push route
WTF isn't that a bit too much for the hap ac 3 hardware?+1
hAP ac^3
OpenVPN (UDP)
over ~ 6000 push route
*) ovpn - added AES-GCM and multicore encryption support;
*) ovpn - improved server stability;
*) ovpn - improved TLS-related error logging;
Same here. Have to create an up and down script in the ovpn profile to set a route to the connection+1 for the issue reported by Ocean. After updating to 7.10.1 from 7.10 OVPN has stopped working, Connection initially established but no traffic through tunnel, and then connection gets dropped due to inactivity timeout (ping restart)
UPDATE: Just checked and am getting the same OVPN issue in release 7.11beta2
Revert to 7.10 and it works again
:local ip [/ppp active get [find name=$user] address]
:local id [/ppp active get [find name=$user] name]
:local gt [/interface/ovpn-server get [find user=$id] name];
/ip/route/add disabled=no distance=1 dst-address=$ip gateway=$gt routing-table=main scope=10 suppress-hw-offload=no target-scope=10 comment="$gt";
/ip/route/remove [find comment="<ovpn-$user>"];
sry, figured it out. queue tree on bridge introduced the error. did not expect this traffic would leave the bridge...Are there any known issues regarding DHCP and mikrotik CPE (wireless bridge) in this version? I have 2 mikrotik devices in CPE mode and the clients connected to them on Ethernet do not receive an IP address anymore. And log on the AP is flooded with messages like "defconf offering lease 192.168.0.2 for 00:1D:EC:06:13:15 without success"
Working fine for meSince this Update my OpenVPN Windows Clients are unable to connect. Mikrotik to Mikrotik with OpenVPN is working. Anyone else see this Problem?
Yes , and it sends escape sequence, not key.terminals only understand characters,
We’ve had F1 on ANSI X3.64 compatible terminals at least since the VT220, released in 1983. If you’re using a terminal emulator that can’t send F1, get a better terminal emulator; they’re plentiful.
F1 is almost universally used as an HELP key for terminal application itself
For example mate terminal, previous gnome terminal as I remember...What is this universal you speak of, then?
For example mate terminal, previous gnome terminal as I remember...
/routing ospf area
add area-id=0.0.0.10 name=site3
/routing ospf instance
set [ find default=yes ] router-id=100.127.255.10 use-dn=no
/routing ospf area range
add area=site3 range=192.168.10.0/24
/routing ospf interface
add authentication=md5 authentication-key=secret dead-interval=10s hello-interval=1s interface=vpn network-type=point-to-point
add interface=vlan1 passive=yes
add interface=vlan666 passive=yes
add interface=vlan667 passive=yes
/routing ospf network
add area=backbone network=100.127.252.36/30
add area=site3 network=100.127.255.10/32
add area=site3 network=192.168.10.0/24
/routing ospf instance
add disabled=no in-filter-chain=ospf-in name=ospf_v2 router-id=100.127.255.10 use-dn=no
/routing ospf area
add disabled=no instance=ospf_v2 name=backbone_v2
add area-id=0.0.0.10 disabled=no instance=ospf_v2 name=site3_v2
/routing ospf area range
add area=site3_v2 disabled=no prefix=192.168.10.0/24
/routing ospf interface-template
add area=backbone_v2 auth=md5 auth-id=1 auth-key=secret cost=10 dead-interval=10s disabled=no hello-interval=1s \
networks=100.127.252.36/30 type=ptp
add area=site3_v2 disabled=no networks=100.127.255.10/32,192.168.10.224/28,192.168.10.240/28 passive
It can check gateway on PPPoE link and other connection such as wireguard interface with v7.8 but it does not work after my Hex S upgraded to v7.10, not only on PPPoE but also any other link.You cannot have "check gateway" on a PPPoE link. And it makes no sense anyway, as the PPPoE protcol is performing that action by itself, and the interface will go down when the link fails, taking all routes configured like that with it.
OSPF was down the following morning, had to also change point-to-point to broadcast, to get it to form adjacency again (yes, this required the other end to also be reconfigured to broadcast as well).OSPF MD5 problem, if I disable authentication it reaches full adjacency.
Hi could you please send me links to thread where it is discussed. ?I have same issue but with Iphone + Android and Windows 10 too.Yes, read the forum... many people reported this bug. It is in 7.9 and 7.10. You should downgrade to 7.8Upgraded both my RB4011 and HAP AX3 using as AP.
RB4011 (Wifi) - stable on 7.9 and 7.10 via LAN and Wifi.
HAP AX3 i upgraded from 7.8 because 7.9 was very unstable with constant Wifi disconnections, random restarts so had to downgrade to 7.8. But even on 7.10 i'm still having the same issue. Downgrading to 7.8 its stable. I have connected Hap Ax3's Ether1 port to ether10 POE port of RB4011 so made my ether1 port of hap ax3 as LAN. DHCP on bridge(ether1, wifi2g, wifi5g). Wifi works for some 30mins then none of my devices are getting connected Mac, iPhone, Homepod, PS5, TV etc until i reboot the ax3.
Is anyone else having the same problem?
do you mean:Now you can upgrade to 7.11 beta4 there is fix for the WiFi issue
*) wifiwave2 - fixed interface hangs on IPQ6010-based boards (introduced in v7.9);
Can you give me a list of software that you have that do not have any bug?build 7.10 and 7.10.1 is no stable... is BUGGED release.
You read previos comments other customers? You answer to get +1 message counter?Can you give me a list of software that you have that do not have any bug?
For me 7.10 and 7.10.1 works fine.
I guess that MTs goal is to make a bug free stable software as possible.
Look at Cisco, there you pay for upgrade, and its still not bug free. Here its free for you to use.
Again, and I have written this already so many times here, "stable" does not mean "the software is stable, it has no bugs, it will not crash" but rather it means "we are not tinkering with it all the time, no new release every week, at some point we make a .1 release which fixes the most apparent bugs".This is "stable" release and they have critical issues. You have testing releases and RC releases - go and do anything. But in stable releases... with no fixes in few days.
Windows 11 is considered stable
Have you considered asking the manufacturer of that device? What firmware version are you using on it? When looking at the forum, quite some of its users are in total despair about the firmware quality, so maybe it has some part of the blame.The device connected to ether1 remains the U6-Enterprise.
Yes, it promises to fix the WiFi problem. So hopefully it does that, for those affected by it (I am not).There is ver 7.10.2 out on the web site ;-)
Who approved this change?What's new in 7.10.1 (2023-Jun-27 12:03):
*) ovpn - fixed OVPN server peer-id negotiation;
*) webfig - use router time zone for date and time;
11:54:44 AM - Ack successfully written to LINK for packetId 5
11:54:44 AM - Reasserting flag cleared
11:54:44 AM - Tunnel interface is now UP
11:54:44 AM - Trigger shutdown (error: Error Domain=TunnelKitOpenVPN Code=302 "(null)")
11:54:44 AM - Session did stop with error: Error Domain=TunnelKitOpenVPN Code=302 "(null)"
11:54:44 AM - Failed LINK read: Error Domain=NSPOSIXErrorDomain Code=57 "Socket is not connected"
11:54:44 AM - Socket state is cancelled (endpoint: <masked> -> in progress)
11:54:44 AM - Cleaning up...
11:54:44 AM - Tunnel did stop (error: Error Domain=TunnelKitOpenVPN Code=302 "(null)")
11:54:44 AM - Dispose tunnel in 1000 milliseconds...
11:54:45 AM - Flushing log...
11:54:46 AM - Cleaning up...
What's new in 7.10.2 (2023-Jul-12 12:45):
*) wifiwave2 - fixed interface hangs on IPQ6010-based boards (introduced in v7.9);
From where is this changelog? i cant find it nowhere what is changes into that version.Code: Select allWhat's new in 7.10.2 (2023-Jul-12 12:45): *) wifiwave2 - fixed interface hangs on IPQ6010-based boards (introduced in v7.9);
Just tested 7.10.2 stable and works good for me. Also noticed that into this build Wifi Led on hAP AX3 now shows activity (led blinks when traffic is made via some of wifi interfaces).https://mikrotik.com/download/changelogs
Top of the page since 7.10.2 is now latest version for stable for ROS7.
What's new in 7.10.2 (2023-Jul-12 12:45):