Re: hex rb750gr3 reset does not work as expected

RouterOS Beginner Basics
1

Hi,
i inherited 2 mikrotik hex (rb750gr3) and i dont get them to work.
My goal is to get them into the delievery status (192.168.88.1 on first port) and configure them as i like via web interface.
Talking about only one now, the 2nd acts identical.

I tried to reset them as described in https://wiki.mikrotik.com/wiki/Manual:Reset#How_to_reset_configuration or https://help.mikrotik.com/docs/display/UM/hEX#hEX-Resetbutton (press reset until the usr led starts to flash, release), did not worked, the device still sends bootp requests like

15:55:08.429106 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:69:f4:fa:9a:0d, length 300

I tried the same with pressing reset before powering - same same.

If i boot it on a dhcp enabled network, it gets an ip and it is pingable, but i cannot reach any port on the assigned address.
Seems to run in a weird bridge mode?

14:12:41.647840 IP 192.168.48.4 > 192.168.48.2: ICMP echo reply, id 4, seq 6, length 64
^C
15 packets captured
15 packets received by filter
0 packets dropped by kernel
master# tcpdump -n -i enp2s0 host 192.168.48.4
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on enp2s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
14:13:02.789743 IP 192.168.48.2.44696 > 192.168.48.4.443: Flags [S], seq 3794430010, win 64240, options [mss 1460,sackOK,TS val 3372931634 ecr 0,nop,wscale 7], length 0
14:13:03.794565 IP 192.168.48.2.44696 > 192.168.48.4.443: Flags [S], seq 3794430010, win 64240, options [mss 1460,sackOK,TS val 3372932639 ecr 0,nop,wscale 7], length 0
14:13:05.810570 IP 192.168.48.2.44696 > 192.168.48.4.443: Flags [S], seq 3794430010, win 64240, options [mss 1460,sackOK,TS val 3372934655 ecr 0,nop,wscale 7], length 0
14:13:07.890523 ARP, Request who-has 192.168.48.4 tell 192.168.48.2, length 28
14:13:07.890932 ARP, Reply 192.168.48.4 is-at b8:69:f4:fa:9a:0d, length 46

I am a unix guy, but as i could not dig deeper into that i decided to use the windows gaming box and install winbox and netinstall, as i could not use one of my linux boxes - they are all headless and i read that i need to wire the device direct (without switches) to the netinstall host.

I was able to flash the current routeros (7.11.2) with ‘apply default config’ on it (‘installation finished successfully’), but still - it starts up in bootp and is not usable.

How can i get rid of this configuration?

I am a littlebit lost now and need some advise what i can try next…
Yes, i read a lot of similar questions here, in reddit, yada yada, but i could not find a similar problem (waiting with bootp, only icmp, no tcp answers) or solution so far.

Aleks

2

When ROS device is running default config, then it should be accessible through LAN ports. On most devices (including your hEX) that’s all ports except for ether1 (sometimes marked as WAN).
Default config has DHCP client running on ether1/WAN and DHCP server running on LAN ports (which are all bridged and thus provide identical services and access to router).

Yes, netinstall has to be done via ether1, so it’s normal to reconnect management PC from ether1 to e.g. ether2 after successfully finishing netinstall.

3

Never mind, looks like i am an idiot :slight_smile:

I found the webinterface as i started to monitor the other ports, i thought i could catch it on the first port, but in default thats the dhcp and natted port to the wan.

Sorry and have a nice weekend.

Aleks

4

I found that right in the same moment by myself, but thanks a lot for that quick answer!
Should i delete the post?

Aleks

5

Posts can be kept.
Doesn’t hurt for others experiencing the same misunderstanding to learn from it :smiley: