Каждый день рандомно ложится сеть - probably loop

Обсуждение ПО, его настройка и функционал
Ответить
LehaMechanic
Сообщения: 4
Зарегистрирован: 15 апр 2022, 11:33

15 апр 2022, 11:50

Добрый день.
У нас такая ситуация. Сеть организации выходит в интернет через шлюз Mikrotik RB2011UiAS-2HnD-IN, RouterOS v6.49
С некоторых пор у нас постоянно начинаются лаги в сети, плохо открываются сайты, либо не открываются вообще. Начинается в разное время, чаще всего именно в конце рабочего дня, что отдельно всех бесит, потому что приходится задерживаться и решать вопрос, а то и вообще возвращаться на работу, т.к. организация круглосуточная. При этом пинги до шлюза идут с прерываниями. Перезагрузка всего шкафа с микротиком и свитчами помогает решить вопрос до следующего сбоя

Чаще всего, в момент обнаружения проблем с сетью, мы смотрим логи микрота и обычно видим картину, что нас сначала ддосят (очевидно в связи с известными событиями в мире), т.е. некто пытается авторизоваться на микротике - эти попытки мы закрыли правилами фаерволла и ограничением белого списка ip адресов доступных для авторизации и теперь видим в логах просто сообщения от фаерволла об отражении атак.
Иногда проскакивают ошибки l2tp, думаю тот же кулхацкер пытается зайти по vpn, который мы тоже отключили, а вот после всех этих попыток появляется сплошной поток ошибок о возможном обнаружении петли, вида:

interface,warning eth_5: bridge port received packet with own address as source address, probably loop

Жалуется на интерфейс, куда у нас воткнута наша локальная сеть, указывает свой собственный мак-адрес. Такие ошибки прут сплошным потоком, судя по логам примерно пару часов в сутки, потом могут пропадать или появляться единичными записями в том же логе.

Сразу скажу - мы дошли до того, что поменяли шлюз на точно такие же модели два раза, это не помогло. Поменяли свитчи в шкафу на новые - не помогло.
А вот по части настройки микрота и его мониторинга у нас нет хороших специалистов в штате, поэтому обращаемся к вам.
Можно ли как-то что-то придумать, чтобы выявить всё-таки источник петли? Ходить ногами проверять всю сеть слишком сложно, у нас много отдельных корпусов, этажей, порядка 300 машин и 20 свитчей


gmx
Модератор
Сообщения: 2847
Зарегистрирован: 01 окт 2012, 14:48

15 апр 2022, 12:47

Вопрос один: коммутаторы управляемые??? Включите на них loop detect. Отключится непосредственно тот порт, на котором обнаружена петля.

Если коммутаторы не управляемые - срочно менять. Вот и весь совет.

Петля в сети может случиться в любой сети и в домашней, и в корпоративной на 1000 компов. Разницы никакой нет, принципы сетей везде одинаковы. Чтобы минимизировать проблемы используют свичи l2, а также разбивают большие сети на сегменты и используют vlan. Все это в конечном счёте приводит к уменьшению количества каскадных включений сетевых клиентов и в итоге все это упростит поиск и борьбу с возможными коллизиями.

Никакого другого способа нет...


LehaMechanic
Сообщения: 4
Зарегистрирован: 15 апр 2022, 11:33

15 апр 2022, 12:53

gmx писал(а):
15 апр 2022, 12:47
Вопрос один: коммутаторы управляемые??? Включите на них loop detect. Отключится непосредственно тот порт, на котором обнаружена петля.
Управляемые. у меня к вам такой вопрос: обязательно ли loop detect должен быть включен на самом ближайшем к источнику проблемы свитче или достаточно включить на промежуточном и он сам отрубит весь сегмент, где обнаружена петля?


gmx
Модератор
Сообщения: 2847
Зарегистрирован: 01 окт 2012, 14:48

18 апр 2022, 13:53

LehaMechanic писал(а):
15 апр 2022, 12:53


Управляемые. у меня к вам такой вопрос: обязательно ли loop detect должен быть включен на самом ближайшем к источнику проблемы свитче или достаточно включить на промежуточном и он сам отрубит весь сегмент, где обнаружена петля?

Это уж как вам угодно. Чем больше портов с включенным loop detect, тем меньше устройств в итоге отключится при его срабатывании. Но тут нужно понимать, что нужна четкая схема сети с полным пониманием, что в какой порт включено. Чаще включают все-таки на достаточно крупных коммутаторах, чтобы отключалось крупными сегментами. Потом, если проблему найти не удалось, проблемный сегмент еще уменьшают, если в нем есть l2 коммутаторы.
Да, в целом вы правы, loop detect сработает в любом месте.
Да, еще есть один момент, более умные коммутаторы умеет делать loop detect не только на портах, но в vlan. И тогда будет отключаться конкретный vlan на конкретном порту. В идеале нужно с коммутаторов собирать SNMP трапы и все станет понятно.


LehaMechanic
Сообщения: 4
Зарегистрирован: 15 апр 2022, 11:33

27 апр 2022, 07:19

В общем включение защиты от петель на ближайшем к микротику свитче не помогло, сеть всё так же ложится с разной периодичностью и неясной симптоматикой. В последний раз, когда опять отвалился интернет, я попытался провести небольшую диагностику. Взял ноутбук, подключил его к шнурку от провайдера напрямую, настроил, в результате интернет на ноутбуке появился и работал стабильно, следовательно проблема не в провайдере и не в его железках.
После этого, я отключил микрот от всех сетей и подключил к нему ноутбук. И вот тут началось странное. Микрот не пинговался, но при этом у ноутбука почему-то слетали настройки IP и маски, но сохранялись шлюз и DNS. Возможно это проблемы самого ноутбука, я уже ни в чем не уверен. Но с какой-то 5-10 попытки настройки ноута сохранились, микротик начал пинговаться, а после подключения к нему всех сетей обратно как было, интернет снова заработал. При этом я не перезагрузил нигде и ничего, как это делалось обычно. Что за магия, не понимаю(

Вот логи с микрота за последние два дня (видимо с последней его перезагрузки), вчера 26 апреля в 15 00 был сбой.
 
Log

# Time Buffer Topics Message
999 Apr/27/2022 08:04:31 memory system, info, account user admin logged in from 192.168.1.252 via web
998 Apr/27/2022 07:24:00 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:44662->81.200.212.113:8291, len 40
997 Apr/27/2022 05:53:02 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:42200->81.200.212.113:8291, len 40
996 Apr/27/2022 05:48:50 memory l2tp, info first L2TP UDP packet received from 146.88.240.4
995 Apr/27/2022 05:12:55 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:21327->81.200.212.113:8291, len 40
994 Apr/27/2022 05:10:07 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 80.66.76.28:41541->81.200.212.113:8291, len 40
993 Apr/27/2022 05:07:45 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:20132->81.200.212.113:8291, len 40
992 Apr/27/2022 04:12:37 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:32091->81.200.212.113:8291, len 40
991 Apr/27/2022 03:55:47 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 89.248.165.60:52825->81.200.212.113:8291, len 40
990 Apr/27/2022 03:54:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
989 Apr/27/2022 03:54:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
988 Apr/27/2022 03:36:02 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 185.142.236.35:23127->81.200.212.113:8291, len 44
987 Apr/27/2022 03:10:35 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 67.229.103.154:53112->81.200.212.113:8291, len 40
986 Apr/27/2022 02:41:26 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:7650->81.200.212.113:8291, len 40
985 Apr/27/2022 02:20:13 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 185.40.4.135:51601->81.200.212.113:8291, len 40
984 Apr/27/2022 01:08:22 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:44435->81.200.212.113:8291, len 40
983 Apr/27/2022 00:56:44 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:12912->81.200.212.113:8291, len 40
982 Apr/26/2022 23:11:22 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:43501->81.200.212.113:8291, len 40
981 Apr/26/2022 22:25:11 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:44624->81.200.212.113:8291, len 40
980 Apr/26/2022 22:18:02 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:36000->81.200.212.113:8291, len 40
979 Apr/26/2022 22:04:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
978 Apr/26/2022 22:04:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
977 Apr/26/2022 22:04:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
976 Apr/26/2022 22:04:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
975 Apr/26/2022 22:04:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
974 Apr/26/2022 22:04:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
973 Apr/26/2022 22:04:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
972 Apr/26/2022 22:03:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
971 Apr/26/2022 22:03:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
970 Apr/26/2022 22:03:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
969 Apr/26/2022 22:03:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
968 Apr/26/2022 22:03:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
967 Apr/26/2022 22:03:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
966 Apr/26/2022 22:03:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
965 Apr/26/2022 22:03:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
964 Apr/26/2022 22:03:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
963 Apr/26/2022 22:03:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
962 Apr/26/2022 22:03:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
961 Apr/26/2022 22:03:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
960 Apr/26/2022 22:02:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
959 Apr/26/2022 22:02:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
958 Apr/26/2022 22:02:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
957 Apr/26/2022 22:02:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
956 Apr/26/2022 22:02:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
955 Apr/26/2022 22:02:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
954 Apr/26/2022 22:02:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
953 Apr/26/2022 22:02:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
952 Apr/26/2022 22:02:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
951 Apr/26/2022 22:02:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
950 Apr/26/2022 22:02:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
949 Apr/26/2022 22:01:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
948 Apr/26/2022 22:01:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
947 Apr/26/2022 22:01:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
946 Apr/26/2022 22:01:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
945 Apr/26/2022 22:01:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
944 Apr/26/2022 22:01:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
943 Apr/26/2022 22:01:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
942 Apr/26/2022 22:01:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
941 Apr/26/2022 22:01:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
940 Apr/26/2022 22:01:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
939 Apr/26/2022 22:01:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
938 Apr/26/2022 22:01:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
937 Apr/26/2022 22:00:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
936 Apr/26/2022 22:00:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
935 Apr/26/2022 22:00:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
934 Apr/26/2022 22:00:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
933 Apr/26/2022 22:00:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
932 Apr/26/2022 22:00:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
931 Apr/26/2022 22:00:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
930 Apr/26/2022 22:00:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
929 Apr/26/2022 22:00:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
928 Apr/26/2022 22:00:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
927 Apr/26/2022 22:00:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
926 Apr/26/2022 22:00:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
925 Apr/26/2022 21:59:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
924 Apr/26/2022 21:59:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
923 Apr/26/2022 21:59:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
922 Apr/26/2022 21:59:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
921 Apr/26/2022 21:59:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
920 Apr/26/2022 21:59:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
919 Apr/26/2022 21:59:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
918 Apr/26/2022 21:59:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
917 Apr/26/2022 21:59:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
916 Apr/26/2022 21:59:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
915 Apr/26/2022 21:59:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
914 Apr/26/2022 21:59:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
913 Apr/26/2022 21:58:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
912 Apr/26/2022 21:58:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
911 Apr/26/2022 21:58:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
910 Apr/26/2022 21:58:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
909 Apr/26/2022 21:58:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
908 Apr/26/2022 21:58:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
907 Apr/26/2022 21:58:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
906 Apr/26/2022 21:58:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
905 Apr/26/2022 21:58:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
904 Apr/26/2022 21:58:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
903 Apr/26/2022 21:58:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
902 Apr/26/2022 21:58:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
901 Apr/26/2022 21:57:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
900 Apr/26/2022 21:57:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
899 Apr/26/2022 21:57:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
898 Apr/26/2022 21:57:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
897 Apr/26/2022 21:57:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
896 Apr/26/2022 21:57:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
895 Apr/26/2022 21:57:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
894 Apr/26/2022 21:57:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
893 Apr/26/2022 21:57:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
892 Apr/26/2022 21:57:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
891 Apr/26/2022 21:57:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
890 Apr/26/2022 21:57:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
889 Apr/26/2022 21:56:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
888 Apr/26/2022 21:56:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
887 Apr/26/2022 21:56:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
886 Apr/26/2022 21:56:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
885 Apr/26/2022 21:56:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
884 Apr/26/2022 21:56:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
883 Apr/26/2022 21:56:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
882 Apr/26/2022 21:56:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
881 Apr/26/2022 21:56:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
880 Apr/26/2022 21:56:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
879 Apr/26/2022 21:56:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
878 Apr/26/2022 21:56:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
877 Apr/26/2022 21:55:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
876 Apr/26/2022 21:55:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
875 Apr/26/2022 21:55:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
874 Apr/26/2022 21:55:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
873 Apr/26/2022 21:55:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
872 Apr/26/2022 21:55:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
871 Apr/26/2022 21:55:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
870 Apr/26/2022 21:55:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
869 Apr/26/2022 21:55:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
868 Apr/26/2022 21:55:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
867 Apr/26/2022 21:55:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
866 Apr/26/2022 21:55:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
865 Apr/26/2022 21:54:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
864 Apr/26/2022 21:54:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
863 Apr/26/2022 21:54:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
862 Apr/26/2022 21:54:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
861 Apr/26/2022 21:54:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
860 Apr/26/2022 21:54:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
859 Apr/26/2022 21:54:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
858 Apr/26/2022 21:54:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
857 Apr/26/2022 21:54:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
856 Apr/26/2022 21:54:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
855 Apr/26/2022 21:54:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
854 Apr/26/2022 21:54:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
853 Apr/26/2022 21:53:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
852 Apr/26/2022 21:53:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
851 Apr/26/2022 21:53:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
850 Apr/26/2022 21:53:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
849 Apr/26/2022 21:53:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
848 Apr/26/2022 21:53:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
847 Apr/26/2022 21:53:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
846 Apr/26/2022 21:53:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
845 Apr/26/2022 21:53:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
844 Apr/26/2022 21:53:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
843 Apr/26/2022 21:53:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
842 Apr/26/2022 21:53:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
841 Apr/26/2022 21:52:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
840 Apr/26/2022 21:52:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
839 Apr/26/2022 21:52:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
838 Apr/26/2022 21:52:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
837 Apr/26/2022 21:52:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
836 Apr/26/2022 21:52:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
835 Apr/26/2022 21:52:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
834 Apr/26/2022 21:52:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
833 Apr/26/2022 21:52:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
832 Apr/26/2022 21:52:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
831 Apr/26/2022 21:52:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
830 Apr/26/2022 21:52:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
829 Apr/26/2022 21:51:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
828 Apr/26/2022 21:51:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
827 Apr/26/2022 21:51:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
826 Apr/26/2022 21:51:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
825 Apr/26/2022 21:51:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
824 Apr/26/2022 21:51:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
823 Apr/26/2022 21:51:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
822 Apr/26/2022 21:51:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
821 Apr/26/2022 21:51:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
820 Apr/26/2022 21:51:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
819 Apr/26/2022 21:51:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
818 Apr/26/2022 21:51:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
817 Apr/26/2022 21:50:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
816 Apr/26/2022 21:50:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
815 Apr/26/2022 21:50:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
814 Apr/26/2022 21:50:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
813 Apr/26/2022 21:50:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
812 Apr/26/2022 21:50:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
811 Apr/26/2022 21:50:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
810 Apr/26/2022 21:50:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
809 Apr/26/2022 21:50:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
808 Apr/26/2022 21:50:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
807 Apr/26/2022 21:50:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
806 Apr/26/2022 21:50:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
805 Apr/26/2022 21:49:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
804 Apr/26/2022 21:49:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
803 Apr/26/2022 21:49:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
802 Apr/26/2022 21:49:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
801 Apr/26/2022 21:49:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
800 Apr/26/2022 21:49:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
799 Apr/26/2022 21:49:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
798 Apr/26/2022 21:49:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
797 Apr/26/2022 21:49:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
796 Apr/26/2022 21:49:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
795 Apr/26/2022 21:49:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
794 Apr/26/2022 21:49:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
793 Apr/26/2022 21:48:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
792 Apr/26/2022 21:48:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
791 Apr/26/2022 21:48:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
790 Apr/26/2022 21:48:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
789 Apr/26/2022 21:48:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
788 Apr/26/2022 21:48:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
787 Apr/26/2022 21:48:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
786 Apr/26/2022 21:48:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
785 Apr/26/2022 21:48:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
784 Apr/26/2022 21:48:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
783 Apr/26/2022 21:48:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
782 Apr/26/2022 21:48:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
781 Apr/26/2022 21:47:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
780 Apr/26/2022 21:47:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
779 Apr/26/2022 21:47:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
778 Apr/26/2022 21:47:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
777 Apr/26/2022 21:47:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
776 Apr/26/2022 21:47:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
775 Apr/26/2022 21:47:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
774 Apr/26/2022 21:47:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
773 Apr/26/2022 21:47:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
772 Apr/26/2022 21:47:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
771 Apr/26/2022 21:47:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
770 Apr/26/2022 21:47:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
769 Apr/26/2022 21:46:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
768 Apr/26/2022 21:46:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
767 Apr/26/2022 21:46:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
766 Apr/26/2022 21:46:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
765 Apr/26/2022 21:46:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
764 Apr/26/2022 21:46:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
763 Apr/26/2022 21:46:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
762 Apr/26/2022 21:46:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
761 Apr/26/2022 21:46:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
760 Apr/26/2022 21:46:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
759 Apr/26/2022 21:46:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
758 Apr/26/2022 21:46:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
757 Apr/26/2022 21:45:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
756 Apr/26/2022 21:45:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
755 Apr/26/2022 21:45:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
754 Apr/26/2022 21:45:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
753 Apr/26/2022 21:45:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
752 Apr/26/2022 21:45:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
751 Apr/26/2022 21:45:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
750 Apr/26/2022 21:45:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
749 Apr/26/2022 21:45:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
748 Apr/26/2022 21:45:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
747 Apr/26/2022 21:45:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
746 Apr/26/2022 21:45:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
745 Apr/26/2022 21:44:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
744 Apr/26/2022 21:44:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
743 Apr/26/2022 21:44:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
742 Apr/26/2022 21:44:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
741 Apr/26/2022 21:44:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
740 Apr/26/2022 21:44:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
739 Apr/26/2022 21:44:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
738 Apr/26/2022 21:44:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
737 Apr/26/2022 21:44:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
736 Apr/26/2022 21:44:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
735 Apr/26/2022 21:44:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
734 Apr/26/2022 21:44:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
733 Apr/26/2022 21:43:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
732 Apr/26/2022 21:43:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
731 Apr/26/2022 21:43:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
730 Apr/26/2022 21:43:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
729 Apr/26/2022 21:43:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
728 Apr/26/2022 21:43:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
727 Apr/26/2022 21:43:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
726 Apr/26/2022 21:43:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
725 Apr/26/2022 21:43:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
724 Apr/26/2022 21:43:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
723 Apr/26/2022 21:43:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
722 Apr/26/2022 21:43:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
721 Apr/26/2022 21:42:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
720 Apr/26/2022 21:42:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
719 Apr/26/2022 21:42:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
718 Apr/26/2022 21:42:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
717 Apr/26/2022 21:42:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
716 Apr/26/2022 21:42:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
715 Apr/26/2022 21:42:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
714 Apr/26/2022 21:42:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
713 Apr/26/2022 21:42:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
712 Apr/26/2022 21:42:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
711 Apr/26/2022 21:42:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
710 Apr/26/2022 21:42:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
709 Apr/26/2022 21:41:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
708 Apr/26/2022 21:41:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
707 Apr/26/2022 21:41:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
706 Apr/26/2022 21:41:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
705 Apr/26/2022 21:41:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
704 Apr/26/2022 21:41:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
703 Apr/26/2022 21:41:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
702 Apr/26/2022 21:41:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
701 Apr/26/2022 21:41:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
700 Apr/26/2022 21:41:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
699 Apr/26/2022 21:41:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
698 Apr/26/2022 21:41:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
697 Apr/26/2022 21:40:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
696 Apr/26/2022 21:40:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
695 Apr/26/2022 21:40:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
694 Apr/26/2022 21:40:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
693 Apr/26/2022 21:40:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
692 Apr/26/2022 21:40:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
691 Apr/26/2022 21:40:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
690 Apr/26/2022 21:40:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
689 Apr/26/2022 21:40:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
688 Apr/26/2022 21:40:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
687 Apr/26/2022 21:40:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
686 Apr/26/2022 21:40:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
685 Apr/26/2022 21:39:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
684 Apr/26/2022 21:39:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
683 Apr/26/2022 21:39:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
682 Apr/26/2022 21:39:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
681 Apr/26/2022 21:39:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
680 Apr/26/2022 21:39:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
679 Apr/26/2022 21:39:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
678 Apr/26/2022 21:39:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
677 Apr/26/2022 21:39:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
676 Apr/26/2022 21:39:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
675 Apr/26/2022 21:39:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
674 Apr/26/2022 21:39:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
673 Apr/26/2022 21:38:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
672 Apr/26/2022 21:38:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
671 Apr/26/2022 21:38:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
670 Apr/26/2022 21:38:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
669 Apr/26/2022 21:38:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
668 Apr/26/2022 21:38:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
667 Apr/26/2022 21:38:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
666 Apr/26/2022 21:38:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
665 Apr/26/2022 21:38:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
664 Apr/26/2022 21:38:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
663 Apr/26/2022 21:38:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
662 Apr/26/2022 21:38:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
661 Apr/26/2022 21:37:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
660 Apr/26/2022 21:37:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
659 Apr/26/2022 21:37:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
658 Apr/26/2022 21:37:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
657 Apr/26/2022 21:37:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
656 Apr/26/2022 21:37:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
655 Apr/26/2022 21:37:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
654 Apr/26/2022 21:37:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
653 Apr/26/2022 21:37:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
652 Apr/26/2022 21:37:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
651 Apr/26/2022 21:37:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
650 Apr/26/2022 21:37:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
649 Apr/26/2022 21:36:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
648 Apr/26/2022 21:36:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
647 Apr/26/2022 21:36:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
646 Apr/26/2022 21:36:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
645 Apr/26/2022 21:36:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
644 Apr/26/2022 21:36:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
643 Apr/26/2022 21:36:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
642 Apr/26/2022 21:36:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
641 Apr/26/2022 21:36:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
640 Apr/26/2022 21:36:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
639 Apr/26/2022 21:36:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
638 Apr/26/2022 21:36:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
637 Apr/26/2022 21:35:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
636 Apr/26/2022 21:35:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
635 Apr/26/2022 21:35:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
634 Apr/26/2022 21:35:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
633 Apr/26/2022 21:35:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
632 Apr/26/2022 21:35:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
631 Apr/26/2022 21:35:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
630 Apr/26/2022 21:35:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
629 Apr/26/2022 21:35:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
628 Apr/26/2022 21:35:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
627 Apr/26/2022 21:35:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
626 Apr/26/2022 21:35:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
625 Apr/26/2022 21:34:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
624 Apr/26/2022 21:34:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
623 Apr/26/2022 21:34:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
622 Apr/26/2022 21:34:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
621 Apr/26/2022 21:34:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
620 Apr/26/2022 21:34:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
619 Apr/26/2022 21:34:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
618 Apr/26/2022 21:34:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
617 Apr/26/2022 21:34:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
616 Apr/26/2022 21:34:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
615 Apr/26/2022 21:34:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
614 Apr/26/2022 21:33:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
613 Apr/26/2022 21:33:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
612 Apr/26/2022 21:33:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
611 Apr/26/2022 21:33:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
610 Apr/26/2022 21:33:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
609 Apr/26/2022 21:33:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
608 Apr/26/2022 21:33:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
607 Apr/26/2022 21:33:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
606 Apr/26/2022 21:33:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
605 Apr/26/2022 21:33:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
604 Apr/26/2022 21:33:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
603 Apr/26/2022 21:33:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
602 Apr/26/2022 21:32:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
601 Apr/26/2022 21:32:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
600 Apr/26/2022 21:32:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
599 Apr/26/2022 21:32:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
598 Apr/26/2022 21:32:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
597 Apr/26/2022 21:32:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
596 Apr/26/2022 21:32:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
595 Apr/26/2022 21:32:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
594 Apr/26/2022 21:32:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
593 Apr/26/2022 21:32:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
592 Apr/26/2022 21:32:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
591 Apr/26/2022 21:32:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
590 Apr/26/2022 21:31:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
589 Apr/26/2022 21:31:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
588 Apr/26/2022 21:31:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
587 Apr/26/2022 21:31:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
586 Apr/26/2022 21:31:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
585 Apr/26/2022 21:31:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
584 Apr/26/2022 21:31:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
583 Apr/26/2022 21:31:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
582 Apr/26/2022 21:31:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
581 Apr/26/2022 21:31:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
580 Apr/26/2022 21:31:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
579 Apr/26/2022 21:31:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
578 Apr/26/2022 21:30:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
577 Apr/26/2022 21:30:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
576 Apr/26/2022 21:30:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
575 Apr/26/2022 21:30:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
574 Apr/26/2022 21:30:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
573 Apr/26/2022 21:30:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
572 Apr/26/2022 21:30:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
571 Apr/26/2022 21:30:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
570 Apr/26/2022 21:30:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
569 Apr/26/2022 21:30:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
568 Apr/26/2022 21:30:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
567 Apr/26/2022 21:30:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
566 Apr/26/2022 21:29:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
565 Apr/26/2022 21:29:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
564 Apr/26/2022 21:29:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
563 Apr/26/2022 21:29:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
562 Apr/26/2022 21:29:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
561 Apr/26/2022 21:29:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
560 Apr/26/2022 21:29:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
559 Apr/26/2022 21:29:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
558 Apr/26/2022 21:29:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
557 Apr/26/2022 21:29:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
556 Apr/26/2022 21:29:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
555 Apr/26/2022 21:29:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
554 Apr/26/2022 21:28:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
553 Apr/26/2022 21:28:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
552 Apr/26/2022 21:28:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
551 Apr/26/2022 21:28:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
550 Apr/26/2022 21:28:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
549 Apr/26/2022 21:28:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
548 Apr/26/2022 21:28:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
547 Apr/26/2022 21:28:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
546 Apr/26/2022 21:28:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
545 Apr/26/2022 21:28:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
544 Apr/26/2022 21:28:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
543 Apr/26/2022 21:28:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
542 Apr/26/2022 21:27:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
541 Apr/26/2022 21:27:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
540 Apr/26/2022 21:27:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
539 Apr/26/2022 21:27:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
538 Apr/26/2022 21:27:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
537 Apr/26/2022 21:27:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
536 Apr/26/2022 21:27:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
535 Apr/26/2022 21:27:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
534 Apr/26/2022 21:27:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
533 Apr/26/2022 21:27:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
532 Apr/26/2022 21:27:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
531 Apr/26/2022 21:27:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
530 Apr/26/2022 21:26:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
529 Apr/26/2022 21:26:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
528 Apr/26/2022 21:26:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
527 Apr/26/2022 21:26:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
526 Apr/26/2022 21:26:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
525 Apr/26/2022 21:26:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
524 Apr/26/2022 21:26:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
523 Apr/26/2022 21:26:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
522 Apr/26/2022 21:26:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
521 Apr/26/2022 21:26:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
520 Apr/26/2022 21:26:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
519 Apr/26/2022 21:26:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
518 Apr/26/2022 21:25:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
517 Apr/26/2022 21:25:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
516 Apr/26/2022 21:25:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
515 Apr/26/2022 21:25:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
514 Apr/26/2022 21:25:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
513 Apr/26/2022 21:25:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
512 Apr/26/2022 21:25:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
511 Apr/26/2022 21:25:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
510 Apr/26/2022 21:25:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
509 Apr/26/2022 21:25:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
508 Apr/26/2022 21:25:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
507 Apr/26/2022 21:25:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
506 Apr/26/2022 21:24:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
505 Apr/26/2022 21:24:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
504 Apr/26/2022 21:24:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
503 Apr/26/2022 21:24:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
502 Apr/26/2022 21:24:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
501 Apr/26/2022 21:24:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
500 Apr/26/2022 21:24:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
499 Apr/26/2022 21:24:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
498 Apr/26/2022 21:24:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
497 Apr/26/2022 21:24:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
496 Apr/26/2022 21:24:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
495 Apr/26/2022 21:24:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
494 Apr/26/2022 21:23:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
493 Apr/26/2022 21:23:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
492 Apr/26/2022 21:23:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
491 Apr/26/2022 21:23:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
490 Apr/26/2022 21:23:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
489 Apr/26/2022 21:23:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
488 Apr/26/2022 21:23:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
487 Apr/26/2022 21:23:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
486 Apr/26/2022 21:23:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
485 Apr/26/2022 21:23:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
484 Apr/26/2022 21:23:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
483 Apr/26/2022 21:23:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
482 Apr/26/2022 21:22:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
481 Apr/26/2022 21:22:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
480 Apr/26/2022 21:22:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
479 Apr/26/2022 21:22:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
478 Apr/26/2022 21:22:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
477 Apr/26/2022 21:22:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
476 Apr/26/2022 21:22:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
475 Apr/26/2022 21:22:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
474 Apr/26/2022 21:22:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
473 Apr/26/2022 21:22:16 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:21677->81.200.212.113:8291, len 40
472 Apr/26/2022 21:22:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
471 Apr/26/2022 21:22:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
470 Apr/26/2022 21:22:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
469 Apr/26/2022 21:21:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
468 Apr/26/2022 21:21:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
467 Apr/26/2022 21:21:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
466 Apr/26/2022 21:21:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
465 Apr/26/2022 21:21:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
464 Apr/26/2022 21:21:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
463 Apr/26/2022 21:21:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
462 Apr/26/2022 21:21:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
461 Apr/26/2022 21:21:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
460 Apr/26/2022 21:21:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
459 Apr/26/2022 21:21:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
458 Apr/26/2022 21:21:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
457 Apr/26/2022 21:20:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
456 Apr/26/2022 21:20:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
455 Apr/26/2022 21:20:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
454 Apr/26/2022 21:20:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
453 Apr/26/2022 21:20:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
452 Apr/26/2022 21:20:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
451 Apr/26/2022 21:20:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
450 Apr/26/2022 21:20:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
449 Apr/26/2022 21:20:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
448 Apr/26/2022 21:20:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
447 Apr/26/2022 21:20:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
446 Apr/26/2022 21:20:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
445 Apr/26/2022 21:19:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
444 Apr/26/2022 21:19:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
443 Apr/26/2022 21:19:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
442 Apr/26/2022 21:19:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
441 Apr/26/2022 21:19:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
440 Apr/26/2022 21:19:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
439 Apr/26/2022 21:19:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
438 Apr/26/2022 21:19:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
437 Apr/26/2022 21:19:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
436 Apr/26/2022 21:19:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
435 Apr/26/2022 21:19:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
434 Apr/26/2022 21:19:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
433 Apr/26/2022 21:18:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
432 Apr/26/2022 21:18:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
431 Apr/26/2022 21:18:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
430 Apr/26/2022 21:18:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
429 Apr/26/2022 21:18:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
428 Apr/26/2022 21:18:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
427 Apr/26/2022 21:18:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
426 Apr/26/2022 21:18:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
425 Apr/26/2022 21:18:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
424 Apr/26/2022 21:18:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
423 Apr/26/2022 21:18:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
422 Apr/26/2022 21:18:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
421 Apr/26/2022 21:17:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
420 Apr/26/2022 21:17:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
419 Apr/26/2022 21:17:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
418 Apr/26/2022 21:17:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
417 Apr/26/2022 21:17:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
416 Apr/26/2022 21:17:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
415 Apr/26/2022 21:17:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
414 Apr/26/2022 21:17:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
413 Apr/26/2022 21:17:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
412 Apr/26/2022 21:17:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
411 Apr/26/2022 21:17:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
410 Apr/26/2022 21:17:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
409 Apr/26/2022 21:16:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
408 Apr/26/2022 21:16:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
407 Apr/26/2022 21:16:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
406 Apr/26/2022 21:16:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
405 Apr/26/2022 21:16:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
404 Apr/26/2022 21:16:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
403 Apr/26/2022 21:16:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
402 Apr/26/2022 21:16:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
401 Apr/26/2022 21:16:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
400 Apr/26/2022 21:16:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
399 Apr/26/2022 21:16:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
398 Apr/26/2022 21:16:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
397 Apr/26/2022 21:15:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
396 Apr/26/2022 21:15:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
395 Apr/26/2022 21:15:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
394 Apr/26/2022 21:15:42 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
393 Apr/26/2022 21:15:37 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
392 Apr/26/2022 21:15:32 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
391 Apr/26/2022 21:15:27 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
390 Apr/26/2022 21:15:22 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
389 Apr/26/2022 21:15:17 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
388 Apr/26/2022 21:15:12 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
387 Apr/26/2022 21:15:07 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
386 Apr/26/2022 21:15:02 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
385 Apr/26/2022 21:14:57 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
384 Apr/26/2022 21:14:52 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
383 Apr/26/2022 21:14:47 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
382 Apr/26/2022 21:14:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
381 Apr/26/2022 21:14:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
380 Apr/26/2022 21:14:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
379 Apr/26/2022 21:14:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
378 Apr/26/2022 21:14:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
377 Apr/26/2022 21:14:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
376 Apr/26/2022 21:14:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
375 Apr/26/2022 21:14:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
374 Apr/26/2022 21:14:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
373 Apr/26/2022 21:13:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
372 Apr/26/2022 21:13:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
371 Apr/26/2022 21:13:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
370 Apr/26/2022 21:13:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
369 Apr/26/2022 21:13:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
368 Apr/26/2022 21:13:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
367 Apr/26/2022 21:13:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
366 Apr/26/2022 21:13:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
365 Apr/26/2022 21:13:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
364 Apr/26/2022 21:13:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
363 Apr/26/2022 21:13:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
362 Apr/26/2022 21:13:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
361 Apr/26/2022 21:12:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
360 Apr/26/2022 21:12:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
359 Apr/26/2022 21:12:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
358 Apr/26/2022 21:12:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
357 Apr/26/2022 21:12:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
356 Apr/26/2022 21:12:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
355 Apr/26/2022 21:12:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
354 Apr/26/2022 21:12:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
353 Apr/26/2022 21:12:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
352 Apr/26/2022 21:12:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
351 Apr/26/2022 21:12:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
350 Apr/26/2022 21:12:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
349 Apr/26/2022 21:11:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
348 Apr/26/2022 21:11:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
347 Apr/26/2022 21:11:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
346 Apr/26/2022 21:11:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
345 Apr/26/2022 21:11:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
344 Apr/26/2022 21:11:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
343 Apr/26/2022 21:11:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
342 Apr/26/2022 21:11:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
341 Apr/26/2022 21:11:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
340 Apr/26/2022 21:11:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
339 Apr/26/2022 21:11:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
338 Apr/26/2022 21:11:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
337 Apr/26/2022 21:10:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
336 Apr/26/2022 21:10:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
335 Apr/26/2022 21:10:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
334 Apr/26/2022 21:10:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
333 Apr/26/2022 21:10:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
332 Apr/26/2022 21:10:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
331 Apr/26/2022 21:10:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
330 Apr/26/2022 21:10:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
329 Apr/26/2022 21:10:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
328 Apr/26/2022 21:10:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
327 Apr/26/2022 21:10:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
326 Apr/26/2022 21:10:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
325 Apr/26/2022 21:09:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
324 Apr/26/2022 21:09:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
323 Apr/26/2022 21:09:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
322 Apr/26/2022 21:09:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
321 Apr/26/2022 21:09:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
320 Apr/26/2022 21:09:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
319 Apr/26/2022 21:09:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
318 Apr/26/2022 21:09:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
317 Apr/26/2022 21:09:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
316 Apr/26/2022 21:09:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
315 Apr/26/2022 21:09:06 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
314 Apr/26/2022 21:09:01 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
313 Apr/26/2022 21:08:56 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
312 Apr/26/2022 21:08:51 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
311 Apr/26/2022 21:08:46 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
310 Apr/26/2022 21:08:41 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
309 Apr/26/2022 21:08:36 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
308 Apr/26/2022 21:08:31 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
307 Apr/26/2022 21:08:26 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
306 Apr/26/2022 21:08:21 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
305 Apr/26/2022 21:08:16 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
304 Apr/26/2022 21:08:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
303 Apr/26/2022 21:08:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
302 Apr/26/2022 21:08:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
301 Apr/26/2022 21:07:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
300 Apr/26/2022 21:07:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
299 Apr/26/2022 21:07:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
298 Apr/26/2022 21:07:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
297 Apr/26/2022 21:07:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
296 Apr/26/2022 21:07:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
295 Apr/26/2022 21:07:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
294 Apr/26/2022 21:07:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
293 Apr/26/2022 21:07:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
292 Apr/26/2022 21:07:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
291 Apr/26/2022 21:07:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
290 Apr/26/2022 21:07:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
289 Apr/26/2022 21:06:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
288 Apr/26/2022 21:06:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
287 Apr/26/2022 21:06:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
286 Apr/26/2022 21:06:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
285 Apr/26/2022 21:06:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
284 Apr/26/2022 21:06:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
283 Apr/26/2022 21:06:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
282 Apr/26/2022 21:06:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
281 Apr/26/2022 21:06:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
280 Apr/26/2022 21:06:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
279 Apr/26/2022 21:06:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
278 Apr/26/2022 21:06:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
277 Apr/26/2022 21:05:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
276 Apr/26/2022 21:05:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
275 Apr/26/2022 21:05:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
274 Apr/26/2022 21:05:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
273 Apr/26/2022 21:05:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
272 Apr/26/2022 21:05:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
271 Apr/26/2022 21:05:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
270 Apr/26/2022 21:05:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
269 Apr/26/2022 21:05:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
268 Apr/26/2022 21:05:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
267 Apr/26/2022 21:05:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
266 Apr/26/2022 21:05:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
265 Apr/26/2022 21:04:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
264 Apr/26/2022 21:04:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
263 Apr/26/2022 21:04:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
262 Apr/26/2022 21:04:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
261 Apr/26/2022 21:04:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
260 Apr/26/2022 21:04:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
259 Apr/26/2022 21:04:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
258 Apr/26/2022 21:04:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
257 Apr/26/2022 21:04:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
256 Apr/26/2022 21:04:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
255 Apr/26/2022 21:04:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
254 Apr/26/2022 21:04:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
253 Apr/26/2022 21:03:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
252 Apr/26/2022 21:03:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
251 Apr/26/2022 21:03:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
250 Apr/26/2022 21:03:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
249 Apr/26/2022 21:03:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
248 Apr/26/2022 21:03:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
247 Apr/26/2022 21:03:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
246 Apr/26/2022 21:03:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
245 Apr/26/2022 21:03:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
244 Apr/26/2022 21:03:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
243 Apr/26/2022 21:03:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
242 Apr/26/2022 21:03:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
241 Apr/26/2022 21:02:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
240 Apr/26/2022 21:02:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
239 Apr/26/2022 21:02:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
238 Apr/26/2022 21:02:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
237 Apr/26/2022 21:02:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
236 Apr/26/2022 21:02:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
235 Apr/26/2022 21:02:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
234 Apr/26/2022 21:02:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
233 Apr/26/2022 21:02:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
232 Apr/26/2022 21:02:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
231 Apr/26/2022 21:02:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
230 Apr/26/2022 21:02:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
229 Apr/26/2022 21:01:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
228 Apr/26/2022 21:01:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
227 Apr/26/2022 21:01:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
226 Apr/26/2022 21:01:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
225 Apr/26/2022 21:01:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
224 Apr/26/2022 21:01:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
223 Apr/26/2022 21:01:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
222 Apr/26/2022 21:01:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
221 Apr/26/2022 21:01:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
220 Apr/26/2022 21:01:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
219 Apr/26/2022 21:01:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
218 Apr/26/2022 21:01:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
217 Apr/26/2022 21:00:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
216 Apr/26/2022 21:00:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
215 Apr/26/2022 21:00:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
214 Apr/26/2022 21:00:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
213 Apr/26/2022 21:00:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
212 Apr/26/2022 21:00:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
211 Apr/26/2022 21:00:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
210 Apr/26/2022 21:00:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
209 Apr/26/2022 21:00:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
208 Apr/26/2022 21:00:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
207 Apr/26/2022 21:00:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
206 Apr/26/2022 20:59:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
205 Apr/26/2022 20:59:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
204 Apr/26/2022 20:59:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
203 Apr/26/2022 20:59:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
202 Apr/26/2022 20:59:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
201 Apr/26/2022 20:59:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
200 Apr/26/2022 20:59:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
199 Apr/26/2022 20:59:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
198 Apr/26/2022 20:59:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
197 Apr/26/2022 20:59:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
196 Apr/26/2022 20:59:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
195 Apr/26/2022 20:59:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
194 Apr/26/2022 20:58:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
193 Apr/26/2022 20:58:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
192 Apr/26/2022 20:58:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
191 Apr/26/2022 20:58:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
190 Apr/26/2022 20:58:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
189 Apr/26/2022 20:58:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
188 Apr/26/2022 20:58:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
187 Apr/26/2022 20:58:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
186 Apr/26/2022 20:58:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
185 Apr/26/2022 20:58:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
184 Apr/26/2022 20:58:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
183 Apr/26/2022 20:58:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
182 Apr/26/2022 20:57:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
181 Apr/26/2022 20:57:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
180 Apr/26/2022 20:57:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
179 Apr/26/2022 20:57:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
178 Apr/26/2022 20:57:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
177 Apr/26/2022 20:57:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
176 Apr/26/2022 20:57:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
175 Apr/26/2022 20:57:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
174 Apr/26/2022 20:57:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
173 Apr/26/2022 20:57:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
172 Apr/26/2022 20:57:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
171 Apr/26/2022 20:57:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
170 Apr/26/2022 20:56:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
169 Apr/26/2022 20:56:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
168 Apr/26/2022 20:56:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
167 Apr/26/2022 20:56:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
166 Apr/26/2022 20:56:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
165 Apr/26/2022 20:56:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
164 Apr/26/2022 20:56:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
163 Apr/26/2022 20:56:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
162 Apr/26/2022 20:56:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
161 Apr/26/2022 20:56:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
160 Apr/26/2022 20:56:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
159 Apr/26/2022 20:56:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
158 Apr/26/2022 20:55:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
157 Apr/26/2022 20:55:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
156 Apr/26/2022 20:55:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
155 Apr/26/2022 20:55:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
154 Apr/26/2022 20:55:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
153 Apr/26/2022 20:55:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
152 Apr/26/2022 20:55:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
151 Apr/26/2022 20:55:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
150 Apr/26/2022 20:55:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
149 Apr/26/2022 20:55:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
148 Apr/26/2022 20:55:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
147 Apr/26/2022 20:55:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
146 Apr/26/2022 20:54:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
145 Apr/26/2022 20:54:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
144 Apr/26/2022 20:54:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
143 Apr/26/2022 20:54:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
142 Apr/26/2022 20:54:39 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
141 Apr/26/2022 20:54:34 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
140 Apr/26/2022 20:54:29 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
139 Apr/26/2022 20:54:24 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
138 Apr/26/2022 20:54:19 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
137 Apr/26/2022 20:54:14 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
136 Apr/26/2022 20:54:09 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
135 Apr/26/2022 20:54:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
134 Apr/26/2022 20:53:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
133 Apr/26/2022 20:53:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
132 Apr/26/2022 20:53:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
131 Apr/26/2022 20:53:44 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
130 Apr/26/2022 20:53:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
129 Apr/26/2022 20:53:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
128 Apr/26/2022 20:53:28 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
127 Apr/26/2022 20:53:23 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
126 Apr/26/2022 20:53:18 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
125 Apr/26/2022 20:53:13 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
124 Apr/26/2022 20:53:08 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
123 Apr/26/2022 20:53:03 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
122 Apr/26/2022 20:52:58 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
121 Apr/26/2022 20:52:53 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
120 Apr/26/2022 20:52:48 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
119 Apr/26/2022 20:52:43 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
118 Apr/26/2022 20:52:38 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
117 Apr/26/2022 20:52:33 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
116 Apr/26/2022 19:23:14 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:24346->81.200.212.113:8291, len 40
115 Apr/26/2022 19:15:06 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:37595->81.200.212.113:8291, len 40
114 Apr/26/2022 19:12:05 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 67.229.103.154:43385->81.200.212.113:8291, len 40
113 Apr/26/2022 17:53:17 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:54605->81.200.212.113:8291, len 40
112 Apr/26/2022 16:54:27 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:60704->81.200.212.113:8291, len 40
111 Apr/26/2022 16:28:25 memory system, info, account user admin logged out from 192.168.1.252 via winbox
110 Apr/26/2022 16:17:35 memory system, info traffic monitor removed by adminse
109 Apr/26/2022 16:17:33 memory system, info traffic monitor changed by adminse
108 Apr/26/2022 16:17:12 memory system, info traffic monitor added by adminse
107 Apr/26/2022 16:11:22 memory system, info queue changed by adminse
106 Apr/26/2022 16:11:21 memory system, info queue changed by adminse
105 Apr/26/2022 16:11:19 memory system, info queue changed by adminse
104 Apr/26/2022 16:10:48 memory system, info simple queue removed by adminse
103 Apr/26/2022 16:10:47 memory system, info simple queue removed by adminse
102 Apr/26/2022 16:10:46 memory system, info simple queue removed by adminse
101 Apr/26/2022 16:10:42 memory system, info simple queue removed by adminse
99 Apr/26/2022 16:10:41 memory system, info simple queue removed by adminse
100 Apr/26/2022 16:10:41 memory system, info simple queue removed by adminse
97 Apr/26/2022 16:10:40 memory system, info simple queue removed by adminse
98 Apr/26/2022 16:10:40 memory system, info simple queue removed by adminse
96 Apr/26/2022 16:10:39 memory system, info simple queue removed by adminse
95 Apr/26/2022 16:10:37 memory system, info simple queue removed by adminse
93 Apr/26/2022 16:10:34 memory system, info simple queue removed by adminse
94 Apr/26/2022 16:10:34 memory system, info simple queue removed by adminse
91 Apr/26/2022 16:10:33 memory system, info simple queue removed by adminse
92 Apr/26/2022 16:10:33 memory system, info simple queue removed by adminse
90 Apr/26/2022 16:10:32 memory system, info simple queue removed by adminse
88 Apr/26/2022 16:10:29 memory system, info simple queue removed by adminse
89 Apr/26/2022 16:10:29 memory system, info simple queue removed by adminse
87 Apr/26/2022 16:10:28 memory system, info simple queue removed by adminse
86 Apr/26/2022 16:10:24 memory system, info simple queue removed by adminse
85 Apr/26/2022 16:10:23 memory system, info simple queue removed by adminse
84 Apr/26/2022 16:08:32 memory system, info nat rule changed by admin
83 Apr/26/2022 16:08:23 memory system, info nat rule changed by admin
81 Apr/26/2022 16:07:48 memory system, info dhcp lease removed by admin
82 Apr/26/2022 16:07:48 memory system, info dhcp lease removed by admin
79 Apr/26/2022 16:07:47 memory system, info dhcp lease removed by admin
80 Apr/26/2022 16:07:47 memory system, info dhcp lease removed by admin
78 Apr/26/2022 16:07:44 memory system, info dhcp lease removed by admin
77 Apr/26/2022 16:07:42 memory system, info dhcp lease removed by admin
76 Apr/26/2022 16:07:41 memory system, info dhcp lease removed by admin
75 Apr/26/2022 16:07:40 memory system, info dhcp lease removed by admin
74 Apr/26/2022 16:07:38 memory system, info dhcp lease removed by admin
73 Apr/26/2022 16:07:14 memory system, info dhcp lease removed by admin
72 Apr/26/2022 16:07:11 memory system, info dhcp lease removed by admin
71 Apr/26/2022 16:07:09 memory system, info dhcp lease removed by admin
70 Apr/26/2022 16:07:05 memory system, info dhcp lease removed by admin
69 Apr/26/2022 16:06:58 memory system, info dhcp lease removed by admin
68 Apr/26/2022 16:05:37 memory system, info address changed by admin
67 Apr/26/2022 16:03:23 memory system, info address changed by admin
66 Apr/26/2022 16:03:02 memory system, info address changed by admin
65 Apr/26/2022 16:00:54 memory system, info interface list member changed by admin
64 Apr/26/2022 16:00:05 memory system, info device changed by admin
63 Apr/26/2022 16:00:02 memory system, info device changed by admin
62 Apr/26/2022 15:59:57 memory system, info bridge port changed by admin
61 Apr/26/2022 15:59:42 memory system, info bridge port changed by admin
60 Apr/26/2022 15:58:46 memory system, info bridge port removed by admin
59 Apr/26/2022 15:50:59 memory system, info ipsec proposal default changed by admin
58 Apr/26/2022 15:50:48 memory system, info ipsec policy changed by admin
57 Apr/26/2022 15:20:05 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:33985->81.200.212.113:8291, len 40
56 Apr/26/2022 15:14:31 memory system, info dhcp server dhcp_wifi changed by admin
55 Apr/26/2022 15:01:52 memory interface, info eth1-wan1 link up (speed 1G, full duplex)
53 Apr/26/2022 15:01:50 memory system, info NTP params changed
54 Apr/26/2022 15:01:50 memory dhcp, info dhcp-client on eth2-wan2 got IP address 10.64.64.217
51 Apr/26/2022 15:01:48 memory system, info device changed by admin
52 Apr/26/2022 15:01:48 memory interface, info eth1-wan1 link down
50 Apr/26/2022 15:01:47 memory interface, info eth2-wan2 link up (speed 1G, full duplex)
46 Apr/26/2022 15:01:43 memory system, info device changed by admin
47 Apr/26/2022 15:01:43 memory interface, info eth2-wan2 link down
48 Apr/26/2022 15:01:43 memory dhcp, info dhcp-client on eth2-wan2 lost IP address 10.64.64.217 - lease stopped locally
49 Apr/26/2022 15:01:43 memory system, info NTP params changed
45 Apr/26/2022 15:01:33 memory interface, info eth5-lan-master link up (speed 1G, full duplex)
43 Apr/26/2022 15:01:30 memory system, info device changed by admin
44 Apr/26/2022 15:01:30 memory interface, info eth5-lan-master link down
42 Apr/26/2022 15:01:15 memory system, info, account user admin logged in from 192.168.1.252 via winbox
41 Apr/26/2022 15:00:15 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 192.241.212.86:52026->81.200.212.113:8291, len 40
40 Apr/26/2022 14:56:21 memory firewall, info DDoS Attack! input: in:eth1-wan1 out:(unknown 0), src-mac a8:9d:21:97:94:40, proto TCP (SYN), 81.200.27.84:36150->81.200.212.113:8291, len 40
39 Apr/26/2022 14:45:11 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
38 Apr/26/2022 14:45:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
37 Apr/26/2022 14:44:59 memory interface, info eth5-lan-master link up (speed 1G, full duplex)
35 Apr/26/2022 14:44:55 memory system, info NTP params changed
36 Apr/26/2022 14:44:55 memory dhcp, info dhcp-client on eth2-wan2 got IP address 10.64.64.217
34 Apr/26/2022 14:44:51 memory interface, info eth2-wan2 link up (speed 1G, full duplex)
33 Apr/26/2022 14:44:39 memory interface, info eth5-lan-master link down
32 Apr/26/2022 14:44:08 memory interface, info eth1-wan1 link up (speed 1G, full duplex)
31 Apr/26/2022 14:42:18 memory interface, info eth5-lan-master link up (speed 1G, full duplex)
30 Apr/26/2022 14:42:15 memory interface, info eth5-lan-master link down
29 Apr/26/2022 14:40:23 memory interface, info eth5-lan-master link up (speed 1G, full duplex)
28 Apr/26/2022 14:36:30 memory interface, info eth5-lan-master link down
25 Apr/26/2022 14:35:00 memory interface, info eth2-wan2 link down
26 Apr/26/2022 14:35:00 memory dhcp, info dhcp-client on eth2-wan2 lost IP address 10.64.64.217 - lease stopped locally
27 Apr/26/2022 14:35:00 memory system, info NTP params changed
24 Apr/26/2022 14:34:59 memory interface, info eth1-wan1 link down
22 Apr/26/2022 14:34:49 memory system, info, account user admin logged out from 192.168.1.252 via web
23 Apr/26/2022 14:34:49 memory system, info, account user admin logged out from 192.168.1.52 via web
21 Apr/26/2022 14:33:30 memory interface, info eth5-lan-master link up (speed 1G, full duplex)
20 Apr/26/2022 14:33:26 memory interface, info eth5-lan-master link down
19 Apr/26/2022 14:33:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
18 Apr/26/2022 14:33:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
17 Apr/26/2022 14:33:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
16 Apr/26/2022 14:33:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
15 Apr/26/2022 14:33:05 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
14 Apr/26/2022 14:33:00 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
13 Apr/26/2022 14:32:55 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
12 Apr/26/2022 14:32:50 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
11 Apr/26/2022 14:32:45 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
10 Apr/26/2022 14:32:40 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
9 Apr/26/2022 14:32:35 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
8 Apr/26/2022 14:32:30 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
7 Apr/26/2022 14:32:25 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
6 Apr/26/2022 14:32:20 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
5 Apr/26/2022 14:32:15 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
4 Apr/26/2022 14:32:10 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
3 Apr/26/2022 14:32:04 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
2 Apr/26/2022 14:31:59 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
1 Apr/26/2022 14:31:54 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop
0 Apr/26/2022 14:31:49 memory interface, warning eth5-lan-master: bridge port received packet with own address as source address (64:d1:54:84:ab:41), probably loop


gmx
Модератор
Сообщения: 2847
Зарегистрирован: 01 окт 2012, 14:48

27 апр 2022, 19:48

Ну ноут - это точно отдельная проблема.
А так, проблема в сети не решена. Надо искать. Чудес не бывает. Проблема точно есть.
Если есть возможность, меняйте сетевое оборудование на заведомо исправное.
Ставьте в разрыв дополнительное и так далее.


LehaMechanic
Сообщения: 4
Зарегистрирован: 15 апр 2022, 11:33

12 май 2022, 10:20

Мы отловили момент, когда ошибки по петле сыпались стеной, отключили всю сеть, выдернули все провода из центрального свитча, и ничего не помогло, ошибки продолжали сыпаться. Что это значит? Неужели в микроте никак нельзя ничего настроить, чтобы хотя бы видеть, что за пакеты лезут, откуда и куда, которые генерируют ошибку петли?


gmx
Модератор
Сообщения: 2847
Зарегистрирован: 01 окт 2012, 14:48

12 май 2022, 21:53

Есть вариант - неисправность оборудования. Я видел свичи, которые сыпали в сеть тысячами пакетов в секунду.
В следующий раз, всё-таки, дергайте кабели из микротика. Причем не просто бездумно все подряд, а по одному, с четким пониманием куда и для чего.

Если есть микротик подменный, то и его тоже стоит попробовать. Ну и конфиг не грех прошерстить. Помнится, в старых конфигурациях, когда vlan через куча бриджей отрабатывались, организовать петлю своими руками было очень легко.


Ответить