FS#1722 - RTL8366rb bridge on tp-link wr1043nd-v1 doesn't activate. #6686
Labels
Comments
|
Pilot6: It seems that the mystery is almost clear now. There was a bug that before vlans were setup, the switch passed through mac addresses from lan to wan. Some ISPs banned for "mac spoofig" It looks like Tp-link fixed that bug in u-boot that stop switch from sending packets on initial stage. Then firmware reverted it. If we use UART and first activate switch from there, then we can boot from the internal flash and switch keeps working. The question is how to discover what locks the switch and how to revert it back. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pilot6:
This a very weird problem.
I am building a 4.14 ath79 image from trunk for wr1043nd-v1.
The dtsi file seems to be correct, because the device works properly without any issues when I boot from initramfs.
If I flash the same image to the router, switch stops working at all. Wireless and usb-net do work OK.
I compared logs, ethtool, swconfig, brctl and everything I could imagine and didn't notice any differences between when boot form RAM or from flash except this one in syslog
overlayfs: upper fs does not support tmpfile.
There must be some tricky race condition. We discussed that at the forums and it is reproducible.
May be anyone has some idea how to debug it?
The text was updated successfully, but these errors were encountered: