Wi-CAT LLC

Wireless Comprehensive Advanced Technology. Build your network now.

Wi-CAT LLC
Навигация Форума
Вы должны войти, чтобы создавать сообщения и темы.

(решено, проблема на стороне сервера) syslog на внешний сервер SNR-CPE-ME1 7.9.9.RU.19022019

SNR-CPE-ME1 7.9.9.RU.19022019

Не получается настроить отправку логов на удаленный сервер syslog.
Вводил адрес на странице Системный журнал, но логи на сервер не попадают.

С других устройств логи собираются без проблем.

Куда копать?

Загруженные файлы:
  • Вам нужно войти, чтобы просматривать прикрепленные файлы..

В сторону https://wi-cat.ru/forums/topic/prochti-menya/ затем со всеми данными от конфига до лога сюда, ну и вывод ps лишним не будет.

У меня прекрасно все логи складываются в удалённый rsyslog. Потому в лоб ничего не скажу, а таким объёмом весьма полезных данных тем более.

Либо баг, либо несовместимость с вашим сервером либо ещё что. Увы гадать по фотографии не умею. Оформите репорт нормально предоставив требуемую для диагностики инфу - разберёмся.

Адрес сислог сервера-то точно верный? И какие-то новые записи с выбранным уровнем есть в локальном логе и нет  в удалённом? На стороне сислог сервера не дропает ли какой фаервол данные и т.д. и т.п. и ещё 13999 подобных вопросов ибо тут неоткуда проблеме взяться.

и что вам покажут логи?

Вот и посмотрим что покажут. Картинки мне вообще ничего не покажут.

2. Задавая вопрос, сообщите модель роутера, точную версию прошивки, тип подключения к провайдеру и другие детали, которые могут быть полезны.

эту информацию я сообщил:  SNR-CPE-ME1 7.9.9.RU.19022019
тип подключения к провайдеру в режиме по моему мнению не может быть полезным в данном случае
единственную настройку я тоже показал

дополнительная запрошенная вами информация:

лог

