Community discussions

 
rzirzi
Member
Member
Posts: 377
Joined: Mon Oct 09, 2006 2:33 pm

Re: v6.44 [stable] is released!

Sun Mar 03, 2019 9:30 am

This is not a bug, it tells you that you must install DHCP package now, read carefully the change list:
*) upgrade - made security package depend on DHCP package
Very stupid dependence! I don't need DHCP at many situations, but need SSH. So i have had installed: advanced-tools, security, system packages only. But now i have to use DHCP?! Nonsense!!!
 
aviper
Member Candidate
Member Candidate
Posts: 186
Joined: Thu Sep 15, 2005 5:48 pm

Re: v6.44 [stable] is released!

Sun Mar 03, 2019 10:53 am

Update from 6.40.8 to 6.44 seems to remove "system note" content.

Resolve: My mistake, I was removing all file, just to make space and be sure, that nothing is left in there. And I've removed the sys-note file.
 
pe1chl
Forum Guru
Forum Guru
Posts: 5711
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.44 [stable] is released!

Sun Mar 03, 2019 12:02 pm

Very stupid dependence! I don't need DHCP at many situations, but need SSH. So i have had installed: advanced-tools, security, system packages only. But now i have to use DHCP?! Nonsense!!!
Ideally, the new function of IKEv2 that requires DHCP would just be disabled until DHCP is installed (preferably with a remark in the user interface).
So DHCP only has to be installed when that function is desired.
But realistically it will probably be difficult to maintain such functions separate in the package dependencies and it would be better to merge packages
like dhcp, security, ipv6 and ppp all into system, leaving the packaging system only for real oddities like gps, ups, ntp, hotspot etc.
Last edited by pe1chl on Sun Mar 03, 2019 3:09 pm, edited 1 time in total.
 
User avatar
marlow
Member Candidate
Member Candidate
Posts: 159
Joined: Thu Mar 16, 2006 6:59 pm
Location: Ireland

Re: v6.44 [stable] is released!

Sun Mar 03, 2019 2:11 pm

saaremaa - Sorry about that. I mixed both services together. We do support Delegated-IPv6-Prefix for DHCP service but not for PPP yet. It is in our plans to add support for this in the future;


Why on earth would you implement it for one service and not for another ? PPPoE is actually the one where it would have been more important to get it implemented, because that's more commonly used in broadband distribution than DHCP.

Especially when it comes to FTTH and VDSL.

/M
Communication is the beginning of understanding
-- AT&T
 
WirelessRudy
Forum Guru
Forum Guru
Posts: 3082
Joined: Tue Aug 08, 2006 5:54 pm
Location: Spain

Re: v6.44 [stable] is released!

Sun Mar 03, 2019 10:27 pm

In my network things were running smoothly without complaints from clients, the day after going from 6.42.3 to 6.44 we starded receiving many complaints about slow internet speed. In two sectors we have two clients with signal going from -68 to -72 and these clients were using the Internet without any complaint along with the other ones on the same sector, but right after upgrading to 6.44 these "bad" signal clients and others that never complained about something started calling us saying the internet was slow...My conclusion is, something is not as good as it was on 6.42.3 in NV2 for misbe devices. You were the one that said something was done to improve things for mixed networks so I assumed that these improvements have caused something negative for mipsbe only networks or for them all regarding "bad" signal clients on the sector. Mikrotik had made a promise a few months ago that from that time on bad clients would not affect other clients on the same sector, but it seems this is not true for the newer ROS versions.
dadoremix gave you a possible answer..

I did not see signal getting less in software updates. But indeed, the country code I used I has to set to 'no_country' to get my network back to where it was.... ;-)
Show your appreciation of this post by giving me Karma! Thanks.

Rudy R. Puister

WISP operator based on MT routerboard & ROS.
 
Raumaster
newbie
Posts: 31
Joined: Fri Sep 28, 2012 2:18 am

Re: v6.44 [stable] is released!

Sun Mar 03, 2019 11:09 pm

In my network things were running smoothly without complaints from clients, the day after going from 6.42.3 to 6.44 we starded receiving many complaints about slow internet speed. In two sectors we have two clients with signal going from -68 to -72 and these clients were using the Internet without any complaint along with the other ones on the same sector, but right after upgrading to 6.44 these "bad" signal clients and others that never complained about something started calling us saying the internet was slow...My conclusion is, something is not as good as it was on 6.42.3 in NV2 for misbe devices. You were the one that said something was done to improve things for mixed networks so I assumed that these improvements have caused something negative for mipsbe only networks or for them all regarding "bad" signal clients on the sector. Mikrotik had made a promise a few months ago that from that time on bad clients would not affect other clients on the same sector, but it seems this is not true for the newer ROS versions.

Check country code in ros
And signals
They kill power in some countrys
We use superchannel.
 
marit
just joined
Posts: 1
Joined: Sun Mar 03, 2019 11:46 pm

Re: v6.44 [stable] is released!

Sun Mar 03, 2019 11:57 pm

Mikrotik RB4011iGS+ from version 6.43.12 to 6.44.

Devices from VLANs stopped responding.
I have created a bridge that contains a sfp port.
VLAN assigned to the bridge.
From the mikrotik SFP port to the other switch.
The port SFP on the other switch is tagged, unfortunately, it does not respond correctly after the update (ping time out).
Rollback old version and now it works correctly.
What could be the reason?
 
xPucTu4
just joined
Posts: 3
Joined: Sun Dec 06, 2009 3:10 pm

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 3:19 am

On 4011iGS.... after update the SFP started flapping 1-2 times per second.
It is 1gb SFP.
The port is not in bridge, it have vlans. Updated to the test version but the flapping continued. Then downgraded back to 6.43.12 and it works again.
The SFP module is @irLAN. They are widely used in Bulgaria because of the price. I moved the SFP to a switch and it works there too.
From the SFP properties page in winbox:
Vendor part number: SFP-LH-SM
Serial: H50001116
 
mducharme
Trainer
Trainer
Posts: 795
Joined: Tue Jul 19, 2016 6:45 pm

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 5:08 am

