Community discussions

 
nuffrespect
just joined
Posts: 18
Joined: Wed Jun 14, 2017 5:21 pm

Re: v6.41.1 [current]

Mon Feb 05, 2018 3:25 pm

nuffrespect - Please generate supout file on your router while you see such behavior and send this file to support@mikrotik.com
@strods, for your attention

Ticket#2018020522000654, Ticket#2018013122002471

DiM
 
Nando_lavras
newbie
Posts: 35
Joined: Tue Jul 11, 2006 4:38 am

Re: v6.41.1 [current]

Mon Feb 05, 2018 3:42 pm

It's possible to use bridge port with horizon=1 with hardware offload activated? I think i misunderstood this question about the horizon.

Using CRS326 when i add a port with horizon=1 hardware offload is deactivated.

Thanks.
 
feris
just joined
Posts: 10
Joined: Tue May 16, 2017 3:58 pm

Re: v6.41.1 [current]

Mon Feb 05, 2018 4:40 pm

feris - Do you see such behavior on single unit? Are you sure that default configuration on this device is not replaced with another one by using Netinstall;
There is no Netinstall service available. Im making reset from CLI.
Reset configuration on wAP ac with 6.41.1 works as expected.

Configuration of RB750Gr3 with 6.41.1 after reset to default:
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/system routerboard mode-button
set enabled=no on-event=""
After downgrade to 6.40.5 configuration reset on RB750Gr3 works fine.
Upgrade to 6.41.1 and problem is coming back.
 
NetflashTechnical
just joined
Posts: 15
Joined: Fri May 10, 2013 3:43 pm

Re: v6.41.1 [current]

Mon Feb 05, 2018 6:43 pm

NetflashTechnical - Please generate supout file on your router while you see such behavior and send this file to support@mikrotik.com
Done! In fact, several supouts attached to it even :)

Ticket#2018020522004918
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2218
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: v6.41.1 [current]

Mon Feb 05, 2018 9:34 pm

CRS125-24G-1S - after upgrade from 6.40.5 to 6.41.1 -> power cycle required :(
LAN, FTTx, Wireless. ISP operator
 
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1384
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.41.1 [current]

Tue Feb 06, 2018 10:43 am

sanitycheck - This is why admin-mac is available. Please select one of interfaces which is configured within bridge, copy its MAC address and specify as bridge MAC address. Now it will not change any more. This is not a bug - it is intended behavior;
tkgit - At the moment there is no other solution to upgrade firmware after RouterOS upgrade. We will consider implementing automated firmware upgrade in future;
Misi, Nando_lavras, honzam - If you have not contacted support yet, then please do so and send supout file from router. If you have, then please wait for a response from us;
nuffrespect - Thank you for providing files. We are looking into this problem. Please, if possible, in future do not create multiple support tickets for the same problem. In such way usually there is miscommunication which slows down debugging process drastically;
feris - What do you mean by Netinstall service is not available? I have tested this on hEX units with 6.41.1 RouterOS version and default configuration works properly. Please try to Netinstall unit and reset after that. If problem persist, then send supout file to support@mikrotik.com. if configuration is not there after reset, then run "/log print" command (after reset) and send it to support@mikrotik.com
 
User avatar
acruhl
Member
Member
Posts: 355
Joined: Fri Jul 03, 2015 7:22 pm

Re: v6.41.1 [current]

Tue Feb 06, 2018 2:14 pm

This just happened to me on a hAP lite RB941-2nD configured a similar way, but on 6.39.3. So problem appears to be older than 6.41.1.

It is configured as a wireless client (station pseudobridge) with all Ethernet ports configured as a switch, a bridge with wlan1, with dhcp-client configured on the bridge. DHCP server would see mac of wlan1 or sometimes mac of bridge/ether1. No admin mac set on the bridge. I recall a reboot would often make it change but not always. It would get a different IP from the DHCP server. I set a static IP on ether1 and disabled the dhcp-client to get around it.
Yeah that's probably a good idea. My last AP was a hAP ac lite, and it had a static IP. Might as well set a static on this one.

The wAP ac has so much better wireless coverage than the hAP ac lite. I'm happy with it.
Upgrade your router! No excuses!
 
mariuslazar
just joined
Posts: 7
Joined: Wed Oct 12, 2016 4:06 pm

Re: v6.41.1 [current]

Tue Feb 06, 2018 3:17 pm

The update resets the hotspot files! I have the login customized and it's now gone!

I just updated an old 951 and it seems the problem is only on the new hap ac's (not the brand new hap ac 2)
Last edited by mariuslazar on Tue Feb 06, 2018 4:12 pm, edited 1 time in total.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8176
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.41.1 [current]

Tue Feb 06, 2018 3:35 pm

The update resets the hotspot files! I have the login customized and it's now gone!
We are sorry for any inconvenience caused. We will fix this problem in 6.41.2 RouterOS release;
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
User avatar
CZFan
Forum Guru
Forum Guru
Posts: 1128
Joined: Sun Oct 09, 2016 8:25 pm
Location: South Africa
Contact:

Re: v6.41.1 [current]

Tue Feb 06, 2018 4:35 pm

What is ETA for v6.41.2?
MTCNA, MTCTCE, MTCRE & MTCINE
 
User avatar
Splash
Member Candidate
Member Candidate
Posts: 144
Joined: Fri Oct 16, 2015 10:09 am
Location: Johannesburg, South Africa

Re: v6.41.1 [current]

Tue Feb 06, 2018 6:12 pm

Has anyone had an issue with DHCP packets not being passed through a bridge using 6.41.1?

I have bridged 2 ports together, with 1 port being the network where a DHCP server resides and the second port where a DHCP client device is connected.

DHCP packets do not pass through the bridge.
MTCNA, MTCRE, MTCINE, MTCTCE, MTCIPv6E, MTCUME
 
onlineuser
Member Candidate
Member Candidate
Posts: 209
Joined: Thu Aug 06, 2015 12:10 pm

Re: v6.41.1 [current]

Tue Feb 06, 2018 6:46 pm

*) ovpn - fixed resource leak on systems with high CPU usage;
Does this fix this problem I reported here?
viewtopic.php?f=2&t=129459
 
