v6.41.1 [current]

Announcements
61

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.

62 
*) ovpn - fixed resource leak on systems with high CPU usage;

Does this fix this problem I reported here?
**http://forum.mikrotik.com/t/100-cpu-ovpn-server-error-tls-failed/115446/1

63

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?

64

Use Wireshark or tcpdump to see whether the machine sends bootp packets after restart. If it does, use netinstall to reinstall the software.

65

Done: Ticket#2018020622006647

66

Send
Ticket#2018020722003201

67

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 :slight_smile:

Sorry to be a bit off-topic but I see here a lot of professionals where a short answer takes some seconds :wink:
Have a nice day !

68

You may use any - they have similar interface and functionality.

69

Thank you !

70
  • 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

71

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

72

podrian ayudarme con la password de este mikrotic

73

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.

74

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

75

junior18 , I think this translated is: “password could help me with this mikrotik”
Not sure I understand your question/statement
North Idaho Tom Jones

76

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.

77

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?

78

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.

79

DHCP client on CHR reappears on purpose. You can not delete it. It is intended behavior.

80

But why?