MikroTik as remote DHCP server for relay purposes (not connected directly to the network that DHCP is used on) stops giving leases after upgrade, seemingly due to new ARP conflict detection feature. Disabling conflict detection resolves the issue. Shouldn't this feature shut itself off if the router doesn't have an IP on the target subnet (and therefore can't make ARP requests)?
 
andriys
Forum Guru
Forum Guru
Posts: 1135
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 9:37 am

We use superchannel.
The country setting now has priority, so your superchannel won't work unless you have country set to no_country_set. The forum is full of discussions about this change...
 
kangarie
just joined
Posts: 11
Joined: Mon Apr 17, 2017 7:28 am

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 10:39 am

i just test https-redirect option

https-redirect=yes
if unlogged user try to open https website, it will be redirected to hostpot login with https. same behavior as previous version
so browser will show cert warning because cert common name is not same with domain

https-redirect=no
if unlogged user try to open https website, it will be rejected/refused so browser will error like there is no internet access

CMIIW
 
unable08
just joined
Posts: 1
Joined: Mon Mar 04, 2019 10:53 am

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 11:06 am

*) lte - fixed LTE interface not working properly after reboot on RBSXTLTE3-7;
Hi, my RBSXTLTE3-7 stops working after firmware upgrade. LTE interface is not working with status "Changing band", also there is an error in log "reply timeout for ate0".
 
tomek242
just joined
Posts: 2
Joined: Mon Mar 04, 2019 11:13 am

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 11:16 am

Hello Every MikroTik fans.
I upgraded my STX LTE router to 6.44 stable version software. Unfortunatelly when i was rebooted my router i have only half signal value on band 7, when i was try to switch router for band 3 everything crashes and I can't connect to any LTE network.
I was try to install oldest stabled versions of software but every time i had same problem: in first use i had only half signal in band 7 and crash when i was switched to band 3.

I have a LTE broadcasting tower some about 400 maybe 500 meters of my location. This is parameters of LTE transmitter:
Play (26006) ID: SKA3305 This transmitter use band 3 GSM1800 GSM900 LTE1800 LTE2100 LTE800 UMTS2100 UMTS900

Greetings Tom
Last edited by tomek242 on Mon Mar 04, 2019 1:23 pm, edited 1 time in total.
 
tomek242
just joined
Posts: 2
Joined: Mon Mar 04, 2019 11:13 am

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 11:18 am

*) lte - fixed LTE interface not working properly after reboot on RBSXTLTE3-7;
Hi, my RBSXTLTE3-7 stops working after firmware upgrade. LTE interface is not working with status "Changing band", also there is an error in log "reply timeout for ate0".
I have same problem :)
 
kalsze
just joined
Posts: 9
Joined: Tue Sep 08, 2015 6:12 am

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 11:26 am

Has anybody else ran into a weird problem where SSH would not connect after upgrading to 6.44? Everything was still working up to and including 6.43.12.

I have a setup that's like this:
[Ubuntu Desktop] <-- Office LAN (172.26.2.0/24) --> [RouterBoard "ovpn-endpoint" running OpenVPN server] <-- OpenVPN --> [RouterBoard "router2" running OpenVPN client] <-- bridge-local --> [Raspberry Pi]
When router2 was running RouterOS 6.43.12, I used to be able to SSH into the Raspberry Pi from my Ubuntu Desktop, by doing:
ssh foo@172.28.2.179
where 172.28.2.179 is the Raspberry Pi's IP from router2's DHCP server, within bridge-local.

I could do this because my Office LAN has a DHCP option telling my Ubuntu Desktop to send packets for 172.28.2.0/24 via the "ovpn-endpoint" RouterBoard.

router2 has an IP route rule so it knows to send back packets destined for 172.26.2.0/24 via the OpenVPN connection.

Now, after upgrading router2 to RouterOS 6.44, I see this when I do `ssh -v foo@172.28.2.179`:
OpenSSH_7.6p1 Ubuntu-4ubuntu0.2, OpenSSL 1.0.2n  7 Dec 2017
debug1: Reading configuration data /home/kal/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 172.28.2.179 [172.28.2.179] port 22.
debug1: Connection established.
debug1: identity file /home/kal/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/kal/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kal/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kal/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kal/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kal/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kal/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kal/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.2
And then it gets stuck.

In router2, I see these IP firewall filter rules:
Flags: X - disabled, I - invalid, D - dynamic 
 0    ;;; default configuration
      chain=input action=accept protocol=icmp log=no log-prefix="" 

 1    ;;; default configuration
      chain=input action=accept connection-state=established,related log=no log-prefix="" 

 2    ;;; default configuration
      chain=input action=drop in-interface=ether1-gateway log=no log-prefix="" 

 3    ;;; default configuration
      chain=forward action=accept connection-state=established,related log=no log-prefix="" 

 4    ;;; Allow only the registration and scan raspberry pis and the scanner to access the internet.
      chain=forward action=accept src-address-list=with_internet_access out-interface=ether1-gateway log=no log-prefix="" 

 5    ;;; Forbid everybody else from accessing the internet.
      chain=forward action=drop out-interface=ether1-gateway log=no log-prefix="" 

 6    ;;; Forward related and established connections from the internet to the registration and scan raspberry pis and the scanner.
      chain=forward action=accept connection-state=established,related in-interface=ether1-gateway log=no log-prefix="" 

 7    ;;; Drop forwarding from the internet for everybody else.
      chain=forward action=drop in-interface=ether1-gateway log=no log-prefix="" 

 8    ;;; default configuration
      chain=forward action=drop connection-state=invalid log=no log-prefix="" 

 9    ;;; default configuration
      chain=forward action=drop connection-state=new connection-nat-state=!dstnat in-interface=ether1-gateway log=no log-prefix="" 
Rule 8 is dropping packets during the SSH handshake for some reason.

