- name: generate new ssh keys
expect:
command: 'ssh {{ inventory_hostname }} "{{ routeros_ip_ssh_command }} regenerate-host-key"'
responses:
(.*)regenerate current SSH host keys(.*): 'y'
viewtopic.php?p=1040526#p1040526Sorry, but this is a pointless post.When will they fix MLAG?
No one can help you here without information about what is not working with MLAG, nor what your config looks like :-/
But the old capsman i used the forwarding logic?WifiWave2 CAPsMAN only passes wireless configuration to the CAP, all forwarding decisions are left to the CAP itself - there is no CAPsMAN forwarding mode.
CAP AX <-> (<- PoE out - Mikrotik PoE adapter - -> Data) <-> CCR2004 eth port1Indeed, just to be sure...CAP as the CAP AX ? I havent done anything to it.
What's in between the router and the cAP ax?
CAP as the CAP AX ? I havent done anything to it.So much to improve...but lets focus on the current problem.
Can you share the CAP config as well?
Uh how would I check that?Solid green I assume?
Did the cAP ax request/get an IP address?
I unplugged PoE Ethernet. Plugged it back in. Waited for 10 seconds until LED is green and then unpressed it. It should turn the CAP AX to cap mode. Correct?Just to be sure...you did reset the cAP ax to CAP mode?
Thanks!For AX devices you have to use a different CAPsMAN:
https://help.mikrotik.com/docs/display/ ... ve2CAPsMAN