Since MT did not post this info, I try to help out. What's new in 6.45.3 (2019-Jul-29 12:11):
What exactly do you have in mind? The incorrect flagging of actually new GRE packets as invalid? If so, then no, this is not fixed in 6.45.3, but it can be worked around by adding protocol=!gre to the action=drop connection-state=invalid rules in the default firewall, or several other equally simple ways. If you mean that GRE "stopped working although it did before", read the 6.45.1 and 6.45.2 topics, it has been discussed there up and through multiple times why this happens and how to fix it.GRE fixed?
I think that statement like "!somthing" is not good... in any iptables on so on firewalls...What exactly do you have in mind? The incorrect flagging of actually new GRE packets as invalid? If so, then no, this is not fixed in 6.45.3, but it can be worked around by adding protocol=!gre to the action=drop connection-state=invalid rules in the default firewall, or several other equally simple ways. If you mean that GRE "stopped working although it did before", read the 6.45.1 and 6.45.2 topics, it has been discussed there up and through multiple times why this happens and how to fix it.GRE fixed?
Why? For security or for CPU load reasons?I think that statement like "!somthing" is not good... in any iptables on so on firewalls...
For me its working. But first I have to remove all files from 'Files' Dialog. There was a file from broken update procedure of 6.45.2 which needs to be removed.UMarcus: are you sure Hap lite has been updated ??
I've tried also to update via /system packages and manually via file upload, it seems it still fails....
npk file is displayed on files section , winbox reports 16MB of16MB used, maybe no more space allowed for updating process....
How are you updating? The device itself downloads the updates if you do it through Winbox so Windows Defender should not have any impact.v6.45.3 is released! but when I tried to update my system then it shows an error windows defender error 577, I really have no idea how to remove this error. if you have any idea about it then please share with me.
Did you only upgrade ROS or remember to also upgrade firmware (/system routerboard upgrade)?edit: power cycle of the router after the upgrade finally resolved the issue. Fortunately this device is local to me...
Not fix dude snmp v3 ?
Hello,
The dude snmp v3 problem not fix ?
As for SNMPv3 and GRE issues. We are aware of these issues and are working on resolving them. However we much rather release a quicker update with fewer bug fixes which may help other users than waiting longer for issues that takes longer to fix.
Everyone just needs to do his job! It is important for us to see the status of the problems.Posted by spacex — Fri Aug 02, 2019 12:25 amNot fix dude snmp v3 ?
Posted by spacex — Sun Aug 04, 2019 2:32 pmHello,
The dude snmp v3 problem not fix ?
No, since it is not mentioned in the change log - Please keep this forum topic strictly related to this particular RouterOS release. - no need to repeat yourself.
emils response in the 6.45.2 topic still applies:
As for SNMPv3 and GRE issues. We are aware of these issues and are working on resolving them. However we much rather release a quicker update with fewer bug fixes which may help other users than waiting longer for issues that takes longer to fix.
I'm not sure - I used the "Download and Install" option in WinBox (per this guide), then the router restarted, then I had to go run some cable to one of the gbit ports to restore management access to the router as the device never came back online (due to the SFP+ port not working).Did you only upgrade ROS or remember to also upgrade firmware (/system routerboard upgrade)?
Yes, firmware is not automatically upgraded together with RouterOS. You have to do /system routerboard upgrade, and once it succeeds (it takes less than three seconds), reboot the machine.Is there some other procedure I should be following?
*) crs317 - fixed multicast packet receiving (introduced in v6.45);
*) hotspot - fixed default profile values not being used (introduced in v6.45);
*) rb4011 - fixed SFP+ interface linking (introduced in v6.45.2);
*) supout - fixed SIM slot printing (introduced in v6.45);
That is actually expected to work exactly like this. The "stable" release channel used to be called "current", and that caused a lot of confusion. So at some point Mikrotik renamed it to "stable", and, in my opinion, it just made the matters worse. Anyways, you can read what "stable" means in the context of Mikrotik releases here.and again mostly fixes for bugs introduced in previous STABLE releases. excuse my harsh criticism but are you kindergarden business or do you want to be known as a serious software development company...?
UPDATE: +2 Tx Drops exactly every 60 secondsBoard: RB4011iGS+5HacQ2HnD
Problem: on all ros 6.44.x-6.45.x on PPP client/server interfaces (L2TP, PPTP, PPPoE) appear at the same time small Tx Drops counters. On ros 6.43.16 works well on same config.
1)You can't decide what to ask me how.
1. I have requested a mod to remove our posts, which are all offtopic.
2. If you want to be helpful, please do not post facts or findings as a question. Describe your issue thoroughly, describe the test you are actually performing with what parameters, what you expect and what you get instead. Mail to support with supout.rif.
Then thanks, that is helpful.2)We already share the necessary files with mikrotik support
Does it mean that LTE modem that is in the USB slot won't work?Changes in this release:
*) smips - reduced RouterOS main package size (disabled LTE modem, dot1x and SwOS support);
Could you please describe to us how you are planning to connect USB interface to devices which do not have USB?Does it mean that LTE modem that is in the USB slot won't work?
Processor architecture, hAP is mipsbe, hAP Lite is smips.I don't know what smips device is, I have hAP and two hAP lites. Maybe I don't need the whole smips package.
ok, thanks, so I assume noone needs LTE on smips so everything's fineProcessor architecture, hAP is mipsbe, hAP Lite is smips.I don't know what smips device is, I have hAP and two hAP lites. Maybe I don't need the whole smips package.
The upgrade package is downloaded to ramdisk, which may be occupied also by hidden files, so try rebooting just before the upgrade. So the 16 MB flash size is not the issue in this case, the issue is small RAM.I am running 6.45.1 and if I try to update to 6.45.3 I get an error : "ERROR: not enough disk space, 7.3MiB required and only 7.3MiB is free." ... I have no files on the device.
yas!!Upgrade Winbox to 3.19
Try individual packageshAP Lite (RouterBOARD 941-2nD) - still problem with space. (32MB RAM)
Last stable version which I could install is something around 6.40.x
Empty file list, almost bare metal config, file download OK, but after reboot it says "no space"
The only answer from support is "It's strange, do netinstall". Yeah.... I've got several dozen of them. It's impossible.
Are you gonna fix thix or should I put it to trash?
The only what I can do now is to use beta channel - packages are smaller and it's working on SMIPS.
/ip neighbor discovery-settingsBoard: RB4011iGS+5HacQ2HnD
Problem: on all ros 6.44.x-6.45.x on PPP client/server interfaces (L2TP, PPTP, PPPoE) appear at the same time small Tx Drops counters. On ros 6.43.16 works well on same config.
I got same problem, Not enough space!hap lite upgrade issue is not fixed! I have a hap lite with very very very basic config (wifi pseudo bridge to local ports + dhcp client). I am running 6.45.1 and if I try to update to 6.45.3 I get an error : "ERROR: not enough disk space, 7.3MiB required and only 7.3MiB is free." ... I have no files on the device.
Looks like 16MiB flash size on hap lite devices was a very bad decision for mikrotik .... hope they learned a lesson from this fiasco!
JF.
The same thing happened to me, I was trying three days, I took another one with version 6.43 and there was no problem.Still Hotspot captive portal not show automatically.
yes my router ccr1009 loss tx packet in ppp client after upgarde to 6.45.xBoard: RB4011iGS+5HacQ2HnD
Problem: on all ros 6.44.x-6.45.x on PPP client/server interfaces (L2TP, PPTP, PPPoE) appear at the same time small Tx Drops counters. On ros 6.43.16 works well on same config.
\.(exe|dmg|cab|msi|flv|mp2|mp3|m4a|mp4|torrent)($|\?)
Seems like you did not read the release notes ...Can't login via linux MAC-Telnet 0.4.4. after update to this version.
Connecting to.......done
Login failed, incorrect username or password
ROS log: echo: system,error,critical login failure for user admin from XX:XX:XX:XX:XX:XX via mac-telnet.
The password is correct.
Important note!!!
Due to removal of compatibility with old version passwords in this version, downgrading to any version prior to v6.43 (v6.42.12 and older) will clear all user passwords and allow password-less authentication. Please secure your router after downgrading.
Old API authentication method will also no longer work, see documentation for new login procedure:
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login
You do understand that this is useless in an ever growing https world, right?This L7 Regexp does not work anymore since update:I used this to block file download. I also don't know which MikroTik version I had before. I think it was the 6.43.Code: Select all\.(exe|dmg|cab|msi|flv|mp2|mp3|m4a|mp4|torrent)($|\?)
rad_recv: Accounting-Request packet from host 192.168.4.254 port 34324, id=124, length=214
User-Name = "B0:4E:26:D0:33:DB"
NAS-Port-Type = Ethernet
NAS-Port = 2213551065
Calling-Station-Id = "1:b0:4e:26:d0:33:db"
Framed-IP-Address = 188.114.223.27
Called-Station-Id = "vlan_22"
Agent-Remote-Id = 0x646f6d5f3630625f355f32
Agent-Circuit-Id = 0x30303334
Event-Timestamp = "Aug 13 2019 08:11:35 MSK"
Acct-Status-Type = Interim-Update
Acct-Session-Id = "d91bf083"
Acct-Authentic = RADIUS
Acct-Session-Time = 1796
Acct-Input-Octets = 381994156
Acct-Input-Gigawords = 0
Acct-Input-Packets = 290516
Acct-Output-Octets = 381994156
Acct-Output-Gigawords = 0
Acct-Output-Packets = 181132
NAS-Identifier = "NAS - Center"
Acct-Delay-Time = 1
NAS-IP-Address = 192.168.4.254
I have seeing this space error already in few devices: A CRS326, hAP AC, hAP ac2 with any 6.45.x version and I have been unable to find a solution. Even when I manually upload the firmware it reports wrongly the free space (i.e. 5% free) but I can upload the firmware that in theory exceeds this space limit.I got same problem, Not enough space!hap lite upgrade issue is not fixed! I have a hap lite with very very very basic config (wifi pseudo bridge to local ports + dhcp client). I am running 6.45.1 and if I try to update to 6.45.3 I get an error : "ERROR: not enough disk space, 7.3MiB required and only 7.3MiB is free." ... I have no files on the device.
Looks like 16MiB flash size on hap lite devices was a very bad decision for mikrotik .... hope they learned a lesson from this fiasco!
JF.
Free HDD Space: 7.3 MiB Architecture Name: smips Board Name: hAP lite Version: 6.45.2 (stable)
Update packages are usually uploaded to RAM so free flash space is not an issue here. Exclusions are devices with >16 MB flash (mostly Routerboard and CCR devices) and hAP lite as it has only 32 MB of RAM so not enough room there either...
I have seeing this space error already in few devices: A CRS326, hAP AC, hAP ac2 with any 6.45.x version and I have been unable to find a solution. Even when I manually upload the firmware it reports wrongly the free space (i.e. 5% free) but I can upload the firmware that in theory exceeds this space limit.
I think this is a bug on the code and way files handling is done and/or how they are reported on the File System.
On hAP Lite, due limitation of storage so upgrade processI got same problem, Not enough space!hap lite upgrade issue is not fixed! I have a hap lite with very very very basic config (wifi pseudo bridge to local ports + dhcp client). I am running 6.45.1 and if I try to update to 6.45.3 I get an error : "ERROR: not enough disk space, 7.3MiB required and only 7.3MiB is free." ... I have no files on the device.
Looks like 16MiB flash size on hap lite devices was a very bad decision for mikrotik .... hope they learned a lesson from this fiasco!
JF.
Free HDD Space: 7.3 MiB Architecture Name: smips Board Name: hAP lite Version: 6.45.2 (stable)
main package *.npk
main package *.npk
$ wget https://download.mikrotik.com/routeros/6.45.3/routeros-mipsbe-6.45.3.npk
Connecting to download.mikrotik.com (download.mikrotik.com)|2a02:610:7501:4000::226|:443... connected.
routeros-mipsbe-6.4 100%[===================>] 11.54M 5.56MB/s in 2.1s
$ wget -4 https://download.mikrotik.com/routeros/6.45.3/routeros-mipsbe-6.45.3.npk
Connecting to download.mikrotik.com (download.mikrotik.com)|159.148.172.226|:443... connected.
routeros-mipsbe-6.4 100%[===================>] 11.54M 7.24MB/s in 1.6s
2019-08-16 13:19:34 (33.2 MB/s) - ‘routeros-mipsbe-6.45.3.npk’ saved [12097165/12097165]
#error exporting /ip ipsec identity
#error exporting /ip ipsec policy
#error exporting /ip ipsec settings
Why did you not fix the firewall instead? Or read about this problem in the earlier discussions about released versions?upgraded an rb450g from 6.44.3 to 6.45.3. my gre tunnel would not come up ike/ipsec working fine but could not get the tunnel up. Also seemed to affect logging, I could not get any debug info, in fact all that filled my logs were fw drops of the gre tunnel establishment traffic.
Provide more detailed information about "crash". After crash appears, write to support@mikrotik.com and send supout file from your router.omnitik crashes after upgrading firmware version to 6.45.3
Same issue here. It seems to be layer 2 side. e.g I can log into the routers if there is layer 3 access. However not via mac telent. Brand new routers, only updated ROS. i.e not downgraded. As soon as layer 3 establishes e.g pppoe then we can login with the correct admin/password combo.Can't login via linux MAC-Telnet 0.4.4. after update to this version.
Connecting to.......done
Login failed, incorrect username or password
ROS log: echo: system,error,critical login failure for user admin from XX:XX:XX:XX:XX:XX via mac-telnet.
The password is correct.
I've got same problem with RB1100-AhX4. I've got 4 RB1100 and all 4 crashing....omnitik crashes after upgrading firmware version to 6.45.3
Search back in the 6.45.x topics for the fix of GRE handling in firewall and the bug introduced by that fix and how to deal with it.After upgrading RB3011 from 6.44.3 to 6.45.3, all my PPTP has stopped working, inbound and outbound.
ok so I would need to also upgrade ROS on the interconnected router I am mac-telneting from?As login method was changed in v6.43 and old login method support was dropped in 6.45, you cannot use old MAC-Telnet clients anymore.
Looks like it's not the same problem as Olexandr999's (he's connecting from third-party Linux client, not from RouterOS or WinBox), but yes, you need to upgrade both MAC Telnet server and clientok so I would need to also upgrade ROS on the interconnected router I am mac-telneting from?
In version 6.45.3 this problem is presented. Still Hotspot captive portal not show automatically. In the client devices the message "Internet not available" is presented
Confirmed. Using the Web-Proxy to form a walled garden with a redirect to sign-up server. Was working under 6.44. Upgraded to 6.45.3 and redirect quit working. Downgraded to 6.44.5. Redirect started working again. Upgraded to 6.45.2 and redirect quit again.web proxy is not working with stable 6.45.3 on hAP Lite, not with the redirect firewall rule, nor with the explicit setting of the proxy server in the browser. Did work before, returned to long term 6.44.5 and it is working again.
Why a web-proxy on such a small device, without even caching something? Well the HTTP request handling by the proxy is much better than a Chrome browser. Pages do load 5 to 10 times faster with the proxy over a line with long round trip delay. (Satellite links have 600ms+ delays). Remote handling of the web interface of a router was not even possible over the direct satellite link, with the proxy server its again workable. It seems to be related to HTTP session reuse. (avoiding the long TCP session setup handshake, 600ms per request or answer)