mla
just joined
Posts: 1
Joined: Tue Feb 06, 2018 9:20 pm

Re: v6.41.1 [current]

Tue Feb 06, 2018 9:35 pm

While updating to 6.41.1 from 6.41 my HAP did not make it, it was powered on port 1 with PoE.

When powering up, the PWR and USR lights up, but nothing else.
There is no response on webfig or winbox. Winbox does not recognize the device.
Neighbors with another Mikrotik device also does not detect the HAP.

Reset to factory defaults does not have any usable effect.

Any other suggestions what to do next?
 
sindy
Forum Guru
Forum Guru
Posts: 2636
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.41.1 [current]

Tue Feb 06, 2018 10:03 pm

While updating to 6.41.1 from 6.41 my HAP did not make it, it was powered on port 1 with PoE.
...
Any other suggestions what to do next?
Use Wireshark or tcpdump to see whether the machine sends bootp packets after restart. If it does, use netinstall to reinstall the software.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.
 
theq
just joined
Posts: 2
Joined: Wed Aug 16, 2017 10:41 pm

Re: v6.41.1 [current]

Tue Feb 06, 2018 10:06 pm

NetflashTechnical, ithierack, theq, Clauu, freemannnn, nuffrespect - Please generate supout file on your router while you see such behavior and send this file to support@mikrotik.com
Done: Ticket#2018020622006647
 
User avatar
SirPrikol
just joined
Posts: 21
Joined: Wed Oct 11, 2017 12:36 pm

Re: v6.41.1 [current]

Wed Feb 07, 2018 12:52 pm

SirPrikol - Did you downgrade to 6.41 routes where working and upgrade to 6.41.1 and they are not working again? Can you provide supout file to support@mikrotik.com which would be generated while there are such routes on router;
Send
Ticket#2018020722003201
 
coliflower
just joined
Posts: 18
Joined: Mon Aug 21, 2017 1:10 pm

Re: v6.41.1 [current]

Wed Feb 07, 2018 4:06 pm

Sorry for an off-topic small question - I am a newbie with MT and not an IT-professional and just update to 6.41.1

