Hiya folks, Long time user and financial supporter of Tomato here. I have two separate issues, the first being that WET (Wireless Ethernet Bridge) mode craps out on me after a few days of usage and my second issue is WDS won't work at all. Issue 1 Router A: RT-AC66U Tomato Firmware 1.28.0000 MIPSR2-114 K26AC USB AIO-64K All settings default (aside from standard WAN/DHCP config) except: 5Ghz radio: AP, N-only, Chan 36, 40MHz, Lower, WPA2/AES security Router B: RT-N66U Tomato Firmware 1.28.0000 MIPSR2-114 K26AC USB AIO-64K All settings default (aside from static IP and default gateway/DNS) except: 5GHz radio: Wireless Ethernet Bridge, Auto, WPA2/AES security Bridge WAN port to primary LAN (so I get one extra Ethernet port if I need it) Advanced->Routing Mode is set to: Router So everything connects up and works fine for a few days but then Router B loses its connection with Router A. Router A is still fine because anything connected to it can still reach the Internet. After rebooting Router B everything is OK again...for a few days and the process repeats. I chose the "AC" version of the firmware for Router B (not AC capable) based on comments from Shibby saying that it includes the latest driver from ASUS and it should work fine on the N66U, and I also thought it would make the most sense to have as close to exactly the same firmware on both routers. Anyone have any idea what's going on here? Seems something gets corrupted after a few days in this mode, but I'm not sure what. Issue 2 Everything is setup the same as above however I set both routers to use WDS and input the respective MAC addresses. I tried in N only and in Auto mode. I tried with the same security as above (WPA2/AES) and with no security. In both cases no packets are ever forwarded between the routers. Upon inspection of the router logs (on both ends) I see they immediately connect in WDS mode according to this (example from Router B): Jan 1 01:41:36 unknown user.info kernel: device wds1.1 entered promiscuous mode Jan 1 01:41:36 unknown user.info kernel: br0: port 3(wds1.1) entering learning state Jan 1 01:41:36 unknown user.info kernel: br0: topology change detected, propagating Jan 1 01:41:36 unknown user.info kernel: br0: port 3(wds1.1) entering forwarding state But no packets ever get through. Anyone have any idea on this one, too? The reason I'm trying this in the first place is A) due to the issue above with WET, and B) because WDS is standardized and as I understand it the bridging is more thorough and less prone to issues due to space being added in the network frame for the source MAC address. Interesting note: WDS worked fine with the above same setup except Router B was a WRT54GL running the appropriate Shibby 114 K26 firmware. Final question: what debug tools are suggested when packets aren't being forwarded such as in the broken state from Issue 1 and in Issue 2? I'm extremely familiar with Linux and networking in general but I'm not sure how to peek into what the WiFi driver is doing other than using tcpdump, iptables, and etc. The WiFi command wlan help spits back an enormous number of command line options so I'd appreciate some direction here. Thank you.