re: Does your ether1 have a static IP bind to it, and the DHCP is still coming back? Then it does actually sound like a bug. RouterOS should never change a configuration on its own..
Since we are asked to make a new topic and there already is one.
Does your ether1 have a static IP bind to it, and the DHCP is still coming back? Then it does actually sound like a bug. RouterOS should never change a configuration on its own..
Cause on my test CHR's (RC20>) we CAN NOT replicate your problem _after_ a restart. We only have a DHCP-Client on ether1 when first booted up. When we add a address, remove the dhcp-client and reboot it has the same configuration.
With first boot its fine that there is a DHCP-client for those who don't have access to console but this should be noted better somewhere.
When you deploy with the use of a OVA and have a little control how to push the configuration (you can enter IP-addresses).
Why it still has a DHCP-client even when you don't configure it?
(on every different CHR 6.4 and newer)
ethe1 static IP addredd
ether2 static IP address
ether3 no IP address (this will be a dhcp-server)
ether4 no IP address (used for out-of-band Winbox MAC management)
There is no dhcp-client anywhere in the configuration - untill I reboot it.
After a reboot , there is a dhcp-client auto-injected into the configuration.
- - -
I am starting to think this might be a security hole
and could lead to un-wanted IP addresses and un-wanted routes.
A CHR has a WAN with a static IP address and optionally a default route
The CHR is also doing BGP and/or OSPF
If the up-stream WAN of the CHR has two or more other routers - and one of the upstream routers is a dhcp-server. Below are some of the possible problems I can think of that deserve some thoughts because of the auto-injected dhcp-client:
- The CHR now has two IP addresses on the WAN (one static and one from the dhcp-client auto-injected configuration.
- The CHR might now have a default route injected from the dhcp-client
- If a default route was supposed to be learned from BGP and/or OSPF , a new default route might now be injected into the CHR because of the now has an auto-injected default-route, resulting in two different 0.0.0.0/0 default routes - and these default routes might point to different up-stream WAN connected routers.
- BGP and OSPF routes might now be contanimated with an additional route from the auto-injected dhcp-client configuration
- With the auto-injected dhcp-client setting, is it now possible to hijack or kill a CHR that has a WAN on your network. Example, Your ISP has a /24 WAN and 10 customers on that /24 from your ISP have CHRs with static IP addresses -and- suppose somebody anywhere puts a dhcp-server on that WAN - then - anybody who reboots their CHR now gets what ever IP address was assigned to them from the dhcp-server and also received a default route to what ever the dhcp-server pointed it to. When a CHR on the /24 WAN network reboots, that CHR can receive corrupt network killing IP address and routes - and possibly get a duplicate IP address already used by something else on the /24 network - now resulting in another network now having problems also.
North Idaho Tom Jones