[alanwreath]

Yes! Recently connected two disparate systems (ubiquiti and mimrotik) using their exposed API’s and a Claude session so that systems I have on either environment could talk to each other. I am not a network engineer so it was liberating to get my gear working together. That said it’s a work in progress and just today I noticed something weird that one of my computers can’t access Minecraft servers while the rest of my network can

[x2tyfi]

Probably a routing issue. Shot in the dark would be that one of these routers is NATing traffic, and the other router doesn’t have a route to that NAT’d range.

[tonyarkles]

Other shot in the dark, misconfigured bridging or similar where ARP isn’t getting forwarded and rewritten quite right

[bombcar]

Or look for something mangling SRV records, Minecraft seems to use those more regularly than everything else.

[doubleg72]

What possibly could you even be talking about? Networking gear already works together due to standards.

[brookst]

LEGOs fit together because they have standards. That doesn’t mean they self-assemble.

Networking can be complex. Standards allow interoperability but they do not magically make everything work with no configuration.

[HDBaseT]

You still would need to know how networking fundamentals and how network protocols work.

Just because standards like DNS, NAT64, OSPF, ARP, etc, exist doesn't means its easy to get these things to communicate.

Ubiquiti isn't exactly known for being the best in terms of standard adherence, especially with their historically week IPv6 support.

[icedchai]

Vendor terminology is often different (tagged VLANs vs trunking, etc.) but, in general, it is close enough that an experienced person can figure it out with a bit of googling. I've built networks with Cisco, Mikrotik, Aruba/HP, custom Linux routers, and others. Mikrotik VLANs are a bit weird, for sure.

In today's world, is generally easy to get things to communicate. It's not 30 years ago and nobody is running DECnet, Appletalk, or IPX.