• Zarejestrowany: 2018-03-05
  • Posty: 135

Temat: Bridge z TL-WR741ND

Mam router główny Xiaomi Mi Router 3G (z LuCI 18.06). I potrzebuję drugi router, TL-WR741ND, na którym mam Gargoyle 1.10, skonfigurować w taki sposób, żeby internet pojawił się w jego gniazdach ethernet, bo mam urządzenie z gniazdem ethernet, które muszę daleko od głównego routera podpiąć.

Tak po prawdzie miałem to skonfigurowane i działało, ale samo z siebie przestało, router przestał odpowiadać i dopiero reset do ustawień fabrycznych zwócił do niego dostęp. Ale kompletnie nie pamiętam jak to poustawiałem, nie znam się na tym za bardzo :-/

Proszę o pomoc, co ustawić w tym Gargoylu, żeby odebrał sieć po WiFi od LuCI i dostarczył do portów ethernet?

2 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

W taki sposób (czytaj do końca): http://openrouter.info/forum/viewtopic. … amp;t=1047

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

3 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

Przeczytałem do końca i ...nadal jestem głupi a sieć nie działa.
Po ustawieniu jak w pierwszym poście (drugiej części z aktualizacją) i zapisaniu konfiguracji połączenie kablowe z tym routerem zniknęło całkiem. Jestem tam podłączony lapkiem z windowsem. Ikona połączenia kilkukrotnie zmieniała wygląd z "Trwa identyfikowanie" na "Kabel sieciowy odłączony" i ostatecznie nie połączył się z siecią.

Xiaomi z LUCI ma adres 192.168.1.1
Bridgowi dałem adres z innej puli czyli 192.168.10.1

Gdy w ustawieniu ethernetu w windows ustawiłem statyczne IP na 192.168.10.2 i bramę na 192.168.10.1 to się sieć pojawiła, jednak internet nie działa. Mało tego, po zalogowaniu do Gargoyla widzę że znowu w ustawieniach jest "Configure device as: Gateway" a nie "Wireless Bridge/repeater" jak ustawiłem i zapisałem. Choć IP zapisał, nie wiem co robię źle.

ps. do którego portu w tym tplinku mam się podpinać kablem, do jednego z czterech LAN czy WAN?

4 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

Do lanu. Jeżeli nie widzisz zmian w gui to może po prostu zapchałeś flash i nie zapisał wszystkich zmian. Przywróć ustawienia domyślnie i zrób to jeszcze raz, nie ruszając niczego innego. Poprzednio działało to teraz też musi, to się w jeden sposób tyko robi.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

5 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

Niestety, to samo. Po przywróceniu ustawień wrócił do starego IP i hasła, wszystko od nowa zrobiłem i efekt ten sam, po restarcie tryb pracy Gateway.
Może ten router jest walnięty? Kupiłem używkę w styczniu z tutejszej giełdy, od obsy'ego.

6 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

Ode mnie smile, nie nie jest walnięty. Zaloguj się przez ssh i pokaż wynik

df -h

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

7 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

root@Gargoyle:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                  448.0K    252.0K    196.0K  56% /
/dev/root                 2.5M      2.5M         0 100% /rom
tmpfs                    14.2M     48.0K     14.1M   0% /tmp
/dev/mtdblock3          448.0K    252.0K    196.0K  56% /overlay
overlayfs:/overlay      448.0K    252.0K    196.0K  56% /
tmpfs                   512.0K         0    512.0K   0% /dev

8 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

Wolnego jeszcze masz. Pokaz

uci show network
uci show wireless

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

9 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

root@Gargoyle:~# uci show network
network.loopback=interface
network.loopback.ifname='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.globals.ula_prefix='fd7e:ade0:942c::/48'
network.lan=interface
network.lan.force_link='1'
network.lan.type='bridge'
network.lan.proto='static'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.lan.ifname='eth0 eth1'
network.lan.ipaddr='192.168.10.1'
network.lan.gateway='192.168.1.1'
network.lan.dns='8.8.8.8 8.8.4.4 62.179.1.62'
network.wan6=interface
network.wan6.ifname='eth1'
network.wan6.proto='dhcpv6'
network.@switch[0]=switch
network.@switch[0].name='switch0'
network.@switch[0].reset='1'
network.@switch[0].enable_vlan='1'
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device='switch0'
network.@switch_vlan[0].vlan='1'
network.@switch_vlan[0].ports='0 1 2 3 4'
network.bridgecfg=interface
network.bridgecfg.proto='relay'
network.bridgecfg.network='lan wwan'
network.wwan=interface
network.wwan.proto='dhcp'

root@Gargoyle:~# uci show wireless
uci: Entry not found

10 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

A gdzie masz plik wireless od wifi?

ls -la /etc/config

pokaż.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

11 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

root@Gargoyle:~# ls -la /etc/config
drwxr-xr-x    1 root     root             0 Oct 25 17:59 .
drwxr-xr-x    1 root     root             0 Oct 25 17:59 ..
-rw-r--r--    1 root     root          3261 Oct 25 16:40 ddns_gargoyle
-rw-r--r--    1 root     root          2079 Oct 25 17:59 dhcp
-rw-r--r--    1 root     root           134 Oct 25 17:46 dropbear
-rw-r--r--    1 root     root          2797 Oct 25 17:59 firewall
-rw-r--r--    1 root     root          3290 Oct 25 17:59 gargoyle
-rw-r--r--    1 root     root           834 Oct 25 17:59 network
-rw-r--r--    1 root     root          2272 Oct 25 17:59 qos_gargoyle
-rw-r--r--    1 root     root          1299 Oct 25 17:56 system
-rw-r--r--    1 root     root           582 Oct 25 17:54 uhttpd
-rw-r--r--    1 root     root           347 Oct 25 17:32 webmon_gargoyle
-rw-r--r--    1 root     root            61 Oct 25 17:32 wol

12 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

wpisz firstboot, zrestartuj, zaloguj się ponownie i pokaż

uci show wireless

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

13 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

Nadal to samo:

root@Gargoyle:~# uci show wireless
uci: Entry not found

A firstboot się wykonał bo zmienił się adres routera oraz hasło na defaultowe.

14 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

Wynik logread pokaż

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

15 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

