1

(14 odpowiedzi, napisanych Oprogramowanie)

To tak stabilnie na tym dachu działa, że zapomniałem, że coś tam jest w ogóle.

2

(27 odpowiedzi, napisanych Inne)

Ja u siebie mam banana pro, kupiłem żeby zobaczyć z czym to się je i dla mnie dramat. SDK nie było, o supporcie od producenta można pomarzyć. Aż dziwne, że firmy robią na tym komercyjne projekty.

3

(14 odpowiedzi, napisanych Oprogramowanie)

Problem namierzony, nie dawało mi to spokoju i mimo, że po ustawieniu ręcznych adresów wszystko chodziło to przeanalizowałem jeszcze raz logi i tknęło mnie coś przy

user.notice dnsmasq: found already running DHCP-server on interface 'br-lan' refusing to start, use 'option force 1' to override

Przypomniałem sobie, że na dachu mam podłączonego wt3020, który jest kombajnem dla mojej stacji pogodowej. Po odłączeniu go od głównego routera tj. n750 server dhcp w końcu zaczął przydzielać poprawne adresy.

4

(14 odpowiedzi, napisanych Oprogramowanie)

Nie zmieniałem nic na klientach. Od czasu aktualizacji I zmianie adresu klienci nie otrzymują poprawnych adresów. Gdy zmienię na defaultowy to wszystko wraca do normy. Gdyby taki objaw był tylko na omawianym telefonie to szukał bym na nim przyczyny, ale nie nieprawidłowa adresacja dotyczy wszystkiego, od laptopów po telewizory.

5

(14 odpowiedzi, napisanych Oprogramowanie)

Wszędzie w klientach jest wymuszone dhcp, nic w tej kwestii nie było zmieniane. Spróbuje najwyżej skompilować latesta i na nim sprawdzić. Dzięki za pomoc.

6

(14 odpowiedzi, napisanych Oprogramowanie)

root@LEDE:~# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:90:A9:0B:A5:0B  
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::290:a9ff:fe0b:a50b/64 Scope:Link
          inet6 addr: fd42:91a4:9528::1/60 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6108 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5992 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:549504 (536.6 KiB)  TX bytes:4711439 (4.4 MiB)

eth0      Link encap:Ethernet  HWaddr 00:90:A9:0B:A5:0B  
          inet6 addr: fe80::290:a9ff:fe0b:a50b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:714 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2503 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:61534 (60.0 KiB)  TX bytes:202411 (197.6 KiB)
          Interrupt:4 

eth0.1    Link encap:Ethernet  HWaddr 00:90:A9:0B:A5:0B  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:714 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2474 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:48682 (47.5 KiB)  TX bytes:189061 (184.6 KiB)

eth0.2    Link encap:Ethernet  HWaddr 00:90:A9:0B:A5:0A  
          inet6 addr: fe80::290:a9ff:fe0b:a50a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:2322 (2.2 KiB)

