v7.16rc [testing] is released!

Hi,

trouble with container on RB3011: pihole and mosquitto (MQTT) in a VLAN-context: tried to update from 7.15.3 first to 7.16.beta3, later tried 7.16.beta7 and today 7.16rc5
With 7.15.3 both container working fine for months.

Updating to 7.16RC5 (or any other 7.16-version): both container starting properly, but Looks like somehow isolated. pihole e.g. Access to pihole Webpage doesn’t work and container has no DNS Outbound. I see traffic in the FW and DSTNAT rules, but not in SRCNAT. And Shell is accessable e.g. for “pihole -d” (Looks good beside notes for missing DNS, noted in log on start already). Same for mosquitto. Seems to run, but MQTT Explorer can’t connect. Everything else (VLAN, usb-drive,… ) works fine.

Back to “stable” 7.15.3 solves it immediatly: Both container run smoothly again without any action.

As there was one other user only mentioning container issues in the previous thread: http://forum.mikrotik.com/t/v7-16beta-testing-is-released/176494/13
and some follwing answer reporting no probs.

Any idea what could be changed from 7.15 to 7.16 in Bridge or VLAN or container or DNS handling which may cause this in a VLAN context? Any new (default?) feature which may cause this and needs just to ba adjusted?
I spent some hours to investigate, but ran out of ideas…

Thankx for any hint. Maybe someone else facing this and solvbed it. Would be happy to use 7.16 - at least for the nice mDNS-feature avoiding my mDSN repeater.

I get this every time I ssh from my iPad using Termius, and never from other platforms or Putty. No idea why but I’m glad it isn’t just me.



/ip/dns/static/
add forward-to=10.10.10.10 match-subdomain=yes name=my.internal.domain type=FWD

Sounds like they are just bringing some minor news to calm down everyone…

[Person A] “Did you read latest messages on 7.16rc thread?”
[Person B] "Yep! They are getting angry…
[Person B] “What if we release something to let then entertained?”
[Person A] “Sounds good! I will check with the wifi and LTE guys if they have something that already can be released.”
… a few moments latter…
[Person A] “They say it not final, but can be released.”
[Person B] “Sounds good enough. I will release a new RC.”

P.S.: Just kidding!

*) dhcpv4-server - added matcher ability to match substring;

It would be even nicer when the matcher could match other DHCP request fields than options…
E.g. the requester’s MAC address. I would like to put IEEE-assigned MAC addresses in a different pool than Locally assigned (“random”) MAC addresses, for example.

I am enterprise user using and operating hundreds of CCR including the most expensive flagship product they have 1072 and 2216, i think you re right.

Calm down? I don’t get the point you want to make. Another RC release instead of final is a bad thing?

What outcome of the dialogue would you like to see instead?

[Person A] “Did you read latest messages on 7.16rc thread?”
[Person B] "Yep! They are getting angry…
[Person B] “What if we release something to let then entertained?”
[Person A] “Sounds good! I will check with the wifi and LTE guys if they have something that already can be released.”
… a few moments latter…
[Person A] “They say it not final, but can be released.”
[Person B] “Sounds good enough. I will release the 7.16 stable.

P.S.: Just kidding too!

RouterOS v7.16 has been released
http://forum.mikrotik.com/t/v7-16-2-stable-is-released/178911/1