It's fixed. The solution was to swap eth0 and eth1. By default, WAN is assigned to eth0 for this router, and others have seen the same issue I encountered. Whether this is a software or hardware bug, I don't know. It's also baffling to me why a switch in-between the cable modem and router fixed the…