eth1      Link encap:Ethernet  HWaddr 0C:5B:8F:27:9A:64  
          inet addr:192.168.8.100  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: fe80::e5b:8fff:fe27:9a64/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4208 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2952 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3960777 (3.7 MiB)  TX bytes:330978 (323.2 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:650 errors:0 dropped:0 overruns:0 frame:0
          TX packets:650 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:42920 (41.9 KiB)  TX bytes:42920 (41.9 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:90:A9:0B:A5:0B  
          inet6 addr: fe80::290:a9ff:fe0b:a50b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7591 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7299 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:742928 (725.5 KiB)  TX bytes:5012465 (4.7 MiB)

wlan1     Link encap:Ethernet  HWaddr 00:90:A9:0B:A5:0D  
          inet6 addr: fe80::290:a9ff:fe0b:a50d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:941 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:92200 (90.0 KiB)

root@LEDE:~# 
root@LEDE:~# cat /var/etc/dnsmasq*
# auto-generated config file from /etc/config/dhcp
conf-file=/etc/dnsmasq.conf
dhcp-authoritative
domain-needed
localise-queries
read-ethers
bogus-priv
expand-hosts
local-service
domain=lan
server=/lan/
dhcp-leasefile=/tmp/dhcp.leases
resolv-file=/tmp/resolv.conf.auto
stop-dns-rebind
rebind-localhost-ok
rebind-domain-ok=free.aero2.net.pl
dhcp-broadcast=tag:needs-broadcast
addn-hosts=/tmp/hosts
conf-dir=/tmp/dnsmasq.d
user=dnsmasq
group=dnsmasq




dhcp-range=lan,192.168.2.100,192.168.2.249,255.255.255.0,12h
no-dhcp-interface=eth1
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.000000] Linux version 4.4.112 (cezary@eko.one.pl) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3785-ceea0ac) ) #0 Fri Jan 26 07:37:28 2018
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.000000] MyLoader: sysp=00000000, boardp=00000000, parts=00000000
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] bootconsole [early0] enabled
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] SoC: Atheros AR9344 rev 2
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Determined physical RAM map:
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000]  memory: 08000000 @ 00000000 (usable)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Initrd not found or empty - disabling initrd
Thu Mar  8 18:25:32 2018 kern.warn kernel: [    0.000000] No valid device tree found, continuing without
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Zone ranges:
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Movable zone start for each node
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Early memory node ranges
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.000000] On node 0 totalpages: 32768
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat 804384d0, node_mem_map 81000000
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.000000]   Normal zone: 256 pages used for memmap
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.000000]   Normal zone: 32768 pages, LIFO batch:7
Thu Mar  8 18:25:32 2018 kern.warn kernel: [    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Thu Mar  8 18:25:32 2018 kern.warn kernel: [    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.000000] Kernel command line:  board=MYNET-N750 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(devdata)ro,64k(devconf)ro,15872k(firmware),64k(radiocfg)ro console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Writing ErrCtl register=00000000
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Readback ErrCtl register=00000000
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Memory: 124944K/131072K available (3122K kernel code, 162K rwdata, 780K rodata, 280K init, 205K bss, 6128K reserved, 0K cma-reserved)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] NR_IRQS:51
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] Clocks: CPU:560.000MHz, DDR:480.000MHz, AHB:240.000MHz, Ref:40.000MHz
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6825930166 ns
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.000009] sched_clock: 32 bits at 280MHz, resolution 3ns, wraps every 7669584382ns
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.008296] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.081137] pid_max: default: 32768 minimum: 301
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.086175] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.093230] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.103141] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.113661] futex hash table entries: 256 (order: -1, 3072 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.121320] NET: Registered protocol family 16
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.127482] MIPS: machine is WD My Net N750
Thu Mar  8 18:25:32 2018 kern.warn kernel: [    0.159297] registering PCI controller with io_map_base unset
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.409374] PCI host bridge to bus 0000:00
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.413744] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.421102] pci_bus 0000:00: root bus resource [io  0x0000]
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.427033] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.434267] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.442736] pci 0000:00:00.0: [168c:0030] type 00 class 0x028000
Thu Mar  8 18:25:32 2018 kern.err kernel: [    0.442767] pci 0000:00:00.0: invalid calibration data
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.448275] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.448334] pci 0000:00:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.448402] pci 0000:00:00.0: supports D1
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.448419] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.448644] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.448679] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit]
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.456475] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref]
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.464194] pci 0000:00:00.0: using irq 40 for pin 1
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.470326] clocksource: Switched to clocksource MIPS
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.477025] NET: Registered protocol family 2
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.482563] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.489986] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.496797] TCP: Hash tables configured (established 1024 bind 1024)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.503646] UDP hash table entries: 256 (order: 0, 4096 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.509872] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.516845] NET: Registered protocol family 1
Thu Mar  8 18:25:32 2018 kern.debug kernel: [    0.521602] PCI: CLS 0 bytes, default 32
Thu Mar  8 18:25:32 2018 kern.warn kernel: [    0.526123] Crashlog allocated RAM at address 0x3f00000
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.546121] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.552389] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.565301] io scheduler noop registered
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.569484] io scheduler deadline registered (default)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.575264] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.584757] console [ttyS0] disabled
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.608628] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a 16550A
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.617817] console [ttyS0] enabled
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.625239] bootconsole [early0] disabled
Thu Mar  8 18:25:32 2018 kern.warn kernel: [    0.638529] m25p80 spi0.0: found mx25l12805d, expected m25p80
Thu Mar  8 18:25:32 2018 kern.info kernel: [    0.644442] m25p80 spi0.0: mx25l12805d (16384 Kbytes)
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.649595] 6 cmdlinepart partitions found on MTD device spi0.0
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.655615] Creating 6 MTD partitions on "spi0.0":
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.660499] 0x000000000000-0x000000040000 : "u-boot"
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.667579] 0x000000040000-0x000000050000 : "u-boot-env"
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.674559] 0x000000050000-0x000000060000 : "devdata"
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.681278] 0x000000060000-0x000000070000 : "devconf"
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.687944] 0x000000070000-0x000000ff0000 : "firmware"
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.719301] 2 seama-fw partitions found on MTD device firmware
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.725256] 0x000000070040-0x0000001c0000 : "kernel"
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.731672] 0x0000001c0000-0x000000ff0000 : "rootfs"
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.738258] mtd: device 6 (rootfs) set to be root filesystem
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.744077] 1 squashfs-split partitions found on MTD device rootfs
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.750370] 0x000000660000-0x000000ff0000 : "rootfs_data"
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    0.757438] 0x000000ff0000-0x000001000000 : "radiocfg"
Thu Mar  8 18:25:32 2018 kern.info kernel: [    1.771727] switch0: Atheros AR8327 rev. 2 switch registered on ag71xx-mdio.0
Thu Mar  8 18:25:32 2018 kern.info kernel: [    2.382027] libphy: ag71xx_mdio: probed
Thu Mar  8 18:25:32 2018 kern.info kernel: [    3.968906] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd033, driver=Atheros AR8216/AR8236/AR8316]
Thu Mar  8 18:25:32 2018 kern.info kernel: [    3.980394] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
Thu Mar  8 18:25:32 2018 kern.info kernel: [    3.988805] NET: Registered protocol family 10
Thu Mar  8 18:25:32 2018 kern.info kernel: [    3.997009] NET: Registered protocol family 17
Thu Mar  8 18:25:32 2018 kern.info kernel: [    4.001655] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Thu Mar  8 18:25:32 2018 kern.info kernel: [    4.014608] 8021q: 802.1Q VLAN Support v1.8
Thu Mar  8 18:25:32 2018 kern.info kernel: [    4.020626] hctosys: unable to open rtc device (rtc0)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    4.030505] VFS: Mounted root (squashfs filesystem) readonly on device 31:6.
Thu Mar  8 18:25:32 2018 kern.info kernel: [    4.038869] Freeing unused kernel memory: 280K
Thu Mar  8 18:25:32 2018 user.info kernel: [    5.104525] init: Console is alive
Thu Mar  8 18:25:32 2018 user.info kernel: [    5.108179] init: - watchdog -
Thu Mar  8 18:25:32 2018 user.info kernel: [    6.635244] kmodloader: loading kernel modules from /etc/modules-boot.d/*
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.771728] usbcore: registered new interface driver usbfs
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.777391] usbcore: registered new interface driver hub
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.782916] usbcore: registered new device driver usb
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    6.827800] SCSI subsystem initialized
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.837573] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.845830] ehci-platform: EHCI generic platform driver
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.851285] ehci-platform ehci-platform: EHCI Host Controller
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.857161] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.867292] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.890365] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.897613] hub 1-0:1.0: USB hub found
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.901770] hub 1-0:1.0: 1 port detected
Thu Mar  8 18:25:32 2018 kern.info kernel: [    6.910251] usbcore: registered new interface driver usb-storage
Thu Mar  8 18:25:32 2018 user.info kernel: [    6.917104] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Thu Mar  8 18:25:32 2018 user.info kernel: [    6.927363] init: - preinit -
Thu Mar  8 18:25:32 2018 kern.info kernel: [    7.400406] usb 1-1: new high-speed USB device number 2 using ehci-platform
Thu Mar  8 18:25:32 2018 kern.info kernel: [    7.479950] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu Mar  8 18:25:32 2018 kern.info kernel: [    7.643683] hub 1-1:1.0: USB hub found
Thu Mar  8 18:25:32 2018 kern.info kernel: [    7.650559] hub 1-1:1.0: 4 ports detected
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    7.670824] random: procd: uninitialized urandom read (4 bytes read, 13 bits of entropy available)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    7.940347] usb 1-1.2: new high-speed USB device number 3 using ehci-platform
Thu Mar  8 18:25:32 2018 kern.info kernel: [    8.198695] usb-storage 1-1.2:1.2: USB Mass Storage device detected
Thu Mar  8 18:25:32 2018 kern.info kernel: [    8.205733] scsi host0: usb-storage 1-1.2:1.2
Thu Mar  8 18:25:32 2018 kern.info kernel: [    9.091583] eth0: link up (1000Mbps/Full duplex)
Thu Mar  8 18:25:32 2018 kern.info kernel: [    9.096351] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    9.216181] scsi 0:0:0:0: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
Thu Mar  8 18:25:32 2018 kern.notice kernel: [    9.229242] sd 0:0:0:0: [sda] Attached SCSI removable disk
Thu Mar  8 18:25:32 2018 user.info kernel: [    9.788505] mount_root: loading kmods from internal overlay
Thu Mar  8 18:25:32 2018 user.info kernel: [    9.830555] kmodloader: loading kernel modules from //etc/modules-boot.d/*
Thu Mar  8 18:25:32 2018 user.info kernel: [    9.839126] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   10.124215] jffs2: notice: (461) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Thu Mar  8 18:25:32 2018 user.info kernel: [   10.140316] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
Thu Mar  8 18:25:32 2018 user.info kernel: [   10.150580] block: extroot: not configured
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   10.194025] jffs2: notice: (458) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Thu Mar  8 18:25:32 2018 user.info kernel: [   10.378229] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
Thu Mar  8 18:25:32 2018 user.info kernel: [   10.394831] block: extroot: not configured
Thu Mar  8 18:25:32 2018 user.info kernel: [   10.399876] mount_root: switching to jffs2 overlay
Thu Mar  8 18:25:32 2018 user.warn kernel: [   10.412379] urandom-seed: Seeding with /etc/urandom.seed
Thu Mar  8 18:25:32 2018 kern.info kernel: [   10.533797] eth0: link down
Thu Mar  8 18:25:32 2018 user.info kernel: [   10.546740] procd: - early -
Thu Mar  8 18:25:32 2018 user.info kernel: [   10.549762] procd: - watchdog -
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.127684] random: jshn: uninitialized urandom read (4 bytes read, 21 bits of entropy available)
Thu Mar  8 18:25:32 2018 user.info kernel: [   11.292234] procd: - watchdog -
Thu Mar  8 18:25:32 2018 user.info kernel: [   11.295684] procd: - ubus -
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.438671] random: jshn: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.692466] random: jshn: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.704060] random: ubusd: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.720502] random: ubusd: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.729832] random: ubus: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.739064] random: ubusd: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.748597] random: ubusd: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
Thu Mar  8 18:25:32 2018 kern.notice kernel: [   11.762096] random: ubusd: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
Thu Mar  8 18:25:32 2018 user.info kernel: [   11.772000] procd: - init -
Thu Mar  8 18:25:32 2018 user.info kernel: [   12.879624] kmodloader: loading kernel modules from /etc/modules.d/*
Thu Mar  8 18:25:32 2018 kern.info kernel: [   12.930153] tun: Universal TUN/TAP device driver, 1.6
Thu Mar  8 18:25:32 2018 kern.info kernel: [   12.935336] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Thu Mar  8 18:25:32 2018 kern.info kernel: [   12.972006] ip6_tables: (C) 2000-2006 Netfilter Core Team
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.011988] fuse init (API version 7.23)
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.026003] usbcore: registered new interface driver cdc_acm
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.031791] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.061948] usbcore: registered new interface driver cdc_wdm
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.082543] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.090709] Backport generated by backports.git backports-20160324-13-g24da7d3c
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.123095] ip_tables: (C) 2000-2006 Netfilter Core Team
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.147812] nf_conntrack version 0.5.0 (1956 buckets, 7824 max)
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.249887] usbcore: registered new interface driver usblp
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.285259] usbcore: registered new interface driver usbserial
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.291333] usbcore: registered new interface driver usbserial_generic
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.298047] usbserial: USB Serial support registered for generic
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.354534] xt_time: kernel timezone is -0000
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.425681] cdc_ether 1-1.2:1.0 eth1: register 'cdc_ether' at usb-ehci-platform-1.2, CDC Ethernet Device, 0c:5b:8f:27:9a:64
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.437182] usbcore: registered new interface driver cdc_ether
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.461585] usbcore: registered new interface driver cdc_ncm
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.527668] usbcore: registered new interface driver huawei_cdc_ncm
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.654002] PPP generic driver version 2.4.2
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.670284] NET: Registered protocol family 24
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.682708] usbcore: registered new interface driver qmi_wwan
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.702998] usbcore: registered new interface driver rndis_host
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.722650] usbcore: registered new interface driver sierra
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.728411] usbserial: USB Serial support registered for Sierra USB modem
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.752566] usbcore: registered new interface driver sierra_net
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.822629] usbcore: registered new interface driver cdc_mbim
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.844154] usbcore: registered new interface driver option
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.849908] usbserial: USB Serial support registered for GSM modem (1-port)
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.885266] usbcore: registered new interface driver qcserial
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.891267] usbserial: USB Serial support registered for Qualcomm USB modem
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.933593] ath: EEPROM regdomain: 0x0
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.933612] ath: EEPROM indicates default country code should be used
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.933623] ath: doing EEPROM country->regdmn map search
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.933644] ath: country maps to regdmn code: 0x3a
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.933655] ath: Country alpha2 being used: US
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.933665] ath: Regpair used: 0x3a
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.945776] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.950480] ieee80211 phy0: Atheros AR9340 Rev:2 mem=0xb8100000, irq=47
Thu Mar  8 18:25:32 2018 kern.warn kernel: [   13.957372] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.968489] ath: EEPROM regdomain: 0x0
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.968506] ath: EEPROM indicates default country code should be used
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.968516] ath: doing EEPROM country->regdmn map search
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.968537] ath: country maps to regdmn code: 0x3a
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.968548] ath: Country alpha2 being used: US
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.968558] ath: Regpair used: 0x3a
Thu Mar  8 18:25:32 2018 kern.debug kernel: [   13.978636] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Thu Mar  8 18:25:32 2018 kern.info kernel: [   13.983396] ieee80211 phy1: Atheros AR9300 Rev:3 mem=0xb0000000, irq=40
Thu Mar  8 18:25:32 2018 user.info kernel: [   14.070766] kmodloader: done loading kernel modules from /etc/modules.d/*
Thu Mar  8 18:25:35 2018 user.notice : Added device handler type: 8021ad
Thu Mar  8 18:25:35 2018 user.notice : Added device handler type: 8021q
Thu Mar  8 18:25:35 2018 user.notice : Added device handler type: macvlan
Thu Mar  8 18:25:35 2018 user.notice : Added device handler type: bridge
Thu Mar  8 18:25:35 2018 user.notice : Added device handler type: Network device
Thu Mar  8 18:25:35 2018 user.notice : Added device handler type: tunnel
Thu Mar  8 18:25:36 2018 daemon.err block: /dev/mtdblock6 is already mounted on /rom
Thu Mar  8 18:25:36 2018 daemon.err block: /dev/mtdblock7 is already mounted on /overlay
Thu Mar  8 18:25:37 2018 authpriv.info dropbear[1159]: Not backgrounding
Thu Mar  8 18:25:41 2018 kern.info kernel: [   25.415198] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu Mar  8 18:25:41 2018 kern.info kernel: [   25.435229] device eth0.1 entered promiscuous mode
Thu Mar  8 18:25:41 2018 kern.info kernel: [   25.440102] device eth0 entered promiscuous mode
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'lan' is enabled
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'lan' is setting up now
Thu Mar  8 18:25:41 2018 kern.info kernel: [   25.457175] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'lan' is now up
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'loopback' is enabled
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'loopback' is now up
Thu Mar  8 18:25:41 2018 kern.err kernel: [   25.517527] cdc_ether 1-1.2:1.0 eth1: kevent 12 may have been dropped
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'wan' is enabled
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'wan6' is enabled
Thu Mar  8 18:25:41 2018 kern.info kernel: [   25.533723] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready
Thu Mar  8 18:25:41 2018 daemon.info odhcpd[1110]: Raising SIGUSR1 due to address change on br-lan
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Network device 'lo' link is up
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'loopback' has link connectivity 
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Network device 'eth1' link is up
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'wan' has link connectivity 
Thu Mar  8 18:25:41 2018 daemon.notice netifd: Interface 'wan' is setting up now
Thu Mar  8 18:25:42 2018 daemon.notice netifd: wan (1295): udhcpc: started, v1.25.1
Thu Mar  8 18:25:42 2018 daemon.info odhcpd[1110]: Using a RA lifetime of 0 seconds on br-lan
Thu Mar  8 18:25:42 2018 daemon.notice odhcpd[1110]: Failed to send to ff02::1%br-lan (Address not available)
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050530] ath: EEPROM regdomain: 0x8268
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050551] ath: EEPROM indicates we should expect a country code
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050566] ath: doing EEPROM country->regdmn map search
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050580] ath: country maps to regdmn code: 0x37
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050593] ath: Country alpha2 being used: PL
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050603] ath: Regpair used: 0x37
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050616] ath: regdomain 0x8268 dynamically updated by user
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050703] ath: EEPROM regdomain: 0x8268
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050713] ath: EEPROM indicates we should expect a country code
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050727] ath: doing EEPROM country->regdmn map search
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050739] ath: country maps to regdmn code: 0x37
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050750] ath: Country alpha2 being used: PL
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050760] ath: Regpair used: 0x37
Thu Mar  8 18:25:42 2018 kern.debug kernel: [   27.050772] ath: regdomain 0x8268 dynamically updated by user
Thu Mar  8 18:25:42 2018 daemon.notice netifd: wan (1295): udhcpc: sending discover
Thu Mar  8 18:25:42 2018 daemon.notice netifd: wan (1295): udhcpc: sending select for 192.168.8.100
Thu Mar  8 18:25:42 2018 daemon.notice netifd: wan (1295): udhcpc: lease of 192.168.8.100 obtained, lease time 86400
Thu Mar  8 18:25:42 2018 daemon.notice netifd: radio0 (1244): sh: acs_survey: out of range
Thu Mar  8 18:25:43 2018 kern.info kernel: [   27.351656] eth0: link up (1000Mbps/Full duplex)
Thu Mar  8 18:25:43 2018 kern.info kernel: [   27.356430] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Mar  8 18:25:43 2018 daemon.notice netifd: Network device 'eth0' link is up
Thu Mar  8 18:25:43 2018 kern.info kernel: [   27.423737] br-lan: port 1(eth0.1) entered forwarding state
Thu Mar  8 18:25:43 2018 kern.info kernel: [   27.429452] br-lan: port 1(eth0.1) entered forwarding state
Thu Mar  8 18:25:43 2018 kern.info kernel: [   27.435253] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Thu Mar  8 18:25:43 2018 daemon.notice netifd: VLAN 'eth0.1' link is up
Thu Mar  8 18:25:43 2018 daemon.notice netifd: VLAN 'eth0.2' link is up
Thu Mar  8 18:25:43 2018 daemon.notice netifd: Interface 'wan6' has link connectivity 
Thu Mar  8 18:25:43 2018 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Mar  8 18:25:43 2018 daemon.notice netifd: bridge 'br-lan' link is up
Thu Mar  8 18:25:43 2018 daemon.notice netifd: Interface 'lan' has link connectivity 
Thu Mar  8 18:25:43 2018 kern.info kernel: [   27.580435] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Thu Mar  8 18:25:43 2018 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu Mar  8 18:25:43 2018 daemon.notice netifd: Interface 'wan' is now up
Thu Mar  8 18:25:44 2018 daemon.info odhcpd[1110]: Using a RA lifetime of 0 seconds on br-lan
Thu Mar  8 18:25:44 2018 daemon.notice odhcpd[1110]: Failed to send to ff02::1%br-lan (Address not available)
Thu Mar  8 18:25:45 2018 kern.info kernel: [   29.420353] br-lan: port 1(eth0.1) entered forwarding state
Thu Mar  8 18:25:45 2018 daemon.err odhcp6c[1436]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
Thu Mar  8 18:25:45 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Thu Mar  8 18:25:46 2018 kern.info kernel: [   30.338990] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Thu Mar  8 18:25:46 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Thu Mar  8 18:25:46 2018 kern.info kernel: [   30.407549] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Thu Mar  8 18:25:46 2018 kern.info kernel: [   30.474267] device wlan0 entered promiscuous mode
Thu Mar  8 18:25:46 2018 kern.info kernel: [   30.498424] device wlan1 entered promiscuous mode
Thu Mar  8 18:25:46 2018 kern.info kernel: [   30.503362] br-lan: port 3(wlan1) entered forwarding state
Thu Mar  8 18:25:46 2018 kern.info kernel: [   30.508956] br-lan: port 3(wlan1) entered forwarding state
Thu Mar  8 18:25:46 2018 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Mar  8 18:25:46 2018 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Thu Mar  8 18:25:46 2018 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ACS
Thu Mar  8 18:25:46 2018 daemon.notice hostapd: wlan0: ACS-STARTED 
Thu Mar  8 18:25:46 2018 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Mar  8 18:25:46 2018 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Thu Mar  8 18:25:46 2018 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ACS
Thu Mar  8 18:25:46 2018 daemon.notice hostapd: wlan1: ACS-STARTED 
Thu Mar  8 18:25:47 2018 kern.info kernel: [   31.340450] br-lan: port 3(wlan1) entered disabled state
Thu Mar  8 18:25:48 2018 daemon.info procd: - init complete -
Thu Mar  8 18:25:49 2018 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Mon Mar 12 21:05:03 2018 user.notice ddns-scripts[1801]: myddns_ipv4: PID '1801' started at 2018-03-12 21:05
Mon Mar 12 21:05:03 2018 user.warn ddns-scripts[1801]: myddns_ipv4: Service section disabled! - TERMINATE
Mon Mar 12 21:05:03 2018 user.warn ddns-scripts[1801]: myddns_ipv4: PID '1801' exit WITH ERROR '1' at 2018-03-12 21:05
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: started, version 2.78 cachesize 150
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: DNS service limited to local subnets
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq-dhcp[1896]: DHCP, IP range 192.168.2.100 -- 192.168.2.249, lease time 12h
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: using local addresses only for domain lan
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: reading /tmp/resolv.conf.auto
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: using local addresses only for domain lan
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: using nameserver 192.168.8.1#53
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: using nameserver 192.168.8.1#53
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: read /etc/hosts - 4 addresses
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: read /tmp/hosts/odhcpd - 0 addresses
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq[1896]: read /tmp/hosts/dhcp.cfg02411c - 2 addresses
Mon Mar 12 21:05:05 2018 daemon.info dnsmasq-dhcp[1896]: read /etc/ethers - 0 addresses
Mon Mar 12 21:05:06 2018 daemon.notice hostapd: wlan0: ACS-COMPLETED freq=2412 channel=1
Mon Mar 12 21:05:06 2018 daemon.notice hostapd: wlan0: interface state ACS->HT_SCAN
Mon Mar 12 21:05:08 2018 daemon.notice hostapd: 20/40 MHz operation not permitted on channel pri=1 sec=5 based on overlapping BSSes
Mon Mar 12 21:05:08 2018 daemon.err hostapd: Using interface wlan0 with hwaddr 00:90:a9:0b:a5:0b and ssid "WD-N750"
Mon Mar 12 21:05:08 2018 kern.info kernel: [   39.766015] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mon Mar 12 21:05:08 2018 kern.info kernel: [   39.772670] br-lan: port 2(wlan0) entered forwarding state
Mon Mar 12 21:05:08 2018 kern.info kernel: [   39.778312] br-lan: port 2(wlan0) entered forwarding state
Mon Mar 12 21:05:08 2018 daemon.notice hostapd: wlan0: interface state HT_SCAN->ENABLED
Mon Mar 12 21:05:08 2018 daemon.notice hostapd: wlan0: AP-ENABLED 
Mon Mar 12 21:05:08 2018 daemon.notice netifd: Network device 'wlan0' link is up
Mon Mar 12 21:05:10 2018 daemon.notice hostapd: wlan1: ACS-COMPLETED freq=5220 channel=44
Mon Mar 12 21:05:10 2018 daemon.notice hostapd: wlan1: interface state ACS->HT_SCAN
Mon Mar 12 21:05:10 2018 daemon.err hostapd: Using interface wlan1 with hwaddr 00:90:a9:0b:a5:0d and ssid "WD-N750-5GHz"
Mon Mar 12 21:05:10 2018 kern.info kernel: [   41.770343] br-lan: port 2(wlan0) entered forwarding state
Mon Mar 12 21:05:10 2018 kern.info kernel: [   41.951357] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Mon Mar 12 21:05:10 2018 kern.info kernel: [   41.958005] br-lan: port 3(wlan1) entered forwarding state
Mon Mar 12 21:05:10 2018 kern.info kernel: [   41.963670] br-lan: port 3(wlan1) entered forwarding state
Mon Mar 12 21:05:10 2018 daemon.notice hostapd: wlan1: interface state HT_SCAN->ENABLED
Mon Mar 12 21:05:10 2018 daemon.notice hostapd: wlan1: AP-ENABLED 
Mon Mar 12 21:05:10 2018 daemon.notice netifd: Network device 'wlan1' link is up
Mon Mar 12 21:05:11 2018 daemon.info hostapd: wlan0: STA 80:ea:23:12:ca:60 IEEE 802.11: authenticated
Mon Mar 12 21:05:11 2018 daemon.info hostapd: wlan0: STA 80:ea:23:12:ca:60 IEEE 802.11: associated (aid 1)
Mon Mar 12 21:05:11 2018 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 80:ea:23:12:ca:60
Mon Mar 12 21:05:11 2018 daemon.info hostapd: wlan0: STA 80:ea:23:12:ca:60 WPA: pairwise key handshake completed (RSN)
Mon Mar 12 21:05:12 2018 kern.info kernel: [   43.960361] br-lan: port 3(wlan1) entered forwarding state
Mon Mar 12 21:05:14 2018 daemon.info odhcpd[1110]: Using a RA lifetime of 0 seconds on br-lan
Mon Mar 12 21:05:14 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:05:14 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:05:15 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:05:15 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:05:16 2018 daemon.info hostapd: wlan0: STA 74:2f:68:9d:4d:a4 IEEE 802.11: authenticated
Mon Mar 12 21:05:16 2018 daemon.info hostapd: wlan0: STA 74:2f:68:9d:4d:a4 IEEE 802.11: associated (aid 2)
Mon Mar 12 21:05:16 2018 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 74:2f:68:9d:4d:a4
Mon Mar 12 21:05:16 2018 daemon.info hostapd: wlan0: STA 74:2f:68:9d:4d:a4 WPA: pairwise key handshake completed (RSN)
Mon Mar 12 21:05:16 2018 daemon.info dnsmasq-dhcp[1896]: DHCPREQUEST(br-lan) 192.168.2.161 74:2f:68:9d:4d:a4 
Mon Mar 12 21:05:16 2018 daemon.info dnsmasq-dhcp[1896]: DHCPACK(br-lan) 192.168.2.161 74:2f:68:9d:4d:a4 bartekk
Mon Mar 12 21:05:17 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:05:17 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:05:18 2018 kern.notice kernel: [   49.317371] random: nonblocking pool is initialized
Mon Mar 12 21:05:19 2018 daemon.info odhcpd[1110]: Using a RA lifetime of 0 seconds on br-lan
Mon Mar 12 21:05:19 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:05:19 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 000494bb969ec98f8fe3c27ecbab5bacd832 on br-lan: ok fd42:91a4:9528::1ce/128 
Mon Mar 12 21:05:20 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:05:21 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:05:21 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:05:25 2018 daemon.info hostapd: wlan0: STA 10:2a:b3:7b:2e:18 IEEE 802.11: authenticated
Mon Mar 12 21:05:25 2018 daemon.info hostapd: wlan0: STA 10:2a:b3:7b:2e:18 IEEE 802.11: associated (aid 3)
Mon Mar 12 21:05:25 2018 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 10:2a:b3:7b:2e:18
Mon Mar 12 21:05:25 2018 daemon.info hostapd: wlan0: STA 10:2a:b3:7b:2e:18 WPA: pairwise key handshake completed (RSN)
Mon Mar 12 21:05:26 2018 daemon.info odhcpd[1110]: Using a RA lifetime of 0 seconds on br-lan
Mon Mar 12 21:05:29 2018 daemon.info dnsmasq-dhcp[1896]: DHCPDISCOVER(br-lan) 10:2a:b3:7b:2e:18 
Mon Mar 12 21:05:29 2018 daemon.info dnsmasq-dhcp[1896]: DHCPOFFER(br-lan) 192.168.2.228 10:2a:b3:7b:2e:18 
Mon Mar 12 21:05:29 2018 daemon.info dnsmasq-dhcp[1896]: DHCPREQUEST(br-lan) 192.168.1.228 10:2a:b3:7b:2e:18 
Mon Mar 12 21:05:29 2018 daemon.info dnsmasq-dhcp[1896]: DHCPNAK(br-lan) 192.168.1.228 10:2a:b3:7b:2e:18 wrong server-ID
Mon Mar 12 21:05:29 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:05:29 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:05:30 2018 daemon.info hostapd: wlan0: STA 74:23:44:a8:e8:c1 IEEE 802.11: authenticated
Mon Mar 12 21:05:30 2018 daemon.info hostapd: wlan0: STA 74:23:44:a8:e8:c1 IEEE 802.11: associated (aid 4)
Mon Mar 12 21:05:30 2018 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 74:23:44:a8:e8:c1
Mon Mar 12 21:05:30 2018 daemon.info hostapd: wlan0: STA 74:23:44:a8:e8:c1 WPA: pairwise key handshake completed (RSN)
Mon Mar 12 21:05:31 2018 daemon.info odhcpd[1110]: Using a RA lifetime of 0 seconds on br-lan
Mon Mar 12 21:05:34 2018 daemon.info dnsmasq-dhcp[1896]: DHCPDISCOVER(br-lan) 74:23:44:a8:e8:c1 
Mon Mar 12 21:05:34 2018 daemon.info dnsmasq-dhcp[1896]: DHCPOFFER(br-lan) 192.168.2.222 74:23:44:a8:e8:c1 
Mon Mar 12 21:05:34 2018 daemon.info dnsmasq-dhcp[1896]: DHCPREQUEST(br-lan) 192.168.1.222 74:23:44:a8:e8:c1 
Mon Mar 12 21:05:34 2018 daemon.info dnsmasq-dhcp[1896]: DHCPNAK(br-lan) 192.168.1.222 74:23:44:a8:e8:c1 wrong server-ID
Mon Mar 12 21:05:36 2018 daemon.info dnsmasq[1896]: read /etc/hosts - 4 addresses
Mon Mar 12 21:05:36 2018 daemon.info dnsmasq[1896]: read /tmp/hosts/odhcpd - 0 addresses
Mon Mar 12 21:05:36 2018 daemon.info dnsmasq[1896]: read /tmp/hosts/dhcp.cfg02411c - 2 addresses
Mon Mar 12 21:05:36 2018 daemon.info dnsmasq-dhcp[1896]: read /etc/ethers - 0 addresses
Mon Mar 12 21:05:41 2018 daemon.warn dnsmasq[1896]: nameserver 192.168.8.1 refused to do a recursive query
Mon Mar 12 21:05:45 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:05:45 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:06:16 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:06:16 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:06:27 2018 authpriv.info dropbear[2721]: Child connection from 192.168.2.161:36616
Mon Mar 12 21:06:30 2018 authpriv.notice dropbear[2721]: Password auth succeeded for 'root' from 192.168.2.161:36616
Mon Mar 12 21:07:14 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:07:14 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:09:23 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:09:23 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:10:10 2018 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 74:23:44:a8:e8:c1
Mon Mar 12 21:10:21 2018 daemon.info odhcpd[1110]: Using a RA lifetime of 0 seconds on br-lan
Mon Mar 12 21:11:15 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:11:15 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
Mon Mar 12 21:13:08 2018 daemon.notice odhcpd[1110]: Got DHCPv6 request
Mon Mar 12 21:13:08 2018 daemon.warn odhcpd[1110]: DHCPV6 SOLICIT IA_NA from 0003000180ea2312ca60 on br-lan: ok fd42:91a4:9528::113/128 
root@LEDE:~# cat /tmp/dhcp.leases
1520928316 74:2f:68:9d:4d:a4 192.168.2.161 bartekk ff:f8:03:89:63:00:02:00:00:ab:11:38:49:a7:1c:a9:87:5c:5b

7

(14 odpowiedzi, napisanych Oprogramowanie)

Po restarcie tak samo, obraz czysty prosto od Ciebie.

8

(14 odpowiedzi, napisanych Oprogramowanie)

Zmieniam tak jak robiłem to od zawsze, w sekcji lan:

config interface 'lan'
    option type 'bridge'
    option ifname 'eth0.1'
    option proto 'static'
    option netmask '255.255.255.0'
    option ip6assign '60'
    option ipaddr '192.168.2.1'

Restart dnsmasq również był, do testów podłączyłem się telefonem i dostałem:

adres ip: 192.168.1.228
mask: 255.255.255.0
brama: 192.168.1.50

9

(14 odpowiedzi, napisanych Oprogramowanie)

Cześć, po dość długim okresie zaktualizowałem soft do LEDE Reboot 17.01-SNAPSHOT r3825-28483d4 i zauważyłem problem z dhcp'em gdy zmienię sobię domyślny adres lan ip na np. 192.168.2.1 to router dalej próbuje klientom przydzielać adresy z podsieci 192.168.1.x. Być może to ja mam zaćmienie, ale nie mam już pomysłu co może być nie tak.

10

(2 odpowiedzi, napisanych Oprogramowanie)

Do zestawu jeszcze addon do przeglądarki ze skrótami z vima i można w spokoju surfować.

11

(15 odpowiedzi, napisanych Oprogramowanie)

Trochę wyskoczę poza obszar LEDE, ale nie chcę kolejnego tematu zakładać. Wszystkie klienty łączą się w porządku, oprócz androida z openvpn:

lis 19 12:05:15 bartekk ovpn-server[815]: TLS Error: cannot locate HMAC in incoming packet from [AF_INET]37.109.33.159:3630
lis 19 12:05:16 bartekk ovpn-server[815]: TLS Error: cannot locate HMAC in incoming packet from [AF_INET]xx
lis 19 12:05:17 bartekk ovpn-server[815]: TLS Error: cannot locate HMAC in incoming packet from [AF_INET]xx
lis 19 12:05:18 bartekk ovpn-server[815]: TLS Error: cannot locate HMAC in incoming packet from [AF_INET]xx
lis 19 12:05:19 bartekk ovpn-server[815]: TLS Error: cannot locate HMAC in incoming packet from [AF_INET]xx
lis 19 12:05:20 bartekk ovpn-server[815]: TLS Error: cannot locate HMAC in incoming packet from [AF_INET]xx
lis 19 12:05:21 bartekk ovpn-server[815]: TLS Error: cannot locate HMAC in incoming packet from [AF_INETxxx
lis 19 12:05:22 bartekk ovpn-server[815]: TLS Error: cannot locate HMAC in incoming packet from [AF_INET]xxx

12

(15 odpowiedzi, napisanych Oprogramowanie)

Zgadza się smile Dzięki.

13

(15 odpowiedzi, napisanych Oprogramowanie)

khain napisał/a:

Jeśli chcecie odrzucić przekierowanie bramy domyślej przez tunel vpn to należy dodać

route-nopull

do konfigu tego klienta oraz wszystkie trasy, które narzuca serwer vpn (czyli do konfigu klienta dodać route z opcjami takimi jakie ma konfig serwera przy push route).

O które dokładnie chodzi??

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         ip_vpsa    0.0.0.0         UG    0      0        0 eth0
10.8.0.0        10.8.0.2        255.255.255.0   UG    0      0        0 tun0
10.8.0.2        0.0.0.0         255.255.255.255 UH    0      0        0 tun0
ip_vpsa    0.0.0.0         255.255.255.0   U     0      0        0 eth0

14

(15 odpowiedzi, napisanych Oprogramowanie)

Cześć,
potrzebuje pomocy z konfiguracją klienta openvpn na routerze n750. Schemat wygląda następująco:

Server openvpn na vps'ie -> różni klienci, których cały ruch idzie przez VPN + omawiany router, który nie ma przerzucać ruchu przez vpna a jedynie ma udostępniać dostęp do jego sieci lan. Wszystko wprawdzie działa, ale nie mam pojęcia jak wyłączyć na routerze, żeby cały ruch nie szedł przez vpna. Konfiguracja klienta:

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

key-direction 1
auth SHA256
# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one.  On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server?  Use the same setting as
# on the server.
;proto tcp
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote xxxxxxxxxxx
;remote my-server-2 1194

# Choose a random host from the remote
# list for load-balancing.  Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server.  Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
user nobody
group nogroup

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here.  See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets.  Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description.  It's best to use
# a separate .crt/.key file pair
# for each client.  A single ca
# file can be used for all clients.
#ca ca.crt
#cert client.crt
#key client.key

# Verify server certificate by checking that the
# certicate has the correct key usage set.
# This is an important precaution to protect against
# a potential attack discussed here:
#  http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the keyUsage set to
#   digitalSignature, keyEncipherment
# and the extendedKeyUsage to
#   serverAuth
# EasyRSA can do this for you.
remote-cert-tls xxxxx

# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x
cipher AES-128-CBC

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20

serwer

#################################################
# Sample OpenVPN 2.0 config file for            #
# multi-client server.                          #
#                                               #
# This file is for the server side              #
# of a many-clients <-> one-server              #
# OpenVPN configuration.                        #
#                                               #
# OpenVPN also supports                         #
# single-machine <-> single-machine             #
# configurations (See the Examples page         #
# on the web site for more info).               #
#                                               #
# This config should work on Windows            #
# or Linux/BSD systems.  Remember on            #
# Windows to quote pathnames and use            #
# double backslashes, e.g.:                     #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
#                                               #
# Comments are preceded with '#' or ';'         #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one.  On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.crt
key server.key  # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
xxxxx 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
push "dhcp-option DNS 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names.  This is recommended
# only for testing purposes.  For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
#   openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
tls-auth ta.key 0 # This file is secret
key-direction 0

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC        # Blowfish (default)
cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES
auth SHA256

# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nogroup

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).
;log         openvpn.log
;log-append  openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

15

(12 odpowiedzi, napisanych Inne)

geos napisał/a:

dobre pytanie. niestety z braku doświadczenia nie pomyślałem o czymś takim. wydaje mi się, że to było trochę utlenione bo problem miałem z dwoma pinami, pozostałe dwa przyjęły lut dość łatwo.

Miałeś problem, bo tym jednym pinem zapewne było GND i nie rozgrzałeś wystarczająco, dlatego nie złapało.

16

(13 odpowiedzi, napisanych Inne)

Na komputerze nie masz tyko kompilatora dla np. x86. Skompiluj to dla armv7 i wrzuć gotową binarkę tylko na zyxela. Wklej log z komputera czym pluje.

Update: Nie zauważyłem wyżej loga, masz napisane co go boli jeszcze:

configure: error: libavutil headers not found or not usable

Doinstaluj do systemu

libavutil-dev
libavcodec-dev
libavformat-dev
libjpeg-dev
libsqlite3-dev
libexif-dev
libid3tag0-dev
libbogg-dev
libvorbis-dev
libflac-dev

i puść jeszcze raz.

17

(13 odpowiedzi, napisanych Inne)

Tak poza tematem, czemu nie skompilujesz sobie tego na komputerze zamiast męczyć tego zyxela?

18

(4 odpowiedzi, napisanych Oprogramowanie)

Ja od siebie polecę dołożyć i kupić coś z normalnym wsparciem i SDK,

Play od jakiegoś czasu leci stanowczo w dół.

20

(101 odpowiedzi, napisanych Oprogramowanie)

Działa, dzięki bardzo smile

21

(101 odpowiedzi, napisanych Oprogramowanie)

Jeszcze pytanie, gdzie w LEDE to umieścić. W buildroocie mamy podział na poszczególne boardy, a tutaj?

22

(101 odpowiedzi, napisanych Oprogramowanie)

Nie tworząc drugiego tematu. Szukam i szukam w LEDE opcji nadpisania rootfsa tak jak to się robi w buildroocie, żeby przy kompilacji przerzucało do obrazu moje rzeczy ale nigdzie nie widzę tej opcji. Czy w LEDE zostało to wycięte?

23

(15 odpowiedzi, napisanych Oprogramowanie)

pepe2k napisał/a:

Tak na marginesie, nie masz żadnych obaw przed wgrywaniem/używaniem chińskiego firmware? Tyle się teraz mówi o prywatności w sieci, o wykradaniu danych osobowych i szpiegowaniu, a ludzie nadal trzymają na swoich routerach/telefonach/kamerach IP chińskie oprogramowanie, prawdopodobnie po brzegi wypełnione backdoorami wink

To tak jak z backupami, niepotrzebne do czasu...

24

(10 odpowiedzi, napisanych Oprogramowanie)

Myślałem o przetwornicy step-up, tylko że one z reguły też swoje biorą a jeśli to będzie zasilane z lipola i solara to trzeba uważać te pobory.  Co do napięć, to tak, patrząc na to zdjęcie

https://postimg.org/image/ngdt31tf7/

od góry po lewej pod micro usb mamy 1 przetwornice, do niej wchodzi 5v, wychodzi 1.54v, nastepnie idzie do tego ldo obok mcu i napiecia na pinach patrzac od lewej to 1.54v / 1.28v i 0.85v. W prawym dolnym rogu jest podobna przetwornica do ktorej wchodzi 1.2v i na wyjsciu daje 3v3.

25

(10 odpowiedzi, napisanych Oprogramowanie)

Pomierzyłem, sprawdziłem pod mikroskopem, marking układu do ZA4G1, google niestety nic nie mówi, na wyjściu daje 1.54v, które leci do ldo, który zbija je do 0.8V do mcu. Dysponuje ktoś jakimś schematem do tego, żeby przeanalizować i dobrać jakiś inny układ?