Host address on ether1 of RB433AH

RouterOS Beginner Basics
1

Hi,

On my new RB433AH if I connect a host that is configured for DHCP, I get the following IP address/Subnet Mask and Default Gateway info

Autoconfiguration IPv4 address: 169.254.232.137
Subnet mask: 255.255.0.0
Default Gateway:

This is confusing me as RouterOS - RouterOS - MikroTik Documentation mentioned that for RB433xx boards, ether1 is preconfigured with 192.168.88.1/24 address.

Thus, I was expecting to that my host will get a address in 192.168.88.0/24 subnet assuming that there is a DCHP server for ether1 preconfigured.

When I assign static IP address of 192.168.88.2, my host does get this IP when connected to ether1.

So I am not sure why in case of DHCP hosts, it is getting an IP address from 169.254.0.0 subnet.

Please advise.

Thank you.

2

Eth1 is normally for wan by default. Therefore does not have sense to run dhcp server on it. For initial connection and setting the device use eth2.

Sent from Android by Tapatalk.

3

Ether 1 is your WAN this must you connect with modem ore router from your provider.
Ether 2,3,4,5 have standard configured a DHCP-server.
Connect the client to ether2,3,4,5

4

Does not have eth4 or eth5.

Sent from Android by Tapatalk.

5

Yes off cource, is a rb 433, sorry about this my mistake :smiley:

6

Thanks all for your help.

I will use eth2 then.

But I still have this question of why does my host connected to ether1 gets an ip in the domain of 169.254.0.0. This tells me that ether1 is indeed running a DCHP server in the 169.253.0.0. Is that correct? If so, why dont I see this DHCP server when I select DHCP servers in my winbox.

7

Occasionally you may encounter a host which has somehow assigned itself an IP address in the 169.254.0.0/16 range. This is a particularly common symptom of Windows machines which have been configured for DHCP but for whatever reason are unable to contact a DHCP server. When a host fails to dynamically acquire an address, it can optionally
assign itself a link-local IPv4 address in accordance with RFC 3927. Microsoft’s term for this is Automatic Private Internet Protocol Addressing (APIPA).

Short for Automatic Private IP Addressing, a feature of later Windows operating systems. With APIPA, DHCP clients can automatically self-configure an IP address and subnet mask when a DHCP server isn’t available

I hope this is clear my friend