LHG XL HP5 configuration issue

We are using several LHG’s in our network, and so far they have been working well. Today I was configuring one of them and ran into an issue. Once I do a basic configuration to it, I can no longer contact it in any way. All I can do is to reset to back to the stoneage and try again. I did take a backup from another identical unit, and plug it into this one and it works, but as soon as I change the IP address, I loose access to it, unless I leave the default 192.168.88.1. Does anyone have any ideas? Here is the working configuration that I put into it and have it work.

/interface bridge
add name=bridge1
/interface wireless
set [ find default-name=wlan1 ] antenna-gain=0 band=5ghz-a/n channel-width=
20/40mhz-eC country=“united states” disabled=no frequency=5200
installation=outdoor mode=bridge ssid=LtoD tx-power=30
tx-power-mode=all-rates-fixed wireless-protocol=802.11 wps-mode=disabled
/interface list
add name=WAN
add name=LAN
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=wlan1
/interface list member
add interface=ether1 list=WAN
add interface=wlan1 list=LAN
/ip address
add address=10.220.1.102/24 interface=wlan1 network=10.220.1.0
/ip dns
set servers=1.1.1.1,8.8.8.8,71.10.216.1,1.0.0.1,8.8.4.4,71.10.216.2
/ip route
add distance=1 gateway=10.220.1.1
/snmp
set contact=“user” enabled=yes location=company trap-generators=interfaces
trap-interfaces=all trap-version=2
/system clock
set time-zone-name=America/Detroit
/system identity
set name=LtoD
/system ntp client
set enabled=yes primary-ntp=10.220.1.50 secondary-ntp=10.250.1.42


Very basic. If I change 10.220.1.102 to 10.220.1.115 I loose all contact with it. Any direction would be very much appreciated.

Hello,
you should set ip address to the “bridge1” interface.

Regards,
M.

I normally do that, and it still had problems. I have since run into this exact same issue on an SXTG-2hnd. Yet I know it is not the way I am doing it, because I have configured other SXT’s and mAP Lites, hAP lite’s and other Mikrotik products without issue. Both before and after this issue. I do my update downloads directly from Mikrotik, and I redownloaded them just in case there was an issue. No change.

Thanks for your help and ideas

Well, that is strange. What is the RouterOS version on that LHG?
In the production environment use only latest long-term version (at the moment 6.45.9).
Try to run “/system check-installation” and see what happens.

One more question - after you lose connectivity with that LHG have you tried to access it from another PC or Mikrotik router via L2 Winbox or mac-telnet?

If nothing of this helps then I would suggest contacting Mikrotik support with your exact configuration steps and supout file.

Regards,
M.

Sorry for taking so long to reply, been crazy busy. The installation was fine, I did try thru winbox thru the IP Address and thru the MAC address, although sometimes I could not even see those. I tried three different computers and a phone.

I did make some progress. Doing a manual reset allowed me to at least get into it. After that, I had to do a reset thru the System>Reset Configuration option, then when it rebooted, I did a remove configuration. After that, everything worked normally. Any other way resulted in a unit that was either partially or totally uncommunicative after configuring. Not sure what the deal is.

I’ve seen this happen when you add a wireless Interface that is set to mode=station into a bridge - be sure to set mode=station-bridge before adding it to the bridge. I note in this case mode=bridge so that should be fine..

I’ve also seen it happen when you use the scan function and then select an SSID with the connect button. It reverrts the wireless into mode=station

Thanks for the tips! Not sure if that is what I did, I have done too much since then, but I will look into it the next time this happens.

Not sure why this is doing what it is doing, but if I reset it with NO configuration, and then configure it from there, they work. And this did not affect just the LHG, but it also affected other Routerboard based devices.