Can't connect to internet via wifi when 10G file-share line is connected

Good morning, folks.

I am relatively new to Mikrotik products. I am still learning the interface and configuration; it’s all more advanced than I’m used to.

I’m working on a project now. A friend has a video studio that is using a massive OWC NAS that has been connected to a Netgear 10G switch with a fiber trunk and the distributed at 10G throughout the studio. The studio is moving into a new building so here’s the new situation:

We got a Mikrotik RB1100AH router and we got a CRS312-10G. I currently have the RB1100 in place routing internet (hardline and ubiquiti wifi) and basic file sharing across the space. My goal is to have the CRS312 take the place of the Netgear switch. The Netgear was never able to properly negotiate jumbo packets and had other problems. So, I’ll use the SPF for my fiber lines to the NAS, and then have the CRS312 hosting its own unique DHCP range that only the editing team is connected to across CAT8 cabling (which we already have in place).

It’s been a fun project for a hobbyist. The language of the MikroTik much more technical than the Netgears and Ciscos that I’ve worked with. It’s better! But I’m a little underwater. I may have a number of questions coming up.

Currently my issue is this: when connect my laptop to the wifi network AND via ethernet to the RB1100, I am able to go online as well as file share with a terminal across the office that is connected via ethernet. However, when I connect to the wifi and then connect via ethernet to the CRS312, everything locks up. I can’t get online, nor can I connect to another terminal. I can, however, go online when I disconnect the cable; I can connect to a LAN terminal when I turn off wifi. So, I’ve goofed something, likely in my configuration of the CRS312. Any thoughts?

The one thing I’ve done correctly on the 10G unit, I think, is set up the MGMT port (ether9) as its own address and connected it to a terminal that’s sitting in my cabinet so I can work on things.

Whatever was happening, I’ve fixed it. I’m not even sure how. All is well now. I may have other questions coming up, but so far so good. Cheers! :folded_hands:t3:

The router probably detects the loop and blocks access

The router probably detects the loop and blocks access

It was actually sillier than that. It was a weird quirk in macOS Ventura. I had everything correct. Go figure… Thank you for the input!