MikroTik

Yesterday it was the OmniTik Upa which had lost control over the poe out function. Finally got it up to ROS5.24 and it works again, but still leds in wrong order.

Today is another bad day!!!!!

Installed groove Metal2SHPn seemed to work ok, however I had noticed that TX signals seemed to be reported by various cpes at 1 moment they are 65db then the next they are 80dB.. It seems to stay like this for a few seconds, then back to 65db

At first I thought it might be localised interference, so did some channel changing, but still the same.

Ran through the night ok... Now this morning I have NO access to it, not by Winbox nor port80, neither by a mac-telnet session from the adjacent omnitik or telnet or ssh...

I can still communicate directly to the attached customers cpe's but not from their cpe's to the AP.

So whilst the customers still have access, I am going to be totally buggered when I have to change channel or add a new client to the AP acl list...

This is not the first time this has happened in the last 2 months of brand new MT equipment.

I was also unable to communicate to a sextant just recently,, the only way forward in that situation was to go to the client site and recycle the supply.

Now I had wished that I had fixed the Omntik poe out problem yesterday before installing one of my modified poe out omnitiks, at least I may have been to recycle the Groove remotely.

Any suggestions anyone? (nice ones!!!)

Any luck with setting the watchdog to ping a problem ip address?

After some reading I think I found my issue with the SXT's so I thought I'd put here in case it helps others.

I use the SXT's primarily as a transparent bridge. Either bridging ether1/wlan1 or ether1/vlanX.

While the mac-server is enable on "*all" interfaces I found that I had to disable the default and add each one individually to make the mac-telnet work properly. Like this:

/tool mac-server
set [ find default=yes ] disabled=yes
add interface=ether1
add interface=bridge1
add interface=wlan1

When I do this I have verified on every machine I've had trouble mac-telnet works now. Why, I don't know.

John