Jump to content

RT-AC1200G+ not giving name localhost to the DHCP lease


Guest house

Recommended Posts

Guest peter1819

Czy mógłby ktoś rzucić okiem na moje logi? To tylko 22 godziny. 

Spoiler

Nov  7 17:23:02 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 17:40:10 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 17:49:13 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 17:50:24 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 17:54:06 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 18:09:03 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:03:32 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:05:39 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:20:29 rc_service: httpd 213:notify_rc restart_wireless
Nov  7 20:20:49 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:20:51 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:20:59 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:21:02 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:21:25 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:21:35 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:23:03 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:23:06 rc_service: httpd 213:notify_rc reboot
Nov  7 20:23:07 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:23:07 kernel: Attempt to kill tasklet from interrupt
Nov  7 20:23:08 dnsmasq-dhcp[207]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:23:08 iTunes: daemon is stoped
Nov  7 20:23:08 FTP Server: daemon is stoped
Nov  7 20:23:08 Samba Server: smb daemon is stoped
Nov  7 20:23:08 kernel: gro disabled
Feb 14 01:00:10 syslogd started: BusyBox v1.17.4
Feb 14 01:00:10 kernel: klogd started: BusyBox v1.17.4 (2017-04-07 09:57:50 CST)
Feb 14 01:00:10 kernel: Linux version 2.6.36.4brcmarm (root@asus) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 PREEMPT Fri Apr 7 10:07:03 CST 2017
Feb 14 01:00:10 kernel: CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7f
Feb 14 01:00:10 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Feb 14 01:00:10 kernel: Machine: Northstar Prototype
Feb 14 01:00:10 kernel: Ignoring unrecognised tag 0x00000000
Feb 14 01:00:10 kernel: Memory policy: ECC disabled, Data cache writealloc
Feb 14 01:00:10 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Feb 14 01:00:10 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
Feb 14 01:00:10 kernel: Memory: 125464k/125464k available, 5608k reserved, 0K highmem
Feb 14 01:00:10 kernel: Virtual kernel memory layout:
Feb 14 01:00:10 kernel:     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Feb 14 01:00:10 kernel:     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
Feb 14 01:00:10 kernel:     DMA     : 0xf7e00000 - 0xffe00000   ( 128 MB)
Feb 14 01:00:10 kernel:     vmalloc : 0x88800000 - 0xf0000000   (1656 MB)
Feb 14 01:00:10 kernel:     lowmem  : 0x80000000 - 0x88000000   ( 128 MB)
Feb 14 01:00:10 kernel:     modules : 0x7f000000 - 0x80000000   (  16 MB)
Feb 14 01:00:10 kernel:       .init : 0x80008000 - 0x80039000   ( 196 kB)
Feb 14 01:00:10 kernel:       .text : 0x80039000 - 0x803e5000   (3760 kB)
Feb 14 01:00:10 kernel:       .data : 0x803fe000 - 0x80420f40   ( 140 kB)
Feb 14 01:00:10 kernel: Mount-cache hash table entries: 512
Feb 14 01:00:10 kernel: Found ST compatible serial flash with 256 64KB blocks; total size 16MB
Feb 14 01:00:10 kernel: ACP (Accelerator Coherence Port) enabled
Feb 14 01:00:10 kernel: bio: create slab <bio-0> at 0
Feb 14 01:00:10 kernel: PCI: no core
Feb 14 01:00:10 kernel: PCI: no core
Feb 14 01:00:10 kernel: PCI: Fixing up bus 0
Feb 14 01:00:10 kernel: PCI: Fixing up bus 1
Feb 14 01:00:10 kernel: PCI: scanning bus 0 !!!
Feb 14 01:00:11 kernel: PCI: Fixing up bus 0
Feb 14 01:00:11 kernel: VFS: Disk quotas dquot_6.5.2
Feb 14 01:00:11 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Feb 14 01:00:11 kernel: pflash: found no supported devices
Feb 14 01:00:11 kernel: bcmsflash: squash filesystem found at block 30
Feb 14 01:00:11 kernel: Creating 5 MTD partitions on "bcmsflash":
Feb 14 01:00:11 kernel: 0x000000000000-0x000000040000 : "boot"
Feb 14 01:00:11 kernel: 0x000000040000-0x000000ff0000 : "linux"
Feb 14 01:00:11 kernel: 0x0000001ef910-0x000000da0000 : "rootfs"
Feb 14 01:00:11 kernel: 0x000000da0000-0x000000ff0000 : "jffs2"
Feb 14 01:00:11 kernel: 0x000000ff0000-0x000001000000 : "nvram"
Feb 14 01:00:11 kernel: === PPTP init ===
Feb 14 01:00:11 kernel: Registering the dns_resolver key type
Feb 14 01:00:11 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Feb 14 01:00:11 kernel: emf: module license 'Proprietary' taints kernel.
Feb 14 01:00:11 kernel: Disabling lock debugging due to kernel taint
Feb 14 01:00:11 kernel: et_module_init: passivemode set to 0x0
Feb 14 01:00:11 kernel: et_module_init: txworkq set to 0x0
Feb 14 01:00:11 kernel: et_module_init: et_txq_thresh set to 0xce4
Feb 14 01:00:11 kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Feb 14 01:00:11 kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Feb 14 01:00:11 kernel: bcm_robo_enable_switch: EEE is disabled
Feb 14 01:00:11 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 kernel: wl_module_init: passivemode set to 0x0
Feb 14 01:00:11 kernel: wl_module_init: txworkq set to 0x0
Feb 14 01:00:11 kernel: PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
Feb 14 01:00:11 kernel: eth1: Broadcom BCM43227 802.11 Wireless Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 kernel: eth2: Broadcom BCM43c8 802.11 Wireless Controller 9.10.178.61 (r667680)
Feb 14 01:00:11 stop_nat_rules: apply the redirect_rules!
Feb 14 01:00:12 WAN Connection: ISP's DHCP did not function properly.
Feb 14 01:00:12 RT-AC1200G+: start httpd
Feb 14 01:00:12 RT-AC1200G+: firmware version: 9.0.0.4.382_10680-gc72d1c8
Feb 14 01:00:13 disk monitor: be idle
Feb 14 01:00:13 jffs2: valid logs(1)
Feb 14 01:00:13 hour monitor: daemon is starting
Feb 14 01:00:13 hour monitor: daemon terminates
Feb 14 01:00:13 miniupnpd[242]: version 1.9 started
Feb 14 01:00:13 miniupnpd[242]: HTTP listening on port 52054
Feb 14 01:00:13 miniupnpd[242]: Listening for NAT-PMP/PCP traffic on port 5351
Feb 14 01:00:13 syslog: Generating SSL certificate...
Feb 14 01:00:13 syslog: module ledtrig-usbdev not found in modules.dep
Feb 14 01:00:13 syslog: module leds-usb not found in modules.dep
Feb 14 01:00:14 rc_service: udhcpc 249:notify_rc start_firewall
Feb 14 01:00:14 wan: finish adding multi routes
Feb 14 01:00:14 kernel: SCSI subsystem initialized
Feb 14 01:00:14 rc_service: udhcpc 249:notify_rc stop_upnp
Feb 14 01:00:14 rc_service: waitting "start_firewall" via udhcpc ...
Feb 14 01:00:15 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Feb 14 01:00:18 WAN Connection: WAN was restored.
Feb 14 01:00:18 miniupnpd[242]: shutting down MiniUPnPd
Feb 14 01:00:18 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Feb 14 01:00:19 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Feb 14 01:00:20 kernel: nf_conntrack_rtsp v0.6.21 loading
Feb 14 01:00:20 kernel: nf_nat_rtsp v0.6.21 loading
Feb 14 01:00:20 miniupnpd[357]: version 1.9 started
Feb 14 01:00:20 miniupnpd[357]: HTTP listening on port 39443
Feb 14 01:00:20 miniupnpd[357]: Listening for NAT-PMP/PCP traffic on port 5351
Feb 14 01:00:20 rc_service: udhcpc 249:notify_rc start_upnp
Feb 14 01:00:20 rc_service: waitting "stop_upnp" via udhcpc ...
Feb 14 01:00:20 miniupnpd[357]: shutting down MiniUPnPd
Feb 14 01:00:22 dhcp client: bound 10.5.91.66 via 10.5.88.1 during 172800 seconds.
Feb 14 01:00:22 miniupnpd[362]: version 1.9 started
Feb 14 01:00:22 miniupnpd[362]: HTTP listening on port 59303
Feb 14 01:00:22 miniupnpd[362]: Listening for NAT-PMP/PCP traffic on port 5351
Feb 14 01:00:23 ntp: start NTP update
Nov  7 20:24:20 rc_service: ntp 359:notify_rc restart_upnp
Nov  7 20:24:20 miniupnpd[362]: shutting down MiniUPnPd
Nov  7 20:24:21 miniupnpd[373]: version 1.9 started
Nov  7 20:24:21 miniupnpd[373]: HTTP listening on port 38246
Nov  7 20:24:21 miniupnpd[373]: Listening for NAT-PMP/PCP traffic on port 5351
Nov  7 20:24:21 rc_service: ntp 359:notify_rc restart_diskmon
Nov  7 20:24:21 disk_monitor: Finish
Nov  7 20:24:22 disk monitor: be idle
Nov  7 20:24:25 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:24:25 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:24:32 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:24:41 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:25:06 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:25:11 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:26:45 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 20:27:21 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 21:00:23 disk_monitor: Got SIGALRM...
Nov  7 21:09:38 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 21:12:33 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 22:38:51 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  7 23:00:51 disk_monitor: Got SIGALRM...
Nov  7 23:15:51 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 00:21:54 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 02:01:02 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 04:09:54 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 05:25:07 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 06:19:08 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 06:46:51 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 07:55:33 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 07:55:47 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 08:24:16 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 08:27:58 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 09:09:17 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 10:25:56 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 13:39:11 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 14:17:13 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 16:13:09 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 16:13:44 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 16:35:20 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 16:43:21 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 16:44:33 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 17:03:16 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 17:16:31 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 17:33:09 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 18:14:43 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 18:45:02 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1
Nov  8 19:13:12 dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.134 because the name exists in /etc/hosts with address 127.0.0.1

 

 