Terminal seems to be the most powerful toll ...
In case of WinBox vs. Browser as interface to ROS ..., what is next to Terminal ( I would like to avoid to install WinBox on my MacBook) ?
I appreciate your opinion very much :-)

Sorry to be a bit off-topic but I see here a lot of professionals where a short answer takes some seconds ;-)
Have a nice day !
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8176
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.41.1 [current]

Wed Feb 07, 2018 4:53 pm

In case of WinBox vs. Browser as interface to ROS ..., what is next to Terminal ( I would like to avoid to install WinBox on my MacBook) ?
You may use any - they have similar interface and functionality.
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
coliflower
just joined
Posts: 18
Joined: Mon Aug 21, 2017 1:10 pm

Re: v6.41.1 [current]

Wed Feb 07, 2018 5:01 pm

Thank you !
 
jackx
just joined
Posts: 4
Joined: Wed Feb 07, 2018 6:33 pm

v6.41.1 [current] bug report

Wed Feb 07, 2018 6:49 pm

  • Changing settings through the Quick Set drop-down menu renders the device unresponsive and requires push-button hardware reset to defaults.
  • Changing IP address through the Quick Set web page renders the device unresponsive (at both old and new IP address) and requires push-button hardware reset to defaults.
  • RouterBOARD 941-2nD does not have Gigabit Ethernet ports but auto-negotiation of 1000M half / 1000M full is enabled by default.

Model RouterBOARD 941-2nD
Current Firmware 6.41.1
Packages version 6.41.1
 
User avatar
TomjNorthIdaho
Forum Veteran
Forum Veteran
Posts: 897
Joined: Mon Oct 04, 2010 11:25 pm
Location: North Idaho
Contact:

Re: v6.41.1 [current] (BUG in dhcp package - I think)

Wed Feb 07, 2018 7:18 pm

I think I found a bug

The problem is on every reboot, the Mikrotik CHR auto injects a dhcp-client option.

Removing the dhcp-client and rebooting the CHR will again show a dhcp-client in the configuration.
Disabeling the dhcp-client in the config , then rebooting will result in two dhcp-client configs - One is disabled and the other is enabled.

I have verified this problem on several different CHR routers.

The problem appears to start at v6.4.anything.
When I downgrade to 6.39 or older on the CHR , it works correctly and does not auto inject a dhcp-client setting in the configuration after reboots.
When I upgrade any CHR (CHR-64) to 6.4anything or even the 6.42rc20 , the problem appears again.

With any version of 6.4 , a reboot will auto inject a dhcp-client into the configuration.
In testing , I disabled the dhcp package then rebooted and because there is no dhcp package at this time , there are no dhcp-client configs in the configuration.
The moment I re-enable the dhcp package on the CHR and reboot , the dhcp-client configuration shows up again.

I have tested/verified this condition on several different CHR (chr-64) systems.

Is this a bug ?
Anybody else seeing this ?

North Idaho Tom Jones
 
junior18
just joined
Posts: 1
Joined: Wed Feb 07, 2018 7:59 pm

Re: v6.41.1 [current]

Wed Feb 07, 2018 8:03 pm

podrian ayudarme con la password de este mikrotic
 
sid5632
Member Candidate
Member Candidate
Posts: 288
Joined: Fri Feb 17, 2017 6:05 pm

Re: v6.41.1 [current] (BUG in dhcp package - I think)

Wed Feb 07, 2018 8:24 pm

Is this a bug ?
Anybody else seeing this ?
Yes and yes. I've already had it confirmed by support as a bug - [Ticket#2018012422000218] [MT Support] CHR keeps recreating unwanted ether1 dhcp-client.
After initially telling me it was correct, I argued my case and then they said:
"This client indeed is created by mistake. We will try to fix this in upcoming RouterOS versions."

I found that creating a bridge and adding ether1 as a bridge port stopped it from doing this, because you can't have a DHCP client on a slave interface.
 
User avatar
TomjNorthIdaho
Forum Veteran
Forum Veteran
Posts: 897
Joined: Mon Oct 04, 2010 11:25 pm
Location: North Idaho
Contact:

Re: v6.41.1 [current] (BUG in dhcp package - I think)

