>> If you're feeling adventurous, there are evidently pins on the system >> board for a serial connection, but not exposed through the case. Could >> possibly eliminate some of the guesswork. I would be curious if there are >> differences between the different eth ports
> It's a sealed case and the problem is not the hardware but the way I did > things. The case is "sealed" with two screws, but yes it is about the way you did things. For a few dollars, you can buy a USB-TTL-serial cable that you can attach to a header on the ER-X board inside and you can see how the device is configured at any particular time without a working network. https://www.amazon.com/JBtek-WINDOWS-Supported-Raspberry-Programming/dp/B00QT7LQ88 That one is a little more expensive, since it is already in North America. They are about $2 each from East Asia, but there may be substantial shipping delays (of a month or more) involved. On the ER-X (as with most COTS routers), there is a switch chip that is programmed by the system. There is one port of the switch chip that goes to the CPU. The other ports of the switch chip go to the external RJ-45 jacks. The ports of the switch are grouped by VLANs internally, and the packets leaving the CPU port remain VLAN tagged, so the CPU can tell the difference between packets coming from a LAN port and a WAN port. The packets leaving the other ports typically have the VLAN tagging stripped off. From the CPU perspective, e.g. the LAN arrives on eth0.1 (that is eth0 with a VLAN tag of 1) and WAN arrives on eth0.2 (eth0 with a VLAN tag of 2). That's the only way the CPU tells the difference. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
