dhc-client will NOT go away - is this a problem ?

RouterOS General
1

dhc-client will NOT go away - is this a problem ?

I am pulling my hair out !!!

dhcp-client will NOT go away !!!

I have a CHR 64-bit system v6.41.1 (virtual running on VMware ESXi)
If I have a single IP address on ether1 -and- an IP address on the bridge (4 ethernet ports total and a bridge) , I can remove all dhcp-client settings and it works. I can reboot it and there is no dhcp-client on the system.

However , I have this problem where I can not remove all dhcp-client options using this config:

If I have a single IP address on ether1 -and- no other IP addresses (4 ethernet ports total and a bridge) , I can remove all dhcp-client settings and it works. However , when I reboot it , the dhcp-client shows up on a reboot. (every time I remove dhcp-client in the config , it shows back up on ether1)

Also - If I just disable the dhcp-client on ether1 and reboot it, I now have two dhcp-client lines in my config.

  • One dhcp-client on ether1 is disabled
  • and a second dhcp-client on ether1 that is enabled

WTF am I doing wrong ? Or is this an un-documented feature (another word for a bug)

Note: neither CHR has a default route ( 0.0.0.0/ ) - or any other static routed

ALSO - I am able to repeat this dhcp-client problem showing up on another different CHR v6.41.1 router.

edit note - If I remove the dhcp package and reboot - there is no dhcp-client injected into the config. However , when I re-enable the dhcp package and reboot , the dhcp-client is re-inserted.
I want the dhcp package because later I will configure a dhcp-server for some other interfaces.

North Idaho Tom Jones

2

Possibly somewhat related to my prior post above

I also have some Mikrotiks that when I upgrade to the same version , the dhcp-client settings on the WAN looses the default-route via dhcp
This results in a client wireless connectiion - but no routed IP traffic on the client

North Idaho Tom Jones

3

And another CHR on the same version is doing the exact same thing with auto injecting a dhcp-client config on a reboot.
This time on the public btest server 207.32.195.2

normally I do not have the dhcp package enabled.
however - i did a test
1 - verify there are no dhcp-client configs in the export
2 - enable the dhcp package and reboot
3 - after reboot , there is a dhcp-cleint option in the export
4 - remove the dhcp-client option from the config and verify there are no dhcp-client lines in the config
5 - reboot , and presto - there it is again
6 - disable the dhcp-client configs and remove all dhcp-clinet configs
7 - reboot and there are no dhcp-client lines in the config

I am beginning to suspect the problem is something to do with the dhcp package

Tomorrow - I will try an older version of ROS and see what happens

North Idaho Tom Jones

4

After more testing , I am seeing this auto injected dhcp-client on all of my 64-Bit CHR systems.

For further information, I am now posting this issue/problem at:

http://forum.mikrotik.com/t/v6-41-1-current/116174/71

North Idaho Tom Jones