root@Gargoyle:~# logread
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000]         ...
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] Call Trace:[<80e8eca8>] 0x80e8eca8 [ath9k_hw@80e80000+0x50c00]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80e91c38>] 0x80e91c38 [ath9k_hw@80e80000+0x50c00]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80e8eea0>] 0x80e8eea0 [ath9k_hw@80e80000+0x50c00]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80e84fec>] 0x80e84fec [ath9k_hw@80e80000+0x50c00]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80e9c4d4>] 0x80e9c4d4 [ath9k_hw@80e80000+0x50c00]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80e87348>] 0x80e87348 [ath9k_hw@80e80000+0x50c00]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80e96a18>] 0x80e96a18 [ath9k_hw@80e80000+0x50c00]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80d61500>] 0x80d61500 [ath9k@80d60000+0x14820]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8021994c>] 0x8021994c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8018dc98>] 0x8018dc98
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8021bd48>] 0x8021bd48
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80d617a8>] 0x80d617a8 [ath9k@80d60000+0x14820]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8018df9c>] 0x8018df9c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80d61444>] 0x80d61444 [ath9k@80d60000+0x14820]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80e3d4ac>] 0x80e3d4ac [mac80211@80e00000+0x5c420]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80d6214c>] 0x80d6214c [ath9k@80d60000+0x14820]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80194e2c>] 0x80194e2c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80d639d4>] 0x80d639d4 [ath9k@80d60000+0x14820]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800a522c>] 0x800a522c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80e006c0>] 0x80e006c0 [mac80211@80e00000+0x5c420]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80d6cbd4>] 0x80d6cbd4 [ath9k@80d60000+0x14820]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8013e33c>] 0x8013e33c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8013e0b4>] 0x8013e0b4
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801c971c>] 0x801c971c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801aa7cc>] 0x801aa7cc
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801cc918>] 0x801cc918
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801ccf3c>] 0x801ccf3c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80190214>] 0x80190214
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801cd168>] 0x801cd168
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801cb728>] 0x801cb728
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801cd0ec>] 0x801cd0ec
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801cb7e0>] 0x801cb7e0
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<802bc6fc>] 0x802bc6fc
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801cb614>] 0x801cb614
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801cc674>] 0x801cc674
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<801cd480>] 0x801cd480
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8009e044>] 0x8009e044
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8009060c>] 0x8009060c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80d75000>] 0x80d75000 [ath9k@80d60000+0x14820]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80d75028>] 0x80d75028 [ath9k@80d60000+0x14820]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800eabc8>] 0x800eabc8
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8006945c>] 0x8006945c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800c90f0>] 0x800c90f0
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800ebe70>] 0x800ebe70
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800ebf48>] 0x800ebf48
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800bbb9c>] 0x800bbb9c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800ebc44>] 0x800ebc44
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800b99dc>] 0x800b99dc
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<8007a7ac>] 0x8007a7ac
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800bbeb0>] 0x800bbeb0
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<800bbf24>] 0x800bbf24
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] [<80062b9c>] 0x80062b9c
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000]
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   14.540000] Code: 02402821  0060f809  00000000 <00541024> 10550008  24020001  0c063a14  2404000a  083a0e1b
Wed Oct 25 16:55:06 2017 kern.warn kernel: [   15.070000] ---[ end trace a5f741dbe9d0b329 ]---
Wed Oct 25 16:55:15 2017 user.emerg syslog: ERROR: No valid dynamic DNS service configurations defined
Wed Oct 25 16:55:15 2017 user.emerg syslog: (Did you specify correct configuration file path?)
Wed Oct 25 16:55:15 2017 user.emerg syslog: setting up led WAN
Wed Oct 25 16:55:15 2017 user.emerg syslog: setting up led LAN1
Wed Oct 25 16:55:15 2017 user.emerg syslog: setting up led LAN2
Wed Oct 25 16:55:15 2017 user.emerg syslog: setting up led LAN3
Wed Oct 25 16:55:15 2017 user.emerg syslog: setting up led LAN4
Wed Oct 25 16:55:16 2017 daemon.info procd: - init complete -
Wed Oct 25 16:55:16 2017 kern.info kernel: [   38.630000] device eth0 entered promiscuous mode
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'lan' is enabled
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'lan' is setting up now
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'lan' is now up
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'loopback' is enabled
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'loopback' is setting up now
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'loopback' is now up
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'wan' is enabled
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'wan6' is enabled
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Network device 'lo' link is up
Wed Oct 25 16:55:16 2017 daemon.notice netifd: Interface 'loopback' has link connectivity
Wed Oct 25 16:55:16 2017 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Wed Oct 25 16:55:17 2017 kern.info kernel: [   40.310000] eth0: link up (1000Mbps/Full duplex)
Wed Oct 25 16:55:17 2017 kern.info kernel: [   40.310000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 16:55:17 2017 kern.info kernel: [   40.320000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 16:55:17 2017 daemon.notice netifd: Network device 'eth0' link is up
Wed Oct 25 16:55:17 2017 daemon.notice netifd: Bridge 'br-lan' link is up
Wed Oct 25 16:55:17 2017 daemon.notice netifd: Interface 'lan' has link connectivity
Wed Oct 25 16:55:19 2017 kern.info kernel: [   42.320000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: started, version 2.78 cachesize 150
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: DNS service limited to local subnets
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: compile time options: no-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
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq-dhcp[2352]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain micro
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain micro
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain micro
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain oss
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain oss
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain oss
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain null
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain null
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain null
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain ing
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain ing
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain ing
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain indy
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain indy
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain indy
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain gopher
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain gopher
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain gopher
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain geek
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain geek
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain geek
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain fur
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain fur
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain fur
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain free
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain free
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain free
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.142.171.235#53 for domain bbs
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 95.211.32.162#53 for domain bbs
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using nameserver 66.244.95.20#53 for domain bbs
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: using 11 more nameservers
Wed Oct 25 16:55:24 2017 daemon.warn dnsmasq[2352]: no servers found in /tmp/resolv.conf.auto, will retry
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: read /etc/hosts - 2 addresses
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq[2352]: read /tmp/hosts/dhcp - 1 addresses
Wed Oct 25 16:55:24 2017 daemon.info dnsmasq-dhcp[2352]: read /etc/ethers - 0 addresses
Wed Oct 25 16:55:25 2017 daemon.info dnsmasq[2352]: exiting on receipt of SIGTERM
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: started, version 2.78 cachesize 150
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: DNS service limited to local subnets
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: compile time options: no-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
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq-dhcp[2412]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain micro
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain micro
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain micro
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain oss
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain oss
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain oss
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain null
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain null
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain null
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain ing
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain ing
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain ing
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain indy
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain indy
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain indy
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain gopher
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain gopher
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain gopher
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain geek
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain geek
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain geek
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain fur
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain fur
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain fur
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain free
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain free
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain free
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.142.171.235#53 for domain bbs
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 95.211.32.162#53 for domain bbs
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using nameserver 66.244.95.20#53 for domain bbs
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: using 11 more nameservers
Wed Oct 25 16:55:29 2017 daemon.warn dnsmasq[2412]: no servers found in /tmp/resolv.conf.auto, will retry
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: read /etc/hosts - 2 addresses
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq[2412]: read /tmp/hosts/dhcp - 1 addresses
Wed Oct 25 16:55:29 2017 daemon.info dnsmasq-dhcp[2412]: read /etc/ethers - 0 addresses
Wed Oct 25 16:55:34 2017 daemon.info dnsmasq-dhcp[2412]: DHCPDISCOVER(br-lan) ec:f4:bb:6c:da:da
Wed Oct 25 16:55:34 2017 daemon.info dnsmasq-dhcp[2412]: DHCPOFFER(br-lan) 192.168.1.161 ec:f4:bb:6c:da:da
Wed Oct 25 16:55:34 2017 daemon.info dnsmasq-dhcp[2412]: DHCPREQUEST(br-lan) 192.168.1.161 ec:f4:bb:6c:da:da
Wed Oct 25 16:55:34 2017 daemon.info dnsmasq-dhcp[2412]: DHCPACK(br-lan) 192.168.1.161 ec:f4:bb:6c:da:da precision
Wed Oct 25 16:55:52 2017 kern.notice kernel: [   75.350000] random: nonblocking pool is initialized
Wed Oct 25 16:55:59 2017 authpriv.info dropbear[2435]: Not backgrounding
Wed Oct 25 16:56:21 2017 authpriv.info dropbear[2514]: Child connection from 192.168.1.161:57178
Wed Oct 25 16:56:39 2017 authpriv.notice dropbear[2514]: Password auth succeeded for 'root' from 192.168.1.161:57178
Wed Oct 25 16:57:15 2017 daemon.notice netifd: Network device 'eth0' link is down
Wed Oct 25 16:57:15 2017 kern.info kernel: [  157.560000] eth0: link down
Wed Oct 25 16:57:15 2017 kern.info kernel: [  157.560000] br-lan: port 1(eth0) entered disabled state
Wed Oct 25 16:57:16 2017 daemon.notice netifd: Bridge 'br-lan' link is down
Wed Oct 25 16:57:16 2017 daemon.notice netifd: Interface 'lan' has link connectivity loss
Wed Oct 25 16:57:16 2017 kern.info kernel: [  159.060000] eth0: link up (1000Mbps/Full duplex)
Wed Oct 25 16:57:16 2017 kern.info kernel: [  159.060000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 16:57:16 2017 kern.info kernel: [  159.070000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 16:57:16 2017 daemon.notice netifd: Network device 'eth0' link is up
Wed Oct 25 16:57:16 2017 daemon.notice netifd: Bridge 'br-lan' link is up
Wed Oct 25 16:57:16 2017 daemon.notice netifd: Interface 'lan' has link connectivity
Wed Oct 25 16:57:18 2017 kern.info kernel: [  161.070000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 17:12:06 2017 authpriv.info dropbear[2514]: Exit (root): Keepalive timeout
Wed Oct 25 17:39:48 2017 daemon.notice netifd: Network device 'eth0' link is down
Wed Oct 25 17:39:48 2017 kern.info kernel: [ 2710.700000] eth0: link down
Wed Oct 25 17:39:48 2017 kern.info kernel: [ 2710.700000] br-lan: port 1(eth0) entered disabled state
Wed Oct 25 17:39:49 2017 daemon.notice netifd: Bridge 'br-lan' link is down
Wed Oct 25 17:39:49 2017 daemon.notice netifd: Interface 'lan' has link connectivity loss
Wed Oct 25 17:39:49 2017 kern.info kernel: [ 2712.200000] eth0: link up (1000Mbps/Full duplex)
Wed Oct 25 17:39:49 2017 kern.info kernel: [ 2712.200000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 17:39:49 2017 kern.info kernel: [ 2712.210000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 17:39:49 2017 daemon.notice netifd: Network device 'eth0' link is up
Wed Oct 25 17:39:49 2017 daemon.notice netifd: Bridge 'br-lan' link is up
Wed Oct 25 17:39:49 2017 daemon.notice netifd: Interface 'lan' has link connectivity
Wed Oct 25 17:39:49 2017 daemon.info dnsmasq-dhcp[2412]: DHCPREQUEST(br-lan) 192.168.1.161 ec:f4:bb:6c:da:da
Wed Oct 25 17:39:49 2017 daemon.info dnsmasq-dhcp[2412]: DHCPACK(br-lan) 192.168.1.161 ec:f4:bb:6c:da:da precision
Wed Oct 25 17:39:51 2017 kern.info kernel: [ 2714.210000] br-lan: port 1(eth0) entered forwarding state
Wed Oct 25 17:40:24 2017 authpriv.info dropbear[2535]: Child connection from 192.168.1.161:57515
Wed Oct 25 17:40:38 2017 authpriv.notice dropbear[2535]: Password auth succeeded for 'root' from 192.168.1.161:57515

16 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

Wyłożył ci się sterownik. Wgraj jedną z poprzednich wersji gargoyle, np. 1.6

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

17 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

a powiedz mi jak to jest praktycznie możliwe skoro działało? co się stało konkretnie? czemu nie da się naprawić?

18 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

Nie wiem. Samo w sobie nie powinno to się stać skoro działało wcześniej.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

19 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

Jeszcze dla pewności spytam czy ta wersja jest poprawna do mojego routera (ma napisane pod spodem, że to wersja 2.4):

gargoyle_1.6.2-ar71xx-generic-tl-wr741nd-v2-squashfs-sysupgrade.bin

20 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

Tak.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

21 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

nie wiem o co kaman, ale:

BusyBox v1.19.4 (2014-08-26 19:54:00 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

------------------------------------------------------------------
|            _____                             _                 |
|           |  __ \                           | |                |
|           | |  \/ __ _ _ __ __ _  ___  _   _| | ___            |
|           | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \           |
|           | |_\ \ (_| | | | (_| | (_) | |_| | |  __/           |
|            \____/\__,_|_|  \__, |\___/ \__, |_|\___|           |
|                             __/ |       __/ |                  |
|                            |___/       |___/                   |
|                                                                |
|----------------------------------------------------------------|
| Gargoyle version 1.6.2    | OpenWrt Attitude Adjustment branch |
| Gargoyle revision b70bfc1 | OpenWrt revision r42171            |
| Built August 26, 2014     | Target  ar71xx/default             |
------------------------------------------------------------------
root@Gargoyle:~# uci show wireless
uci: Entry not found


czyli ten sam problem

22 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

root@Gargoyle:~# logread
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.090000] NET: Registered protocol family 16
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.090000] gpiochip_add: registered GPIOs 0 to 17 on device: ath79
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.100000] MIPS: machine is TP-LINK TL-WR741ND
Jan  1 00:00:19 Gargoyle kern.warn kernel: [    0.500000] registering PCI controller with io_map_base unset
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.520000] bio: create slab <bio-0> at 0
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.520000] PCI host bridge to bus 0000:00
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.530000] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.530000] pci_bus 0000:00: root bus resource [io  0x0000]
Jan  1 00:00:19 Gargoyle kern.debug kernel: [    0.540000] pci 0000:00:00.0: [168c:002b] type 0 class 0x000280
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.540000] pci 0000:00:00.0: fixup device configuration
Jan  1 00:00:19 Gargoyle kern.debug kernel: [    0.540000] pci 0000:00:00.0: reg 10: [mem 0x00000000-0x0000ffff 64bit]
Jan  1 00:00:19 Gargoyle kern.debug kernel: [    0.540000] pci 0000:00:00.0: supports D1
Jan  1 00:00:19 Gargoyle kern.debug kernel: [    0.540000] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.540000] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1000ffff 64bit]
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.550000] pci 0000:00:00.0: using irq 40 for pin 1
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.550000] Switching to clocksource MIPS
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.560000] NET: Registered protocol family 2
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.560000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.570000] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.580000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.580000] TCP: Hash tables configured (established 1024 bind 1024)
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.590000] TCP reno registered
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.590000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.600000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.610000] NET: Registered protocol family 1
Jan  1 00:00:19 Gargoyle kern.debug kernel: [    0.610000] PCI: CLS 0 bytes, default 32
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.630000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.640000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.650000] msgmni has been set to 56
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.650000] io scheduler noop registered
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.660000] io scheduler deadline registered (default)
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.660000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.690000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.700000] console [ttyS0] enabled, bootconsole disabled
Jan  1 00:00:19 Gargoyle kern.warn kernel: [    0.710000] m25p80 spi0.0: found en25f32, expected m25p80
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.720000] m25p80 spi0.0: en25f32 (4096 Kbytes)
Jan  1 00:00:19 Gargoyle kern.notice kernel: [    0.720000] 5 tp-link partitions found on MTD device spi0.0
Jan  1 00:00:19 Gargoyle kern.notice kernel: [    0.730000] Creating 5 MTD partitions on "spi0.0":
Jan  1 00:00:19 Gargoyle kern.notice kernel: [    0.730000] 0x000000000000-0x000000020000 : "u-boot"
Jan  1 00:00:19 Gargoyle kern.notice kernel: [    0.740000] 0x000000020000-0x000000109000 : "kernel"
Jan  1 00:00:19 Gargoyle kern.warn kernel: [    0.740000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Jan  1 00:00:19 Gargoyle kern.notice kernel: [    0.760000] 0x000000109000-0x0000003f0000 : "rootfs"
Jan  1 00:00:19 Gargoyle kern.warn kernel: [    0.760000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Jan  1 00:00:19 Gargoyle kern.notice kernel: [    0.780000] mtd: partition "rootfs" set to be root filesystem
Jan  1 00:00:19 Gargoyle kern.info kernel: [    0.780000] mtd: partition "rootfs_data" created automatically, ofs=390000, len=60000
Jan  1 00:00:19 Gargoyle kern.notice kernel: [    0.790000] 0x000000390000-0x0000003f0000 : "rootfs_data"
Jan  1 00:00:19 Gargoyle kern.notice kernel: [    0.800000] 0x0000003f0000-0x000000400000 : "art"
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] $ 4   : b0009860 00009860 00000001 00000000
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] $ 8   : 00000038 80165c78 00000002 00000013
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] $12   : 000000ff fffffffb 0000003f 00000001
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] $16   : 81872010 00009860 00000003 00000001
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] $20   : 00000000 00002710 0000000a 00000001
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] $24   : 00000008 80c61360
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] $28   : 81b4a000 81b4ba20 000cfde7 80d03cb4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] Hi    : 00000001
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] Lo    : 398f4000
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] epc   : 80d03cb4 0x80d03cb4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000]     Tainted: G           O
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] ra    : 80d03cb4 0x80d03cb4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] Status: 1000f403    KERNEL EXL IE
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] Cause : 1080001c
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] PrId  : 00019374 (MIPS 24Kc)
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] Modules linked in: ath9k(O+) ath9k_common(O) ath9k_hw(O) ath(O) mac80211(O) usbcore usb_common nls_base ts_fsm ts_bm ts_kmp crc_ccitt cfg80211(O) compat(O) arc4 aes_generic crypto_algapi ledtrig_timer ledtrig_defa
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] Process insmod (pid: 485, threadinfo=81b4a000, task=81b1ba30, tls=77778440)
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] Stack : 00000000 00000000 00000000 00000000 00000000 00009860 81872010 00009860
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000]         818722e4 00000000 81800964 80d0d6f4 00000000 00000000 81872010 81872010
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000]         000186a0 81872010 81872010 818722e4 00000000 80d0e650 81872010 81873390
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000]         81872010 80d1bcc8 00000030 03940000 81872010 818722e4 00000000 00023f60
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000]         00000000 81800964 0000000a 00000001 000cfde7 80d06d50 00000003 81872414
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000]         ...
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] Call Trace:[<80d0d6f4>] 0x80d0d6f4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80d0e650>] 0x80d0e650
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80d1bcc8>] 0x80d1bcc8
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80d06d50>] 0x80d06d50
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c614d0>] 0x80c614d0
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<8016413c>] 0x8016413c
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80d05cf4>] 0x80d05cf4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80164490>] 0x80164490
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c61478>] 0x80c61478
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80cb3338>] 0x80cb3338
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c61fd4>] 0x80c61fd4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c6c8f0>] 0x80c6c8f0
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c639c4>] 0x80c639c4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<800a56d0>] 0x800a56d0
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c80f0c>] 0x80c80f0c
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c6cb7c>] 0x80c6cb7c
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801250ec>] 0x801250ec
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a0efc>] 0x801a0efc
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c6c8f0>] 0x80c6c8f0
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801863dc>] 0x801863dc
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a47ec>] 0x801a47ec
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a4a74>] 0x801a4a74
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a4b94>] 0x801a4b94
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a2fb4>] 0x801a2fb4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a4b28>] 0x801a4b28
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a32cc>] 0x801a32cc
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<8015d5dc>] 0x8015d5dc
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<8015df8c>] 0x8015df8c
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a4288>] 0x801a4288
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<801a4f4c>] 0x801a4f4c
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<802085b4>] 0x802085b4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80186898>] 0x80186898
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c76000>] 0x80c76000
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c76000>] 0x80c76000
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80c76028>] 0x80c76028
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<800b2080>] 0x800b2080
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80060900>] 0x80060900
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<800cecd0>] 0x800cecd0
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<8008fd84>] 0x8008fd84
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<800a3610>] 0x800a3610
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<8006a2e4>] 0x8006a2e4
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000] [<80165c9c>] 0x80165c9c
Jan  1 00:00:19 Gargoyle kern.warn kernel: [   12.850000]
Jan  1 00:00:25 Gargoyle daemon.notice netifd: Interface 'lan' is now up
Jan  1 00:00:25 Gargoyle kern.info kernel: [   25.880000] device eth0 entered promiscuous mode
Jan  1 00:00:25 Gargoyle daemon.notice netifd: Interface 'loopback' is now up
Jan  1 00:00:25 Gargoyle kern.info kernel: [   25.900000] device eth1 entered promiscuous mode
Jan  1 00:00:26 Gargoyle user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Jan  1 00:00:26 Gargoyle kern.info kernel: [   26.480000] eth0: link up (1000Mbps/Full duplex)
Jan  1 00:00:26 Gargoyle kern.info kernel: [   26.480000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:00:26 Gargoyle kern.info kernel: [   26.490000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:00:28 Gargoyle kern.info kernel: [   28.490000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:23:07 Gargoyle authpriv.info dropbear[915]: Running in background
Jan  1 00:23:07 Gargoyle daemon.warn httpd_gargoyle[940]: started as root without requesting chroot(), warning only
Jan  1 00:23:07 Gargoyle daemon.notice httpd_gargoyle[940]: httpd_gargoyle/1.0 14mar2008 starting on Gargoyle, port 80
Jan  1 00:23:08 Gargoyle user.info sysinit: ERROR: No valid dynamic DNS service configurations defined
Jan  1 00:23:08 Gargoyle user.info sysinit: (Did you specify correct configuration file path?)
Jan  1 00:23:08 Gargoyle user.info sysinit: setting up led WAN
Jan  1 00:23:08 Gargoyle user.info sysinit: setting up led LAN1
Jan  1 00:23:08 Gargoyle user.info sysinit: setting up led LAN2
Jan  1 00:23:08 Gargoyle user.info sysinit: setting up led LAN3
Jan  1 00:23:08 Gargoyle user.info sysinit: setting up led LAN4
Jan  1 00:23:25 Gargoyle kern.info kernel: [   50.100000] eth0: link down
Jan  1 00:23:25 Gargoyle kern.info kernel: [   50.100000] br-lan: port 1(eth0) entered disabled state
Jan  1 00:23:28 Gargoyle kern.info kernel: [   53.100000] eth0: link up (1000Mbps/Full duplex)
Jan  1 00:23:28 Gargoyle kern.info kernel: [   53.100000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:23:28 Gargoyle kern.info kernel: [   53.110000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:23:30 Gargoyle kern.info kernel: [   55.110000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:24:50 Gargoyle kern.info kernel: [  135.170000] eth0: link down
Jan  1 00:24:50 Gargoyle kern.info kernel: [  135.170000] br-lan: port 1(eth0) entered disabled state
Jan  1 00:24:52 Gargoyle kern.info kernel: [  136.670000] eth0: link up (1000Mbps/Full duplex)
Jan  1 00:24:52 Gargoyle kern.info kernel: [  136.670000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:24:52 Gargoyle kern.info kernel: [  136.680000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:24:54 Gargoyle kern.info kernel: [  138.680000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:25:32 Gargoyle kern.info kernel: [  176.670000] eth0: link down
Jan  1 00:25:32 Gargoyle kern.info kernel: [  176.670000] br-lan: port 1(eth0) entered disabled state
Jan  1 00:25:34 Gargoyle kern.info kernel: [  178.670000] eth0: link up (1000Mbps/Full duplex)
Jan  1 00:25:34 Gargoyle kern.info kernel: [  178.670000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:25:34 Gargoyle kern.info kernel: [  178.680000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:25:36 Gargoyle kern.info kernel: [  180.680000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:35:52 Gargoyle authpriv.info dropbear[1691]: Child connection from 192.168.1.20:60786
Jan  1 00:36:04 Gargoyle authpriv.notice dropbear[1691]: Password auth succeeded for 'root' from 192.168.1.20:60786
Jan  1 00:37:37 Gargoyle kern.info kernel: [  901.730000] eth0: link down
Jan  1 00:37:37 Gargoyle kern.info kernel: [  901.730000] br-lan: port 1(eth0) entered disabled state
Jan  1 00:37:38 Gargoyle kern.info kernel: [  903.230000] eth0: link up (1000Mbps/Full duplex)
Jan  1 00:37:38 Gargoyle kern.info kernel: [  903.230000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:37:38 Gargoyle kern.info kernel: [  903.240000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:37:40 Gargoyle kern.info kernel: [  905.240000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:46:16 Gargoyle kern.info kernel: [ 1420.730000] eth0: link down
Jan  1 00:46:16 Gargoyle kern.info kernel: [ 1420.730000] br-lan: port 1(eth0) entered disabled state
Jan  1 00:46:18 Gargoyle kern.info kernel: [ 1422.730000] eth0: link up (1000Mbps/Full duplex)
Jan  1 00:46:18 Gargoyle kern.info kernel: [ 1422.730000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:46:18 Gargoyle kern.info kernel: [ 1422.740000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:46:20 Gargoyle kern.info kernel: [ 1424.740000] br-lan: port 1(eth0) entered forwarding state
Jan  1 00:46:25 Gargoyle authpriv.info dropbear[1700]: Child connection from 192.168.1.20:60944
Jan  1 00:46:37 Gargoyle authpriv.notice dropbear[1700]: Password auth succeeded for 'root' from 192.168.1.20:60944

23 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

pokaż

hexdump -C /dev/mtd4

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

24 Odpowiedź przez jerzyha

  • Zarejestrowany: 2018-03-05
  • Posty: 135

Odp: Bridge z TL-WR741ND

root@Gargoyle:~# hexdump -C /dev/mtd4
00000000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
00001000  a5 5a 00 00 00 03 50 00  16 8c 00 2b 50 08 00 01  |.Z....P....+P...|
00001010  02 80 50 2c 16 8c a0 91  50 64 8c c0 05 04 50 6c  |..P,....Pd....Pl|
00001020  38 11 00 03 40 04 05 cb  00 4a 40 74 00 03 00 00  |8...@....J@t....|
00001030  40 00 50 01 01 c2 51 0c  20 10 00 06 51 64 14 12  |@.P...Q. ...Qd..|
00001040  ff 24 51 68 17 ff 00 15  50 68 20 10 00 19 ff ff  |.$Qh....Ph .....|
00001050  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
00001080  01 78 39 4a e0 0d 02 01  00 00 00 1f 00 19 e0 66  |.x9J...........f|
00001090  66 68 01 01 00 00 00 00  00 00 00 09 07 00 05 00  |fh..............|
000010a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000010b0  00 00 00 00 00 00 00 00  00 00 00 00 00 2d 20 00  |.............- .|
000010c0  e2 00 0d 00 02 0e 1c ba  0c 01 00 00 06 46 34 01  |.............F4.|
000010d0  0e 0e 00 00 1f 2d 00 00  34 04 44 84 33 93 33 03  |.....-..4.D.3.3.|
000010e0  00 00 00 00 80 00 00 00  00 00 00 00 00 00 00 00  |................|
000010f0  00 00 00 00 00 00 00 00  70 89 ac 19 1b 32 3e 52  |........p....2>R|
00001100  48 58 68 74 76 00 00 00  0a 3f 22 3e 6b a2 aa 19  |HXhtv....?">k...|
00001110  1b 32 3c 53 48 57 68 74  74 0a 05 1b 2d 62 24 3e  |.2<SHWhtt...-b$>|
00001120  6f a7 a7 1c 1d 29 3e 51  4c 5a 69 70 70 08 08 14  |o....)>QLZipp...|
00001130  33 6d 2f 4c 83 a8 a8 70  24 24 24 24 b8 24 24 24  |3m/L...p$$$$.$$$|
00001140  24 ff 00 00 00 00 70 24  24 22 20 89 24 24 22 20  |$.....p$$" .$$" |
00001150  ac 24 24 22 20 70 24 24  24 24 24 24 20 1e 89 24  |.$$" p$$$$$$ ..$|
00001160  24 24 24 24 24 20 1e ac  24 24 24 24 24 24 20 1e  |$$$$$ ..$$$$$$ .|
00001170  70 1e 1e 1e 1e 1e 1c 1a  18 89 1e 1e 1e 1e 1e 1c  |p...............|
00001180  1a 18 ac 1e 1e 1e 1e 1e  1c 1a 18 11 12 15 17 41  |...............A|
00001190  42 45 47 31 32 35 37 70  22 75 22 7a 62 a2 22 70  |BEG1257p"u"zb."p|
000011a0  1c 75 60 9d 60 a2 1d 70  1a 75 60 9d 60 a2 1c 7a  |.u`.`..p.u`.`..z|
000011b0  13 7f 5b 93 1b 98 13 70  22 75 62 ac 22 b8 22 70  |..[....p"ub."."p|
000011c0  22 75 62 ac 22 00 00 70  22 75 62 ac 22 00 00 7a  |"ub."..p"ub."..z|
000011d0  1c 7f 5c 93 5c a2 1c 70  1c 75 5d ac 1c 00 00 70  |..\.\..p.u]....p|
000011e0  1c 75 5e ac 1c 00 00 70  1c 75 5e ac 1c 00 00 7a  |.u^....p.u^....z|
000011f0  1c 7f 5c 93 5c a2 1c 00  ff ff ff ff ff ff ff ff  |..\.\...........|
00001200  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
00010000

25 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,904

Odp: Bridge z TL-WR741ND

Czyli arta masz. Co z nim zrobiłeś jeszcze skoro cały czas wywala się sterownik?

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona