Possible bug in 3.27 with the bridging and a whacky port

Ok so I have a 493AH with a bridge on it. This is on a noise tower that is co-located with a radio station. We got all of the noise off via some super grounded cables to kill off our “alien noise”. All was going great except one known port on the 493AH. It has a switch from inside the radio hut come out and plug via only Ethernet into our 493AH.

Well everything was working fine except we did see that the interface port would blink on and off and on and off etc.. Not a problem some low user Ethernet port. We did not think anything about it until we upgraded from 3.24 (the better of the ROS versions) to 3.27 Everything worked fine even through a very intense rain storm filled with heavy lightning. Next morning at a sunshiny 8-9am the port starts to flake out again and all interface ports on our software bridge stop responding. The only thing that sort of works while the port is blinking is the primary ip address on the bridge interface. Once I get onto the port I shutoff the culprit blinking port. this stops all of the interfaces from blinking as soon as I disable the interface that I thought was the culprit. Well the problem goes away for a little bit and then it starts again. All interfaces start to stop and start continuously.

In desperation I decided to downgrade the 3.27 to 3.24. All problems disappeared. AM I crazy or is there any one else who has seen any weird bridge related problems. Now the port that was flaking out I understand could have been a very static charged port but this killing of all interfaces does not make any sense. And this only started with 24 hours of the 3.27 upgrade. this configuration has been fine for a very long time until now.

We still have 3.27 running on some of our other APs but they are just APs they are not back hauls with bridges on them. Any input on or enlightenment on this would be greatly appreciated. I hope maybe I did discover a bug for you all I just would like to not see the problem in the next ROS version if it is a bug. Thanks.

-Sincerely,
DesertAdmin

I corrected the issue by downgrading and then re-upgrading. But I think the problem was that the X86 PowerRouter732 ran out of flash space when it was upgrading. So I went to the package folder and removed all of the unnecessary stuff and then I was able to complete my upload and then upgrade properly to the 3.30 version. Everything seemed to work fine from there.

Thanks for all who read on this.

-Sincerely,
DesertAdmin