Wed Feb 07, 2018 8:35 pm

Is this a bug ?
Anybody else seeing this ?
Yes and yes. I've already had it confirmed by support as a bug - [Ticket#2018012422000218] [MT Support] CHR keeps recreating unwanted ether1 dhcp-client.
After initially telling me it was correct, I argued my case and then they said:
"This client indeed is created by mistake. We will try to fix this in upcoming RouterOS versions."

I found that creating a bridge and adding ether1 as a bridge port stopped it from doing this, because you can't have a DHCP client on a slave interface.
sid5632 - thanks for your prompt input/reply.
So far, I have only seen this on CHRs. Have you (or anybody else) seen the dhcp-client issues auto-showing up on x86-ROS-32-Bit or other physical Mikrotik platforms ?

North Idaho Tom Jones
 
User avatar
TomjNorthIdaho
Forum Veteran
Forum Veteran
Posts: 897
Joined: Mon Oct 04, 2010 11:25 pm
Location: North Idaho
Contact:

Re: v6.41.1 [current]

Wed Feb 07, 2018 8:39 pm

podrian ayudarme con la password de este mikrotic
junior18 , I think this translated is: "password could help me with this mikrotik"
Not sure I understand your question/statement
North Idaho Tom Jones
Last edited by TomjNorthIdaho on Wed Feb 07, 2018 8:40 pm, edited 1 time in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 5004
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.41.1 [current] (BUG in dhcp package - I think)

Wed Feb 07, 2018 8:39 pm

I think I found a bug

The problem is on every reboot, the Mikrotik CHR auto injects a dhcp-client option.
There must be a little more to it, as on my CHR (which has ether1 and ether2 both with static address and no DHCP) I cannot reproduce it.
 
russman
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Thu May 20, 2010 7:23 pm

Re: v6.41.1 [current]

Wed Feb 07, 2018 9:08 pm

I'm running 6.41.1 on a CCR-1016-12S-1S+RM router that I'm testing SFP compatibility/behavior in. The non-mikrotik modules worked on gigabit only when manually set to 1Gbps (no auto negotiation) they would not work on 100Mbps when manually set even though the modules support it (UBNT and Fiberstore SFPs). After upgrading the board firmware/BIOS, whatever you want to call it, from 3.39 to 6.41.1 the non-mikrotik modules will not work under any settings configured. Is this a bug or are you guys removing the minimal level of compatibility we did have?
Last edited by russman on Wed Feb 07, 2018 9:26 pm, edited 1 time in total.
 
SPKA16
newbie
Posts: 25
Joined: Fri Aug 05, 2016 8:41 pm

Re: v6.41.1 [current] (BUG in dhcp package - I think)

Wed Feb 07, 2018 9:15 pm

I think I found a bug

The problem is on every reboot, the Mikrotik CHR auto injects a dhcp-client option.
There must be a little more to it, as on my CHR (which has ether1 and ether2 both with static address and no DHCP) I cannot reproduce it.
Can not reproduce it either. It does however create a DHCP client on ether1 when deploying the CHR with the use of the ova template even when you use 'static IP' in the wizard without actually entering an IP-address.
 
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1384
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.41.1 [current]

Wed Feb 07, 2018 10:24 pm

DHCP client on CHR reappears on purpose. You can not delete it. It is intended behavior.
 
XaTTa6bl4
just joined
Posts: 11
Joined: Wed Dec 16, 2015 10:53 pm

Re: v6.41.1 [current]

Wed Feb 07, 2018 10:42 pm

DHCP client on CHR reappears on purpose. You can not delete it. It is intended behavior.
But why?
 
Paternot
Member
Member
Posts: 473
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: v6.41.1 [current]

Wed Feb 07, 2018 10:45 pm

podrian ayudarme con la password de este mikrotic
junior18 , I think this translated is: "password could help me with this mikrotik"
Not sure I understand your question/statement
North Idaho Tom Jones
Not quite. It's more like "could you help me with this mikrotik password?"
 
coliflower
just joined
Posts: 18
Joined: Mon Aug 21, 2017 1:10 pm

Re: v6.41.1 [current]

Wed Feb 07, 2018 11:06 pm

