Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0 Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] Linux version 4.4.74 (buildbot@catfish) (gcc version 5.4.0 (LEDE GCC 5.4.0 r0-97f3a33) ) #0 SMP Wed May 8 05:42:28 UTC 2019 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=30c5383d Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Machine model: LS1043A RDB Board Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Reserved memory: initialized node bman-fbpr, compatible id fsl,bman-fbpr Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Reserved memory: initialized node qman-pfdr, compatible id fsl,qman-pfdr Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Reserved memory: initialized node qman-fqd, compatible id fsl,qman-fqd Sun May 12 00:11:52 2019 kern.warn kernel: [ 0.000000] Forcing write-allocate cache policy for SMP Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Memory policy: Data cache writealloc Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.000000] On node 0 totalpages: 130560 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.000000] free_area_init_node: node 0, pgdat 804c4100, node_mem_map 9bb80000 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.000000] Normal zone: 1020 pages used for memmap Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.000000] Normal zone: 0 pages reserved Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.000000] Normal zone: 130560 pages, LIFO batch:31 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] PERCPU: Embedded 13 pages/cpu @9fdae000 s21580 r8192 d23476 u53248 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.000000] pcpu-alloc: s21580 r8192 d23476 u53248 alloc=13*4096 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129540 Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] Kernel command line: root=/dev/mtdblock3 rootfstype=squashfs,jffs2 noinitrd earlycon=uart8250,mmio,0x21c0500 console=ttyS0,115200 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Memory: 454064K/522240K available (3594K kernel code, 122K rwdata, 984K rodata, 252K init, 467K bss, 68176K reserved, 0K cma-reserved, 0K highmem) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] Virtual kernel memory layout: Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] vmalloc : 0xa0000000 - 0xff800000 (1528 MB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] lowmem : 0x80000000 - 0x9fe00000 ( 510 MB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] modules : 0x7f000000 - 0x7fe00000 ( 14 MB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] .text : 0x80008000 - 0x80480eb4 (4580 kB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] .init : 0x80481000 - 0x804c0000 ( 252 kB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] .data : 0x804c0000 - 0x804deb14 ( 123 kB) Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.000000] .bss : 0x804deb14 - 0x80553950 ( 468 kB) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Hierarchical RCU implementation. Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] NR_IRQS:16 nr_irqs:16 16 Sun May 12 00:11:52 2019 kern.warn kernel: [ 0.000000] GIC: Adjusting CPU interface base to 0x000000000142f000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] GIC: Using split EOI/Deactivate mode Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] Architected cp15 timer(s) running at 25.00MHz (phys). Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x5c40939b5, max_idle_ns: 440795202646 ns Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000003] sched_clock: 56 bits at 25MHz, resolution 40ns, wraps every 4398046511100ns Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000010] Switching to timer-based delay loop, resolution 40ns Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000876] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=25000) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000884] pid_max: default: 32768 minimum: 301 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000961] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.000968] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.001286] CPU: Testing write buffer coherency: ok Sun May 12 00:11:52 2019 kern.info kernel: [ 0.001438] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.001458] Setting up static identity map for 0x800082c0 - 0x800082f4 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.002810] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.003098] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.003381] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.003413] Brought up 4 CPUs Sun May 12 00:11:52 2019 kern.info kernel: [ 0.003425] SMP: Total of 4 processors activated (200.00 BogoMIPS). Sun May 12 00:11:52 2019 kern.info kernel: [ 0.003430] CPU: All CPU(s) started in HYP mode. Sun May 12 00:11:52 2019 kern.info kernel: [ 0.003433] CPU: Virtualization extensions available. Sun May 12 00:11:52 2019 kern.info kernel: [ 0.003661] devtmpfs: initialized Sun May 12 00:11:52 2019 kern.info kernel: [ 0.008011] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.008116] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns Sun May 12 00:11:52 2019 kern.info kernel: [ 0.008130] futex hash table entries: 1024 (order: 4, 65536 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.008231] pinctrl core: initialized pinctrl subsystem Sun May 12 00:11:52 2019 kern.info kernel: [ 0.008597] NET: Registered protocol family 16 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.008766] DMA: preallocated 256 KiB pool for atomic coherent allocations Sun May 12 00:11:52 2019 kern.info kernel: [ 0.009083] Bman ver:0a02,02,01 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.012387] qman-fqd addr 0x9f000000 size 0x800000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.012393] qman-pfdr addr 0x9c000000 size 0x2000000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.012400] Qman ver:0a01,03,02,00 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.022356] console [pstore-1] enabled Sun May 12 00:11:52 2019 kern.info kernel: [ 0.022362] pstore: Registered ramoops as persistent store backend Sun May 12 00:11:52 2019 kern.info kernel: [ 0.022368] ramoops: attached 0x80000@0x9bf80000, ecc: 0/0 Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.028638] SCSI subsystem initialized Sun May 12 00:11:52 2019 kern.info kernel: [ 0.029268] i2c i2c-0: IMX I2C adapter registered Sun May 12 00:11:52 2019 kern.info kernel: [ 0.029277] i2c i2c-0: can't use DMA Sun May 12 00:11:52 2019 kern.info kernel: [ 0.029438] pps_core: LinuxPPS API ver. 1 registered Sun May 12 00:11:52 2019 kern.info kernel: [ 0.029445] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti Sun May 12 00:11:52 2019 kern.info kernel: [ 0.029466] PTP clock support registered Sun May 12 00:11:52 2019 kern.info kernel: [ 0.029543] bman-fbpr addr 0x9e000000 size 0x1000000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.029573] Bman err interrupt handler present Sun May 12 00:11:52 2019 kern.info kernel: [ 0.030078] Bman portal initialised, cpu 0 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.030155] Bman portal initialised, cpu 1 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.030230] Bman portal initialised, cpu 2 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.030298] Bman portal initialised, cpu 3 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.030304] Bman portals initialised Sun May 12 00:11:52 2019 kern.info kernel: [ 0.031584] Qman err interrupt handler present Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032150] Qman portal initialised, cpu 0 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032212] Qman portal initialised, cpu 1 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032271] Qman portal initialised, cpu 2 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032329] Qman portal initialised, cpu 3 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032334] Qman portals initialised Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032484] Bman: BPID allocator includes range 32:32 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032553] Qman: FQID allocator includes range 256:256 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032559] Qman: FQID allocator includes range 32768:32768 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032635] Qman: CGRID allocator includes range 0:256 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032803] Qman: pool channel allocator includes range 1025:15 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.032902] No USDPAA memory, no 'fsl,usdpaa-mem' in device-tree Sun May 12 00:11:52 2019 kern.info kernel: [ 0.033558] clocksource: Switched to clocksource arch_sys_counter Sun May 12 00:11:52 2019 kern.info kernel: [ 0.034567] NET: Registered protocol family 2 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.034877] TCP established hash table entries: 4096 (order: 2, 16384 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.034911] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.034962] TCP: Hash tables configured (established 4096 bind 4096) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.034988] UDP hash table entries: 256 (order: 1, 8192 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.035005] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.035101] NET: Registered protocol family 1 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.035127] PCI: CLS 0 bytes, default 64 Sun May 12 00:11:52 2019 kern.warn kernel: [ 0.035807] No memory allocated for crashlog Sun May 12 00:11:52 2019 kern.info kernel: [ 0.039429] squashfs: version 4.0 (2009/01/31) Phillip Lougher Sun May 12 00:11:52 2019 kern.info kernel: [ 0.039442] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. Sun May 12 00:11:52 2019 kern.info kernel: [ 0.040201] io scheduler noop registered Sun May 12 00:11:52 2019 kern.info kernel: [ 0.040211] io scheduler deadline registered (default) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041395] PCI host bridge /soc/pcie@3500000 ranges: Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041416] IO 0x4800010000..0x480001ffff -> 0x00000000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041428] MEM 0x4840000000..0x487fffffff -> 0x40000000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041565] layerscape-pcie 3500000.pcie: PCI host bridge to bus 0000:00 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041576] pci_bus 0000:00: root bus resource [bus 00-ff] Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041585] pci_bus 0000:00: root bus resource [io 0x0000-0xffff] Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041596] pci_bus 0000:00: root bus resource [mem 0x4840000000-0x487fffffff] (bus address [0x40000000-0x7fffffff]) Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.041619] pci 0000:00:00.0: [1957:8080] type 01 class 0x060400 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.041649] pci 0000:00:00.0: reg 0x38: [mem 0x4840000000-0x48400007ff pref] Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.041680] pci 0000:00:00.0: supports D1 D2 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.041686] pci 0000:00:00.0: PME# supported from D0 D1 D2 D3hot Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041810] PCI: bus0: Fast back to back transfers disabled Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041876] PCI: bus1: Fast back to back transfers enabled Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041931] pci 0000:00:00.0: BAR 6: assigned [mem 0x4840000000-0x48400007ff pref] Sun May 12 00:11:52 2019 kern.info kernel: [ 0.041941] pci 0000:00:00.0: PCI bridge to [bus 01] Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.042113] aer 0000:00:00.0:pcie02: service driver aer loaded Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042176] PCI host bridge /soc/pcie@3600000 ranges: Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042191] IO 0x5000010000..0x500001ffff -> 0x00000000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042200] MEM 0x5040000000..0x507fffffff -> 0x40000000 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042299] layerscape-pcie 3600000.pcie: PCI host bridge to bus 0001:00 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042308] pci_bus 0001:00: root bus resource [bus 00-ff] Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042318] pci_bus 0001:00: root bus resource [io 0x10000-0x1ffff] (bus address [0x0000-0xffff]) Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042329] pci_bus 0001:00: root bus resource [mem 0x5040000000-0x507fffffff] (bus address [0x40000000-0x7fffffff]) Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.042346] pci 0001:00:00.0: [1957:8080] type 01 class 0x060400 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.042371] pci 0001:00:00.0: reg 0x38: [mem 0x5040000000-0x50400007ff pref] Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.042394] pci 0001:00:00.0: supports D1 D2 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.042401] pci 0001:00:00.0: PME# supported from D0 D1 D2 D3hot Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042522] PCI: bus0: Fast back to back transfers disabled Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042595] PCI: bus1: Fast back to back transfers enabled Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042639] pci 0001:00:00.0: BAR 6: assigned [mem 0x5040000000-0x50400007ff pref] Sun May 12 00:11:52 2019 kern.info kernel: [ 0.042648] pci 0001:00:00.0: PCI bridge to [bus 01] Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.042809] aer 0001:00:00.0:pcie02: service driver aer loaded Sun May 12 00:11:52 2019 kern.info kernel: [ 0.043050] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled Sun May 12 00:11:52 2019 kern.info kernel: [ 0.043781] console [ttyS0] disabled Sun May 12 00:11:52 2019 kern.info kernel: [ 0.043804] 21c0500.serial: ttyS0 at MMIO 0x21c0500 (irq = 32, base_baud = 18750000) is a 16550A Sun May 12 00:11:52 2019 kern.info kernel: [ 0.800558] console [ttyS0] enabled Sun May 12 00:11:52 2019 kern.info kernel: [ 0.804270] 21c0600.serial: ttyS1 at MMIO 0x21c0600 (irq = 32, base_baud = 18750000) is a 16550A Sun May 12 00:11:52 2019 kern.warn kernel: [ 0.813235] of_serial: probe of 21d0500.serial failed with error -28 Sun May 12 00:11:52 2019 kern.warn kernel: [ 0.819663] of_serial: probe of 21d0600.serial failed with error -28 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.829749] loop: module loaded Sun May 12 00:11:52 2019 kern.info kernel: [ 0.834318] 60000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x00aa55 Chip ID 0x00aa55 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.844361] 60000000.nor: Found an alias at 0x2000000 for the chip at 0x0 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.844375] 60000000.nor: Found an alias at 0x4000000 for the chip at 0x0 Sun May 12 00:11:52 2019 kern.debug kernel: [ 0.844388] 60000000.nor: Found an alias at 0x6000000 for the chip at 0x0 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.844396] Amd/Fujitsu Extended Query Table at 0x0040 Sun May 12 00:11:52 2019 kern.info kernel: [ 0.849567] Amd/Fujitsu Extended Query version 1.5. Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.854634] number of CFI chips: 1 Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.859075] Creating 10 MTD partitions on "60000000.nor": Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.864494] 0x000000100000-0x000000200000 : "boot" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.869817] 0x000001200000-0x000001600000 : "linux" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.875185] 0x000001600000-0x000001f00000 : "rootfs" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.880632] mtd: device 3 (rootfs) set to be root filesystem Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.886323] 1 squashfs-split partitions found on MTD device rootfs Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.892522] 0x000001b00000-0x000001f00000 : "rootfs_data" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.898396] 0x000000400000-0x000001180000 : "linux_backup" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.904376] 0x000001f00000-0x000001f20000 : "priv_data1" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.910178] 0x000001f20000-0x000001f40000 : "priv_data2" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.915989] 0x000001f40000-0x000002000000 : "conf_save" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.921737] 0x000000200000-0x000000300000 : "boot_env" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.927380] 0x000001180000-0x000001f00000 : "linux_current" Sun May 12 00:11:52 2019 kern.notice kernel: [ 0.933467] 0x000000880000-0x000001180000 : "rootfs_backup" Sun May 12 00:11:52 2019 kern.info kernel: [ 0.940767] libphy: Fixed MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 0.945672] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.556474] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.563065] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.568117] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.573163] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.578208] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.583257] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.588303] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.593352] libphy: Freescale XGMAC MDIO Bus: probed Sun May 12 00:11:52 2019 kern.crit kernel: [ 1.613817] Freescale FM module, FMD API version 21.1.0 Sun May 12 00:11:52 2019 kern.crit kernel: [ 1.622262] Freescale FM Ports module Sun May 12 00:11:52 2019 kern.info kernel: [ 1.625943] fsl_mac: fsl_mac: FSL FMan MAC API based driver Sun May 12 00:11:52 2019 kern.info kernel: [ 1.631900] fsl_mac 1ae2000.ethernet: FMan MEMAC Sun May 12 00:11:52 2019 kern.info kernel: [ 1.636542] fsl_mac 1ae2000.ethernet: FMan MAC address: 28:76:10:13:69:f9 Sun May 12 00:11:52 2019 kern.info kernel: [ 1.643528] fsl_mac 1af0000.ethernet: FMan MEMAC Sun May 12 00:11:52 2019 kern.info kernel: [ 1.648166] fsl_mac 1af0000.ethernet: FMan MAC address: 28:76:10:13:69:f8 Sun May 12 00:11:52 2019 kern.info kernel: [ 1.655098] fsl_dpa: FSL DPAA Ethernet driver Sun May 12 00:11:52 2019 kern.info kernel: [ 1.661627] fsl_dpa: fsl_dpa: Probed interface eth0 Sun May 12 00:11:52 2019 kern.info kernel: [ 1.667986] fsl_dpa: fsl_dpa: Probed interface eth1 Sun May 12 00:11:52 2019 kern.info kernel: [ 1.672944] i2c /dev entries driver Sun May 12 00:11:52 2019 kern.info kernel: [ 1.677764] Freescale USDPAA process driver Sun May 12 00:11:52 2019 kern.warn kernel: [ 1.681958] fsl-usdpaa: no region found Sun May 12 00:11:52 2019 kern.info kernel: [ 1.685806] Freescale USDPAA process IRQ driver Sun May 12 00:11:52 2019 kern.info kernel: [ 1.690590] NET: Registered protocol family 17 Sun May 12 00:11:52 2019 kern.info kernel: [ 1.695084] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. Sun May 12 00:11:52 2019 kern.info kernel: [ 1.707738] 8021q: 802.1Q VLAN Support v1.8 Sun May 12 00:11:52 2019 kern.info kernel: [ 1.711957] tipc: Activated (version 2.0.0) Sun May 12 00:11:52 2019 kern.info kernel: [ 1.716179] NET: Registered protocol family 30 Sun May 12 00:11:52 2019 kern.info kernel: [ 1.720710] tipc: Started in single node mode Sun May 12 00:11:52 2019 kern.notice kernel: [ 1.725138] Registering SWP/SWPB emulation handler Sun May 12 00:11:52 2019 kern.info kernel: [ 1.730411] hctosys: unable to open rtc device (rtc0) Sun May 12 00:11:52 2019 kern.warn kernel: [ 1.736120] fdt: not creating '/sys/firmware/fdt': CRC check failed Sun May 12 00:11:52 2019 kern.info kernel: [ 1.745204] VFS: Mounted root (squashfs filesystem) readonly on device 31:3. Sun May 12 00:11:52 2019 kern.info kernel: [ 1.754143] devtmpfs: mounted Sun May 12 00:11:52 2019 kern.info kernel: [ 1.757373] Freeing unused kernel memory: 252K (80481000 - 804c0000) Sun May 12 00:11:52 2019 user.info kernel: [ 2.138375] init: Console is alive Sun May 12 00:11:52 2019 user.info kernel: [ 2.141890] init: - watchdog - Sun May 12 00:11:52 2019 user.info kernel: [ 2.178179] kmodloader: loading kernel modules from /etc/modules-boot.d/* Sun May 12 00:11:52 2019 kern.info kernel: [ 2.204354] Button Hotplug driver version 0.4.1 Sun May 12 00:11:52 2019 user.info kernel: [ 2.210546] kmodloader: done loading kernel modules from /etc/modules-boot.d/* Sun May 12 00:11:52 2019 user.info kernel: [ 2.221636] init: - preinit - Sun May 12 00:11:52 2019 kern.notice kernel: [ 2.587502] random: jshn: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 kern.notice kernel: [ 2.602722] random: jshn: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 kern.notice kernel: [ 4.820713] jffs2: notice: (670) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. Sun May 12 00:11:52 2019 user.info kernel: [ 4.836653] mount_root: switching to jffs2 overlay Sun May 12 00:11:52 2019 user.warn kernel: [ 4.847057] urandom-seed: Seeding with /etc/urandom.seed Sun May 12 00:11:52 2019 user.info kernel: [ 4.903919] procd: - early - Sun May 12 00:11:52 2019 user.info kernel: [ 4.906837] procd: - watchdog - Sun May 12 00:11:52 2019 user.info kernel: [ 5.456594] procd: - watchdog - Sun May 12 00:11:52 2019 user.info kernel: [ 5.459844] procd: - ubus - Sun May 12 00:11:52 2019 kern.notice kernel: [ 5.512979] random: ubusd: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 kern.notice kernel: [ 5.521959] random: ubusd: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 kern.notice kernel: [ 5.530870] random: ubusd: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 kern.notice kernel: [ 5.539828] random: ubusd: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 kern.notice kernel: [ 5.548734] random: ubusd: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 kern.notice kernel: [ 5.557676] random: ubusd: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 kern.notice kernel: [ 5.566617] random: ubusd: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 user.info kernel: [ 5.575601] procd: - init - Sun May 12 00:11:52 2019 kern.notice kernel: [ 5.700718] jffs2: notice: (800) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. Sun May 12 00:11:52 2019 user.info kernel: [ 5.727266] kmodloader: loading kernel modules from /etc/modules.d/* Sun May 12 00:11:52 2019 kern.info kernel: [ 5.735422] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Sun May 12 00:11:52 2019 user.info kernel: [ 5.743994] kmodloader: done loading kernel modules from /etc/modules.d/* Sun May 12 00:11:52 2019 kern.notice kernel: [ 6.900910] random: jshn: uninitialized urandom read (4 bytes read, 0 bits of entropy available) Sun May 12 00:11:52 2019 daemon.info mini_snmpd[972]: started, listening on port 161/udp and 161/tcp Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: can't get info No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: can't get info No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: can't get info No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: can't get info No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: /usr/sbin/mgmt_vlan: line 8: can't create /sys/class/net/br-wan/bridge/mgmt_vlan_id: nonexistent directory Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: Command failed: Not found Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: Command failed: Not found Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: Command failed: Not found Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: can't get info No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: can't get info No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: can't get info No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S20network: can't get info No such device Sun May 12 00:11:53 2019 user.notice : Added device handler type: tunnel Sun May 12 00:11:53 2019 user.notice : Added device handler type: Network device Sun May 12 00:11:53 2019 user.notice : Added device handler type: bridge Sun May 12 00:11:53 2019 user.notice : Added device handler type: veth Sun May 12 00:11:53 2019 user.notice : Added device handler type: macvlan Sun May 12 00:11:53 2019 user.notice : Added device handler type: 8021ad Sun May 12 00:11:53 2019 user.notice : Added device handler type: 8021q Sun May 12 00:11:53 2019 daemon.warn netifd: You have delegated IPv6-prefixes but haven't assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces? Sun May 12 00:11:53 2019 kern.info kernel: [ 8.253881] device eth1 entered promiscuous mode Sun May 12 00:11:53 2019 kern.info kernel: [ 8.259966] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:11:53 2019 kern.info kernel: [ 8.265434] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:11:53 2019 daemon.notice netifd: Interface 'wan' is enabled Sun May 12 00:11:53 2019 daemon.notice netifd: Interface 'loopback' is enabled Sun May 12 00:11:53 2019 daemon.notice netifd: Interface 'loopback' is setting up now Sun May 12 00:11:53 2019 daemon.notice netifd: Interface 'loopback' is now up Sun May 12 00:11:53 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:11:53 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:11:53 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:11:53 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:11:53 2019 daemon.notice netifd: Network device 'lo' link is up Sun May 12 00:11:53 2019 daemon.notice netifd: Interface 'loopback' has link connectivity Sun May 12 00:11:53 2019 authpriv.info dropbear[1231]: Not backgrounding Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: ifconfig: SIOCGIFFLAGS: No such device Sun May 12 00:11:53 2019 daemon.notice netifd: wan (1271): udhcpc: started, v1.26.2 Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: Cannot get current device settings: No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: not setting autoneg Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: ifconfig: SIOCGIFFLAGS: No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: Cannot get current device settings: No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: not setting autoneg Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: ifconfig: SIOCGIFFLAGS: No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: Cannot get current device settings: No such device Sun May 12 00:11:53 2019 daemon.notice procd: /etc/rc.d/S50ethernet: not setting autoneg Sun May 12 00:11:53 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:11:53 2019 daemon.notice netifd: wan (1271): udhcpc: sending discover Sun May 12 00:11:54 2019 daemon.notice netifd: wan (1271): udhcpc: performing DHCP renew Sun May 12 00:11:54 2019 daemon.notice netifd: wan (1271): udhcpc: sending discover Sun May 12 00:11:54 2019 daemon.notice procd: /etc/rc.d/S60quagga: quagga.init: Starting watchquagga ... Must specify one or more daemons to monitor. Sun May 12 00:11:54 2019 daemon.notice procd: /etc/rc.d/S60quagga: Try `watchquagga --help' for more information. Sun May 12 00:11:54 2019 daemon.notice procd: /etc/rc.d/S60quagga: failed. Sun May 12 00:11:54 2019 kern.info kernel: [ 8.694410] bonding: bond1 is being created... Sun May 12 00:11:54 2019 kern.notice kernel: [ 8.736572] jffs2: Write of 47 bytes at 0x0013497c failed. returned -5, retlen 46 Sun May 12 00:11:54 2019 user.err : an error occurred updating password for root Sun May 12 00:11:54 2019 kern.notice kernel: [ 8.745742] jffs2: Write of 47 bytes at 0x001349ac failed. returned -5, retlen 46 Sun May 12 00:11:54 2019 daemon.notice procd: /etc/rc.d/S91users: chpasswd: can't create '/etc/shadow+': I/O error Sun May 12 00:11:54 2019 daemon.notice procd: /etc/rc.d/S91users: chpasswd: an error occurred updating password for root Sun May 12 00:11:54 2019 daemon.notice procd: /etc/rc.d/S95done: /etc/rc.common: line 5: can't create /sys/class/leds/usb3pwr/brightness: nonexistent directory Sun May 12 00:11:54 2019 daemon.notice procd: /etc/rc.d/S95done: /sbin/phystatus: local: line 22: not in a function Sun May 12 00:11:54 2019 daemon.err lighttpd[1369]: (server.c.1423) server started (lighttpd/1.4.49) Sun May 12 00:11:54 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:11:54 2019 kern.info kernel: [ 9.263599] br-wan: port 1(eth1) entered disabled state Sun May 12 00:11:54 2019 kern.warn kernel: [ 9.445568] mtdblock: erase of region [0x280000, 0x80000] on "60000000.nor" failed Sun May 12 00:11:54 2019 daemon.info procd: - init complete - Sun May 12 00:11:55 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:11:55 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:11:55 2019 daemon.notice netifd: wan (1271): udhcpc: received SIGTERM Sun May 12 00:11:56 2019 kern.info kernel: [ 11.237778] device eth0.101 entered promiscuous mode Sun May 12 00:11:56 2019 kern.info kernel: [ 11.242772] device eth0 entered promiscuous mode Sun May 12 00:11:56 2019 kern.info kernel: [ 11.247485] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:11:56 2019 kern.info kernel: [ 11.253269] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:11:56 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:11:56 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:11:56 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:11:56 2019 daemon.notice netifd: wan (1872): udhcpc: started, v1.26.2 Sun May 12 00:11:56 2019 kern.info kernel: [ 11.327833] device eth0.102 entered promiscuous mode Sun May 12 00:11:56 2019 kern.info kernel: [ 11.332894] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:11:56 2019 kern.info kernel: [ 11.338705] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:11:56 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:11:56 2019 kern.info kernel: [ 11.408496] device eth0.103 entered promiscuous mode Sun May 12 00:11:56 2019 kern.info kernel: [ 11.413549] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:11:56 2019 kern.info kernel: [ 11.419346] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:11:56 2019 daemon.notice netifd: wan (1872): udhcpc: sending discover Sun May 12 00:11:56 2019 kern.info kernel: [ 11.475801] device eth0.104 entered promiscuous mode Sun May 12 00:11:56 2019 kern.info kernel: [ 11.480850] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:11:56 2019 kern.info kernel: [ 11.486628] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:11:57 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:11:57 2019 kern.info kernel: [ 11.991407] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:11:57 2019 kern.info kernel: [ 11.996839] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:11:58 2019 kern.info kernel: [ 12.987897] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:11:58 2019 kern.info kernel: [ 13.011803] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:11:58 2019 kern.info kernel: [ 13.036180] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:11:58 2019 kern.info kernel: [ 13.059838] device eth0 left promiscuous mode Sun May 12 00:11:58 2019 kern.info kernel: [ 13.064260] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:11:58 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:11:58 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:11:58 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:11:58 2019 kern.info kernel: [ 13.536379] br-wan: port 1(eth1) entered disabled state Sun May 12 00:11:58 2019 daemon.notice netifd: wan (1872): udhcpc: read error: Network is down, reopening socket Sun May 12 00:11:58 2019 daemon.notice netifd: wan (1872): udhcpc: received SIGTERM Sun May 12 00:12:01 2019 kern.notice kernel: [ 16.578350] jffs2: Write of 70 bytes at 0x001349dc failed. returned -5, retlen 68 Sun May 12 00:12:01 2019 kern.notice kernel: [ 16.587189] jffs2: Write of 70 bytes at 0x00134a24 failed. returned -5, retlen 68 Sun May 12 00:12:02 2019 daemon.warn trilld[2258]: rtnetlink is supported: using new api Sun May 12 00:12:03 2019 kern.info kernel: [ 17.689860] device eth0 entered promiscuous mode Sun May 12 00:12:03 2019 kern.info kernel: [ 17.694720] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:12:03 2019 kern.info kernel: [ 17.700499] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:12:03 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:12:03 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:12:03 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:12:03 2019 kern.info kernel: [ 17.707308] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:12:03 2019 kern.info kernel: [ 17.713097] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:12:03 2019 kern.info kernel: [ 17.719186] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:12:03 2019 kern.info kernel: [ 17.724984] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:12:03 2019 kern.info kernel: [ 17.731072] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:12:03 2019 kern.info kernel: [ 17.736869] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.notice netifd: wan (2338): udhcpc: started, v1.26.2 Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:03 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:12:03 2019 daemon.notice netifd: wan (2338): udhcpc: sending discover Sun May 12 00:12:04 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:04 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:04 2019 daemon.warn trilld[2260]: isis_recv_packet_bcast(): ifname eth0.101, fd 10, bytesread -1, recvfrom(): Network is down Sun May 12 00:12:04 2019 kern.info kernel: [ 19.267579] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:12:04 2019 daemon.warn trilld[2260]: isis_recv_packet_bcast(): ifname eth0.102, fd 13, bytesread -1, recvfrom(): Network is down Sun May 12 00:12:04 2019 kern.info kernel: [ 19.290177] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:12:04 2019 daemon.warn trilld[2260]: isis_recv_packet_bcast(): ifname eth0.103, fd 14, bytesread -1, recvfrom(): Network is down Sun May 12 00:12:04 2019 kern.info kernel: [ 19.313207] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:12:04 2019 daemon.warn trilld[2260]: isis_recv_packet_bcast(): ifname eth0.104, fd 15, bytesread -1, recvfrom(): Network is down Sun May 12 00:12:04 2019 kern.info kernel: [ 19.337957] device eth0 left promiscuous mode Sun May 12 00:12:04 2019 kern.info kernel: [ 19.342383] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:12:05 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:12:05 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:12:05 2019 daemon.notice netifd: wan (2338): udhcpc: received SIGTERM Sun May 12 00:12:15 2019 daemon.notice watchquagga[2916]: watchquagga 0.99.22.4 watching [zebra trilld], mode [global restart] Sun May 12 00:12:15 2019 daemon.notice watchquagga[2916]: zebra state -> up : connect succeeded Sun May 12 00:12:15 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:12:15 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:15 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:12:15 2019 kern.info kernel: [ 30.460624] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:12:15 2019 kern.info kernel: [ 30.466079] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:12:15 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:15 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:15 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:12:15 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:12:15 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:12:15 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:15 2019 daemon.notice netifd: wan (2925): udhcpc: started, v1.26.2 Sun May 12 00:12:15 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:12:15 2019 daemon.notice netifd: wan (2925): udhcpc: sending discover Sun May 12 00:12:17 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:12:17 2019 kern.info kernel: [ 32.472558] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:12:18 2019 daemon.notice netifd: wan (2925): udhcpc: sending discover Sun May 12 00:12:21 2019 daemon.notice netifd: wan (2925): udhcpc: sending discover Sun May 12 00:12:24 2019 kern.warn kernel: [ 39.565764] RTNETLINK:TRILL Ready! Sun May 12 00:13:21 2019 kern.notice kernel: [ 96.204901] random: nonblocking pool is initialized Sun May 12 00:18:10 2019 kern.info kernel: [ 385.166142] device eth0 entered promiscuous mode Sun May 12 00:18:10 2019 kern.info kernel: [ 385.171099] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:10 2019 kern.info kernel: [ 385.176889] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 kern.info kernel: [ 385.218164] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:18:10 2019 kern.info kernel: [ 385.223955] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 kern.warn kernel: [ 385.235774] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:10 2019 daemon.warn trilld[2260]: circuit already connected Sun May 12 00:18:10 2019 kern.warn kernel: [ 385.523679] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:10 2019 kern.warn kernel: [ 385.569704] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:11 2019 kern.warn kernel: [ 385.857705] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:11 2019 kern.warn kernel: [ 385.903701] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:11 2019 kern.warn kernel: [ 386.191703] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:11 2019 daemon.crit trilld[2260]: Assertion `isis_find_vertex (spftree->paths, id, vtype) == ((void*)0)' failed in file isis_spf.c, line 529, function isis_spf_add2tent Sun May 12 00:18:11 2019 daemon.crit trilld[2260]: No backtrace available on this platform. Sun May 12 00:18:11 2019 daemon.err watchquagga[2916]: trilld state -> down : read returned EOF Sun May 12 00:18:11 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:18:11 2019 daemon.err watchquagga[2916]: trilld state -> down : unexpected read error: Connection reset by peer Sun May 12 00:18:12 2019 kern.info kernel: [ 387.180554] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:12 2019 kern.info kernel: [ 387.224552] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:18:16 2019 daemon.err watchquagga[2916]: Forked background command [pid 12806]: /etc/init.d/quagga restart Sun May 12 00:18:16 2019 kern.info kernel: [ 391.290797] device eth0.101 left promiscuous mode Sun May 12 00:18:16 2019 kern.info kernel: [ 391.295587] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:18:16 2019 kern.info kernel: [ 391.318185] device eth0.102 left promiscuous mode Sun May 12 00:18:16 2019 kern.info kernel: [ 391.322970] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:18:16 2019 kern.info kernel: [ 391.342204] device eth0.103 left promiscuous mode Sun May 12 00:18:16 2019 kern.info kernel: [ 391.346968] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:18:16 2019 kern.info kernel: [ 391.365991] device eth0.104 left promiscuous mode Sun May 12 00:18:16 2019 kern.info kernel: [ 391.370778] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:18:16 2019 kern.info kernel: [ 391.380944] device eth0 left promiscuous mode Sun May 12 00:18:16 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:18:16 2019 kern.info kernel: [ 391.420626] br-wan: port 1(eth1) entered disabled state Sun May 12 00:18:16 2019 kern.info kernel: [ 391.476566] device eth0 entered promiscuous mode Sun May 12 00:18:17 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:18:17 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:18:17 2019 daemon.notice netifd: wan (2925): udhcpc: received SIGTERM Sun May 12 00:18:18 2019 kern.info kernel: [ 393.531978] device eth0.101 entered promiscuous mode Sun May 12 00:18:18 2019 kern.info kernel: [ 393.537079] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:18:18 2019 kern.info kernel: [ 393.542907] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:18:18 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:18:18 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:18:18 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:18:18 2019 daemon.notice netifd: wan (13086): udhcpc: started, v1.26.2 Sun May 12 00:18:18 2019 kern.info kernel: [ 393.593332] device eth0.102 entered promiscuous mode Sun May 12 00:18:18 2019 kern.info kernel: [ 393.598399] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:18 2019 kern.info kernel: [ 393.604237] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:19 2019 kern.info kernel: [ 393.647888] device eth0.103 entered promiscuous mode Sun May 12 00:18:19 2019 kern.info kernel: [ 393.652986] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:18:19 2019 kern.info kernel: [ 393.658785] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:18:19 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:18:19 2019 kern.info kernel: [ 393.701393] device eth0.104 entered promiscuous mode Sun May 12 00:18:19 2019 kern.info kernel: [ 393.706504] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:18:19 2019 kern.info kernel: [ 393.712300] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:18:19 2019 daemon.notice netifd: wan (13086): udhcpc: sending discover Sun May 12 00:18:20 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:18:20 2019 kern.info kernel: [ 394.749715] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:18:20 2019 kern.info kernel: [ 394.755158] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:18:20 2019 kern.info kernel: [ 395.544557] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:18:20 2019 kern.info kernel: [ 395.608559] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:20 2019 kern.info kernel: [ 395.616486] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:18:21 2019 kern.info kernel: [ 395.641093] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:18:21 2019 kern.info kernel: [ 395.664562] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:18:21 2019 kern.info kernel: [ 395.670455] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:18:21 2019 kern.info kernel: [ 395.693157] device eth0 left promiscuous mode Sun May 12 00:18:21 2019 kern.info kernel: [ 395.697589] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:18:21 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:18:21 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:18:21 2019 kern.info kernel: [ 395.768707] br-wan: port 1(eth1) entered disabled state Sun May 12 00:18:21 2019 daemon.notice netifd: wan (13086): udhcpc: read error: Network is down, reopening socket Sun May 12 00:18:21 2019 daemon.notice netifd: wan (13086): udhcpc: received SIGTERM Sun May 12 00:18:21 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:18:23 2019 kern.info kernel: [ 397.752490] device eth0 entered promiscuous mode Sun May 12 00:18:24 2019 kern.notice kernel: [ 398.810030] jffs2: Write of 70 bytes at 0x00134a6c failed. returned -5, retlen 68 Sun May 12 00:18:24 2019 kern.notice kernel: [ 398.818875] jffs2: Write of 70 bytes at 0x00134ab4 failed. returned -5, retlen 68 Sun May 12 00:18:24 2019 daemon.warn trilld[13401]: rtnetlink is supported: using new api Sun May 12 00:18:24 2019 kern.info kernel: [ 398.856084] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:18:24 2019 kern.info kernel: [ 398.861897] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:18:24 2019 kern.info kernel: [ 398.867676] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:24 2019 kern.info kernel: [ 398.873453] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:24 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:18:24 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:18:24 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:18:24 2019 kern.warn kernel: [ 398.882791] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:24 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:24 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:24 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:24 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:24 2019 daemon.notice netifd: wan (13418): udhcpc: started, v1.26.2 Sun May 12 00:18:24 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:18:24 2019 daemon.notice netifd: wan (13418): udhcpc: sending discover Sun May 12 00:18:25 2019 kern.info kernel: [ 399.883016] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:18:25 2019 kern.info kernel: [ 399.888810] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:18:25 2019 kern.info kernel: [ 399.897310] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:18:25 2019 kern.info kernel: [ 399.903091] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:18:25 2019 kern.info kernel: [ 399.911190] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:18:25 2019 kern.info kernel: [ 399.916621] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:25 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:26 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:26 2019 kern.info kernel: [ 400.864558] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:18:26 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:26 2019 kern.info kernel: [ 400.876553] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:18:26 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:18:27 2019 kern.warn kernel: [ 401.812727] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:27 2019 kern.warn kernel: [ 401.834708] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:27 2019 kern.warn kernel: [ 401.847725] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:27 2019 kern.warn kernel: [ 401.855318] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:27 2019 kern.info kernel: [ 401.892565] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:18:27 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:27 2019 daemon.warn trilld[13404]: isis_recv_packet_bcast(): ifname eth0.101, fd 16, bytesread -1, recvfrom(): Network is down Sun May 12 00:18:27 2019 kern.info kernel: [ 401.900537] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:18:27 2019 kern.info kernel: [ 401.906556] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:18:27 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:27 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:27 2019 kern.info kernel: [ 401.920559] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:18:27 2019 daemon.warn trilld[13404]: isis_recv_packet_bcast(): ifname eth0.103, fd 17, bytesread -1, recvfrom(): Network is down Sun May 12 00:18:27 2019 kern.info kernel: [ 401.945332] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:18:27 2019 daemon.notice netifd: wan (13418): udhcpc: sending discover Sun May 12 00:18:28 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:18:28 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:28 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:28 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:28 2019 kern.info kernel: [ 402.908825] br-wan: port 1(eth1) entered disabled state Sun May 12 00:18:29 2019 kern.warn kernel: [ 403.849759] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:29 2019 kern.warn kernel: [ 403.857359] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:29 2019 kern.warn kernel: [ 404.547759] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:29 2019 kern.warn kernel: [ 404.594708] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:30 2019 daemon.notice netifd: wan (13418): udhcpc: sending discover Sun May 12 00:18:31 2019 kern.warn kernel: [ 405.851710] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:32 2019 kern.warn kernel: [ 407.291872] net_ratelimit: 1 callbacks suppressed Sun May 12 00:18:32 2019 kern.warn kernel: [ 407.296604] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:32 2019 kern.warn kernel: [ 407.498714] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:33 2019 kern.warn kernel: [ 407.853790] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:33 2019 kern.warn kernel: [ 407.861390] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:33 2019 kern.warn kernel: [ 407.868990] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:33 2019 kern.warn kernel: [ 407.876588] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:35 2019 kern.warn kernel: [ 409.855746] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:35 2019 kern.warn kernel: [ 409.863351] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:35 2019 kern.warn kernel: [ 409.870952] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:35 2019 kern.warn kernel: [ 409.878547] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:36 2019 daemon.warn watchquagga[2916]: Warning: restart all child process 12806 still running after 20 seconds, sending signal 15 Sun May 12 00:18:36 2019 daemon.warn watchquagga[2916]: restart all process 12806 terminated due to signal 15 Sun May 12 00:18:38 2019 kern.warn kernel: [ 412.679746] net_ratelimit: 12 callbacks suppressed Sun May 12 00:18:38 2019 kern.warn kernel: [ 412.684564] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:38 2019 kern.warn kernel: [ 412.875730] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:38 2019 kern.warn kernel: [ 413.013710] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:38 2019 kern.warn kernel: [ 413.209701] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:38 2019 kern.warn kernel: [ 413.347703] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:38 2019 kern.warn kernel: [ 413.543702] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:39 2019 kern.warn kernel: [ 413.681705] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:39 2019 kern.warn kernel: [ 413.859724] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:39 2019 kern.warn kernel: [ 413.867316] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:39 2019 kern.warn kernel: [ 413.874913] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:42 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:18:42 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:42 2019 kern.info kernel: [ 416.857540] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:18:42 2019 kern.info kernel: [ 416.863001] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:18:42 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:42 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:42 2019 daemon.warn trilld[13404]: circuit already connected Sun May 12 00:18:43 2019 kern.warn kernel: [ 417.885710] net_ratelimit: 32 callbacks suppressed Sun May 12 00:18:43 2019 kern.warn kernel: [ 417.890522] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:43 2019 kern.warn kernel: [ 418.023708] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:43 2019 kern.warn kernel: [ 418.219704] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:43 2019 kern.warn kernel: [ 418.357701] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:43 2019 kern.warn kernel: [ 418.553814] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:18:44 2019 kern.warn kernel: [ 418.691806] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:18:44 2019 daemon.crit trilld[13404]: Assertion `isis_find_vertex (spftree->paths, id, vtype) == ((void*)0)' failed in file isis_spf.c, line 529, function isis_spf_add2tent Sun May 12 00:18:44 2019 daemon.crit trilld[13404]: No backtrace available on this platform. Sun May 12 00:18:44 2019 daemon.err watchquagga[2916]: trilld state -> down : read returned EOF Sun May 12 00:18:44 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:18:44 2019 daemon.err watchquagga[2916]: trilld state -> down : unexpected read error: Connection reset by peer Sun May 12 00:18:44 2019 kern.info kernel: [ 418.864556] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:19:39 2019 daemon.err watchquagga[2916]: Forked background command [pid 15598]: /etc/init.d/quagga restart Sun May 12 00:19:39 2019 kern.info kernel: [ 473.989512] device eth0.101 left promiscuous mode Sun May 12 00:19:39 2019 kern.info kernel: [ 473.994298] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:19:39 2019 kern.info kernel: [ 474.015319] device eth0.102 left promiscuous mode Sun May 12 00:19:39 2019 kern.info kernel: [ 474.020098] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:19:39 2019 kern.info kernel: [ 474.041249] device eth0.103 left promiscuous mode Sun May 12 00:19:39 2019 kern.info kernel: [ 474.046011] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:19:39 2019 kern.info kernel: [ 474.067188] device eth0.104 left promiscuous mode Sun May 12 00:19:39 2019 kern.info kernel: [ 474.071973] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:19:39 2019 kern.info kernel: [ 474.085008] device eth0 left promiscuous mode Sun May 12 00:19:39 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:19:39 2019 kern.info kernel: [ 474.119607] br-wan: port 1(eth1) entered disabled state Sun May 12 00:19:39 2019 kern.info kernel: [ 474.160542] device eth0 entered promiscuous mode Sun May 12 00:19:40 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:19:40 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:19:40 2019 daemon.notice netifd: wan (13418): udhcpc: received SIGTERM Sun May 12 00:19:41 2019 kern.info kernel: [ 476.204349] device eth0.101 entered promiscuous mode Sun May 12 00:19:41 2019 kern.info kernel: [ 476.209409] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:19:41 2019 kern.info kernel: [ 476.215200] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:19:41 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:19:41 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:19:41 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:19:41 2019 daemon.notice netifd: wan (15822): udhcpc: started, v1.26.2 Sun May 12 00:19:41 2019 kern.info kernel: [ 476.257824] device eth0.102 entered promiscuous mode Sun May 12 00:19:41 2019 kern.info kernel: [ 476.262884] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:19:41 2019 kern.info kernel: [ 476.268677] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:19:41 2019 kern.info kernel: [ 476.310856] device eth0.103 entered promiscuous mode Sun May 12 00:19:41 2019 kern.info kernel: [ 476.315920] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:19:41 2019 kern.info kernel: [ 476.321716] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:19:41 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:19:41 2019 kern.info kernel: [ 476.365602] device eth0.104 entered promiscuous mode Sun May 12 00:19:41 2019 kern.info kernel: [ 476.370680] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:19:41 2019 kern.info kernel: [ 476.376478] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:19:41 2019 daemon.notice netifd: wan (15822): udhcpc: sending discover Sun May 12 00:19:42 2019 kern.info kernel: [ 476.744826] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:19:42 2019 kern.info kernel: [ 476.768878] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:19:42 2019 kern.info kernel: [ 476.793755] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:19:42 2019 kern.info kernel: [ 476.817135] device eth0 left promiscuous mode Sun May 12 00:19:42 2019 kern.info kernel: [ 476.821569] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:19:42 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:19:42 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:19:42 2019 daemon.notice netifd: wan (15822): udhcpc: received SIGTERM Sun May 12 00:19:42 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:19:42 2019 kern.info kernel: [ 477.409162] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:19:42 2019 kern.info kernel: [ 477.414612] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:19:42 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:19:42 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:19:42 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:19:42 2019 daemon.notice netifd: wan (16010): udhcpc: started, v1.26.2 Sun May 12 00:19:42 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:19:42 2019 daemon.notice netifd: wan (16010): udhcpc: sending discover Sun May 12 00:19:43 2019 daemon.notice netifd: wan (16010): udhcpc: read error: Network is down, reopening socket Sun May 12 00:19:43 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:19:43 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:19:43 2019 kern.info kernel: [ 478.430701] br-wan: port 1(eth1) entered disabled state Sun May 12 00:19:43 2019 daemon.notice netifd: wan (16010): udhcpc: received SIGTERM Sun May 12 00:19:43 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:19:46 2019 kern.info kernel: [ 480.950508] device eth0 entered promiscuous mode Sun May 12 00:19:46 2019 kern.notice kernel: [ 481.472247] jffs2: Write of 70 bytes at 0x00134afc failed. returned -5, retlen 68 Sun May 12 00:19:46 2019 kern.notice kernel: [ 481.481098] jffs2: Write of 70 bytes at 0x00134b44 failed. returned -5, retlen 68 Sun May 12 00:19:46 2019 daemon.warn trilld[16227]: rtnetlink is supported: using new api Sun May 12 00:19:46 2019 kern.info kernel: [ 481.519212] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:19:46 2019 kern.info kernel: [ 481.525025] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:19:46 2019 kern.info kernel: [ 481.530803] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:19:46 2019 kern.info kernel: [ 481.536578] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:19:46 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:19:46 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:19:46 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:19:46 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:46 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:46 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:46 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:46 2019 kern.warn kernel: [ 481.543859] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:46 2019 daemon.notice netifd: wan (16244): udhcpc: started, v1.26.2 Sun May 12 00:19:46 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:19:47 2019 daemon.notice netifd: wan (16244): udhcpc: sending discover Sun May 12 00:19:47 2019 kern.info kernel: [ 482.554270] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:19:47 2019 kern.info kernel: [ 482.560061] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 kern.info kernel: [ 482.567523] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:19:47 2019 kern.info kernel: [ 482.573303] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:19:47 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:19:47 2019 kern.info kernel: [ 482.581576] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:19:47 2019 kern.info kernel: [ 482.587004] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:47 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:48 2019 daemon.warn trilld[16229]: isis_recv_packet_bcast(): ifname eth0.101, fd 16, bytesread -1, recvfrom(): Network is down Sun May 12 00:19:48 2019 kern.info kernel: [ 483.022973] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:19:48 2019 daemon.warn trilld[16229]: isis_recv_packet_bcast(): ifname eth0.103, fd 17, bytesread -1, recvfrom(): Network is down Sun May 12 00:19:48 2019 kern.info kernel: [ 483.064819] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:19:48 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:48 2019 kern.info kernel: [ 483.528558] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:19:48 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:48 2019 kern.info kernel: [ 483.540554] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:19:49 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:19:49 2019 kern.warn kernel: [ 484.443726] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:49 2019 kern.warn kernel: [ 484.461702] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:19:49 2019 kern.warn kernel: [ 484.509721] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:49 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:49 2019 kern.info kernel: [ 484.592554] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:19:50 2019 daemon.notice netifd: wan (16244): udhcpc: sending discover Sun May 12 00:19:50 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:19:50 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:50 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:50 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:19:50 2019 kern.info kernel: [ 485.031809] br-wan: port 1(eth1) entered disabled state Sun May 12 00:19:51 2019 kern.warn kernel: [ 486.511763] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:52 2019 kern.warn kernel: [ 487.248814] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:52 2019 kern.warn kernel: [ 487.325803] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:19:52 2019 kern.warn kernel: [ 487.511743] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:19:53 2019 daemon.notice netifd: wan (16244): udhcpc: sending discover Sun May 12 00:19:53 2019 kern.warn kernel: [ 488.512750] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:54 2019 kern.warn kernel: [ 489.513821] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:19:55 2019 kern.warn kernel: [ 490.115748] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:19:55 2019 kern.warn kernel: [ 490.163745] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:55 2019 kern.warn kernel: [ 490.514727] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:55 2019 kern.warn kernel: [ 490.522320] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:56 2019 kern.warn kernel: [ 491.515806] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:19:56 2019 kern.warn kernel: [ 491.523412] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:19:57 2019 kern.warn kernel: [ 492.516756] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:57 2019 kern.warn kernel: [ 492.524360] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:19:58 2019 kern.warn kernel: [ 492.849758] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:19:59 2019 daemon.warn watchquagga[2916]: Warning: restart all child process 15598 still running after 20 seconds, sending signal 15 Sun May 12 00:19:59 2019 daemon.warn watchquagga[2916]: restart all process 15598 terminated due to signal 15 Sun May 12 00:20:00 2019 kern.warn kernel: [ 495.186707] net_ratelimit: 11 callbacks suppressed Sun May 12 00:20:00 2019 kern.warn kernel: [ 495.191521] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:00 2019 kern.warn kernel: [ 495.519846] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:00 2019 kern.warn kernel: [ 495.527476] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:00 2019 kern.warn kernel: [ 495.535091] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:01 2019 kern.warn kernel: [ 495.790739] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:01 2019 kern.warn kernel: [ 495.853709] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:01 2019 kern.warn kernel: [ 496.124707] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:01 2019 kern.warn kernel: [ 496.187704] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:01 2019 kern.warn kernel: [ 496.458708] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:01 2019 kern.warn kernel: [ 496.520714] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:05 2019 kern.warn kernel: [ 500.524730] net_ratelimit: 30 callbacks suppressed Sun May 12 00:20:05 2019 kern.warn kernel: [ 500.529545] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:05 2019 kern.warn kernel: [ 500.537139] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:05 2019 kern.warn kernel: [ 500.544734] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:05 2019 kern.warn kernel: [ 500.552328] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:06 2019 kern.warn kernel: [ 500.800707] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:06 2019 kern.warn kernel: [ 500.858706] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:06 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:20:06 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:20:06 2019 kern.info kernel: [ 500.998100] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:20:06 2019 kern.info kernel: [ 501.003546] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:20:06 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:20:06 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:20:06 2019 daemon.warn trilld[16229]: circuit already connected Sun May 12 00:20:06 2019 kern.warn kernel: [ 501.134709] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:06 2019 kern.warn kernel: [ 501.192706] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:20:06 2019 kern.warn kernel: [ 501.468704] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:20:06 2019 daemon.crit trilld[16229]: Assertion `isis_find_vertex (spftree->paths, id, vtype) == ((void*)0)' failed in file isis_spf.c, line 529, function isis_spf_add2tent Sun May 12 00:20:06 2019 daemon.crit trilld[16229]: No backtrace available on this platform. Sun May 12 00:20:06 2019 daemon.err watchquagga[2916]: trilld state -> down : read returned EOF Sun May 12 00:20:06 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:20:06 2019 daemon.err watchquagga[2916]: trilld state -> down : unexpected read error: Connection reset by peer Sun May 12 00:20:08 2019 kern.info kernel: [ 503.008558] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:22:01 2019 daemon.err watchquagga[2916]: Forked background command [pid 20065]: /etc/init.d/quagga restart Sun May 12 00:22:02 2019 kern.info kernel: [ 616.655651] device eth0.101 left promiscuous mode Sun May 12 00:22:02 2019 kern.info kernel: [ 616.660430] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:22:02 2019 kern.info kernel: [ 616.678228] device eth0.102 left promiscuous mode Sun May 12 00:22:02 2019 kern.info kernel: [ 616.683008] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:22:02 2019 kern.info kernel: [ 616.702304] device eth0.103 left promiscuous mode Sun May 12 00:22:02 2019 kern.info kernel: [ 616.707066] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:22:02 2019 kern.info kernel: [ 616.726134] device eth0.104 left promiscuous mode Sun May 12 00:22:02 2019 kern.info kernel: [ 616.730916] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:22:02 2019 kern.info kernel: [ 616.740971] device eth0 left promiscuous mode Sun May 12 00:22:02 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:22:02 2019 kern.info kernel: [ 616.775605] br-wan: port 1(eth1) entered disabled state Sun May 12 00:22:02 2019 kern.info kernel: [ 616.816527] device eth0 entered promiscuous mode Sun May 12 00:22:03 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:22:03 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:22:03 2019 daemon.notice netifd: wan (16244): udhcpc: received SIGTERM Sun May 12 00:22:04 2019 kern.info kernel: [ 618.859062] device eth0.101 entered promiscuous mode Sun May 12 00:22:04 2019 kern.info kernel: [ 618.864134] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:22:04 2019 kern.info kernel: [ 618.869929] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:22:04 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:22:04 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:22:04 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:22:04 2019 daemon.notice netifd: wan (20293): udhcpc: started, v1.26.2 Sun May 12 00:22:04 2019 kern.info kernel: [ 618.912969] device eth0.102 entered promiscuous mode Sun May 12 00:22:04 2019 kern.info kernel: [ 618.918050] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:22:04 2019 kern.info kernel: [ 618.923847] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:22:04 2019 kern.info kernel: [ 618.966536] device eth0.103 entered promiscuous mode Sun May 12 00:22:04 2019 kern.info kernel: [ 618.971618] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:22:04 2019 kern.info kernel: [ 618.977409] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:22:04 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:22:04 2019 kern.info kernel: [ 619.024932] device eth0.104 entered promiscuous mode Sun May 12 00:22:04 2019 kern.info kernel: [ 619.030034] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:22:04 2019 kern.info kernel: [ 619.035845] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:22:04 2019 daemon.notice netifd: wan (20293): udhcpc: sending discover Sun May 12 00:22:05 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:22:05 2019 kern.info kernel: [ 620.073818] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:22:05 2019 kern.info kernel: [ 620.079256] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:22:05 2019 kern.info kernel: [ 620.237676] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:22:05 2019 kern.info kernel: [ 620.261277] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:22:05 2019 kern.info kernel: [ 620.284662] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:22:05 2019 kern.info kernel: [ 620.309261] device eth0 left promiscuous mode Sun May 12 00:22:05 2019 kern.info kernel: [ 620.313684] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:22:06 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:22:06 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:22:06 2019 kern.info kernel: [ 621.092743] br-wan: port 1(eth1) entered disabled state Sun May 12 00:22:06 2019 daemon.notice netifd: wan (20293): udhcpc: read error: Network is down, reopening socket Sun May 12 00:22:06 2019 daemon.notice netifd: wan (20293): udhcpc: received SIGTERM Sun May 12 00:22:06 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:22:07 2019 kern.info kernel: [ 622.368581] device eth0 entered promiscuous mode Sun May 12 00:22:09 2019 kern.notice kernel: [ 624.135214] jffs2: Write of 70 bytes at 0x00134b8c failed. returned -5, retlen 68 Sun May 12 00:22:09 2019 kern.notice kernel: [ 624.144383] jffs2: Write of 70 bytes at 0x00134bd4 failed. returned -5, retlen 68 Sun May 12 00:22:09 2019 daemon.warn trilld[20612]: rtnetlink is supported: using new api Sun May 12 00:22:09 2019 kern.info kernel: [ 624.182247] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:22:09 2019 kern.info kernel: [ 624.188065] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:22:09 2019 kern.info kernel: [ 624.193843] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:22:09 2019 kern.info kernel: [ 624.199621] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:22:09 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:22:09 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:22:09 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:22:09 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:09 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:09 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:09 2019 kern.warn kernel: [ 624.205833] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:09 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:09 2019 daemon.notice netifd: wan (20629): udhcpc: started, v1.26.2 Sun May 12 00:22:09 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:22:09 2019 daemon.notice netifd: wan (20629): udhcpc: sending discover Sun May 12 00:22:10 2019 kern.info kernel: [ 625.217083] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:22:10 2019 kern.info kernel: [ 625.222871] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:22:10 2019 kern.info kernel: [ 625.230225] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:22:10 2019 kern.info kernel: [ 625.236004] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:22:10 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:22:10 2019 kern.info kernel: [ 625.244062] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:22:10 2019 kern.info kernel: [ 625.249491] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:10 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:11 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:11 2019 kern.info kernel: [ 626.192557] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:22:11 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:11 2019 kern.info kernel: [ 626.200553] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:22:11 2019 daemon.warn trilld[20614]: isis_recv_packet_bcast(): ifname eth0.101, fd 16, bytesread -1, recvfrom(): Network is down Sun May 12 00:22:11 2019 kern.info kernel: [ 626.520350] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:22:11 2019 daemon.warn trilld[20614]: isis_recv_packet_bcast(): ifname eth0.103, fd 17, bytesread -1, recvfrom(): Network is down Sun May 12 00:22:11 2019 kern.info kernel: [ 626.562430] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:22:11 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:22:12 2019 kern.warn kernel: [ 626.970738] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:12 2019 kern.warn kernel: [ 627.011710] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:12 2019 kern.warn kernel: [ 627.173722] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:12 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:12 2019 kern.info kernel: [ 627.252555] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:22:12 2019 daemon.notice netifd: wan (20629): udhcpc: sending discover Sun May 12 00:22:12 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:22:12 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:12 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:12 2019 daemon.warn trilld[20614]: circuit already connected Sun May 12 00:22:12 2019 kern.info kernel: [ 627.528816] br-wan: port 1(eth1) entered disabled state Sun May 12 00:22:14 2019 kern.warn kernel: [ 629.175792] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:15 2019 kern.warn kernel: [ 629.726747] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:15 2019 kern.warn kernel: [ 629.751705] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:15 2019 kern.warn kernel: [ 630.176721] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:15 2019 daemon.notice netifd: wan (20629): udhcpc: sending discover Sun May 12 00:22:16 2019 kern.warn kernel: [ 631.177759] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:17 2019 kern.warn kernel: [ 632.178742] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:17 2019 kern.warn kernel: [ 632.445746] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:18 2019 kern.warn kernel: [ 632.682749] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:18 2019 kern.warn kernel: [ 633.179824] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:18 2019 kern.warn kernel: [ 633.187431] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:19 2019 kern.warn kernel: [ 634.180714] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:19 2019 kern.warn kernel: [ 634.188317] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:20 2019 kern.warn kernel: [ 635.181768] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:20 2019 kern.warn kernel: [ 635.189373] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:20 2019 kern.warn kernel: [ 635.370734] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:21 2019 daemon.warn watchquagga[2916]: Warning: restart all child process 20065 still running after 20 seconds, sending signal 15 Sun May 12 00:22:21 2019 daemon.warn watchquagga[2916]: restart all process 20065 terminated due to signal 15 Sun May 12 00:22:23 2019 kern.warn kernel: [ 637.708704] net_ratelimit: 11 callbacks suppressed Sun May 12 00:22:23 2019 kern.warn kernel: [ 637.713519] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:23 2019 kern.warn kernel: [ 638.042733] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:23 2019 kern.warn kernel: [ 638.184713] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:23 2019 kern.warn kernel: [ 638.192308] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:23 2019 kern.warn kernel: [ 638.376759] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:23 2019 kern.warn kernel: [ 638.480700] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:24 2019 kern.warn kernel: [ 638.710700] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:24 2019 kern.warn kernel: [ 638.814700] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:24 2019 kern.warn kernel: [ 639.044816] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:24 2019 kern.warn kernel: [ 639.148800] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:28 2019 kern.warn kernel: [ 643.052731] net_ratelimit: 29 callbacks suppressed Sun May 12 00:22:28 2019 kern.warn kernel: [ 643.057546] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:28 2019 kern.warn kernel: [ 643.156703] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:28 2019 kern.warn kernel: [ 643.189871] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:28 2019 kern.warn kernel: [ 643.197510] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:28 2019 kern.warn kernel: [ 643.205128] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:28 2019 kern.warn kernel: [ 643.386746] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:28 2019 kern.warn kernel: [ 643.490713] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:29 2019 kern.warn kernel: [ 643.720708] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:29 2019 kern.warn kernel: [ 643.824707] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:22:29 2019 kern.warn kernel: [ 644.054704] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:22:29 2019 daemon.crit trilld[20614]: Assertion `isis_find_vertex (spftree->paths, id, vtype) == ((void*)0)' failed in file isis_spf.c, line 529, function isis_spf_add2tent Sun May 12 00:22:29 2019 daemon.crit trilld[20614]: No backtrace available on this platform. Sun May 12 00:22:29 2019 daemon.err watchquagga[2916]: trilld state -> down : read returned EOF Sun May 12 00:22:29 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:22:29 2019 daemon.err watchquagga[2916]: trilld state -> down : unexpected read error: Connection reset by peer Sun May 12 00:22:32 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:22:32 2019 kern.info kernel: [ 646.808349] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:22:32 2019 kern.info kernel: [ 646.813806] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:22:34 2019 kern.info kernel: [ 648.816558] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:23 2019 daemon.err watchquagga[2916]: Forked background command [pid 27740]: /etc/init.d/quagga restart Sun May 12 00:26:23 2019 kern.info kernel: [ 878.375448] device eth0.101 left promiscuous mode Sun May 12 00:26:23 2019 kern.info kernel: [ 878.380231] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:26:23 2019 kern.info kernel: [ 878.398238] device eth0.102 left promiscuous mode Sun May 12 00:26:23 2019 kern.info kernel: [ 878.403025] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:26:23 2019 kern.info kernel: [ 878.423323] device eth0.103 left promiscuous mode Sun May 12 00:26:23 2019 kern.info kernel: [ 878.428084] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:26:23 2019 kern.info kernel: [ 878.448173] device eth0.104 left promiscuous mode Sun May 12 00:26:23 2019 kern.info kernel: [ 878.452961] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:26:23 2019 kern.info kernel: [ 878.465037] device eth0 left promiscuous mode Sun May 12 00:26:23 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:26:23 2019 kern.info kernel: [ 878.499604] br-wan: port 1(eth1) entered disabled state Sun May 12 00:26:23 2019 kern.info kernel: [ 878.541097] device eth0 entered promiscuous mode Sun May 12 00:26:24 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:26:24 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:26:24 2019 daemon.notice netifd: wan (20629): udhcpc: received SIGTERM Sun May 12 00:26:25 2019 kern.info kernel: [ 880.583290] device eth0.101 entered promiscuous mode Sun May 12 00:26:25 2019 kern.info kernel: [ 880.588350] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:26:25 2019 kern.info kernel: [ 880.594141] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:26:25 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:26:25 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:26:25 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:26:25 2019 daemon.notice netifd: wan (27966): udhcpc: started, v1.26.2 Sun May 12 00:26:26 2019 kern.info kernel: [ 880.640145] device eth0.102 entered promiscuous mode Sun May 12 00:26:26 2019 kern.info kernel: [ 880.645209] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:26:26 2019 kern.info kernel: [ 880.651003] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:26:26 2019 kern.info kernel: [ 880.694058] device eth0.103 entered promiscuous mode Sun May 12 00:26:26 2019 kern.info kernel: [ 880.699144] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:26:26 2019 kern.info kernel: [ 880.704948] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:26:26 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:26:26 2019 kern.info kernel: [ 880.752423] device eth0.104 entered promiscuous mode Sun May 12 00:26:26 2019 kern.info kernel: [ 880.757499] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:26:26 2019 kern.info kernel: [ 880.763298] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:26:26 2019 daemon.notice netifd: wan (27966): udhcpc: sending discover Sun May 12 00:26:27 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:26:27 2019 kern.info kernel: [ 881.796724] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:27 2019 kern.info kernel: [ 881.802165] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:27 2019 kern.info kernel: [ 882.241987] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:26:27 2019 kern.info kernel: [ 882.265471] br-wan: port 3(eth0.102) entered disabled state Sun May 12 00:26:27 2019 kern.info kernel: [ 882.289073] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:26:27 2019 kern.info kernel: [ 882.313708] device eth0 left promiscuous mode Sun May 12 00:26:27 2019 kern.info kernel: [ 882.318131] br-wan: port 5(eth0.104) entered disabled state Sun May 12 00:26:28 2019 daemon.notice netifd: bridge 'br-wan' link is down Sun May 12 00:26:28 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Sun May 12 00:26:28 2019 kern.info kernel: [ 882.815645] br-wan: port 1(eth1) entered disabled state Sun May 12 00:26:28 2019 daemon.notice netifd: wan (27966): udhcpc: read error: Network is down, reopening socket Sun May 12 00:26:28 2019 daemon.notice netifd: wan (27966): udhcpc: received SIGTERM Sun May 12 00:26:28 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:26:29 2019 kern.info kernel: [ 884.374132] device eth0 entered promiscuous mode Sun May 12 00:26:31 2019 kern.notice kernel: [ 885.857371] jffs2: Write of 70 bytes at 0x00134c1c failed. returned -5, retlen 68 Sun May 12 00:26:31 2019 kern.notice kernel: [ 885.866210] jffs2: Write of 70 bytes at 0x00134c64 failed. returned -5, retlen 68 Sun May 12 00:26:31 2019 daemon.warn trilld[28283]: rtnetlink is supported: using new api Sun May 12 00:26:31 2019 kern.info kernel: [ 885.903646] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:26:31 2019 kern.info kernel: [ 885.909458] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:26:31 2019 kern.info kernel: [ 885.915238] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:26:31 2019 kern.info kernel: [ 885.921014] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:26:31 2019 daemon.notice netifd: bridge 'br-wan' link is up Sun May 12 00:26:31 2019 daemon.notice netifd: Interface 'wan' has link connectivity Sun May 12 00:26:31 2019 daemon.notice netifd: Interface 'wan' is setting up now Sun May 12 00:26:31 2019 kern.warn kernel: [ 885.927073] net_ratelimit: 1 callbacks suppressed Sun May 12 00:26:31 2019 kern.warn kernel: [ 885.931804] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:31 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:31 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:31 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:31 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:31 2019 daemon.notice netifd: wan (28300): udhcpc: started, v1.26.2 Sun May 12 00:26:31 2019 daemon.notice netifd: Interface 'wan' is now up Sun May 12 00:26:31 2019 daemon.notice netifd: wan (28300): udhcpc: sending discover Sun May 12 00:26:32 2019 kern.info kernel: [ 886.938021] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:26:32 2019 kern.info kernel: [ 886.943810] br-wan: port 2(eth0.101) entered forwarding state Sun May 12 00:26:32 2019 kern.info kernel: [ 886.951170] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:26:32 2019 kern.info kernel: [ 886.956950] br-wan: port 4(eth0.103) entered forwarding state Sun May 12 00:26:32 2019 kern.info kernel: [ 886.965095] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:32 2019 kern.info kernel: [ 886.970523] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:32 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:33 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:33 2019 kern.info kernel: [ 887.912558] br-wan: port 5(eth0.104) entered forwarding state Sun May 12 00:26:33 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:33 2019 kern.info kernel: [ 887.924553] br-wan: port 3(eth0.102) entered forwarding state Sun May 12 00:26:33 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:26:33 2019 daemon.warn trilld[28285]: isis_recv_packet_bcast(): ifname eth0.101, fd 16, bytesread -1, recvfrom(): Network is down Sun May 12 00:26:33 2019 kern.info kernel: [ 888.528054] br-wan: port 2(eth0.101) entered disabled state Sun May 12 00:26:33 2019 daemon.warn trilld[28285]: isis_recv_packet_bcast(): ifname eth0.103, fd 17, bytesread -1, recvfrom(): Network is down Sun May 12 00:26:33 2019 kern.info kernel: [ 888.570944] br-wan: port 4(eth0.103) entered disabled state Sun May 12 00:26:34 2019 kern.warn kernel: [ 888.675783] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:34 2019 kern.warn kernel: [ 888.729714] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:34 2019 kern.warn kernel: [ 888.895730] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:34 2019 kern.warn kernel: [ 888.903324] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:34 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:34 2019 kern.info kernel: [ 888.976554] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:34 2019 daemon.notice netifd: wan (28300): udhcpc: sending discover Sun May 12 00:26:34 2019 daemon.notice netifd: Network device 'eth1' link is down Sun May 12 00:26:34 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:34 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:34 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:34 2019 kern.info kernel: [ 889.536823] br-wan: port 1(eth1) entered disabled state Sun May 12 00:26:36 2019 kern.warn kernel: [ 890.897762] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:36 2019 kern.warn kernel: [ 890.905369] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:36 2019 kern.warn kernel: [ 891.522746] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:36 2019 kern.warn kernel: [ 891.628760] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:37 2019 daemon.notice netifd: wan (28300): udhcpc: sending discover Sun May 12 00:26:38 2019 kern.warn kernel: [ 892.899806] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:39 2019 kern.warn kernel: [ 894.355821] net_ratelimit: 1 callbacks suppressed Sun May 12 00:26:39 2019 kern.warn kernel: [ 894.360549] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:39 2019 kern.warn kernel: [ 894.432711] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:40 2019 kern.warn kernel: [ 894.901831] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:40 2019 kern.warn kernel: [ 894.909435] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:40 2019 kern.warn kernel: [ 894.917037] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:40 2019 kern.warn kernel: [ 894.924635] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:41 2019 daemon.notice netifd: Network device 'eth1' link is up Sun May 12 00:26:41 2019 kern.info kernel: [ 895.905341] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:41 2019 kern.info kernel: [ 895.910795] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:41 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:41 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:41 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:41 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:42 2019 kern.warn kernel: [ 896.905861] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:42 2019 kern.warn kernel: [ 896.913469] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:42 2019 kern.warn kernel: [ 896.921091] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:42 2019 kern.warn kernel: [ 896.928704] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:43 2019 daemon.warn trilld[28285]: circuit already connected Sun May 12 00:26:43 2019 kern.info kernel: [ 897.912561] br-wan: port 1(eth1) entered forwarding state Sun May 12 00:26:43 2019 daemon.warn watchquagga[2916]: Warning: restart all child process 27740 still running after 20 seconds, sending signal 15 Sun May 12 00:26:43 2019 daemon.warn watchquagga[2916]: restart all process 27740 terminated due to signal 15 Sun May 12 00:26:45 2019 kern.warn kernel: [ 899.726714] net_ratelimit: 12 callbacks suppressed Sun May 12 00:26:45 2019 kern.warn kernel: [ 899.731528] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:45 2019 kern.warn kernel: [ 900.060709] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:45 2019 kern.warn kernel: [ 900.076703] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:45 2019 kern.warn kernel: [ 900.394704] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:45 2019 kern.warn kernel: [ 900.410705] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:46 2019 kern.warn kernel: [ 900.728676] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:46 2019 kern.warn kernel: [ 900.744702] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:46 2019 kern.warn kernel: [ 900.909723] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:46 2019 kern.warn kernel: [ 900.917316] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:46 2019 kern.warn kernel: [ 900.924911] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:50 2019 kern.warn kernel: [ 905.070713] net_ratelimit: 32 callbacks suppressed Sun May 12 00:26:50 2019 kern.warn kernel: [ 905.075526] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:50 2019 kern.warn kernel: [ 905.086703] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:50 2019 kern.warn kernel: [ 905.404735] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:50 2019 kern.warn kernel: [ 905.420707] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:51 2019 kern.warn kernel: [ 905.738702] br-wan: received packet on eth0.104 with own address as source address Sun May 12 00:26:51 2019 kern.warn kernel: [ 905.754702] br-wan: received packet on eth0.102 with own address as source address Sun May 12 00:26:51 2019 daemon.crit trilld[28285]: Assertion `isis_find_vertex (spftree->paths, id, vtype) == ((void*)0)' failed in file isis_spf.c, line 529, function isis_spf_add2tent Sun May 12 00:26:51 2019 daemon.crit trilld[28285]: No backtrace available on this platform. Sun May 12 00:26:51 2019 daemon.err watchquagga[2916]: trilld state -> down : read returned EOF Sun May 12 00:26:51 2019 daemon.notice watchquagga[2916]: trilld state -> up : connect succeeded Sun May 12 00:26:51 2019 daemon.err watchquagga[2916]: trilld state -> down : unexpected read error: Connection reset by peer