This bug (or feature?) costs us 24 hours working in our routing center (2 Linux NAT boxes, 2 all-purpose Linux routers, ~ 15 VLANS), beating heads to the wall, changing a half of VLANs structure, checking a half of switches and about 200 angry phone calls from customers :). The last day to holidays :).
We think, the kernel 3.2.0-65 was made by Microsoft :). Reverting to 3.2.0-64 solved this NAT problems
Sorry of not fluently english...
This bug (or feature?) costs us 24 hours working in our routing center (2 Linux NAT boxes, 2 all-purpose Linux routers, ~ 15 VLANS), beating heads to the wall, changing a half of VLANs structure, checking a half of switches and about 200 angry phone calls from customers :). The last day to holidays :).
We think, the kernel 3.2.0-65 was made by Microsoft :). Reverting to 3.2.0-64 solved this NAT problems