Dear all,

with 6.40.3 I had on my wAP-ac for each vAP a VLAN (on ether1 = Trunk) and a separate bridge, connected together - e.g.: bridge-vlan10 + vlan10 + vAP10 ... it worked fine.

With 6.41.1 there is some "spezial" bridge solution ... is there any need to change my old vAP configuration, please ?
If yes or if better ... is there any kind of red-line/best-prctice or some configuration file available to avoid to get in troubles, please ?

Thanks a lot in advance !
 
sindy
Forum Guru
Forum Guru
Posts: 2636
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.41.1 [current]

Wed Feb 07, 2018 11:21 pm

The "special" bridge solution brings some advantages (namely, hardware switching where possible and a possibility to run MSTP protocol and better operation of other flavours of STP).

However, in your setup where you just need to bridge several VLANs from a single Ethernet port to virtual APs running on the very same box, you can safely stay with your existing configuration. It continues to work and none of the advantages of the new method is applicable for your setup.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.
 
myke1124
just joined
Posts: 16
Joined: Fri Mar 28, 2014 2:15 am

Re: v6.41.1 [current]

Wed Feb 07, 2018 11:31 pm

I was upgrading some routers from previous versions to 6.41, when all of a sudden I notice the most recent version is now 6.41.1. :-)

I noticed that on 6.41.1 I am unable to change the neighbor discover-setting. Shown below are console output from a 6.41 router and a 6.41.1 router. They are the same router. I performed the first neighbor discovery setting change from !dynamic to all, then upgraded the router from 6.41 to 6.41.1. When the router came back online, the neighbor discovery setting was reset from all to !dynamic, and I am unable to get it to change at all now, even after multiple reboots. This occurs from the console and winbox. Interesting... :-)
# running v6.41 - can make changes to neighbor discovery-settings
[user@router] > /ip neighbor discovery-settings 
[user@router] /ip neighbor discovery-settings> print 
  discover-interface-list: !dynamic
[user@router] /ip neighbor discovery-settings> set discover-interface-list=all 
[user@router] /ip neighbor discovery-settings> print 
  discover-interface-list: all
[user@router] /ip neighbor discovery-settings> /system package update install 

# now running v6.41.1 - after reboot - can NOT make changes to neighbor discovery-settings from cli or winbox
[user@router] /ip neighbor discovery-settings> /ip neighbor discovery-settings 
[user@router] /ip neighbor discovery-settings> print 
  discover-interface-list: !dynamic
[user@router] /ip neighbor discovery-settings> set discover-interface-list=all 
[user@router] /ip neighbor discovery-settings> print 
  discover-interface-list: !dynamic
[user@router] /ip neighbor discovery-settings> 

I have noticed that you can change discovery interfaces. It seems viewing the setting always reports !dynamic. As a test I have set to none. The setting appears to be !dynamic. No neighbors appear in the neighbor list. It works like none. It seems to work with whatever it is set to, however it always displays !dynamic.
 
User avatar
TomjNorthIdaho
Forum Veteran
Forum Veteran
Posts: 897
Joined: Mon Oct 04, 2010 11:25 pm
Location: North Idaho
Contact:

Re: v6.41.1 [current]

Wed Feb 07, 2018 11:49 pm

DHCP client on CHR reappears on purpose. You can not delete it. It is intended behavior.
ditto on the why question ?

There are some/many reasons an admin would not want a dhcp-client configuation on their CHR.
- If dhcp-client is not needed , why does it auto add the dhcp-client on reboot
- Why is not needed prior to v6.39x and earlier and now needed after v6.4x ?
- What happens if a CHR has a static IP address on a network that also has a DHCP server and the CHR also injects a dhcp-client configuration on the same network - now you have two IP addresses and possibly two different gateways ?
- Is there a way to remove the dhcp-client auto inject into the configuration without disabeling the dhcp package ? ( A CHR may need to be a dhcp-server and and not be also a dhcp-client )

Will this dhcp-client auto inject feature stay in all future versions/updates of CHR ROS or can/will the auto inject of dhcp-client be disabled or removed.
Am I correct in thinking the auto inject of dhcp-client was a planned function on CHR reboots if the dhcp package is enabled ?

confused - North Idaho Tom Jones
 
coliflower
just joined
Posts: 18
Joined: Mon Aug 21, 2017 1:10 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 1:03 am

The "special" bridge solution brings some advantages (namely, hardware switching where possible and a possibility to run MSTP protocol and better operation of other flavours of STP).
Hello Sindy,

thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?

Thanks !
 
LIV2
just joined
Posts: 24
Joined: Sat Jan 23, 2016 7:42 am

Re: v6.41.1 [current]

Thu Feb 08, 2018 2:47 am

Hello Sindy,

thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?

Thanks !
The change in bridging is to do with hardware switching I thought, and since the wAP-ac doesn't use a switch chip you shouldn't be having any problems
Can you share your config?
 
minhcoi
just joined
Posts: 5
Joined: Wed Jan 17, 2018 4:53 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 7:40 am

After update 6.41.1 my RB951Ui 2HnD has alway reboot, and i cant winbox to interface address. How can I fix this?
 
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1384
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.41.1 [current]

Thu Feb 08, 2018 9:36 am

Splash - We are not aware about such problem. Usually such issues appear due to some configuration issue. Please send supout file to support@mikrotik.com
onlineuser - It might affect your situation, however, we can not give you precise yes or no answer. If the problem that you have is caused by delayed/slow responses to/from OVPN server, then this might help and your problem might go away;
mla, minhcoi - Have you tried to Netinstall your device;
jackx - Did you have such problem also in 6.41 release;
TomjNorthIdaho, sid5632, pe1chl, SPKA16, XaTTa6bl4 - This is intended behavior, because it is required in order to access CHR (when used on cloud services not hosted by yourself and you do not have access to the console). Also this was the behavior also before 6.41.1 RouterOS release. Please in future for such cases either contact support or create a new forum topic. Such posts might make other users to think that this release has some bug which affects CHR installations, however, it has nothing to do with concrete RouterOS release;
russman - Please send supout file from your router generated while SFP is not working properly to support@mikrotik.com;
myke1124 - Please before posting look through previous posts in the same topic. This problem is already resolved in 6.42rc version and fix will be included in 6.41.2 RouterOS release;
 
LIV2
just joined
Posts: 24
Joined: Sat Jan 23, 2016 7:42 am

Re: v6.41.1 [current]

Thu Feb 08, 2018 9:52 am

The DHCP on CHR thing is annoying, I guess we can all add drop rules to the output chain to block the requests :/
 
sindy
Forum Guru
Forum Guru
Posts: 2636
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 10:14 am

Hello Sindy,

thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?

Thanks !
The change in bridging is to do with hardware switching I thought, and since the wAP-ac doesn't use a switch chip you shouldn't be having any problems
Can you share your config?
@coliflower, @LIV2 has put in another words what I've already written: the new way of bridging won't bring anything useful to you until you decide to deploy more than one Ethernet port, as it unites "bridge" and "switch" configuration into one and lets the RouterOS itself decide which functionality to execute in hardware and which in software. But you can change the settings if you want, so if the documentation is not clear enough, try to read the same in another wording in this post.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.
 
minhcoi
just joined
Posts: 5
Joined: Wed Jan 17, 2018 4:53 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 11:24 am

Splash
mla, minhcoi - Have you tried to Netinstall your device;
Because device canot stable so I tried to Netinstall but doesnt work.
 
coliflower
just joined
Posts: 18
Joined: Mon Aug 21, 2017 1:10 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 12:19 pm

Hello Sindy,

thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?

Thanks !
The change in bridging is to do with hardware switching I thought, and since the wAP-ac doesn't use a switch chip you shouldn't be having any problems
Can you share your config?
Yes, can do it if I am back from my business-trip.
 
coliflower
just joined
Posts: 18
Joined: Mon Aug 21, 2017 1:10 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 12:41 pm

Hello Sindy,

thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?

