Umdns cross-vlan problem

2023 report. Not working for cross-vlan situation.
I gdb the code, and the design of it is really bizzar.
Find the service_reply function, it traverses the services avl, and got different outcomes comparing to umdns_browse.
Turns out, "service_reply" only check the json-added service but but not the cached services learned from different vlans, in my case, only find the default ssh and http which were added by json as I wanted to announce them to see what's going on.
So I figure, umdns need me to add the usefull services from cached-services to the annouced-service manually. Emmmm, that's really balls-aching for someone didn't know that.