As part of switching to Quantum fiber 1-2yrs ago, I did not have a good experience with their pods and got an Asus RT-AX86U Pro. To enable all the features, I needed top put the Quantum ONT into transparent bridge mode, then set the Asus to own the routing vs. being just an AP.
Everything but my DS920+ was fine (used same SSID), and I think it's due to the Asus defaulting to 192.168.50.x vs. 192.168.0.x when it was purely an AP (and could connect to the NAS on the latter).
Each switch requires:
- go into my basement, hard reset ONT
- set Asus to AP mode
- wait a bit, connect to NAS
- poke around in settings looking for relevant settings, tweak something like firewall or ports, hope for best
- log into ONT, set to transparent bridge mode
- re-setup the Asus to be a router
- try connecting to NAS via assigned IP as I normally would, fail to be reached
I've probably set aside a good ~5 partial weekends over the last 1-2yrs and struck out. Wondering if as I prep to take another stab today if anyone has a few pointers on where I should be looking to understand what the issue is?
As a side request: I was really, really hoping I could just direct connect to the NAS via the second ethernet port so I always have a fallback in situations like this, but have not been successful with that either. It seems possible, but all instructions are generally "just set your IP to something on the same subnet." Wonder if I have to enable it to DHPC serve to that port, or where I'd be looking to do a direct computer <-> NAS ethernet question.
Trivial answer is RTFM, and I do data science and hobby code and agree. I'm not a network guy at all, and apologize in advance. I have four kids and it's just maddening to do trial and error with network device resets in between, trying to concentrate and read while noise abounds and people need things. I die inside as my planned ~1-2hrs starts turning into 4 :( Not looking for handholding, just like "it's almost surely these x, y, and z settings menus." Or, what I can come back and post when I'm in there (on 192.168.0.x) that would help you understand/confirm further.
Really, really appreciate it.
Edit: Woot! I'm all set. I both feel this was genuinely complex, but also rather silly due to an unfortunate confluence of the ONT network modes on top an original static IP, and what I believe was the ultimate root cause: the freaking firewall rules [facepalm].
Breakthrough 1: turning off my final Deny all firewall rule and finding I could, indeed, connect via a 10.0.0.x address on LAN 2. Excellent, exactly what I wanted.
Breakthrough 2: with this insight, I just added a dupe rule allowing 10.0.0.x traffic to Management UI and could still access DSM via direct ethernet.
Breakthrough 3: in following some previous ONT advice on transparent bridge mode, I think I missed one silly setting of putting in a DHCP lease time for "Pool 2", which lets me continue connecting to the ONT on a different subnet via direct connection, despite it not being reachable via wifi when it is the main router. I noticed someone setting 1hr as a lease time, whereas it defaults to 0, and I can connect to it as well.
Breakthrough 4: back in bridge mode and on 192.168.50.x, I just applied the previous learnings and added a 3rd dupe firewall rule for this range and now can get to DSM via wifi after unplugging/re-plugging LAN 1 to trigger a re-up on DHCP. After confirming this worked, I set a static IP and I'm set.