86U modprobe xt_TEE Device Fails at 00:00 When Scripted

[GHammer]

I have been using a manually applied (ssh in and enter commands) iptables configuration successfully for a while. When the TEE Netfilter target was added to the 384.9 series I changed to that load and also used firewall-start script to enter the configuration so it would be active at restart with no intervention.

The first night, the device I am mirroring the traffic for lost its connection at 00:00. I just toggled the radio on the 2.4 GHz band off/on and the device was online again.

Next night, same thing at 00:00. So, I returned to a test build that @john9527 had provided me a while ago.
Device came online after toggling the radio again.

Next night, same. Return to an alpha build and decided that 00:00 was a clue. Deleted the firewall_start script and entered the commands manually.

Last night, the device stayed online.

So, with a few different builds of the firmware, having a startup script issue the commands results in an offline device, and only this device. I have two other devices that use 2.4 GHz and they were unaffected.

Remove the startup script and all is well.
Here is the startup script (/jffs/scripts/firewall-start)

#!/bin/sh
modprobe xt_TEE
iptables -t mangle -A PREROUTING -s 10.10.100.121 -j TEE --gateway 10.10.100.122
iptables -t mangle -A POSTROUTING -d 10.10.100.121 -j TEE --gateway 10.10.100.122

Configuring manually isn't the best place to be long term. Any ideas?

 

[GHammer]

I solved this problem the old fashioned way.
I got an SDR dongle, added some drivers, a bit of brain grease, and now get the data directly from the sensors.
No WiFi, sniffing, routing, iptables involved. Just the magic of technology.

I'm sure something will happen...