If I enable logging (`/ip firewall filter set 8 log=yes log-prefix="debug"`), I see that it's dropping packets like these:
16:05:46 firewall,info debug forward: in:bridge-local out:ovpn-out1, src-mac b8:27:eb:53:4c:91, proto TCP (SYN,ACK), 172.28.2.179:22->172.26.2.229:55490, len 60 
16:05:48 firewall,info debug forward: in:ovpn-out1 out:bridge-local, proto TCP (ACK,FIN), 172.26.2.229:55490->172.28.2.179:22, len 52 
16:05:57 firewall,info debug forward: in:ovpn-out1 out:bridge-local, proto TCP (ACK,PSH), 172.26.2.229:55500->172.28.2.179:22, len 93 
16:05:58 firewall,info debug forward: in:bridge-local out:ovpn-out1, src-mac b8:27:eb:53:4c:91, proto TCP (SYN,ACK), 172.28.2.179:22->172.26.2.229:55500, len 60 
16:06:04 firewall,info debug forward: in:ovpn-out1 out:bridge-local, proto TCP (ACK,PSH), 172.26.2.229:55500->172.28.2.179:22, len 93 
16:06:06 firewall,info debug forward: in:bridge-local out:ovpn-out1, src-mac b8:27:eb:53:4c:91, proto TCP (SYN,ACK), 172.28.2.179:22->172.26.2.229:55500, len 60 
16:06:18 firewall,info debug forward: in:ovpn-out1 out:bridge-local, proto TCP (ACK,PSH), 172.26.2.229:55500->172.28.2.179:22, len 93 
16:06:22 firewall,info debug forward: in:bridge-local out:ovpn-out1, src-mac b8:27:eb:53:4c:91, proto TCP (SYN,ACK), 172.28.2.179:22->172.26.2.229:55500, len 60 
If I disable rule 8 (`/ip firewall filter disable 8`), SSH goes through.

Does anybody have any idea why the packets are being dropped as invalid in RouterOS 6.44?

To be clear, my SSH connections are *not* NAT'ed. All of the RouterBoards involved have `/ip route` rules that just forward the packets through the correct connection without NAT'ing. They're only acting as gateways.
Last edited by kalsze on Wed Mar 06, 2019 4:58 am, edited 1 time in total.
 
ste
Forum Guru
Forum Guru
Posts: 1796
Joined: Sun Feb 13, 2005 11:21 pm

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 3:08 pm

i update to 6.44 but when i wana use ip cloud sometimes about half of time i try "Error: request Timed out" what should i do?
Send report to support@mikrotik.com including .rif File.
 
Redmor
Member Candidate
Member Candidate
Posts: 248
Joined: Wed May 31, 2017 7:40 pm
Location: Italy

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 3:49 pm

PWR-Line port on hAP
ImageImage
 
rzirzi
Member
Member
Posts: 377
Joined: Mon Oct 09, 2006 2:33 pm

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 3:59 pm

After upgrade from ROS 6.43.12 to 6.44 - I have lost possibility co connect to my MT with L2TP (with preshared key) VPN. I was changing firewall settings, trying other.... but after downgrade to 6.43.12 - IT WORKS AGAIN. So something is BAD with ROS 6.44 and L2TP VPN ! MikroTik team - please repir that ROS 6.44 BUG.
 
Halfeez92
newbie
Posts: 36
Joined: Tue Oct 30, 2012 12:58 pm
Contact:

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 5:00 pm

*) lte - fixed LTE interface not working properly after reboot on RBSXTLTE3-7;
Hi, my RBSXTLTE3-7 stops working after firmware upgrade. LTE interface is not working with status "Changing band", also there is an error in log "reply timeout for ate0".
Exactly my problem.

I remotely upgraded my SXTLTE3-7 from far away. After that I didnt see the VPN connection. Luckily I have other friends that can help me remote to downgrade to the previous version.
 
User avatar
spacex
Frequent Visitor
Frequent Visitor
Posts: 51
Joined: Sun Aug 19, 2018 6:03 pm

Re: v6.44 [stable] is released!

Mon Mar 04, 2019 10:52 pm

PWR-Line port on hAP
I am wondering too
 
Askey307
newbie
Posts: 49
Joined: Fri Sep 29, 2017 10:20 am
Location: South Africa
Contact:

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 12:52 pm

Hi

Since the last update we have had multiple clients complaining about existing sites where VoIP experiences issues, from de-registration, no audio, one way audio.
Currently we downgrading the clients back to 6.43.8 which works.

I've sent multiple supouts and support tickets to Support with no feedback.

We're a big distributor of Mikrotik, and this is the first we get with VoIP.
 
DenisPDA
newbie
Posts: 30
Joined: Tue Sep 04, 2018 5:42 pm

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 1:10 pm

Hi

Since the last update we have had multiple clients complaining about existing sites where VoIP experiences issues, from de-registration, no audio, one way audio.
Currently we downgrading the clients back to 6.43.8 which works.

I've sent multiple supouts and support tickets to Support with no feedback.

We're a big distributor of Mikrotik, and this is the first we get with VoIP.
I have a suggestion that the problem is in the firewall (6.44)
Connection-state errors (estabilished, invalid, related)
To be precise
That connection is dropped for reasons that are not understandable.
I found a solution for myself
Create an allow rule above (estabilished, related)
But it's not right
 
User avatar
Deantwo
Member Candidate
Member Candidate
Posts: 290
Joined: Tue Sep 30, 2014 4:07 pm

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 1:20 pm

Upgrading my RB750 from RouterOS 6.40.8 to 6.44 leaves all IPsec peers with "unknown" profiles.
And it looks like any IPsec peer settings were lost since only "default" profile exist.

Do I have to jump to another version first and then jump to 6.44?

Gonna go test if it also happen if I upgrade to 6.42.12 long-trem.
Last edited by Deantwo on Tue Mar 05, 2019 1:31 pm, edited 2 times in total.
I wish my FTP was FTL.
 
Askey307
newbie
Posts: 49
Joined: Fri Sep 29, 2017 10:20 am
Location: South Africa
Contact:

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 1:23 pm

Hi

Since the last update we have had multiple clients complaining about existing sites where VoIP experiences issues, from de-registration, no audio, one way audio.
Currently we downgrading the clients back to 6.43.8 which works.

I've sent multiple supouts and support tickets to Support with no feedback.

We're a big distributor of Mikrotik, and this is the first we get with VoIP.
I have a suggestion that the problem is in the firewall (6.44)
Connection-state errors (estabilished, invalid, related)
To be precise
That connection is dropped for reasons that are not understandable.
I found a solution for myself
Create an allow rule above (estabilished, related)
But it's not right
Can you share an example of this established related firewall rule please if you don't mind.
Yeah I agree, this is no right.
Would love some answers from Mikrotik, because I have 6 cases in 3 last week and open cases open since last week.
 
DenisPDA
newbie
Posts: 30
Joined: Tue Sep 04, 2018 5:42 pm

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 1:53 pm

Hi

Since the last update we have had multiple clients complaining about existing sites where VoIP experiences issues, from de-registration, no audio, one way audio.
Currently we downgrading the clients back to 6.43.8 which works.