Thanks !
The change in bridging is to do with hardware switching I thought, and since the wAP-ac doesn't use a switch chip you shouldn't be having any problems
Can you share your config?
@coliflower, @LIV2 has put in another words what I've already written: the new way of bridging won't bring anything useful to you until you decide to deploy more than one Ethernet port, as it unites "bridge" and "switch" configuration into one and lets the RouterOS itself decide which functionality to execute in hardware and which in software. But you can change the settings if you want, so if the documentation is not clear enough, try to read the same in another wording in this post.
Thank you Sindy,
I will read and check ... Who knows when I need some additional Switch or to replace the current one :-)
 
fibernet4u
newbie
Posts: 33
Joined: Sat Dec 03, 2016 12:44 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 2:15 pm

Dear,

Below netwatch issue has been checked under this release and still facing the same fetch issue at same time. You really need to fix this issue.

viewtopic.php?f=2&t=130587&p=641235#p641235
 
sid5632
Member Candidate
Member Candidate
Posts: 288
Joined: Fri Feb 17, 2017 6:05 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 2:29 pm

TomjNorthIdaho, sid5632, pe1chl, SPKA16, XaTTa6bl4 - This is intended behavior, because it is required in order to access CHR (when used on cloud services not hosted by yourself and you do not have access to the console).
Please look at my comments on [Ticket#2018012422000218] [MT Support] CHR keeps recreating unwanted ether1 dhcp-client

Creating it initially makes sense, but recreating it automatically after the user has deliberately chosen to remove it and do something else is just plain STUPIDITY.
Your support person did seem to agree with me eventually.
 
jackx
just joined
Posts: 4
Joined: Wed Feb 07, 2018 6:33 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 3:41 pm

I have downgraded all RouterBOARD 941-2nD to version 6.39.3 (bugfix) firmware 3.41 because version 6.41.1 causes slowdown that renders the devices too slow to even use their web interface.
 
User avatar
TomjNorthIdaho
Forum Veteran
Forum Veteran
Posts: 897
Joined: Mon Oct 04, 2010 11:25 pm
Location: North Idaho
Contact:

Re: v6.41.1 [current]

Thu Feb 08, 2018 4:03 pm

strods,sid5632, pe1chl, SPKA16, XaTTa6bl4

strods - please go ahead and create a new thread on this topic and we can follow this topic there.


Re: ... This is intended behavior...
Who decided to make all CHRs only operate as DHCP-CLIENTS , and deny you the ability to disable dhcp-client?
There is no other operating system or router or any type of network device I can think of that forces you to only be a DHCP-Client.
You can't disable it - You can't remove it - You can't turn it off - You can't even factory default reset it without it comming back.
Just think about the world-wide impact if every network device, every router, every switch, every PC was suddenly forced to be a DHCP-CLIENT after a software upgrade , and there was no option to change/disable it ?

Re: Also this was the behavior also before 6.41.1 RouterOS release.
No, it was not.
The problem was not there prior to v6.4 (v6.39x and older work correctly)
The problem is there at v6.4 and later

Re: Please in future for such cases either contact support or create a new forum topic.
please go ahead and create a new thread on this topic and we can follow this topic there.

Re: ... think that this release has some bug ...
Lets just call it a new un-documented feature


North Idaho Tom Jones
 
russman
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Thu May 20, 2010 7:23 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 4:32 pm

@strods

It didn't generate a support file automatically. It didn't crash the router, this is all regarding link negotiation via 10/100/1000M RJ45 SFP modules. Before the aforementioned update, the non-mikrotik modules would link up if the port was manually set to 1Gbps but wouldn't let anything connect under any speed but 1Gbps even though the module supported it. The mikrotik one just did some odd things with auto-negotiation below 1Gbps and the speed reported that was fixed with the firmware update. After the update however, now only the mikrotik SFP will work regardless of link negotiation settings applied (auto and manual).

Testing was performed with:
  • Mikrotik S-RJ01
  • UBNT UF-RJ45-1G
  • FiberStore SFP-GB-GE-T (#34976)
 
sindy
Forum Guru
Forum Guru
Posts: 2636
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.41.1 [current]

Thu Feb 08, 2018 4:40 pm

The supout.rif contains telemetry which is needed to analyze the issue. It is not mandatory that it is created "spontaneously" after a crash. So insert the previously-supported SFP and manually create the supout.rif for support.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.

Who is online

Users browsing this forum: No registered users and 6 guests