received packet with own address as source address
 

Добрый День!

Столкнулся с проблемой:
Сеть поделена на vlan-ы и поднят брижд (br0). К бриджу привязаны 2 vlan-а (vlan5 и vlan6). В vlan5 сидит офис, в vlan6 сидят сервера. С недавнего времени ночью стал пропадать доступ в интернет (vlan2), шлюз провайдера не пингуется и причем рестарт службы network результатов не даёт. После перезагрузки шлюза доступ в инет появляется. В /var/log/messages постоянно сыпятся следующие ошибки:
Nov 25 15:35:59 ROUTER kernel: [24303.204715] vlan5: received packet with own address as source address
Nov 25 15:35:59 ROUTER kernel: [24303.800219] vlan5: received packet with own address as source address
Nov 25 15:37:00 ROUTER kernel: [24364.694522] vlan5: received packet with own address as source address
Nov 25 15:38:01 ROUTER kernel: [24425.589733] vlan5: received packet with own address as source address
Nov 25 15:39:02 ROUTER kernel: [24486.484548] vlan5: received packet with own address as source address
Nov 25 15:39:07 ROUTER kernel: [24491.474988] vlan5: received packet with own address as source address
Nov 25 15:40:03 ROUTER kernel: [24547.378986] vlan5: received packet with own address as source address
Nov 25 15:41:04 ROUTER kernel: [24608.274709] vlan5: received packet with own address as source address
Nov 25 15:42:05 ROUTER kernel: [24669.168899] vlan5: received packet with own address as source address
Nov 25 15:43:06 ROUTER kernel: [24730.062637] vlan5: received packet with own address as source address
Nov 25 15:44:07 ROUTER kernel: [24790.958361] vlan5: received packet with own address as source address

На сколько я понимаю, эти сообщения свидетельствуют о наличии петли, но сетка не провисает. На коммутаторах запущен stp, в логах коммутаторов всё чисто..

Вот вывод лога шлюза перед исчезновением инета:

Nov 24 16:05:45 ROUTER kernel: [198455.754225] br0: port 3(vlan6) entering disabled state
Nov 24 16:05:45 ROUTER kernel: [198455.754254] br0: port 2(vlan5) entering disabled state
Nov 24 16:05:48 ROUTER kernel: [198459.486184] device vlan5 left promiscuous mode
Nov 24 16:05:48 ROUTER kernel: [198459.486210] br0: port 2(vlan5) entering disabled state
Nov 24 16:05:49 ROUTER kernel: [198460.086418] device vlan6 left promiscuous mode
Nov 24 16:05:49 ROUTER kernel: [198460.086444] device eth0 left promiscuous mode
Nov 24 16:05:49 ROUTER kernel: [198460.086477] br0: port 3(vlan6) entering disabled state
Nov 24 16:05:50 ROUTER kernel: [198460.964051] device eth0 entered promiscuous mode
Nov 24 16:06:04 ROUTER kernel: [198474.849410] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Nov 24 16:06:04 ROUTER kernel: [198474.860134] device eth0 left promiscuous mode
Nov 24 16:06:04 ROUTER kernel: [198475.046432] device vlan5 entered promiscuous mode
Nov 24 16:06:04 ROUTER kernel: [198475.046452] device eth0 entered promiscuous mode
Nov 24 16:06:07 ROUTER kernel: [198477.885852] br0: port 3(vlan6) entering learning state
Nov 24 16:06:07 ROUTER kernel: [198477.885859] br0: port 2(vlan5) entering learning state
Nov 24 16:06:07 ROUTER kernel: [198477.887692] br0: topology change detected, propagating
Nov 24 16:06:07 ROUTER kernel: [198477.887696] br0: port 3(vlan6) entering forwarding state
Nov 24 16:06:07 ROUTER kernel: [198477.887700] br0: topology change detected, propagating
Nov 24 16:06:07 ROUTER kernel: [198477.887702] br0: port 2(vlan5) entering forwarding state
Nov 24 16:06:07 ROUTER kernel: [198477.887706] br0: topology change detected, propagating

Подскажите пожадуйста, как совладать с этой гадостью.

..Выяснил, что проблема не в том, о чём писалось выше..

Каждый день ночью отваливается доступ в инэт, пингов до шлюза провайдера нет, но он доступен (проверял другого интернет канала). После перезагрузки шлюза, проблема исчезает, попытки перезапустить службу network результатов не дают.. Грешил на свитч, заменил, проблема не решилась..