I've sent multiple supouts and support tickets to Support with no feedback.

We're a big distributor of Mikrotik, and this is the first we get with VoIP.
I have a suggestion that the problem is in the firewall (6.44)
Connection-state errors (estabilished, invalid, related)
To be precise
That connection is dropped for reasons that are not understandable.
I found a solution for myself
Create an allow rule above (estabilished, related)
But it's not right
Can you share an example of this established related firewall rule please if you don't mind.
Yeah I agree, this is no right.
Would love some answers from Mikrotik, because I have 6 cases in 3 last week and open cases open since last week.
This is a rough example.
1 action=accept chain=forward dst-address=10.10.10.10 src-address=8.8.8.8
1 rule without specifying connection-state
2 action=accept chain=forward connection-state=established,related
3 action=drop chain=forward connection-state=invalid
 
pe1chl
Forum Guru
Forum Guru
Posts: 5711
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 1:57 pm

Hi

Since the last update we have had multiple clients complaining about existing sites where VoIP experiences issues, from de-registration, no audio, one way audio.
Currently we downgrading the clients back to 6.43.8 which works.

I've sent multiple supouts and support tickets to Support with no feedback.

We're a big distributor of Mikrotik, and this is the first we get with VoIP.
I have a suggestion that the problem is in the firewall (6.44)
Connection-state errors (estabilished, invalid, related)
To be precise
That connection is dropped for reasons that are not understandable.
I found a solution for myself
Create an allow rule above (estabilished, related)
But it's not right
Maybe it could be related to the bug that I reported above? (loose TCP connection tracking no longer works)
It could be that there were changes in the connection tracking firewall that have side effects like this.
 
DenisPDA
newbie
Posts: 30
Joined: Tue Sep 04, 2018 5:42 pm

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 2:26 pm

Maybe it could be related to the bug that I reported above? (loose TCP connection tracking no longer works)
It could be that there were changes in the connection tracking firewall that have side effects like this.
I can say with complete confidence that on average I have 15% fewer connections. (6.44)
 
buset1974
Frequent Visitor
Frequent Visitor
Posts: 50
Joined: Wed Sep 13, 2006 12:12 pm
Location: Jakarta

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 6:02 pm

*) bgp - properly update keepalive time after peer restart;

what exactly this fix for?
i still having problem with bgp withdraw on PE - CE
and also i still having bgp stuck on vrf.

thx
 
pe1chl
Forum Guru
Forum Guru
Posts: 5711
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.44 [stable] is released!

Tue Mar 05, 2019 6:59 pm

*) bgp - properly update keepalive time after peer restart;

what exactly this fix for?
I have seen issues with BGP when the keepalive time is not set equal at both peers.
According to the protocol spec the lower of the two keepalive times should be used by both peers.
But in practice it sometimes happened that each peer used its own local keepalive time and the route was flapping when one is >3 times the other.
(e.g. default is 180 and I sometimes set this to 15 on wireless links where BFD is not in use)

Maybe this has been fixed now. But you could always work around it by configuring the same keepalive time on both routers.
 
tarcisionmjr
just joined
Posts: 17
Joined: Thu Sep 21, 2006 1:47 pm

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 2:06 am

2 x CRS326-24G-2S+ - Updated to version 6.44 and working fine ..
1 x CCR1072-1G-8S+ - Updated to version 6.44 and working fine ..

1 x CRS317-1G-16S+ - Upgraded to version 6.44 and running fine for up to 4 hours, the SNMP and Graphics Tool features stop working and, consequently, the interface view no longer looks like winbox ...
 
buset1974
Frequent Visitor
Frequent Visitor
Posts: 50
Joined: Wed Sep 13, 2006 12:12 pm
Location: Jakarta

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 2:27 am

*) bgp - properly update keepalive time after peer restart;

what exactly this fix for?
I have seen issues with BGP when the keepalive time is not set equal at both peers.
According to the protocol spec the lower of the two keepalive times should be used by both peers.
But in practice it sometimes happened that each peer used its own local keepalive time and the route was flapping when one is >3 times the other.
(e.g. default is 180 and I sometimes set this to 15 on wireless links where BFD is not in use)

Maybe this has been fixed now. But you could always work around it by configuring the same keepalive time on both routers.
i see, yes i have that problem too, after migration, we have all bgp's flapping so i have to set keepalive on both side.

thanks for the info.
 
kalsze
just joined
Posts: 9
Joined: Tue Sep 08, 2015 6:12 am

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 3:38 am

Hi

Since the last update we have had multiple clients complaining about existing sites where VoIP experiences issues, from de-registration, no audio, one way audio.
Currently we downgrading the clients back to 6.43.8 which works.

I've sent multiple supouts and support tickets to Support with no feedback.

We're a big distributor of Mikrotik, and this is the first we get with VoIP.
I have a suggestion that the problem is in the firewall (6.44)
Connection-state errors (estabilished, invalid, related)
To be precise
That connection is dropped for reasons that are not understandable.
I found a solution for myself
Create an allow rule above (estabilished, related)
But it's not right
Maybe it could be related to the bug that I reported above? (loose TCP connection tracking no longer works)
It could be that there were changes in the connection tracking firewall that have side effects like this.
Looks like we're all hit by the same problem, manifested over different application protocols. See my post above.
 
tarcisionmjr
just joined
Posts: 17
Joined: Thu Sep 21, 2006 1:47 pm

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 7:25 am

2 x CRS326-24G-2S+ - Updated to version 6.44 and working fine ..
1 x CCR1072-1G-8S+ - Updated to version 6.44 and working fine ..

1 x CRS317-1G-16S+ - Upgraded to version 6.44 and running fine for up to 4 hours, the SNMP and Graphics Tool features stop working and, consequently, the interface view no longer looks like winbox ...
1 x CRS317-1G-16S+ - Upgraded to version 6.44 and running fine for up to 4 hours, the SNMP and Graphics Tool features stop working and, consequently, the interface view no longer looks like winbox...

CRS317-1G-16S+ - After 4 hours the switch stops responding to the command ... which gets frozen when digit is not returned by the console ...
/interface print
 
llag
newbie
Posts: 31
Joined: Sat Aug 04, 2018 12:12 am

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 12:23 pm

I Installed 6.44 on my CRS328-24p and my CRS317 switches.

