Not only that, but mandate a route only to 192.168.1.1 (or whatever) and not the whole 192.168.x.x address space (which this exploit uses -- I didn't know there

Not only that, but mandate a route only to 192.168.1.1 (or whatever) and not the whole 192.168.x.x address space (which this exploit uses -- I didn't know there was a separate management interface on 192.168.100.1 until a poster above mentioned it.