Thanks for this info. I was wrong, I have a CRS320, not CRS310. And, here’s an Imgur album of how things are laid out: https://imgur.com/a/DT3htLJ
Now that I understand the topology better, I have questions about how the VLANs are assigned. Are you using a RADIUS server?
Also, I’m a little confused about the VLAN participation in both switches. I would expect an end client device (like those in your diagram) to connect to an untagged VLAN ports. But, your VLAN assignment screenshots only show your client VLANs on the trunk port.
For example, here’s how I’m doing untagged VLANs on my CRS320:
So, the fact that you can only reach VLAN10 targets from the CSS610 clients makes me think it’s related to VLAN assignment. Yes, it’s different than what’s being observed on your CRS310 clients, but one step at a time.
Its features are much more than mimicking your browser bookmark functionality.
The most important feature to me is the offline archiving of the target link/page. Link rot is real and content can change. Capturing the site as it is when I link it means the info I wanted is now safely stored.
There’s also the multi-user features. A family can centralize and collaborate on links.
Here’s the Features list from the projects GitHub page.
Features