I now have some real problems logging in to the web interface using Firefox on the CRS317: I type the userid and passwd but login fails with: ERROR: Not Found.
This does not happen all the time, but only 1 in 30 logins or so succeeds.
Login through Chromium works all the time.
I have seen the same on the CRS328 but only sporadically.
Does anybody have a suggestion how to solve this?
 
pe1chl
Forum Guru
Forum Guru
Posts: 5711
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 4:05 pm

Maybe it could be related to the bug that I reported above? (loose TCP connection tracking no longer works)
It could be that there were changes in the connection tracking firewall that have side effects like this.
Looks like we're all hit by the same problem, manifested over different application protocols. See my post above.
Indeed there really appears to be some bug. Not only are the existing connections lost after reboot (not working loose-tcp-tracking) but also I see firewall log messages that indicate that tracking of existing connections has been lost at some time even though te connections still exist.
(of course that was less of a problem when loose tracking was still working)
In my case it were TCP TLS connections (port 443) and the loss of those is often not catastrophic, they will be re-established without the user noticing, but in case of VoIP it could be different.

I hope MikroTik will look into this matter. I see no changelog entry that explains what is happening here.
 
admir
just joined
Posts: 11
Joined: Sun Jun 24, 2018 4:49 pm

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 7:06 pm

BUG – v.6.44 on ARM boxes RB3011 is losing IPSEC configuration

After upgrade of ARM boxes (RB3011) to latest stable version 6.44, IPSEC is not working.
Winbox GUI /ip ipsec section in is empty and no new config parameters can be added;
In console /ip ipsec export gives just info that all subsections can’t be exported.
 
User avatar
osc86
newbie
Posts: 49
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 7:22 pm

BUG – v.6.44 on ARM boxes RB3011 is losing IPSEC configuration

After upgrade of ARM boxes (RB3011) to latest stable version 6.44, IPSEC is not working.
Winbox GUI /ip ipsec section in is empty and no new config parameters can be added;
In console /ip ipsec export gives just info that all subsections can’t be exported.
I had the same problem.
Official response from support:
Yes, this confirms the issue is caused by some old 6.44beta version converting some of the configuration. And when you downgraded and upgraded again, it run into these issues.
I downgraded to 6.43, exported the config (and certificates), removed everything in /ip ipsec from the text file, fresh installed 6.44 and imported the config from the text file.
Making a backup of the router running 6.43 and importing it in 6.44 won't work.
Once 6.44 is installed, you have to redo the ipsec configuration by hand.
CCR1009-7G-1C-1S+ ROS6.45.2
 
Raumaster
newbie
Posts: 31
Joined: Fri Sep 28, 2012 2:18 am

Re: v6.44 [stable] is released!

Wed Mar 06, 2019 7:42 pm

We use superchannel.
The country setting now has priority, so your superchannel won't work unless you have country set to no_country_set. The forum is full of discussions about this change...
All our APs are set to "no_country_set" since forever.
 
kalsze
just joined
Posts: 9
Joined: Tue Sep 08, 2015 6:12 am

Re: v6.44 [stable] is released!

Thu Mar 07, 2019 4:36 am

Maybe it could be related to the bug that I reported above? (loose TCP connection tracking no longer works)
It could be that there were changes in the connection tracking firewall that have side effects like this.
Looks like we're all hit by the same problem, manifested over different application protocols. See my post above.
Indeed there really appears to be some bug. Not only are the existing connections lost after reboot (not working loose-tcp-tracking) but also I see firewall log messages that indicate that tracking of existing connections has been lost at some time even though te connections still exist.
(of course that was less of a problem when loose tracking was still working)
In my case it were TCP TLS connections (port 443) and the loss of those is often not catastrophic, they will be re-established without the user noticing, but in case of VoIP it could be different.

I hope MikroTik will look into this matter. I see no changelog entry that explains what is happening here.
A bit more info: it appears (for me at least) that this problem crops up if the forward and return paths of the connections are somehow not symmetrical.

In my case, somebody disabled DHCP options 121 and 249 in our office router without telling me, so this is what was happening to the packets:

Forward path:
[ My PC ] ==(office LAN)==>
[ Main RouterBoard of my office (RouterOS 6.43.2) ] ==(office LAN)==>
[ OpenVPN endpoint RouterBoard (RouterOS 6.43.12) ] ==(OpenVPN connection)==>
[ Remote RouterBoard (RouterOS 6.44) ] ==(bridge-local)==>
[ Raspberry Pi ]
Return path:
[ Raspberry Pi ] ==(bridge-local)==>
[ Remote RouterBoard ] ==(OpenVPN connection)==>
[ OpenVPN endpoint RouterBoard ] ==(office LAN)==>
[ My PC ]
Note how the "Main RouterBoard of my office" is skipped in the return path. This is because my OpenVPN endpoint RouterBoard and my PC are actually in the same office LAN.

The Main RouterBoard used to serve out DHCP options 121 and 249 that tell PCs on the office LAN to just use the OpenVPN endpoint RouterBoard as gateway for reaching the Remote RouterBoard's bridge-local network.

Instead, with those DHCP options disabled, my PC sent packets to the Main RouterBoard first because its the default route, then, the Main RouterBoard (with its own `/ip route` rule) re-routed the packets to the OpenVPN endpoint RouterBoard. My Raspberry Pi would reply directly to my PC's IP (remember, no NAT'ing), and the packet eventually reaches the OpenVPN endpoint RouterBoard, which sends the reply packet directly to my PC, without going through the Main RouterBoard.

Once I re-enabled those DHCP options, the Main RouterBoard of my office is skipped in the forward path as well, so the forward and return paths are symmetrical again, and SSH is working again without having to allow "invalid" packets through the Remote RouterBoard. Still, I don't understand why the Remote RouterBoard can be sensitive to path symmetry.
Last edited by kalsze on Thu Mar 07, 2019 6:28 am, edited 1 time in total.
 
tarcisionmjr
just joined
Posts: 17
Joined: Thu Sep 21, 2006 1:47 pm

Re: v6.44 [stable] is released!

Thu Mar 07, 2019 5:48 am

2 x CRS326-24G-2S+ - Updated to version 6.44 and working fine ..
1 x CCR1072-1G-8S+ - Updated to version 6.44 and working fine ..

1 x CRS317-1G-16S+ - Upgraded to version 6.44 and running fine for up to 4 hours, the SNMP and Graphics Tool features stop working and, consequently, the interface view no longer looks like winbox ...
1 x CRS317-1G-16S+ - Upgraded to version 6.44 and running fine for up to 4 hours, the SNMP and Graphics Tool features stop working and, consequently, the interface view no longer looks like winbox...