Link to comment
Share on other sites

  • Replies 17
  • Created
  • Last Reply
  • Administrator

i powiedz jeszcze, że to smartv samsung :) W ustawieniach TV sprawdź czy ma włączone pobieranie adresu z dhcp i przestaw w ustawieniach sieciowych jego nazwę (zapewne jest pusta albo właśnie localhost).

Link to comment
Share on other sites

Guest peter1819

Bingo. 

Jak połówka odejdzie od telewizora to sprawdzę jakie są ustawienia. Teraz lepiej nie przerywać "Na Wspólnej" ☺️

Tak na 192.168.1. 134 chodzi po Lanie lokalhost SmartTv Sam. Ale nie znalazłem w jego menu możliwości zmiany nazwy i wpisania na sztywno IP. 

Chyba, że w routerze mam to ustawić na sztywno? 

W TV nazwa jest nadana przeze mnie. W routerze nazwa też nadana przeze mnie. Jak zmieniam IP na np. 192.168.1.103 lub 192.168.1.202 nadal w logu sypie tym błędem 

dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.xxx because the name exists in /etc/hosts with address 127.0.0.1

Co robić? 

Link to comment
Share on other sites

Guest peter1819
W dniu 11/8/2017 o 20:34, peter1819 napisał:

Bingo. 

Jak połówka odejdzie od telewizora to sprawdzę jakie są ustawienia. Teraz lepiej nie przerywać "Na Wspólnej" ☺️

Tak na 192.168.1. 134 chodzi po Lanie lokalhost SmartTv Sam. Ale nie znalazłem w jego menu możliwości zmiany nazwy i wpisania na sztywno IP. 

Chyba, że w routerze mam to ustawić na sztywno? 

W TV nazwa jest nadana przeze mnie. W routerze nazwa też nadana przeze mnie. Jak zmieniam IP na np. 192.168.1.103 lub 192.168.1.202 nadal w logu sypie tym błędem 

dnsmasq-dhcp[204]: not giving name localhost to the DHCP lease of 192.168.1.xxx because the name exists in /etc/hosts with address 127.0.0.1

Co robić? 

Wczoraj, znalazłem parę informacji na zagranicznych forach o tym problemie.

Ponoć to wina Samsunga, że tak nazywa swoje produkty po sieci.

A jak się nada nazwę TV np. SamsungTV to automatyczne do wyświetlanej nazwy dodają się nawiasy kwadratowe i wygląda to tak [SamsungTV] a ponoć nie można używać znaków specjalnych.

Zmieniłem też serwery na Googlowskie i nic.

Ktoś nawet dzwonił do wsparcia Samsunga, ale oni nie widzą problemu i spychają odpowiedzialność na providera ISP.

Jak to ugryźć ?

Link to comment
Share on other sites

  • Administrator
36 minut temu, peter1819 napisał:

Jak to ugryźć ?

zmienić TV ? Winy routera tutaj raczej nie widzę. Również mam Samsung TV, ale ja mu przydzielam adres statyczny z dhcp z ręcznym hostname - dziad mi się zgłasza w nazwie swoim adresem MAC.

Link to comment
Share on other sites

  • Administrator

wybacz, to oczywiście był żart, zapomniałem dodać ";):) trudno wymieniać TV z powodu tak błahego błędu  

 

Link to comment
Share on other sites

Guest peter1819

Wiem :)

Ale rozwiązania problemu nadal widzę. A do tego rouera nie ma alternatywnegio FW. Ani Merlina, ani Openwrt, Tomato, Gargoyle.... Posucha.

 

Link to comment
Share on other sites

Guest peter1819

Czy tańszych to nie wiem.  Choć ja kupiłem go okazjonalnie to ma wolnym rynku stoi ponad 200pln.

I z zasięgiem też dość słabo w porównaniu do Rt-ac51u tak jak pisałem wcześniej.  Ile z niego wychodzi w podstawie? (z rt+ac1200g+) 100mW w obu pasmach? Czy mniej?  Da się ewentualnie ciut zwiększyć. Tak wiem, że to ciut musiałoby być o rząd aby uzyskać 2-3dBm. 

Ok,   ale co dalej z moim problem złego adresu i nazwy Tv?

Link to comment
Share on other sites

  • Administrator

Przydzielając rezerwację adresu IP po MAC powinieneś mieć możliwość ustawienia DHCP option 12 - hostname. Wbij jakąkolwiek nazwę, pokrywającą się z nazwą wklepaną w TV i zobacz czy coś się zmieniło. Takie rozwiązanie działa na asuswrt-merlin, nie pamiętam jak jest w OFW. Tak jak pisałem wcześniej, przyczyna leży w TV, nie w FW routera.

36 minut temu, peter1819 napisał:

Czy tańszych to nie wiem

wyrzuć 2 antenowe rt-n12d i rt-ac51u, starszy rt-n18u i kolejny w kolejce cenowo jest rt-ac1200g+. 

Link to comment
Share on other sites

  • 2 months later...
Guest peter1819

Po długich bojach udało mi się zlikwidować zapis w logu odnośnie "locahost". Ustawiłem na sztywno adres IP w telewizorze i w routerze.I bangla☺️

Ale za to mam teraz coś takiego. Raz dziennie :

Jan 11 20:30:36 rc_service: httpd 13982:notify_rc start_lltdc

Link to comment
Share on other sites

  • Administrator
52 minuty temu, peter1819 napisał:

Ale za to mam teraz coś takiego. Raz dziennie :

Jan 11 20:30:36 rc_service: httpd 13982:notify_rc start_lltdc

networkmap poprawie pokazuje wszystkich klientów?

Link to comment
Share on other sites

  • Administrator

jak najbardziej, ten log pochodzi od Link Layer Topology Discovery Daemon 

You do not have the required permissions to view links attached to this post.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, please see ours Guidelines and Privacy Policy.