By lots I meant that I had a lot of different problems (mounting the USB stick, formatting to ext4, creating/extracting/importing container etc) when I tried to re-create Pi-hole container to a new USB stick with 7.14.2 and 7.15beta9, but after downgrading to 7.13.5 everything worked like they should.
The last time I created one was with 7.13.x version, and it worked just fine when I upgraded to 7.14.1, but the USB stick filesystem went read-only with 7.14.2, so it got corrupted or USB stick broke, and when I tried to re-create a new one with new USB sticks I couldn’t. After founding the topic that I linked, and downgrading to 7.13.5 everything went smoothly, formatting the USB stick with ext4, creating Pi-hole container and starting it. All of those steps failed at some point with 7.14.2 and 7.15beta9, and if by some miracle the container was imported successfully then the container start would loop with the read-only filesystem error. None of those are happening with 7.13.5, so something has been broken with the newer versions.
And still you refer to LOTS of problems but it’s only you ?
I am not saying you did not see those problems. But I am not (yet) convinced it’s related to the ROS versions you refer to.
I have pihole running via container on USB stick via RB5009 (same ARM64), using every single ROS7 version you can think of since I have that router (currently 7.15b9).
I also have other containers running on usb stick on AX3 (7.15b9).
So it’s not a generic problem or I would see it too. What’s different then ? Most likely config.
I suggest you create a new topic detailing exactly all the steps you did with full disclosure of your config so others can review.
If we can not find the mistake / config error, I suggest you create a support ticket (in case you haven’t already) with reference to that thread.
IS-IS to non-MikroTik is not working, tried with Cisco and Juniper
Cisco is not receiving IIH message from MikroTik
Network type broadcast, stuck in INIT state
Network type ptp, neighbor not coming up at all
isis to cisco works for me and there are no isis changes that could break isis with cisco in v7.15beta versions. There must be something specific to your config which is not related to v7.15release
FYI, I contacted support@mikrotik.com about my issue above. I will keep you posted once I know more. Sorry for the trouble, just tried to be helpful.
And to be clear, the problem is not running the container, it’s creating a new ext4 USB stick & Pi-hole container to it. I was only able to get it done with 7.13.5. Not with 7.14.2 or 7.15beta9. I believe if I would now update to either of those the container would work, but I would not be able create a new one once the USB stick gets corrupted or broken. Because I was running 7.14.1 successfully for a long time with the old USB stick & Pi-hole container in it.
I have had same behavior with CAP AX and 7.14.2. Looks like it won’t be fixed in 7.15 release. Downgraded ros to 7.10.2 - looks like it is the last version with working FT aka roaming.
Is there a SUP id for this? I’d like to reference it/other people in this thread might like to reference it. I’ve been seeing a lot of the same, and would prefer to piggyback on existing issues, as surely MT is aware of it by this point with how often it’s been mentioned in this thread and the previous 7.14.x thread.
No there is not any SUP. I have managed to get it working by downgrading to 7.10.2 and now i do not have any spare devices and free time to deep dive in it.
My support ticket got closed, stating that the issue I reported was fixed and the fix will be included in a RouterOS release in the upcoming days. So lets see about that
? So long and no new beta?