CRS317-1G-16S+ - After 4 hours the switch stops responding to the command ... which gets frozen when digit is not returned by the console ...
/interface print
unfortunately, I had to go back to version 6.43.12, the CRS317, which turned out to be good again and did not crash or give graphics anymore ...

mikrotik friends check it out on CRS317 that has problems with version 6.44 ...
 
admir
just joined
Posts: 11
Joined: Sun Jun 24, 2018 4:49 pm

Re: v6.44 [stable] is released!

Thu Mar 07, 2019 11:12 am

The same IPSEC config problem on some RB2011 (mipsBE) device too.

Console output:
/ip ipsec profile> add .....
error - contact MikroTik support and send a supout file

/ip ipsec export
#error exporting /ip ipsec mode-config
#error exporting /ip ipsec peer
#error exporting /ip ipsec policy group
#error exporting /ip ipsec profile
#error exporting /ip ipsec proposal
#error exporting /ip ipsec identity
#error exporting /ip ipsec policy
#error exporting /ip ipsec settings

Upgrade was done from latest stable 6.43.12 to next release stable 6.44.
 
MikrotikBGSHOP
just joined
Posts: 4
Joined: Mon Apr 23, 2018 1:14 pm
Location: Bulgaria

Re: v6.44 [stable] is released!

Thu Mar 07, 2019 6:24 pm

PWR-Line port on hAP
I am wondering too
Not a bug.
Interface for new PWR line adapter comming next months.
hAP mini & hAP lite has it. Basicly power the device and transfer data via microusb port.

Sent from my SM-G950F using Tapatalk

 
MikrotikBGSHOP
just joined
Posts: 4
Joined: Mon Apr 23, 2018 1:14 pm
Location: Bulgaria

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 1:21 pm

PWR-Line port on hAP
I am wondering too
Not a bug.
Interface for new PWR line adapter comming next months.
hAP mini & hAP lite has it. Basicly power the device and transfer data via microusb port.

Sent from my SM-G950F using Tapatalk
And the new powerline with microusbImage

Sent from my SM-G950F using Tapatalk

 
nostromog
Member Candidate
Member Candidate
Posts: 149
Joined: Wed Jul 18, 2018 3:39 pm

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 2:31 pm

Interface for new PWR line adapter comming next months.
hAP mini & hAP lite has it. Basicly power the device and transfer data via microusb port.
Also the mAP Lite 2nd (at least mine, revision r2. I'm not sure about older ones)

I just bought a few and they came with this surprise. :)
 
Alastair
just joined
Posts: 4
Joined: Tue Jun 05, 2018 10:14 pm

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 2:50 pm

Will UK users be disappointed again though, with no UK variant plug? :/
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 1295
Joined: Sat Dec 24, 2016 11:17 am
Location: jo.overland at gmail.com

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 2:55 pm

Maybe its time for UK to change to EU plug.
Ahh, I did forget UK goes out of EU :)

I have travel around the world and UK plug is one the ugliest and largest plug out there....
 
How to use Splunk to monitor your MikroTik Router

MikroTik->Splunk
 
 
Kindis
Member Candidate
Member Candidate
Posts: 245
Joined: Tue Nov 01, 2011 6:54 pm

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 3:34 pm

Maybe its time for UK to change to EU plug.
Ahh, I did forget UK goes out of EU :)

I have travel around the world and UK plug is one the ugliest and largest plug out there....
I live in Sweden but I must say the UK plug is one of the bulkiest to work work with it is also one if the smartest with fuse in the plug and designed for a large contact surface and also be child friendly.
 
raffav
Member Candidate
Member Candidate
Posts: 286
Joined: Wed Oct 24, 2012 4:40 am

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 4:47 pm

Maybe its time for UK to change to EU plug.
Ahh, I did forget UK goes out of EU :)

I have travel around the world and UK plug is one the ugliest and largest plug out there....
I live in Sweden but I must say the UK plug is one of the bulkiest to work work with it is also one if the smartest with fuse in the plug and designed for a large contact surface and also be child friendly.
They say that is the most safety Plug, as you need to insert the earth ping to "unlock" the energizing plug as well with this individually surge protection with fuses another handly about the UK plug is that they have a switch so y can shut down the plug without removing the plug I think this clever move, the only downside of this is that you lose a lot of space, so in a wall outlet can be only 2 plug
 
WirelessRudy
Forum Guru
Forum Guru
Posts: 3082
Joined: Tue Aug 08, 2006 5:54 pm
Location: Spain

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 5:07 pm

Maybe its time for UK to change to EU plug.
Ahh, I did forget UK goes out of EU :)

I have travel around the world and UK plug is one the ugliest and largest plug out there....
I live in Sweden but I must say the UK plug is one of the bulkiest to work work with it is also one if the smartest with fuse in the plug and designed for a large contact surface and also be child friendly.
They say that is the most safety Plug, as you need to insert the earth ping to "unlock" the energizing plug as well with this individually surge protection with fuses another handly about the UK plug is that they have a switch so y can shut down the plug without removing the plug I think this clever move, the only downside of this is that you lose a lot of space, so in a wall outlet can be only 2 plug
Houses with proper electrical installation like most in (West-?)Europe have fuses and differential to protect the user. An extra protection in the plug is overdone.

Apart from that, the flat pins in fact are worse for surface contact then round. With round pins there is always change for better contact with the clamp then when its flat.
No, the English design is not the best.... we remove them where we can (many English customers in this Western European country I work!)
Show your appreciation of this post by giving me Karma! Thanks.

Rudy R. Puister

WISP operator based on MT routerboard & ROS.
 
User avatar
eworm
Member
Member
Posts: 378
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 7:22 pm