.warn kernel: Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Zone PFN ranges:
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: DMA 0x00000000 -> 0x00001000
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Normal 0x00001000 -> 0x00010000
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Movable zone start PFN for each node
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Early memory PFN ranges
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: 0: 0x00000000 -> 0x00010000
Jan 1 03:00:03 wive-ng-mt kern.info kernel: PERCPU: Embedded 7 pages/cpu @8162a000 s4544 r8192 d15936 u32768
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: Kernel command line: console=ttyS0,57600n8 root=/dev/mtdblock4 rootfstype=squashfs
Jan 1 03:00:03 wive-ng-mt kern.info kernel: PID hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Writing ErrCtl register=0000c020
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Readback ErrCtl register=0000c020
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Memory: 255488k/262144k available (3212k kernel code, 6656k reserved, 696k data, 244k init, 0k highmem)
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: start_kernel(): bug: interrupts were enabled *very* early, fixing it
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Hierarchical RCU implementation.
Jan 1 03:00:03 wive-ng-mt kern.info kernel: NR_IRQS:72
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: MIPS GIC RevID: 3.0
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Setting up vectored interrupts
Jan 1 03:00:03 wive-ng-mt kern.info kernel: console [ttyS0] enabled
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Calibrating delay loop... 577.53 BogoMIPS (lpj=288768)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pid_max: default: 32768 minimum: 301
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Mount-cache hash table entries: 512
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Jan 1 03:00:03 wive-ng-mt kern.info kernel: CPU revision is: 0001992f (MIPS 1004Kc)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Synchronize counters for CPU 1: done.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Jan 1 03:00:03 wive-ng-mt kern.info kernel: CPU revision is: 0001992f (MIPS 1004Kc)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Synchronize counters for CPU 2: done.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Jan 1 03:00:03 wive-ng-mt kern.info kernel: CPU revision is: 0001992f (MIPS 1004Kc)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Synchronize counters for CPU 3: done.
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Brought up 4 CPUs
Jan 1 03:00:03 wive-ng-mt kern.info kernel: NET: Registered protocol family 16
Jan 1 03:00:03 wive-ng-mt kern.info kernel: bio: create slab <bio-0> at 0
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: SCSI subsystem initialized
Jan 1 03:00:03 wive-ng-mt kern.info kernel: USB led has gpio 13
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usbcore: registered new interface driver usbfs
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usbcore: registered new interface driver hub
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usbcore: registered new device driver usb
Jan 1 03:00:03 wive-ng-mt kern.info kernel: PCI host bridge to bus 0000:00
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci_bus 0000:00: root bus resource [io 0x1e160000-0x1e16ffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:00:00.0: BAR 0: can't assign mem (size 0x80000000)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:00:01.0: BAR 0: can't assign mem (size 0x80000000)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:00:00.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:00:01.0: BAR 8: assigned [mem 0x60100000-0x602fffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:01:00.0: BAR 0: assigned [mem 0x60000000-0x600fffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:00:00.0: PCI bridge to [bus 01-01]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:00:00.0: bridge window [mem 0x60000000-0x600fffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:02:00.0: BAR 0: assigned [mem 0x60100000-0x601fffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:02:00.1: BAR 0: assigned [mem 0x60200000-0x602fffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:00:01.0: PCI bridge to [bus 02-02]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: pci 0000:00:01.0: bridge window [mem 0x60100000-0x602fffff]
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Switching to clocksource GIC
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: FS-Cache: Loaded
Jan 1 03:00:03 wive-ng-mt kern.info kernel: CacheFiles: Loaded
Jan 1 03:00:03 wive-ng-mt kern.info kernel: NET: Registered protocol family 1
Jan 1 03:00:03 wive-ng-mt kern.info kernel: NET: Registered protocol family 2
Jan 1 03:00:03 wive-ng-mt kern.info kernel: IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: TCP: Hash tables configured (established 8192 bind 8192)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: TCP: reno registered
Jan 1 03:00:03 wive-ng-mt kern.info kernel: UDP hash table entries: 128 (order: 0, 4096 bytes)
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: 4 CPUs re-calibrate udelay (lpj = 289792)
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Load Ralink WDG Timer Module
Jan 1 03:00:03 wive-ng-mt kern.info kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jan 1 03:00:03 wive-ng-mt kern.info kernel: msgmni has been set to 499
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: io scheduler noop registered (default)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
Jan 1 03:00:03 wive-ng-mt kern.info kernel: serial8250: ttyS0 at MMIO 0x1e000c00 (irq = 34) is a 16550A
Jan 1 03:00:03 wive-ng-mt kern.info kernel: USB power down at bootup use inverted gpio 17
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Ralink gpio driver initialized
Jan 1 03:00:03 wive-ng-mt kern.info kernel: loop: module loaded
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: MediaTek SPI flash driver, SPI clock: 44MHz
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: SPI flash chip: GD25Q128CSIG (c8 4018c840) (16384 Kbytes)
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: Creating 7 MTD partitions on "raspi":
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: 0x000000000000-0x000000030000 : "Bootloader"
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: 0x000000030000-0x000000040000 : "Config"
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: 0x000000040000-0x000000050000 : "Factory"
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: 0x000000050000-0x0000001ad350 : "Kernel_stub"
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: 0x0000001ad350-0x000000f00000 : "RootFS_stub"
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: 0x000000f00000-0x000001000000 : "RW-FS"
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: 0x000000050000-0x000000f00000 : "Kernel_RootFS"
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Ralink APSoC Ethernet Driver v3.2.4 (raeth)
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: raeth: PDMA RX ring 512, QDMA TX pool 1024. Max packet size 1536
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: raeth: NAPI & GRO support, weight 128
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: raeth: Byte Queue Limits (BQL) support
Jan 1 03:00:03 wive-ng-mt kern.info kernel: PPP generic driver version 2.4.2
Jan 1 03:00:03 wive-ng-mt kern.info kernel: PPP vpn led has gpio 16
Jan 1 03:00:03 wive-ng-mt kern.info kernel: PPP MPPE Compression module registered
Jan 1 03:00:03 wive-ng-mt kern.info kernel: NET: Registered protocol family 24
Jan 1 03:00:03 wive-ng-mt kern.info kernel: PPTP driver version 0.8.5
Jan 1 03:00:03 wive-ng-mt kern.info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan 1 03:00:03 wive-ng-mt kern.info kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: U2PHY P0 set SRCTRL calibration value: 2
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: U2PHY P1 set SRCTRL calibration value: 2
Jan 1 03:00:03 wive-ng-mt kern.info kernel: xhci-hcd xhci-hcd: xHCI Host Controller
Jan 1 03:00:03 wive-ng-mt kern.info kernel: xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 1
Jan 1 03:00:03 wive-ng-mt kern.info kernel: xhci-hcd xhci-hcd: irq 30, io mem 0x1e1c0000
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usb usb1: Product: xHCI Host Controller
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usb usb1: Manufacturer: Linux 3.4.113.185 xhci-hcd
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usb usb1: SerialNumber: xhci-hcd
Jan 1 03:00:03 wive-ng-mt kern.info kernel: hub 1-0:1.0: USB hub found
Jan 1 03:00:03 wive-ng-mt kern.info kernel: hub 1-0:1.0: 2 ports detected
Jan 1 03:00:03 wive-ng-mt kern.info kernel: xhci-hcd xhci-hcd: xHCI Host Controller
Jan 1 03:00:03 wive-ng-mt kern.info kernel: xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 2
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usb usb2: Product: xHCI Host Controller
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usb usb2: Manufacturer: Linux 3.4.113.185 xhci-hcd
Jan 1 03:00:03 wive-ng-mt user.notice sysctl: Tune kernel with sysctl.
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usb usb2: SerialNumber: xhci-hcd
Jan 1 03:00:03 wive-ng-mt kern.info kernel: hub 2-0:1.0: USB hub found
Jan 1 03:00:03 wive-ng-mt kern.info kernel: hub 2-0:1.0: 1 port detected
Jan 1 03:00:03 wive-ng-mt kern.info kernel: usbcore: registered new interface driver libusual
Jan 1 03:00:03 wive-ng-mt kern.info kernel: 8021q: 802.1Q VLAN Support v1.8
Jan 1 03:00:03 wive-ng-mt kern.info kernel: NET: Registered protocol family 17
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Netfilter messages via NETLINK v0.30.
Jan 1 03:00:03 wive-ng-mt kern.info kernel: nf_conntrack version 0.5.0 (16384 buckets, 32768 max)
Jan 1 03:00:03 wive-ng-mt kern.info kernel: gre: GRE over IPv4 demultiplexor driver
Jan 1 03:00:03 wive-ng-mt kern.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 03:00:03 wive-ng-mt kern.info kernel: TCP: cubic registered
Jan 1 03:00:03 wive-ng-mt kern.info kernel: NET: Registered protocol family 10
Jan 1 03:00:03 wive-ng-mt kern.info kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 03:00:03 wive-ng-mt kern.info kernel: L2TP core driver, V2.0
Jan 1 03:00:03 wive-ng-mt kern.info kernel: PPPoL2TP kernel driver, V2.0
Jan 1 03:00:03 wive-ng-mt kern.info kernel: L2TP netlink interface
Jan 1 03:00:03 wive-ng-mt kern.notice kernel: Registering the dns_resolver key type
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: NVRAM: Kernel NVRAM start init.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: NVRAM: Particion 0 CRC d313c2df OK.
Jan 1 03:00:03 wive-ng-mt kern.info kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: mount /proc file system ok!
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: mount /proc/bus/usb file system ok!
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: mount /sys file system ok!
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: mount /dev file system ok!
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: mount /var file system ok!
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Freeing unused kernel memory: 244k freed
Jan 1 03:00:03 wive-ng-mt kern.info kernel: Build the /dev/console node.
Jan 1 03:00:03 wive-ng-mt kern.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 03:00:03 wive-ng-mt user.notice pass: Set current password
Jan 1 03:00:03 wive-ng-mt user.err syslog: password for 'iddi' changed
Feb 21 17:17:00 wive-ng-mt user.notice ntp: Starting NTPD
Feb 21 17:17:00 wive-ng-mt user.notice hotplug: Generate config file.
Feb 21 17:17:00 wive-ng-mt user.notice hotplug: Set mdev as kernel hotplug helper and enable device autoprobe.
Feb 21 17:17:00 wive-ng-mt user.notice hotplug: Refresh dev nodes.
Feb 21 17:17:00 wive-ng-mt user.notice hotplug: Rescan connected devices
Feb 21 17:17:00 wive-ng-mt user.notice usbctrl(531): TYPE=9/0/1 INTERFACE=9/0/0
Feb 21 17:17:00 wive-ng-mt user.notice lo: Start loopback interface.
Feb 21 17:17:00 wive-ng-mt user.notice lan: Start LAN network interfaces.
Feb 21 17:17:00 wive-ng-mt user.notice ESW: Double vlan tag disabled.
Feb 21 17:17:00 wive-ng-mt user.notice ESW: eth2 MACADDR F8:F0:82:55:B2:DD txqueuelen 200
Feb 21 17:17:00 wive-ng-mt kern.warn kernel: raeth: HW IP/TCP/UDP checksum RX/TX offload enabled
Feb 21 17:17:00 wive-ng-mt kern.warn kernel: raeth: HW VLAN TX offload enabled
Feb 21 17:17:00 wive-ng-mt kern.warn kernel: raeth: HW Scatter/Gather TX offload enabled
Feb 21 17:17:00 wive-ng-mt user.notice ESW: eth3 MACADDR 00:14:fd:17:9c:ce txqueuelen 200
Feb 21 17:17:00 wive-ng-mt user.notice ESW: Restore internal MT7621 switch mode to dumb mode
Feb 21 17:17:00 wive-ng-mt user.notice ESW: Reset LAN ports phys
Feb 21 17:17:01 wive-ng-mt user.notice usbctrl(537): TYPE=9/0/3 INTERFACE=9/0/0
Feb 21 17:17:01 wive-ng-mt user.notice lan: Add bridge in the system
Feb 21 17:17:01 wive-ng-mt user.notice lan: br0_MACADDR F8:F0:82:55:B2:DD
Feb 21 17:17:01 wive-ng-mt user.notice lan: Up bridge interface
Feb 21 17:17:01 wive-ng-mt user.notice lan: Add LAN1 Mode is 0 lan iface br0, adress 192.168.1.2
Feb 21 17:17:01 wive-ng-mt user.notice resolv: Generate resolv DNS1: 192.168.1.1 DNS2:
Feb 21 17:17:01 wive-ng-mt user.notice resolv: Add user ipv6 servers 2001:4860:4860::8888 2001:4860:4860::8844 for local resolv
Feb 21 17:17:01 wive-ng-mt user.notice dnsserver: Generate /etc/hosts file.
Feb 21 17:17:01 wive-ng-mt user.notice dnsserver: Starting DNSMASQ
Feb 21 17:17:01 wive-ng-mt user.notice inetd: Starting inetd
Feb 21 17:17:01 wive-ng-mt kern.info kernel: Ralink APSoC Hardware Watchdog Timer
Feb 21 17:17:01 wive-ng-mt daemon.info dnsmasq[953]: started, version 2.80 cachesize 512
Feb 21 17:17:01 wive-ng-mt daemon.info dnsmasq[953]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN no-DHCP no-scripts no-TFTP no-conntrack no-ipset no-auth DNSSEC no-loop-detect inotify no-dumpfile
Feb 21 17:17:01 wive-ng-mt daemon.info dnsmasq[953]: read /etc/hosts - 6 addresses
Feb 21 17:17:01 wive-ng-mt daemon.info dnsmasq[953]: using nameserver 192.168.1.1#53
Feb 21 17:17:01 wive-ng-mt daemon.info dnsmasq[953]: using nameserver 2001:4860:4860::8888#53
Feb 21 17:17:01 wive-ng-mt daemon.info dnsmasq[953]: using nameserver 2001:4860:4860::8844#53
Feb 21 17:17:02 wive-ng-mt kern.info kernel: Started WatchDog Timer.
Feb 21 17:17:03 wive-ng-mt user.notice 2nd_stage: Switch to 2nd boot stage and start webui.
Feb 21 17:17:03 wive-ng-mt user.notice reconfig: all tunnels in ipv6 deconfig before modules reload (prevent race)
Feb 21 17:17:03 wive-ng-mt user.notice reconfig: Reload modules.
Feb 21 17:17:03 wive-ng-mt user.notice modules: link wifi down first
Feb 21 17:17:03 wive-ng-mt user.notice modules: Shutdown all wireless interfaces.
Feb 21 17:17:04 wive-ng-mt user.notice modules: Load conntrack helpers modules.
Feb 21 17:17:04 wive-ng-mt user.notice modules: Load application depended modules.
Feb 21 17:17:04 wive-ng-mt user.notice modules: Prepare wifi config.
Feb 21 17:17:04 wive-ng-mt user.notice modules: Load wireless modules.
Feb 21 17:17:04 wive-ng-mt user.notice modules: Load wifi AP module.
Feb 21 17:17:05 wive-ng-mt kern.warn kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
Feb 21 17:17:05 wive-ng-mt kern.warn kernel: MT7610 AP Driver version: 3.0.0.9.P54
Feb 21 17:17:05 wive-ng-mt kern.warn kernel: PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
Feb 21 17:17:05 wive-ng-mt kern.warn kernel: MT7603 AP Driver version: 4.1.0.0.P54
Feb 21 17:17:05 wive-ng-mt user.notice modules: WiFi ra0 interface up with txqueuelen 50.
Feb 21 17:17:05 wive-ng-mt kern.warn kernel: MT7603 Andes FW Version: ap_pcie
Feb 21 17:17:05 wive-ng-mt kern.warn kernel: MT7603 Andes FW Build Date: 20160107100755
Feb 21 17:17:06 wive-ng-mt user.notice modules: WiFi rai0 interface up with txqueuelen 50.
Feb 21 17:17:06 wive-ng-mt kern.warn kernel: load fw spent 17ms
Feb 21 17:17:06 wive-ng-mt kern.warn kernel: MT7610: 5GHz ePA used.
Feb 21 17:17:07 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=1 to 2.4GHz AP 78:e3:b5:8d:74:4d
Feb 21 17:17:07 wive-ng-mt kern.warn kernel: Legacy STA ASSOC - MODE=1, MCS=7
Feb 21 17:17:08 wive-ng-mt user.notice reconfig: Reconfigure lan.
Feb 21 17:17:08 wive-ng-mt user.notice lan: Stop LAN network interfaces.
Feb 21 17:17:08 wive-ng-mt user.notice lan: Start LAN network interfaces.
Feb 21 17:17:08 wive-ng-mt user.notice lan: Add bridge in the system
Feb 21 17:17:08 wive-ng-mt user.notice lan: br0_MACADDR F8:F0:82:55:B2:DD
Feb 21 17:17:08 wive-ng-mt user.notice lan: Up bridge interface
Feb 21 17:17:08 wive-ng-mt kern.warn kernel: raeth: HW IP/TCP/UDP checksum RX/TX offload enabled
Feb 21 17:17:08 wive-ng-mt kern.warn kernel: raeth: HW VLAN TX offload enabled
Feb 21 17:17:08 wive-ng-mt kern.warn kernel: raeth: HW Scatter/Gather TX offload enabled
Feb 21 17:17:08 wive-ng-mt user.notice lan: Add LAN1 Mode is 0 lan iface br0, adress 192.168.1.2
Feb 21 17:17:08 wive-ng-mt user.notice reconfig: Bridge OperationMode: 0
Feb 21 17:17:08 wive-ng-mt user.notice reconfig: Readd eth2 in br0
Feb 21 17:17:08 wive-ng-mt kern.warn kernel: raeth: HW IP/TCP/UDP checksum RX/TX offload enabled
Feb 21 17:17:08 wive-ng-mt kern.warn kernel: raeth: HW VLAN TX offload enabled
Feb 21 17:17:08 wive-ng-mt kern.warn kernel: raeth: HW Scatter/Gather TX offload enabled
Feb 21 17:17:08 wive-ng-mt kern.info kernel: device eth2 entered promiscuous mode
Feb 21 17:17:08 wive-ng-mt kern.info kernel: br0: port 1(eth2) entered forwarding state
Feb 21 17:17:08 wive-ng-mt user.notice reconfig: Readd ra0 in br0
Feb 21 17:17:08 wive-ng-mt kern.warn kernel: ASSOC - MLME disassociates 78:e3:b5:8d:74:4d; Send DISASSOC request
Feb 21 17:17:10 wive-ng-mt kern.info kernel: device ra0 entered promiscuous mode
Feb 21 17:17:10 wive-ng-mt kern.info kernel: br0: port 2(ra0) entered forwarding state
Feb 21 17:17:10 wive-ng-mt user.notice reconfig: Readd rai0 in br0
Feb 21 17:17:10 wive-ng-mt kern.warn kernel: load fw spent 13ms
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device rai0 entered promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 3(rai0) entered forwarding state
Feb 21 17:17:12 wive-ng-mt user.notice reconfig: Readd ra1 in br0
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device ra1 entered promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 4(ra1) entered forwarding state
Feb 21 17:17:12 wive-ng-mt user.notice reconfig: Readd ra2 in br0
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device ra2 entered promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 5(ra2) entered forwarding state
Feb 21 17:17:12 wive-ng-mt user.notice reconfig: Readd rai1 in br0
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device rai1 entered promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 6(rai1) entered forwarding state
Feb 21 17:17:12 wive-ng-mt user.notice reconfig: Readd rai2 in br0
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device rai2 entered promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 7(rai2) entered forwarding state
Feb 21 17:17:12 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=1 to 5GHz AP 00:6d:52:13:44:66
Feb 21 17:17:12 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=0 , fAnyStationIsLegacy=0, fAnyStation20Only=0, fAnyStationNonGF=1
Feb 21 17:17:12 wive-ng-mt kern.warn kernel: ReASSOC - Assign AID=1 to 2.4GHz AP 78:e3:b5:8d:74:4d
Feb 21 17:17:12 wive-ng-mt kern.warn kernel: Legacy STA ReASSOC - MODE=1, MCS=7
Feb 21 17:17:12 wive-ng-mt user.notice wan: Start WAN config
Feb 21 17:17:12 wive-ng-mt user.notice wan: Bridge interface adress set and up.
Feb 21 17:17:12 wive-ng-mt user.notice wan: Add default route via 192.168.1.1.
Feb 21 17:17:12 wive-ng-mt user.notice vlan: Add VLAN interface eth2.4 to system
Feb 21 17:17:12 wive-ng-mt user.notice vlan: Add BRIDGE brvl4wl2 to system
Feb 21 17:17:12 wive-ng-mt user.notice vlan: Add VLAN interface eth2.4 to bridge brvl4wl2
Feb 21 17:17:12 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=2 to 2.4GHz AP 5c:8d:4e:c3:34:6c
Feb 21 17:17:12 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3, fAnyStationIsLegacy=1, fAnyStation20Only=1, fAnyStationNonGF=1
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device eth2.4 entered promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: brvl4wl2: port 1(eth2.4) entered forwarding state
Feb 21 17:17:12 wive-ng-mt user.notice vlan: Move wlan interface ra2 from br0 and to new bridge brvl4wl2
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 5(ra2) entered disabled state
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device ra2 left promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 5(ra2) entered disabled state
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device ra2 entered promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: brvl4wl2: port 2(ra2) entered forwarding state
Feb 21 17:17:12 wive-ng-mt user.notice vlan: Move wlan interface rai2 from br0 and to new bridge brvl4wl2
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 7(rai2) entered disabled state
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device rai2 left promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: br0: port 7(rai2) entered disabled state
Feb 21 17:17:12 wive-ng-mt kern.info kernel: device rai2 entered promiscuous mode
Feb 21 17:17:12 wive-ng-mt kern.info kernel: brvl4wl2: port 3(rai2) entered forwarding state
Feb 21 17:17:13 wive-ng-mt user.notice ESW: Restore internal MT7621 switch mode to dumb mode
Feb 21 17:17:13 wive-ng-mt user.notice ESW: Reset LAN ports phys
Feb 21 17:17:13 wive-ng-mt user.notice advanced: Tune wifi advanced parametrs for ra0.
Feb 21 17:17:13 wive-ng-mt user.notice advanced: Tune wifi advanced parametrs for rai0.
Feb 21 17:17:13 wive-ng-mt user.notice services: Restart needed services and scripts. Mode all
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=3 to 2.4GHz AP 60:01:94:16:61:12
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3, fAnyStationIsLegacy=1, fAnyStation20Only=1, fAnyStationNonGF=1
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=4 to 2.4GHz AP a0:20:a6:17:47:a5
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3, fAnyStationIsLegacy=1, fAnyStation20Only=1, fAnyStationNonGF=1
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=5 to 2.4GHz AP 5c:cf:7f:ed:f4:d7
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3, fAnyStationIsLegacy=1, fAnyStation20Only=1, fAnyStationNonGF=1
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=6 to 2.4GHz AP 5c:cf:7f:a4:28:10
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3, fAnyStationIsLegacy=1, fAnyStation20Only=1, fAnyStationNonGF=1
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=7 to 2.4GHz AP 5c:cf:7f:a4:80:b8
Feb 21 17:17:13 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3, fAnyStationIsLegacy=1, fAnyStation20Only=1, fAnyStationNonGF=1
Feb 21 17:17:14 wive-ng-mt user.notice QoS: Stopping SHAPER
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Add netfiler rules
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Allow established/related in input
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Drop invalid state connections
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Service limit set
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Set macipport input filter rules
Feb 21 17:17:14 wive-ng-mt user.notice iptables: DHCP server allow
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Dnsproxy allow to connect
Feb 21 17:17:14 wive-ng-mt user.notice iptables: allow local port range 32768:61000 from LAN, need for some local service
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Remote managment web limit
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Remote managment ssh limit
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Remote managment telnet limit
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Allow rate limited ping from all interfaces.
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Allow established/related in forward
Feb 21 17:17:14 wive-ng-mt user.notice iptables: V6: Add netfiler rules
Feb 21 17:17:14 wive-ng-mt user.notice iptables: V6: Allow established/related in input
Feb 21 17:17:14 wive-ng-mt user.notice iptables: V6: Dnsproxy allow to connect
Feb 21 17:17:14 wive-ng-mt user.notice iptables: V6: allow local port range 32768:61000 from LAN, need for some local service
Feb 21 17:17:14 wive-ng-mt user.notice iptables: V6: Allow ratelimited icmp echo requests to router.
Feb 21 17:17:14 wive-ng-mt user.notice iptables: Allow established/related in forward
Feb 21 17:17:15 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=8 to 2.4GHz AP b4:e6:2a:b3:45:e3
Feb 21 17:17:15 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3, fAnyStationIsLegacy=1, fAnyStation20Only=1, fAnyStationNonGF=1
Feb 21 17:17:15 wive-ng-mt user.notice resolv: Generate resolv DNS1: 192.168.1.1 DNS2:
Feb 21 17:17:15 wive-ng-mt user.notice resolv: Add user ipv6 servers 2001:4860:4860::8888 2001:4860:4860::8844 for local resolv
Feb 21 17:17:15 wive-ng-mt user.notice dnsserver: Generate /etc/hosts file.
Feb 21 17:17:15 wive-ng-mt user.notice dnsserver: Send HUP to dnsmasq.
Feb 21 17:17:15 wive-ng-mt daemon.info dnsmasq[953]: read /etc/hosts - 8 addresses
Feb 21 17:17:15 wive-ng-mt daemon.info dnsmasq[953]: using nameserver 192.168.1.1#53
Feb 21 17:17:15 wive-ng-mt daemon.info dnsmasq[953]: using nameserver 2001:4860:4860::8888#53
Feb 21 17:17:15 wive-ng-mt daemon.info dnsmasq[953]: using nameserver 2001:4860:4860::8844#53
Feb 21 17:17:15 wive-ng-mt user.notice ntp: Stopping NTPD
Feb 21 17:17:16 wive-ng-mt user.notice ntp: Starting NTPD
Feb 21 17:17:16 wive-ng-mt user.notice kext: Nat mode Linux Hybrid
Feb 21 17:17:16 wive-ng-mt user.notice kext: NAT Offload mode not supported in this device mode (bridge/apclibridge/etc), hw_nat and all fastpaths disabled.
Feb 21 17:17:16 wive-ng-mt user.notice kext: Enable multicast to unicast conversion for rai0 ra0 ra1 ra2 rai1 rai2
Feb 21 17:17:17 wive-ng-mt user.notice arpwatch: Starting arpwatch
Feb 21 17:17:17 wive-ng-mt kern.info kernel: device br0 entered promiscuous mode
Feb 21 17:17:17 wive-ng-mt daemon.info arpwatch: listening on br0
Feb 21 17:17:17 wive-ng-mt user.notice inetd: Stopping inetd
Feb 21 17:17:17 wive-ng-mt user.notice inetd: Starting inetd
Feb 21 17:17:18 wive-ng-mt user.notice transmission: Not any disk connected.
Feb 21 17:17:18 wive-ng-mt user.notice dhcpd: DHCP server disabled. OPMODE=0 APCLIBR=0
Feb 21 17:17:18 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.1 00:e0:67:0a:5a:48
Feb 21 17:17:18 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.170 00:6d:52:13:44:66
Feb 21 17:17:18 wive-ng-mt user.notice irqbalance: Start irqbalance routing/wifi optimize mode
Feb 21 17:17:19 wive-ng-mt user.notice irqbalance: Start irqbalance auto mode
Feb 21 17:18:01 wive-ng-mt user.notice 2nd_stage: Copy web pages to tmpfs.
Feb 21 17:18:02 wive-ng-mt user.notice 2nd_stage: Start WEB Managment Server.
Feb 21 17:18:02 wive-ng-mt user.notice 2nd_stage: USB Port power ON.
Feb 21 17:18:02 wive-ng-mt user.notice hotplug: Rescan connected devices
Feb 21 17:18:02 wive-ng-mt user.notice usbctrl(3807): TYPE=9/0/1 INTERFACE=9/0/0
Feb 21 17:18:02 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=2 to 5GHz AP 10:cd:b6:02:fa:b3
Feb 21 17:18:02 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3 , fAnyStationIsLegacy=0, fAnyStation20Only=0, fAnyStationNonGF=1
Feb 21 17:18:02 wive-ng-mt kern.warn kernel: ASSOC - VHT support STA
Feb 21 17:18:03 wive-ng-mt user.notice usbctrl(3811): TYPE=9/0/3 INTERFACE=9/0/0
Feb 21 17:18:06 wive-ng-mt kern.info kernel: br0: port 1(eth2) entered forwarding state
Feb 21 17:18:07 wive-ng-mt kern.info kernel: br0: port 2(ra0) entered forwarding state
Feb 21 17:18:09 wive-ng-mt kern.info kernel: br0: port 3(rai0) entered forwarding state
Feb 21 17:18:09 wive-ng-mt kern.info kernel: br0: port 4(ra1) entered forwarding state
Feb 21 17:18:09 wive-ng-mt kern.info kernel: br0: port 6(rai1) entered forwarding state
Feb 21 17:18:10 wive-ng-mt kern.info kernel: brvl4wl2: port 1(eth2.4) entered forwarding state
Feb 21 17:18:10 wive-ng-mt kern.info kernel: brvl4wl2: port 2(ra2) entered forwarding state
Feb 21 17:18:10 wive-ng-mt kern.info kernel: brvl4wl2: port 3(rai2) entered forwarding state
Feb 21 17:18:10 wive-ng-mt daemon.notice arpwatch: new station 169.254.116.77 78:e3:b5:8d:74:4d
Feb 21 17:18:10 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.156 5c:8d:4e:c3:34:6c
Feb 21 17:18:10 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.225 60:01:94:16:61:12
Feb 21 17:18:10 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.220 5c:cf:7f:a4:28:10
Feb 21 17:18:10 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.223 5c:cf:7f:ed:f4:d7
Feb 21 17:18:10 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.221 5c:cf:7f:a4:80:b8
Feb 21 17:18:10 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.224 a0:20:a6:17:47:a5
Feb 21 17:18:16 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.100 10:cd:b6:02:fa:b3
Feb 21 17:18:16 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.147 b4:e6:2a:b3:45:e3
Feb 21 17:18:16 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.2 f8:f0:82:55:b2:dd
Feb 21 17:18:16 wive-ng-mt daemon.err arpwatch: report: pausing (cdepth 3)
Feb 21 17:18:16 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.176 34:29:8f:92:3a:16
Feb 21 17:18:16 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.188 78:e3:b5:8d:74:4d
Feb 21 17:18:16 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.38 00:14:fd:17:9c:ce
Feb 21 17:18:22 wive-ng-mt kern.warn kernel: ASSOC - Assign AID=8 to 2.4GHz AP b4:e6:2a:b3:45:e3
Feb 21 17:18:22 wive-ng-mt kern.warn kernel: ASSOC - HT support STA. Update AP OperaionMode=3, fAnyStationIsLegacy=1, fAnyStation20Only=1, fAnyStationNonGF=1
Feb 21 17:18:31 wive-ng-mt daemon.notice arpwatch: new station 192.168.1.37 00:90:a9:b0:70:70
Feb 21 17:18:59 wive-ng-mt local7.info nginx: 2019/02/21 17:18:59 [info] 3819#0: *1 Authentication successful: user=iddi , client: 192.168.1.176, server: localhost, request: "POST /goform/auth HTTP/1.1", host: "192.168.1.2", referrer: "http://192.168.1.2/login.asp"

ps

iddi@192.168.1.2's password: 

[homeAP@/]# ps w 

  PID USER       VSZ STAT COMMAND

    1 daemon    1772 S    {linuxrc} init

    2 daemon       0 SW   [kthreadd]

    3 daemon       0 SW   [ksoftirqd/0]

    4 daemon       0 SW   [kworker/0:0]

    5 daemon       0 SW   [kworker/u:0]

    6 daemon       0 SW   [migration/0]

    7 daemon       0 SW   [migration/1]

    8 daemon       0 SW   [kworker/1:0]

    9 daemon       0 SW   [ksoftirqd/1]

   10 daemon       0 SW   [kworker/0:1]

   11 daemon       0 SW   [migration/2]

   12 daemon       0 SW   [kworker/2:0]

   13 daemon       0 SW   [ksoftirqd/2]

   14 daemon       0 SW   [migration/3]

   15 daemon       0 SW   [kworker/3:0]

   16 daemon       0 SW   [ksoftirqd/3]

   17 daemon       0 SW<  [khelper]

  106 daemon       0 SW   [sync_supers]

  108 daemon       0 SW   [bdi-default]

  109 daemon       0 SW<  [kintegrityd]

  110 daemon       0 SW<  [crypto]

  111 daemon       0 SW<  [kblockd]

  120 daemon       0 SW   [khubd]

  150 daemon       0 SW   [kswapd0]

  151 daemon       0 SW<  [vmstat]

  152 daemon       0 SW   [fsnotify_mark]

  294 daemon       0 SW   [kworker/3:1]

  299 daemon       0 SW   [kworker/2:1]

  375 daemon       0 SW<  [deferwq]

  443 daemon     228 S    butcheck -t 10

  445 daemon    1732 S    haveged -r 0 -v 0 -w 1024 -d 32 -i 32

  454 daemon    1772 S    /bin/sh

  953 nobody    1776 S    dnsmasq -N -c 512 --dns-forward-max=384 --no-poll --all-servers --clear-on-reload --leasefile-ro -u nobod

  954 daemon    1760 S<   watchdog -T 120 -t 10 -F /dev/watchdog

 1578 daemon       0 SW   [kworker/u:2]

 2157 daemon       0 SW   [RtmpCmdQTask]

 2158 daemon       0 SW   [RtmpMlmeTask]

 2159 daemon       0 SW   [kworker/1:2]

 2169 daemon       0 SW   [RtmpCmdQTask]

 3053 daemon    1760 S    ntpd -d -p 192.168.1.1

 3382 daemon    4620 S    arpwatch -N -f /tmp/arp.dat -i br0

 3416 daemon    1768 S    inetd -R 30 -q 64

 3709 daemon    1144 S    irqbalance --banirq=64 --banirq=65 --banirq=66 --banirq=67 --banirq=68 --banirq=69 --banirq=70 --banirq=7

 3818 daemon   14180 S    nginx -g user iddi ;

 3819 daemon   14360 S    nginx -g user iddi ;

 3861 daemon    1760 S    klogd

 3862 daemon    1760 S    syslogd -b0 -s100 -l8 -R 192.168.1.38 -D -L

 3867 daemon    1400 R    /bin/dropbear -i -R -K 60 -I 43200 -j

 3868 daemon    1772 S    -sh

 3875 daemon    1764 R    ps w

[homeAP@/]#

 

Ну вот что видим. Что роутерная часть запущена корректно, из буфера оно логи выгребает и вполне локально их складывает, значит и посылает в сторону -R 192.168.1.38

Порт 514 UDP по дефолту, на сервере надеюсь тот же?

В общем проверяем дальше доступность сервера логирования с роутера. Можно tcpdump`ом по 514 порту посмотреть льётся что-то или нет. Всяко льётся т.к. туда ьётся по сути тоже самое что и локально (ключ -L).

Скорее всего локально проблем нет, по логу криминала не увидел.

В конфиге визуально в лоб тоже не вижу прям чего-то страшного за исключением зачем-то повырубленных оффлоадов, перевода с codel на pfifo, зачем-то включенного фильтра в INPUT (ну тут фиг знает, оптварь и что-то локальное стоит?) и т.д. и т.п.

Грубо говоря со стороны роутера визуально проблем нет. tcpdump`ом глянуть что пукает логами в нужную сторону и успокоиться на тему роутерной части и начинать смотреть что с обратной стороны не так или по пути.

По шагам проверяем дальше. Не лишним будет загуглить на предмет нет ли проблем с совместимостью busybox syslogd с вашим remote syslog севрвером. У себя использую r-syslog и syslog-ng проблем не замечал.

Послать чего-нить в сислог на железке можно например так logger -p8 TEST.

P.S. Для логов используем code insert в редакторе.

спасибо, разобрался

Чего было-то? Ну что бы народ в будущем по граблям не ходил?

проблема конфигурации на стороне сервера, китайские товарищи при включенном ipv6 генерили конфиг для syslog только с udp6

Прелесть какая...

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

Дык никто и не скрывал вроде. Тут борьба 2х миров. Требований в тендерах (чистый текстовый конфиг) и тотальной безопасности. Благо железки суть одноюзерьные. А все возможные варианты аля CWMP опровождаются у нас сразу оповещением юзверя, что возможен доступ 3их лиц (операторов например). Грубо говоря сами не пустите - никто не узнает.

Т.е. само по себе хранение паролей as is проблемой не является пока доступа нет и не предвидиться.

При сохранении да, надо наверное выкусывать, однако драйверу хэши не отдашь и на радио один фиг открытым текстом будут.

В общем не пускайте никого на свою железку, используйте уникальные, криптостойкие пароли, ну и при публикации конфигова да стоит помнить об этом моменте. Благо сложностей немного.

Было когда-то в туду сделать кнопку аля отправить репорт, ну что бы сразу без всего лишнего. Надо поднять чутка в роадмапе это дело.

Если вы нашли ошибку, пожалуйста, выделите фрагмент текста и нажмите Ctrl+Enter.

Сообщить об опечатке

Текст, который будет отправлен нашим редакторам: