Please keep this forum topic strictly related to this particular RouterOS release.
Tested with: RB2011UiAS on v7.9. Netwatch is running fine (after the 5 min delay)Netwatch not working on RB2011UiAS-2HnD !!!
.*) webfig - added inline comments;
yeah it's working after rebooting.Tested with: RB2011UiAS on v7.9. Netwatch is running fine (after the 5 min delay)Netwatch not working on RB2011UiAS-2HnD !!!
Why? Genuinely curious as to why anyone would use WebFig over Winbox if they have the option to use Winbox.Being a person that uses the webfig much more than winbox, this change:
/routing bgp connection
add address-families=vpnv4 as=65000 disabled=no local.address=10.10.1.4 \
.role=ibgp name=to_R3 remote.address=10.10.1.5/32 routing-table=mpls \
templates=default vrf=mpls
/routing bgp vpn
add disabled=no export.route-targets=65000:1 import.route-targets=65000:1 \
label-allocation-policy=per-vrf name=bgp-mpls-vpn-1 route-distinguisher=\
65000:1 vrf=cust1
Personal preference? I prefer CLI over Winbox/webfig.Genuinely curious as to why anyone would use WebFig over Winbox if they have the option to use Winbox.
Someone told me it works on my computer.upgraded from 7.6 (x86), looks like "PPPoE Scan" is broken
Someone told me that is broken from 7.8
Can someone elaborate what this line fixes please?dhcpv4-server - release lease if "check-status" reveals no conflict;
.Why? Genuinely curious as to why anyone would use WebFig over Winbox if they have the option to use Winbox.
Does that someone happen to be you!!!Someone told me it works on my computer.upgraded from 7.6 (x86), looks like "PPPoE Scan" is broken
Someone told me that is broken from 7.8
hAP ac^2 item "Sector writes" is present. But the item "Bad Blocks" is missing*) winbox - fixed missing "Sector Writes" for certain devices under "System/Resources" menu (introduced in v7.8 );
Considering I complained about this on the CRS310 very recently, I was pretty happy to see this implemented already... sadly it doesn't appear to work, at least on this particular model.*) health - added limited manual control over fans for CRS3xx, CRS5xx, CCR2xxx devices
I don't know specifically, but it comes with a 4 pin fan, and has a 4 pin header.Does the hardware has pwm speed control of some sorts? Otherwise you can wait until year 2500 for software solution.
I can see there are traces on pin 4 (PWM) but I can't trace them very far and I don't think the PCB is double sided. Doesn't look promising.That tells not much on pcb setup. I can put 4 pins anywhere and connect only 2. You can have a detailed look to the pcb.
I use the web interface from multiple Macs and my iPhone all day long. Winbox has its place, but can be finicky at times where the web browser from most any device "just works."Why? Genuinely curious as to why anyone would use WebFig over Winbox if they have the option to use Winbox.Being a person that uses the webfig much more than winbox, this change:
It's way off topic for this thread of course, but I can't stand Winbox. The windowed and tabular format for sub-config items drives me mad. Don't know why, it just does.Why? Genuinely curious as to why anyone would use WebFig over Winbox if they have the option to use Winbox.Being a person that uses the webfig much more than winbox
Try yourself.Anybody know if the DHCP server on 7.9 stable is borking stuff like Google Nest Doorbell DHCP requests?
Me too... "PPPoE Scan" feature broken (tested with RouterOS 7.9 on 4011 and ChateauLTE12)upgraded from 7.6 (x86), looks like "PPPoE Scan" is broken
Someone told me that is broken from 7.8
Winbox needs to be installed, WebFig is available using pre-installed browser. So why even bother with Winbox ?Why? Genuinely curious as to why anyone would use WebFig over Winbox if they have the option to use Winbox.Being a person that uses the webfig much more than winbox, this change:
Because it can be used with MAC addresses as well as via IP. Well...at least for me this is one of the reasons for using Winbox.Winbox needs to be installed, WebFig is available using pre-installed browser. So why even bother with Winbox ?
There's no installer, it's just a stand alone executable you can run from anywhere, but to each their own, nothing wrong with using webfig, though I do agree that Winbox is generally preferred and more versatile, they will both get the job done.Winbox needs to be installed, WebFig is available using pre-installed browser. So why even bother with Winbox ?
Why? Genuinely curious as to why anyone would use WebFig over Winbox if they have the option to use Winbox.
Yes, it’s still broken.Me too... "PPPoE Scan" feature broken (tested with RouterOS 7.9 on 4011 and ChateauLTE12)upgraded from 7.6 (x86), looks like "PPPoE Scan" is broken
Someone told me that is broken from 7.8
are you experiencing memory leak on v7.8 ?Getting many packet loss to router after upgrading on CR2004-16G-2S+. Downgrading to 7.8 fixed it.
:-(are you experiencing memory leak on v7.8 ?Getting many packet loss to router after upgrading on CR2004-16G-2S+. Downgrading to 7.8 fixed it.
I am going to update ccr2004 to v7.9 only because of memory leak issue.
no, tried disabling all services one by one.:-(
are you experiencing memory leak on v7.8 ?
I am going to update ccr2004 to v7.9 only because of memory leak issue.
Do you suspect any service reponsible of this memory leak?
Pingflood testWhere do you find this information, @ufm?
Or is this a ping test (and are you referring to packet loss)?
Pinging router's IP address ... or through router another device? Does it help if you increase timeout?Pingflood testWhere do you find this information, @ufm?
Or is this a ping test (and are you referring to packet loss)?
And smokeping monitoring.
I agree, previous format was better to read commentsBeing a person that uses the webfig much more than winbox, this change:
..*) webfig - added inline comments;
is plain terrible. I'd love being able to at least choose the old behavior and having the comments on a different line instead of inline. Please consider having this as an option and not fixed inline. For those who don't have very big screens/resolutions, this is a TERRIBLE change.
I quite like it! The previous form of comments on a separated line wasted way more screen space. And the default column width is quite narrow, but you can still decrease it.Being a person that uses the webfig much more than winbox, this change:
..*) webfig - added inline comments;
is plain terrible. I'd love being able to at least choose the old behavior and having the comments on a different line instead of inline. Please consider having this as an option and not fixed inline. For those who don't have very big screens/resolutions, this is a TERRIBLE change.
If your comments are short, like 10-30 characters, this might be fine. But I rely heavily on the comments in my routing filters and DHCP pools and lease tables, with explanations and/or snippets of filter "code" on the former, and customer VLAN info or hostnames (or reasons for enabling/disabling leases) on the latter. Other routers might have more verbose comments on interfaces or settings I commonly enable/disable in different scenarios.The previous form of comments on a separated line wasted way more screen space. And the default column width is quite narrow, but you can still decrease it.I'd love being able to at least choose the old behavior and having the comments on a different line instead of inline.
I hear you - it's the same for me. That thing get me crawling up the walls. No idea why, it just does.It's way off topic for this thread of course, but I can't stand Winbox. The windowed and tabular format for sub-config items drives me mad. Don't know why, it just does.
+ovpn still unstable like in 7.8, so downgrade to 7.7 again...
It's the same here... OpenVPN client randomly restarts in the 24h with >=7.8. 7.7 it's ok (4011, CCR1009, MapLite, ... and others).ovpn still unstable like in 7.8, so downgrade to 7.7 again...
i have similiar issue with RB750Gr3 it have only 1 vlan in bridge and RSTP is enable,and cisco 2960 switch after upgrade to 7.9 my internet connection become really slow, after disable the RSTP to none in the bridge my internet become normal again, i decided to enable RSTP in cisco 2960 switch it seem the problem solved for nowIn case if anybody has misbehaving rb4011 using vlans, please make sure you have MSTP enabled on bridge.
Interestingly I had RSTP used previously and all was working fine on 7.7 and older.
Took me some reading to find it.
Winbox is fantastic in "Windows world", apple / linux... wine I guess, but its fast, reliable( usually ), and networkable protocol(if you use IP) especially if you using units that don't expose or have IP addresses on the box, as you can get to the box/VM via MAC-ADDRESS only ( FYI. I manage 100+ MT devices with ), and the use of ROMON too is a fantastic way of doing router config when you dont have direct layer-3 to a downstream device ( Eg. CRS series gear ). So yes, I'll keep winbox going...Winbox needs to be installed, WebFig is available using pre-installed browser. So why even bother with Winbox ?
Why? Genuinely curious as to why anyone would use WebFig over Winbox if they have the option to use Winbox.
Ping through router. For examplePinging router's IP address ... or through router another device? Does it help if you increase timeout?
Pingflood test
And smokeping monitoring.
/interface bridge add name=dockers
/interface veth add address=172.17.0.2/24 gateway=172.17.0.1 name=veth2
/interface bridge port add bridge=dockers interface=veth2
/container mounts add dst=/data name=npm_data src=/slot1/docker/npm/data
/container mounts add dst=/etc/letsencrypt name=npm_etc_letsencrypt src=/slot1/docker/npm/etc/letsencrypt
/container add interface=veth2 mounts=npm_data,npm_etc_letsencrypt root-dir=/slot1/docker/npm/root-dir/ remote-image=jc21/nginx-proxy-manager:latest
.Any more info on the new radio/reg-info console command?
/interface/wifiwave2/radio/reg-info country=Greenland number=???????????
*) wifiwave2 - added "radio/reg-info" command to show regulatory requirements (currently implemented for 802.11ac interfaces) (CLI only);
[xyz@MikroTik] > interface/wifiwave2/radio/reg-info country=Belgium number=0
ranges: 2402-2482/20
5170-5250/23/indoor
5250-5330/23/indoor/dfs
5490-5710/30/dfs
doesn't work on my RB and also on other two one... on 7.6 works without any problemSomeone told me it works on my computer.upgraded from 7.6 (x86), looks like "PPPoE Scan" is broken
Someone told me that is broken from 7.8
And where is the packet loss in winbox?"rx drop" is not packet loss.
Can you explain to me how do you count lost packets if they never arrived?And where is the packet loss in winbox?"rx drop" is not packet loss.
Could you give me an example with a transport?moderation
So what is your problem?And where is the packet loss in winbox?"rx drop" is not packet loss.
I make a ping www.google.com packet-loss=0%
It seems that something in bridging code has indeed been changed - in my case the wired bridge ports on RB952 (CPU mipsbe, switch chip 8227) with hw=yes setting do not communicate (except DHCP) if they turn up AFTER another port with hw=no is already up. If the port with hw=yes turns up as the first one in the bridge, everything works as configured. I worked around this inconsistent behavior by setting hw=no on all wired bridge ports and will investigate it in a detail when I find some spare time.Some users have bad performances with ipv4 and enabled bridge filters actives.
In previous versions (7.7 and 7.8) there was no issue. Since 7.9 (stable) ipv4 bandwith is lower for about 35%.
It is just as fantastic on any other platform where wine can be used as MAC-address and ROMON access works on there as well...Winbox is fantastic in "Windows world", apple / linux... wine I guess, but its fast, reliable( usually ), and networkable protocol(if you use IP) especially if you using units that don't expose or have IP addresses on the box, as you can get to the box/VM via MAC-ADDRESS only ( FYI. I manage 100+ MT devices with ), and the use of ROMON too is a fantastic way of doing router config when you dont have direct layer-3 to a downstream device ( Eg. CRS series gear ). So yes, I'll keep winbox going...
Winbox needs to be installed, WebFig is available using pre-installed browser. So why even bother with Winbox ?
Checked on my Hex, can't confirm (pretty basic config as well).I'm having issues with the switch ports on RB750Gr3. Very strange behaviour. Sometimes no packets Tx or Rx shown under "interfaces" (but the port is active and transmitting packets). Shows no link active (but it is...). Seems to be the last port plugged in. E.g., by unplugging the "bad" port and one "good" port, then plugging back in the bad port first, the "good" port now becomes bad!
And the log shows link up and link down all the time, even though... it isn't. And sometimes, all the switch ports go inactive. Setup is basically stock. Reverting to 7.8 fixes all issues. Going back to 7.9 brings them back.
...
... importing remote image: adguard/adguardhome, tag: latest
... was unable to import, container d9f3b14b-efe0-4788-90ee-edeb024f08fb
Thanks for checking. Mine ran okay for around 10 hours or so. I also noted something in the logs about configuring switch ports for hw offload (not sure if I have seen that before?) after upgrading to 7.9. System is performing normally now I have "downgraded" to 7.8. I am reluctant to revert to 7.9 to get a support.rif or dig deeper for fear of inducing user anger (I have teenagers...).Checked on my Hex, can't confirm (pretty basic config as well).I'm having issues with the switch ports on RB750Gr3....
I switched it on this morning around 7 AM and up til now (16h11), no messages in log about ports being toggled.
Best to create supout.rif and send it to support.
Assuming you are using IPv6, take a look at the IPv6 firewall connections. Are there any connections to global IPv6 addresses? As I reported earlier, IPv6 does not work for me with V7.9.Since I upgraded to 7.9 (from 7.9rc2) my Homepod seems to have connection issues. I'm getting "The Home hub is not responding / The Home hub is now responding" notifications several times a day.
Wifi controller shows an uptime of 1d+ for this device without an increased rate in retransmissions in comparison to the last few days, so I'd rule this out.
Nothing else was changed, may be related to the packet loss issue, a few people have reported. I'm still investigating, I'll update this post if I have found the cause.
Are you using stateful or slaac? I am using slaac. The dhcpv6 client asks for and gets a prefix for ND. I add an address from the pool for the router which creates a route. This works fine with 7.8 but not 7.9. I will dig into it later but was curious what is working for you.IPv6 works fine for me on version 7.9
I am using DHCPv6 PD client over PPPoE to the ISP, obtain a /48 pool from the provider, and assign that to local clients using SLAAC.Are you using stateful or slaac? I am using slaac. The dhcpv6 client asks for and gets a prefix for ND. I add an address from the pool for the router which creates a route. This works fine with 7.8 but not 7.9. I will dig into it later but was curious what is working for you.IPv6 works fine for me on version 7.9
Sorry I didn't :)
@stathismes didn't you read the last line of the post?
Please keep this forum topic strictly related to this particular RouterOS release.
I got IPv6 working but I am not sure why things worked in 7.8 and earlier releases, but I had to make a change to get it working in 7.9.I am using DHCPv6 PD client over PPPoE to the ISP, obtain a /48 pool from the provider, and assign that to local clients using SLAAC.
Are you using stateful or slaac? I am using slaac. The dhcpv6 client asks for and gets a prefix for ND. I add an address from the pool for the router which creates a route. This works fine with 7.8 but not 7.9. I will dig into it later but was curious what is working for you.
I have been doing that forever and it works, also in 7.9.
The only issue I have is (as mentioned before) that dynamic VLAN assignment to Wireless connections has a bug. It does not pass multicast for the assigned VLAN to the client, hence no SLAAC and no IPv6 on dynamically assigned VLAN.
But I think that issue has started earlier than 7.9.
Most likely the config is wrong and it happened to work.I got IPv6 working but I am not sure why things worked in 7.8 and earlier releases, but I had to make a change to get it working in 7.9.
You are also thinking that "rx drop" indicates a problem?Also showing dropped packets making it unusable on RB4011iGS+
@pe1chl
Because the user @jimint some users probably don't understand the difference between data transport and the services transported by transport....
I try to pull jc21/nginx-proxy-manager on CHR
No, actually dropped packets and very slow/dropping speeds (nothing more than 100-200kbps).. took a lot of playing around and rebuilding to discover that 7.9 package stopped XS+2733LC15D from negotiating at 10G.. setting to 1G for now will work under 7.9 or back the software to 7.8 and seems to use 10G without issue again.You are also thinking that "rx drop" indicates a problem?Also showing dropped packets making it unusable on RB4011iGS+
I've confirmed that DHCP is working for all my devices on 7.9 stable. This includes the Google Nest Doorbell.Anybody know if the DHCP server on 7.9 stable is borking stuff like Google Nest Doorbell DHCP requests?
Sorry but I lost track of that discussion due to excessive quote stripping (probably mandated by a dictator moderator).@pe1chl
Because the user @jimint some users probably don't understand the difference between data transport and the services transported by transport....
I guess that number=X is supposed to refer to wireless interface (or something). It is silly that then command returns exactly the same info regardless the interface indicated. I'm running this on Audience, which has 3 radio interfaces (1x 2.4GHz and 2x 5GHz) and I can set number to values 0-2. But then it returns the same info..Any more info on the new radio/reg-info console command?
/interface/wifiwave2/radio/reg-info country=Greenland number=???????????
Works but as indicated only on AC interfaces (e.g. AC3 using wifiwave2)
After first boot there was probably something in /log/print about it. If device doesn't have logging set up with destination other than memory, then this information was lost. So if you feel adventurous and decide to try again (and it fails again), do check the log about the reasons. And if reasons are not clean, create supout.rif file and send it to MT support.I tried upgrading CRS 317 from 7.6 to 7.9. It failed lost the switch. After connecting with console. Switch was up but os version was old. Resetting the switch brought back the switch. The reconfigured it with older versihn 7.6
ty
I hear You. This is getting out of hand. I just lost the will to post here - too much hassle.Sorry but I lost track of that discussion due to excessive quote stripping (probably mandated by a dictator moderator).
It looks like it is time for another complaint...
/system logging action add name=System target=memory
/system logging add action=System topics=interface
/system logging add action=System topics=system,!account
/system logging add action=System topics=health
I have the same problem. IPV6 works directly on the router. No downstream device gets an IPV6 address with ROS 7.9. IPV6 ND shows invalid prefixes.ROS 7.9 seems to have broken IPv6 for at least tile on a CCR1009-7G-1C. With 7.9 there are no connections to global WAN addresses. Trying to ping one says there is no route. I downgraded to 7.8 and immediately had lots of IPv6 global connections. I reinstalled 7.9 and again could not get any global connections. I have downgraded to 7.9 for now.
I have upgraded my routers from 7.7 to 7.9 everything is running OK.
The issue with L3-HW is still not resolved. The ticket is open since january.
We wait...
I have noticed that on the 4011 the CPU is now set to auto and its speed is dynamic. Maybe to reduce heat?
In my situation I got a valid prefix and clients could configure their addresses with it. They just couldn't get to global address because there was no gateway to the WAN. I am using slaac and the DHCPv6 client just asks for a prefix and creates a pool with it. I then add a ::1/64 address from the pool for the bridge with all my LAN and wifi interfaces. If you are getting a bad prefix, then maybe there is something wrong with your DHCPv6 client configuration. In case you didn't see a later post, I had to enable ND on my WAN (ether1) interface to get things working, whereas that wasn't needed before 7.9.I have the same problem. IPV6 works directly on the router. No downstream device gets an IPV6 address with ROS 7.9. IPV6 ND shows invalid prefixes.ROS 7.9 seems to have broken IPv6 for at least tile on a CCR1009-7G-1C. With 7.9 there are no connections to global WAN addresses. Trying to ping one says there is no route. I downgraded to 7.8 and immediately had lots of IPv6 global connections. I reinstalled 7.9 and again could not get any global connections. I have downgraded to 7.9 for now.
Same for me. Working ProtonVPN connection broke. Uploaded the root certificate again and still doesn't work.I am getting error "can't verify peer's certificate from store" again on the ipsec setup. I tried reupload the root CA again but no avail.
<IP Address>: disconnected <TLS error: std failure: unknown id (4)>
[interface name]: terminating... - TLS error: std failure: unknown id (4)
[interface name]: disconnected <TLS error: ssl: wrong alert structure (6)>
[interface name]: terminating... - TLS error: ssl: wrong alert structure (6)
Yours looks like a configuration problem...Upgraded my RB4011(Wifi) to 7.9, working stable both on WIfi/LAN. Using Hap AX3 as AP connected from port 1 of AX3 to POE port of 4011 which i'm using for my AX devices. After few hours/mins wifi is very unstable, devices are getting disconnected and unable to connect until device(AX3) reboot. After reboot i am able to connect again and it gets disconnected permanently after few hours/mins, i'm able to see my access point on Mac/iPhone but unable to connect.
It was perfectly stable and working fine on 7.6,7.7,7.8.Yours looks like a configuration problem...Upgraded my RB4011(Wifi) to 7.9, working stable both on WIfi/LAN. Using Hap AX3 as AP connected from port 1 of AX3 to POE port of 4011 which i'm using for my AX devices. After few hours/mins wifi is very unstable, devices are getting disconnected and unable to connect until device(AX3) reboot. After reboot i am able to connect again and it gets disconnected permanently after few hours/mins, i'm able to see my access point on Mac/iPhone but unable to connect.
You were right. It was a config issue. On my RB4011 i had to goto IP->DHCP->Leases->Select the IP/Mac/Device Name for Hap Ax3-> Make it Static IP. Seems to have worked and been stable for hours.Yours looks like a configuration problem...Upgraded my RB4011(Wifi) to 7.9, working stable both on WIfi/LAN. Using Hap AX3 as AP connected from port 1 of AX3 to POE port of 4011 which i'm using for my AX devices. After few hours/mins wifi is very unstable, devices are getting disconnected and unable to connect until device(AX3) reboot. After reboot i am able to connect again and it gets disconnected permanently after few hours/mins, i'm able to see my access point on Mac/iPhone but unable to connect.
invalid mtu 9086 on sfp-sfpplus1 from fe80::ea5c:aff:fe83:f43c
Code: Select allinvalid mtu 9086 on sfp-sfpplus1 from fe80::ea5c:aff:fe83:f43c
Well, my take is more radical. The web interface looks really awful for quite some time already, just scrap it. I would prefer Mikrotik Mobile app ported to the desktop anyday, especially if you turn on the table/grid design. It is good enough to slowly start replacing Winbox imo.What alternatively gifted person thought up in the web interface to cram a comment as a column into the firewall tables (and the rest of the tables look no better)?! Now to see the rules, you either need to compress the comment column, or turn the horizontal scroll! Return it as it was!
new_comment.jpg
Normal design. Functional. It is quite sufficient to perform most administrative tasks. Ubi Unifi - does not contain even 25% of the functionality of mikrotik, therefore they can afford to draw a pretty interface in which you can change a couple of parameters. If you try to cram dozens of parameters into such an interface (as in mikrotik), the router processor will die in an attempt to draw it. Or it will jump significantly in price.In today's world, there is no place for such a shitty design, looking like a 90ties Unix clone. Just look at Ubi Unifi interface - that's how modern interface should look like.
I have this problem too (occurs for me from rc2-rc5.) Seems to happen less on v7.9 Stable. Similarly, only a reboot will revive the ax3. Still observing the problem before I make a report to support.v7.9 on hap ax^3 drops wifi registrations and will not allow new ones until a reboot. This problem was observed and reported by at least 2 of us using v7.9 rc4. It seemed fixed in rc5 and v7.9 stable but after 3 days of running, all registrations were gone. There were registrations last evening and this morning there were none. The log had nothing related to disconnects, reauthenticating or connections. Immediately after a reboot, connections started occurring and the log shows that activity.
To control the setup of the SOHO router, a standard 15-inch screen like most laptops should be enough.@revan: Or get a bigger monitor?
Or use winbox?
Or file a bug report to include some options to hide columns in the webfig that few gifted persons use it?
Same here. I've been getting "radvd, warning invalid mtu 1492 on pppoe-out1 from fe80::200:5eff:fe00:10d" Not sure what to make of it.After upgrading, I'm getting these:
.. warnings. Not sure what to do about it, since it's the upstream gateway to the router and I have no control over it, and the interface is set to mtu 1500.Code: Select allinvalid mtu 9086 on sfp-sfpplus1 from fe80::ea5c:aff:fe83:f43c
maybe they are using 1492 mtu at their end? maybe safely ignore?Same here. I've been getting "radvd, warning invalid mtu 1492 on pppoe-out1 from fe80::200:5eff:fe00:10d" Not sure what to make of it.After upgrading, I'm getting these:
.. warnings. Not sure what to do about it, since it's the upstream gateway to the router and I have no control over it, and the interface is set to mtu 1500.Code: Select allinvalid mtu 9086 on sfp-sfpplus1 from fe80::ea5c:aff:fe83:f43c
fe80::200:5eff:fe00:10d is my ISPs DHCP server. (as reported by my DHCPv6 client)
Unsure where the MTU 1492 is coming. My PPPoE is currently set at MTU 1480. The highest I can set it to is MTU 1488.
Same here :(. Downgraded AX3 to 7.8 and its been stable so far.Just noticed problems connecting wifi clients to AX2 ( after 4 days uptime).
Normal network using wpa2/3 became unavailable.
IoT network with only wpa2 was still possible.
Reboot of AX2 solved it, for now.
I am not sure if I am one of the three but include me in the list. I am using wpa2 & 3 and as I had reported, registrations get dropped and no new ones can be created with my ax^3, thus requiring a reboot. Holvoeth's post hopefully narrowed things down to wpa2 & 3. I may roll back to v7.8 which was stable.So 3 people with the same problem then so far.
Yeah, atm I'm just ignoring it. Doesn't seem to affect anything. Highly possible a configuration error on the ISP's side.maybe they are using 1492 mtu at their end? maybe safely ignore?
Same here. I've been getting "radvd, warning invalid mtu 1492 on pppoe-out1 from fe80::200:5eff:fe00:10d" Not sure what to make of it.
fe80::200:5eff:fe00:10d is my ISPs DHCP server. (as reported by my DHCPv6 client)
Unsure where the MTU 1492 is coming. My PPPoE is currently set at MTU 1480. The highest I can set it to is MTU 1488.
you really cannot compare unifi (home and small business grade) with the flexibility and function richness of routerOS
In today's world, there is no place for such a shitty design, looking like a 90ties Unix clone. Just look at Ubi Unifi interface - that's how modern interface should look like.
Then don't :-)is there something for me from 7.7 to 7.9 that would benefit me? looking at the changelog i see nothing and i'm kind of, if not broken dont updating it
I concur - two cAP ax units managed via CAPsMAN with the same issue.ok, make that 4 of us, both of my Hap AX3 completely drop wireless clients after around 24 hours. They continue to advertise the SSIDs but no new registrations occur. I'm using CAPsMAN server on one AX3, the other AX3 is a client. Both stop registrations. As a test I rebooted the remote 'client' AX3 and registrations started working again on it (The CAPsMAN AX3 showed the remote registrations). The other AX3 (CAPsMAN Server) still did not accept any client registrations, So this appears to be at the wifiwave2 driver level, since other functions (SSH/CAPsMAN server etc) continued to function.
This issue became very obvious with the 7.9 release, the RC's all had the same problem (reported in the RC beta thread), but could sometimes stay up for over a week.
I am using WPA2 authentication only (No WPA3). Since rebooting AP restores connections, and this has been reported by multiple people (standalone config, CAPsMAN config etc), it appears to be at the wifiwave2 driver level.
I wonder (yet again) if it's that hard for them to have a test bench where they have devices pre-configured with every fancy feature they offer and actually test the releases before launching a stable version.
When the look of the user interface is important to you, select the product that has the look you like!Just look at Ubi Unifi interface - that's how modern interface should look like.
Was already discussed in the 7.8 thread, and promised to be fixed in the RC following the 7.9 release.Hardware: RB5009
Issue: Container import problem in v7.9. After upgraded firmware v7.9 to RB5009, I tried to update the existing working container for Adguardhome to the latest version as well (adguard/adguardhome:latest). The following error was found in the log.
Registry in use : https://registry-1.docker.io
Solution: viewtopic.php?t=192810#p981824
Code: Select all... importing remote image: adguard/adguardhome, tag: latest ... was unable to import, container d9f3b14b-efe0-4788-90ee-edeb024f08fb
One use case which is very hard to test is a (known) fact that devices, which are continuously upgraded and have jumped from v6 to v7 at some point, can run into unstable operation. Netinstalling them and re-configuring (either from scratch or by using text export of config) them seems to improve stability. But such a history is extremely hard to include into test bed ... because there are so many combinations of different versions available and it's not known which combination triggers the issue and when.
Personally, I don't mind for my home devices. I know this can be unstable.So again we're back to the well known fact that we, advanced users, are their "gamma" testers ... and with some luck (and after ROS v7 stabilizes enough) our test reports will get due attention and resolutions (in form of dot releases).
I have a very similar setup to yours and have never had any problems.ok, make that 4 of us, both of my Hap AX3 completely drop wireless clients after around 24 hours. They continue to advertise the SSIDs but no new registrations occur. I'm using CAPsMAN server on one AX3, the other AX3 is a client. Both stop registrations. As a test I rebooted the remote 'client' AX3 and registrations started working again on it (The CAPsMAN AX3 showed the remote registrations). The other AX3 (CAPsMAN Server) still did not accept any client registrations, So this appears to be at the wifiwave2 driver level, since other functions (SSH/CAPsMAN server etc) continued to function.
This issue became very obvious with the 7.9 release, the RC's all had the same problem (reported in the RC beta thread), but could sometimes stay up for over a week.
I am using WPA2 authentication only (No WPA3). Since rebooting AP restores connections, and this has been reported by multiple people (standalone config, CAPsMAN config etc), it appears to be at the wifiwave2 driver level.
I requested 7.10alpha. and the response was negative. :DTime for 7.10 beta?!
Hello,
Thank You, for contacting Mikrotik support team!
The answer to Your inquiry is - no.
We are not at liberty to provide You alpha or beta builds of our software.
All the publicly available software is listed on Mikrotik`s official page:
https://mikrotik.com/download
Have a Good day!
Gļebs K.
looks like a timeout issue, for someone there is an output. May be the remote RAS reply faster than others... anyway on 7.6 was working, so hope they fix in the next release.Yes, it’s still broken.
Me too... "PPPoE Scan" feature broken (tested with RouterOS 7.9 on 4011 and ChateauLTE12)
Same behavior on hap ac2. And got two kernel panics in with out of memory. Downgraded to 7.8 and everything is stable.Same here. I've been getting "radvd, warning invalid mtu 1492 on pppoe-out1 from fe80::200:5eff:fe00:10d" Not sure what to make of it.After upgrading, I'm getting these:
.. warnings. Not sure what to do about it, since it's the upstream gateway to the router and I have no control over it, and the interface is set to mtu 1500.Code: Select allinvalid mtu 9086 on sfp-sfpplus1 from fe80::ea5c:aff:fe83:f43c
fe80::200:5eff:fe00:10d is my ISPs DHCP server. (as reported by my DHCPv6 client)
Unsure where the MTU 1492 is coming. My PPPoE is currently set at MTU 1480. The highest I can set it to is MTU 1488.
I confirm, after 5 days of uptime I just had the same problem...Yes I have multiple SSIDs and VLANs. Due to 7.9 not dynamically adding VLANs to remote CAPsMAN managed AXs (Works on a local AX if that AX is the CAPsMAN server also), I have to manually bridge the wifi SSID's to the appropriate VLANs.
Having said that, others are experiencing the same issues with standalone AX3's also.
The general symptom of failure is phones come back saying invalid password (IOS 14 and Samsung S10), Windows 11 also says the password is invalid. (Static WPA2 password). I have tried disabling and re-enabling SSID interfaces without success. Only solution is to reboot the AP. Once the AP is rebooted, on the phones you need to select the SSID from the list again before they re-connect (I guess they give up trying after a certain number of attempts). The laptop seems to reconnect automatically.
It will fail again in a day or two. It has failed for me 3 times already (Deployed 7.9 as soon as it was released). Time for 7.10 beta?!
For the record, I have the problem and do not have vlans. Also, I do not have to do anything special after a reboot for devices to start registering again.
I have a very similar setup to yours and have never had any problems.
Do you use vlans?
Update: It only happens on one of my devices and I think it is an ssl prblem! One of CPU cores is always 100 and the profile show it is ssl!Thanks for this version features. However, It has a issue on SSTP Server! It does not start correctly and I could not connect after upgrade! I had to downgrade to 7.8 !
Plus one from us also.. Ax3s suddenly stop allowing registrations until a reboot.ok, make that 4 of us, both of my Hap AX3 completely drop wireless clients after around 24 hours. They continue to advertise the SSIDs but no new registrations occur. I'm using CAPsMAN server on one AX3, the other AX3 is a client. Both stop registrations. As a test I rebooted the remote 'client' AX3 and registrations started working again on it (The CAPsMAN AX3 showed the remote registrations). The other AX3 (CAPsMAN Server) still did not accept any client registrations, So this appears to be at the wifiwave2 driver level, since other functions (SSH/CAPsMAN server etc) continued to function.
This issue became very obvious with the 7.9 release, the RC's all had the same problem (reported in the RC beta thread), but could sometimes stay up for over a week.
I am using WPA2 authentication only (No WPA3). Since rebooting AP restores connections, and this has been reported by multiple people (standalone config, CAPsMAN config etc), it appears to be at the wifiwave2 driver level.
I don't understand the cause...Plus one from us also.. Ax3s suddenly stop allowing registrations until a reboot.ok, make that 4 of us, both of my Hap AX3 completely drop wireless clients after around 24 hours. They continue to advertise the SSIDs but no new registrations occur. I'm using CAPsMAN server on one AX3, the other AX3 is a client. Both stop registrations. As a test I rebooted the remote 'client' AX3 and registrations started working again on it (The CAPsMAN AX3 showed the remote registrations). The other AX3 (CAPsMAN Server) still did not accept any client registrations, So this appears to be at the wifiwave2 driver level, since other functions (SSH/CAPsMAN server etc) continued to function.
This issue became very obvious with the 7.9 release, the RC's all had the same problem (reported in the RC beta thread), but could sometimes stay up for over a week.
I am using WPA2 authentication only (No WPA3). Since rebooting AP restores connections, and this has been reported by multiple people (standalone config, CAPsMAN config etc), it appears to be at the wifiwave2 driver level.
i decided too go back to 7.8, my wan port ether1 behave like that too, i tried to change to ether2 for WAN port remove from bridge port still same behavior, there must be something change on bridge, in 7.9 my internet become really slow, Reverting to 7.8 fixes all issues.I'm having issues with the switch ports on RB750Gr3. Very strange behaviour. Sometimes no packets Tx or Rx shown under "interfaces" (but the port is active and transmitting packets). Shows no link active (but it is...). Seems to be the last port plugged in. E.g., by unplugging the "bad" port and one "good" port, then plugging back in the bad port first, the "good" port now becomes bad!
And the log shows link up and link down all the time, even though... it isn't. And sometimes, all the switch ports go inactive. Setup is basically stock. Reverting to 7.8 fixes all issues. Going back to 7.9 brings them back.
Never had this kind of issue before. Anyone else, or am I blessed or have done something daft?
You need to check the logs in ax3 (or is it ac3?). I have noticed, that my phone (Galaxy S22) get disconnected whit error: "blā, blā rejected, can't find PMKSA". After, I assume, SAE process resets it get connected. Did a "forget and reconnect", didn't helped. I dunno if this is 7.9 related issue, but noticed just now.Also Wifi issues with ax3. At random times the phone stopped working even though the Wifi was active. The phone receives the IP "169.254.57.102" and keeps trying to connect to Wifi.
Only ac3 reboot helped.
For me now it is completely broken.vpn4 works!!!
mwaaa MT
Open a separate topic, do not pollut this topic.export your config
nothing really special :export your config
/routing bgp template
set default address-families=vpnv4 disabled=no multihop=yes router-id=\
10.29.193.27 routing-table=main
/routing bgp connection
add address-families=vpnv4 as=65530 connect=yes disabled=no local.address=\
10.29.193.27 .role=ibgp-rr-client multihop=yes name=bgp1 remote.address=\
10.29.192.19/32 .as=65530 routing-table=main templates=default
/routing bgp vpn
add disabled=no export.route-targets=10.29.192.2:10013 import.route-targets=\
10.29.192.2:13 label-allocation-policy=per-vrf name=bgp-mpls-vpn-1 \
route-distinguisher=10.29.193.27 vrf=CeV10001
.There is a new bug in WebFig. When toggling the enabled/disabled state from disabled to enabled, the entire row stays grey as if it were disabled.
For example in WiFi Interfaces or Firewall rules, I think it applies all the tables with rows which can be toggled.
Didn’t work in long run. I tried also disabling hw offloading on bridge ports or enable ign snooping as someone suggested and none of it helped.In case if anybody has misbehaving rb4011 using vlans, please make sure you have MSTP enabled on bridge.
My bad. I have hap ax3.You need to check the logs in ax3 (or is it ac3?). I have noticed, that my phone (Galaxy S22) get disconnected whit error: "blā, blā rejected, can't find PMKSA". After, I assume, SAE process resets it get connected. Did a "forget and reconnect", didn't helped. I dunno if this is 7.9 related issue, but noticed just now.Also Wifi issues with ax3. At random times the phone stopped working even though the Wifi was active. The phone receives the IP "169.254.57.102" and keeps trying to connect to Wifi.
Only ac3 reboot helped.
My 4011 is doing VLAN on 7.9 OK.Didn’t work in long run. I tried also disabling hw offloading on bridge ports or enable ign snooping as someone suggested and none of it helped.In case if anybody has misbehaving rb4011 using vlans, please make sure you have MSTP enabled on bridge.
Gave up and reverted to 7.7 again.
Same here.MikroTik guys, PLEASE release version 7.10 (or 7.9.1) as soon as possible with fixes to above problems. I have all of my OpenVPN links down due to it's instability in version 7.9.
In my case it was fine for even about 90 minutes, so keep looking at it.Just updated to 7.10 beta rc5 and openvpn clients seems to be stable, no disconnect after 20 min uptime.
I will monitor it and update with results
SUP-95367I have upgraded my routers from 7.7 to 7.9 everything is running OK.
The issue with L3-HW is still not resolved. The ticket is open since january.
We wait...
I have noticed that on the 4011 the CPU is now set to auto and its speed is dynamic. Maybe to reduce heat?
Hi,
What is the issue with l3-hw please ?
Thanks
I couldn't agree more. I waited a long time for ax^3 availability and was shocked when I found out about the capsman situation. Luckily, I only have one wifiwave2 device and as it turns out, new capsman couldn't configure it anyway so I configure it directly and use old capsman to configure my 6 non-wifiwave2 access points.... the "patch" of having a different capsman for wifiwave2 is *horrible*...
As one with the same problem, I have upgraded my ax^3 to v7.10 beta 5. The topic will probably continue in that thread but hopefully not.I upgraded my AX3 from 7.8 to 7.9 and it killed my wireless with disconnection issues, see https://www.reddit.com/r/mikrotik/comme ... 79_issues/ for more people who are having the issues. I downgraded back to 7.8 and wifi is working again. Configuration is pretty basic with 2 VLANs and 3 SSIDs. Can't wait for 7.10, yikes!
which is why us old timers used to love the long term release tree, but now that it has been left to wither and die for v6 and totally forgotten & abandoned for v7, we're forced to choose between being able to install new devices that are v7 only, or migrate to something other than MikroTik... There is an institutional lack of understanding with the needs for bigger organizations and enterprises that value stability and reliability over new features. Continually ignoring requests for BFD, breaking scripts with timestamp format changes, breaking deployment processes and workflows, suddenly buggy SFP support that was stable before, problems with skins and branding packages, PPPoE scan breaking every other update (though it being so heavily used surprises me, I run lots of PPPoE servers yet see zero use for the tool) and all while focusing most of the development efforts on new features like zerotier, rose, wave2... it's frustrating to have a product that we have stood behind and utilized for nearly 20 years now lose focus on what made us love it to begin with, and that was the affordable reliability, now regularly break core features to release ancillary features.Many of the bugs fixed in version 7.9 have been introduced in the 7.8 beta. And many errors seem to occur randomly.
This is a sign of bad programming: before 'fixing' old bugs, you should review your development team.
which is why us old timers used to love the long term release tree, but now that it has been left to wither and die for v6 and totally forgotten & abandoned for v7, we're forced to choose between being able to install new devices that are v7 only, or migrate to something other than MikroTik... There is an institutional lack of understanding with the needs for bigger organizations and enterprises that value stability and reliability over new features. Continually ignoring requests for BFD, breaking scripts with timestamp format changes, breaking deployment processes and workflows, suddenly buggy SFP support that was stable before, problems with skins and branding packages, PPPoE scan breaking every other update (though it being so heavily used surprises me, I run lots of PPPoE servers yet see zero use for the tool) and all while focusing most of the development efforts on new features like zerotier, rose, wave2... it's frustrating to have a product that we have stood behind and utilized for nearly 20 years now lose focus on what made us love it to begin with, and that was the affordable reliability, now regularly break core features to release ancillary features.Many of the bugs fixed in version 7.9 have been introduced in the 7.8 beta. And many errors seem to occur randomly.
This is a sign of bad programming: before 'fixing' old bugs, you should review your development team.
I have seen that problem with Romon ID duplicated since Ros 6.xx , easy to solve manually setting a Static MAC of one interface of the switch for Romon IDI found an issue on v7.9 (also in v7.8):
There is an issue in the algorithm used for choosing the (random?) MAC address of a bridge (e.g. loopback).
Two switches CRS317 in the same network got the same MAC address on the loopack interface.
RoMON Address also is duplicated. Only one of both devices is shown in "RoMON Neighbors" list.
Prints:
Switch 1:
https://drive.google.com/file/d/1jjyxKf ... share_link
Switch 2:
https://drive.google.com/file/d/1nrfwP7 ... share_link
Same here with 7.10beta5, 7.7 is rock solid for OpenVPN client.Started again with disconnects after one hour and 10 minutes... so no improvement so far.
Only solution now to go back to 7.7
Actually, as stated, this is upstream of my LAN. sfp-sfpplus1 is connected to my ISP's gateway device, I have no control over its settings. I figured it's harmless, since I've been running at mtu 1500 the entire time and there were no instructions with the service that recommended I use anything other than that, but it is polluting the logs with that warning every minute or so.fe80::/10 is the prefix for IPv6 link-local addresses, so it means one of your LAN hostsCode: Select allinvalid mtu 9086 on sfp-sfpplus1 from fe80::ea5c:aff:fe83:f43c
Sorry, I can´t confirm:RB 4011 after upgrading to v7.9 does not connect using SFP S+DA0001. It has been tested on other RB4011's, and they all have the same problem.
Try v7.10beta5 for see if the problem is already solved on future version...RB 4011 after upgrading to v7.9 does not connect using SFP S+DA0001. It has been tested on other RB4011's, and they all have the same problem.
I already did this test. v7.10beta5 still has the same problem.Try v7.10beta5 for see if the problem is already solved on future version...RB 4011 after upgrading to v7.9 does not connect using SFP S+DA0001. It has been tested on other RB4011's, and they all have the same problem.
RB 4011 after upgrading to v7.9 does not connect using SFP S+DA0001. It has been tested on other RB4011's, and they all have the same problem.
https://mikrotik.com/product/rb4011igs_rmPassive DAC (MikroTik S+DA0001/S+DA0003) are not supported.
I understand and have always known this, however, it has always worked normally.RB 4011 after upgrading to v7.9 does not connect using SFP S+DA0001. It has been tested on other RB4011's, and they all have the same problem.
Says right on the product page:
https://mikrotik.com/product/rb4011igs_rmPassive DAC (MikroTik S+DA0001/S+DA0003) are not supported.
I had used the passive DACs from MikroTik on my RB4011iGS+ without any issue on 6.x. Didn’t use any of those with 7.x, however, I have been using the CAB-10GSFP-P1M (Passive Copper DAC) from 10GTek on my 4011 for more than 4 years with 6.x and 7.x since 7.8 without any problem (working well with 7.9 too).I understand and have always known this, however, it has always worked normally.
I use this RB4011 like this for more than 3 years, even with v7.8 everything was normal.
Same here. Very unstable setup with CAPsMAN and two CAPs.Anyone else now got an issue where devices will fail to connect to wifi while complaining that the saved password is incorrect? Suddenly everything reconnects after restarting the router.
hAP ax^2
/local SnmpCommunity "test";
/snmp/community/
set [find default] name=$SnmpCommunity read-access=yes write-access=no securit
/local SnmpCommunity "test";
/snmp/community/
set [find default] name=$SnmpCommunity read-access=yes write-access=no securitConnection to 192.168.88.101 closed.
jlgonzalez@Joses-MacBook-Air ~ %
xkcd: New BugMany of the bugs fixed in version 7.9 have been introduced in the 7.8 beta. And many errors seem to occur randomly.
xkcd: Epoch failbreaking scripts with timestamp format changes, breaking deployment processes and workflows
Good for you.@ttrs I use hAP ax2 too. Wifi works fine for clients. I don't use capsman, though.