Interface for new PWR line adapter comming next months.
hAP mini & hAP lite has it. Basicly power the device and transfer data via microusb port.
Also the mAP Lite 2nd (at least mine, revision r2. I'm not sure about older ones)
This requires the new hardware, old mAP lite can not get this from software.
Manage RouterOS scripts and extend your devices' functionality: RouterOS Scripts
 
raffav
Member Candidate
Member Candidate
Posts: 286
Joined: Wed Oct 24, 2012 4:40 am

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 7:24 pm

I still do not get what really is this new power line.
 
nostromog
Member Candidate
Member Candidate
Posts: 149
Joined: Wed Jul 18, 2018 3:39 pm

Re: v6.44 [stable] is released!

Fri Mar 08, 2019 9:58 pm

I still do not get what really is this new power line.
If you compare this Image (the block diagram of a mAP Lite


with this Image you will see that what they have presented
is a power supply that turns a mAP lite into a PL7411-2nD. I hope it will not be too expensive, because I don't need it
but I would like to play with it, and I have a couple of mAP lites and a hAP ac lite to play with :D

Sorry I can't find a way to resize images
 
User avatar
CZFan
Forum Guru
Forum Guru
Posts: 1361
Joined: Sun Oct 09, 2016 8:25 pm
Location: South Africa, Randburg
Contact:

Re: v6.44 [stable] is released!

Sat Mar 09, 2019 1:02 am

Hi

Since the last update we have had multiple clients complaining about existing sites where VoIP experiences issues, from de-registration, no audio, one way audio.
Currently we downgrading the clients back to 6.43.8 which works.

I've sent multiple supouts and support tickets to Support with no feedback.

We're a big distributor of Mikrotik, and this is the first we get with VoIP.

Hi,

I have noticed on this forum that many times the problem is not due to updates, but in fact due to incorrect configurations.

Maybe a suggestion will be to engage with one of your registered dealers / re-sellers which are also Mikrotik Certified to look into the issue (I am both).

This way the Mikrotik Certified consultants can also gain financially and the distributor also supports the registered dealers / re-sellers
MTCNA, MTCTCE, MTCRE & MTCINE
 
DenisPDA
newbie
Posts: 30
Joined: Tue Sep 04, 2018 5:42 pm

Re: v6.44 [stable] is released!

Sat Mar 09, 2019 10:29 pm

Hi,

I have noticed on this forum that many times the problem is not due to updates, but in fact due to incorrect configurations.

Maybe a suggestion will be to engage with one of your registered dealers / re-sellers which are also Mikrotik Certified to look into the issue (I am both).

This way the Mikrotik Certified consultants can also gain financially and the distributor also supports the registered dealers / re-sellers
Greetings
Can you clarify what the error is?
 
Borage
Member Candidate
Member Candidate
Posts: 170
Joined: Sun Sep 26, 2004 10:19 pm

Re: v6.44 [stable] is released!

Sun Mar 10, 2019 3:47 am

Static host route is very unreliable in this release. I have a web server that I need to reach through another gateway and it works sporadically.

I didn't count but it works approx. 30 seconds and then a timeout for 30 seconds and so on.
 
DenisPDA
newbie
Posts: 30
Joined: Tue Sep 04, 2018 5:42 pm

Re: v6.44 [stable] is released!

Sun Mar 10, 2019 8:40 am

Static host route is very unreliable in this release. I have a web server that I need to reach through another gateway and it works sporadically.

I didn't count but it works approx. 30 seconds and then a timeout for 30 seconds and so on.
I confirm
This is a firewall problem.
 
susoldmitriy
just joined
Posts: 1
Joined: Sun Mar 10, 2019 9:00 pm

Re: v6.44 [stable] is released!

Sun Mar 10, 2019 9:08 pm

hi all. i have a problem with dude 6.44. I will stopped dude and have problem. router CCR1009-7G-1C-1S+
>dude print
enabled: no
data-directory: disk1/dude.db
status: applying settings: disabling: waiting for config changes to
flush (12061435 bytes in queue)

what i can to do?
 
bitdoctor
just joined
Posts: 1
Joined: Tue Oct 30, 2018 3:49 am

Re: v6.44 [stable] is released!

Mon Mar 11, 2019 7:02 am

!) ipsec - added new "identity" menu with common peer distinguishers;
!) ipsec - removed "users" menu, XAuth user configuration is now handled by "identity" menu;

Upgrade (via Terminal) from 6.43.12 Stable to 6.44 Stable on CRS125-24G-1S and RB450G.

Upgrade went smooth, but on devices that had IPSec configured, WebFig still shows the old Users menu (now empty) and does not show the new Identity menu. Under Terminal, the "/ip ipsec identity" was created. All previously configured IPSec tunnels and RW logins are working without problem.

On other devices that had no IPSec configured, the WebFig Users menu was removed and the new Identity menu is shown as expected.
 
Askey307
newbie
Posts: 49
Joined: Fri Sep 29, 2017 10:20 am
Location: South Africa
Contact:

Re: v6.44 [stable] is released!

Mon Mar 11, 2019 8:22 am

Hi

Since the last update we have had multiple clients complaining about existing sites where VoIP experiences issues, from de-registration, no audio, one way audio.
Currently we downgrading the clients back to 6.43.8 which works.

I've sent multiple supouts and support tickets to Support with no feedback.

We're a big distributor of Mikrotik, and this is the first we get with VoIP.

Hi,

I have noticed on this forum that many times the problem is not due to updates, but in fact due to incorrect configurations.

Maybe a suggestion will be to engage with one of your registered dealers / re-sellers which are also Mikrotik Certified to look into the issue (I am both).

This way the Mikrotik Certified consultants can also gain financially and the distributor also supports the registered dealers / re-sellers
@CZFan

Not sure if you read the thread properly, however, we're also both and all of us are at least up to MTCRE. I also cannot share the config of our clients due to a Non-Disclosure agreement. This is companies that's been using these units quite a lot, we talk few thousands of the routers especially the RB750 and 951G. We don't touch their config which work. When they downgrade with the exact same config everything works. When they use 6.44, it stops working. Even our in house Mikrotik Certified Trainer looked at it and suggested to downgrade.
So config is not a problem.

Currently all our clients are happy with 6.43.8. No issues reported or anything. We'll keep it that way till another update has been released.
Also you're welcome to look at our site to get some input to what we do and what we are:)
www.miro.co.za
 
User avatar
Deantwo
Member Candidate
Member Candidate
Posts: 290
Joined: Tue Sep 30, 2014 4:07 pm

Re: v6.44 [stable] is released!

Mon Mar 11, 2019 10:08 am

Not sure if you read the thread properly, however, we're also both and all of us are at least up to MTCRE. I also cannot share the config of our clients due to a Non-Disclosure agreement. This is companies that's been using these units quite a lot, we talk few thousands of the routers especially the RB750 and 951G. We don't touch their config which work. When they downgrade with the exact same config everything works. When they use 6.44, it stops working. Even our in house Mikrotik Certified Trainer looked at it and suggested to downgrade.
So config is not a problem.

Currently all our clients are happy with 6.43.8. No issues reported or anything. We'll keep it that way till another update has been released.
Without knowing even a little bit about your configuration, no one here will be able to help identify the issue. Since we don't even know which router features you are using (bridge, ike1, ike2, IPsec, etc.), it is hard to know what might have changed in the update that can cause you issues.
If you can't share the config here and believe it is a bug in the update, make a supout while the issue is occurring and mail it to support@mikrotik.com. Then they can help you troubleshoot it and find the issue.
I wish my FTP was FTL.
 
Askey307
newbie
Posts: 49
Joined: Fri Sep 29, 2017 10:20 am
Location: South Africa
Contact:

Re: v6.44 [stable] is released!

Mon Mar 11, 2019 10:17 am

Not sure if you read the thread properly, however, we're also both and all of us are at least up to MTCRE. I also cannot share the config of our clients due to a Non-Disclosure agreement. This is companies that's been using these units quite a lot, we talk few thousands of the routers especially the RB750 and 951G. We don't touch their config which work. When they downgrade with the exact same config everything works. When they use 6.44, it stops working. Even our in house Mikrotik Certified Trainer looked at it and suggested to downgrade.
So config is not a problem.

Currently all our clients are happy with 6.43.8. No issues reported or anything. We'll keep it that way till another update has been released.
Without knowing even a little bit about your configuration, no one here will be able to help identify the issue. Since we don't even know which router features you are using (bridge, ike1, ike2, IPsec, etc.), it is hard to know what might have changed in the update that can cause you issues.
If you can't share the config here and believe it is a bug in the update, make a supout while the issue is occurring and mail it to support@mikrotik.com. Then they can help you troubleshoot it and find the issue.
@DeanTwo

Wer'e currently awaiting Mikrotik's response for several cases.
I just posted here as some feedback regarding our finds with the firmware. Not looking for a fix:) more also trying to see if others experiencing the same and what the outcome was. Only feedback I got so far is their looking into it. None since then.
 
cdemers
Member Candidate
Member Candidate
Posts: 184
Joined: Sun Feb 26, 2006 3:32 pm
Location: Canada
Contact:

Re: v6.44 [stable] is released!

Mon Mar 11, 2019 7:18 pm

Been experiencing random ethernet link negotiation problems since this version. Have a rb1100x2 and a wireless wire dish refusing to keep a gigabit connection. And on a ccr1036 unable to negotiate 100mbps with a Cisco router, have to set speed and duplex. Everything fine on older version.
Just a couple examples.


Sent from my SM-A520W using Tapatalk

 
kayander
just joined
Posts: 6
Joined: Thu Feb 14, 2019 2:43 pm

Re: v6.44 [stable] is released!

Mon Mar 11, 2019 7:52 pm

Upgraded hAP ac^2 with an active l2tp/IPsec connection, also some CRS305, CRS326, hEX. Had no issues whatsoever (ipSec input accept rules existed)

Thanks to Mikrotik for the hard work on supporting their great product and pushing such big updates. Keep it up!

Отправлено с моего Mi A1 через Tapatalk

 
GWerewolf
just joined
Posts: 1
Joined: Mon Mar 11, 2019 9:30 pm

Re: v6.44 [stable] is released!

Mon Mar 11, 2019 9:39 pm

Is it ok that we have < 3 MB of free space on our 16 MB devices after update?
 
User avatar
Caci99
Forum Guru
Forum Guru
Posts: 1052
Joined: Wed Feb 21, 2007 2:26 pm
Location: Tirane
Contact:

Re: v6.44 [stable] is released!

Tue Mar 12, 2019 11:30 am

Is it ok that we have < 3 MB of free space on our 16 MB devices after update?
It depends on your files, for example on mine Hap ac lite there is nearly 4MB. On these boards the update package is saved on RAM instead of HDD.
-Toni-
Don't crash the ambulance, whatever you do
 
User avatar
rushlife
Frequent Visitor
Frequent Visitor
Posts: 95
Joined: Thu Nov 05, 2015 12:30 pm
Location: czech republic

Re: v6.44 [stable] is released!

Tue Mar 12, 2019 12:24 pm

ip neighbor

In most cases I don't see ip address.

All mikrotiks around are on the same version, 6.44 stable.
"Discovery interace" is set for "all" on all my devices.
 
kadety
just joined
Posts: 17
Joined: Tue Mar 12, 2019 1:42 pm

Re: v6.44 [stable] is released!

Tue Mar 12, 2019 3:29 pm

I had problem with IPSEC VPN connection. This 6.44 created one dynamic peer, and not working my VPN's with dynamic IP.
 
N0X
just joined
Posts: 2
Joined: Tue Mar 12, 2019 8:05 pm

Re: v6.44 [stable] is released!

Tue Mar 12, 2019 8:13 pm

Hi, i update my SXT SQ lite 5 to this new version, i use in ethernet ARP ¨reply-only¨ and i have problems, random clients lost the acces for long time, is random ... i put ARP to ¨enable¨ and all is ok ... in other versions of routerOS i don´t have this problem ...
 
jokke
just joined
Posts: 1
Joined: Wed Mar 13, 2019 2:04 pm

Re: v6.44 [stable] is released!

Wed Mar 13, 2019 2:12 pm

No reply to the issues observed in comment #148 and Comment #183?

I see the problems as well.

If SNMP is active, I see "snmp,warning timeout while waiting for program 20" in the logs.

All CLI interaction touching the interfaces in any way hangs.
I.e.
/interface print
Must be Ctrl+C'ed.
/export
# mar/13/2019 13:07:54 by RouterOS 6.44
# software id = QS0J-S1KQ
#
# model = CRS328-24P-4S+
# serial number = xxxxxxxxx
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
#interrupted
must be Ctrl+C'ed, and prints the #interrupted sequence after Ctrl+C
 
User avatar
emils
MikroTik Support
MikroTik Support
Topic Author
Posts: 481
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.44 [stable] is released!

Thu Mar 14, 2019 1:12 pm

New version 6.44.1 has been released in stable RouterOS channel:

viewtopic.php?f=21&t=146485

Who is online

Users browsing this forum: No registered users and 4 guests