26 Odpowiedź przez Cezary

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

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Pod linuksem pod vi. Windows ma inne końce linii, innymi słowami - to co zrobiłeś nie jest skryptem z punktu widzenia uniksów.

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

Cezary's Strona

27 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

czyli Virtualbox i instalacja linuxa, tak ?

28 Odpowiedź przez Cezary

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

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Po co? vi masz pod openwrt, tak samo jak kilka innych edytorów.

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

Cezary's Strona

29 Odpowiedź przez Mikrotik23 (edytowany przez Mikrotik23 2014-05-07 22:10:54)

  • Zarejestrowany: 2014-03-31
  • Posty: 37

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Możesz zainstalować nano, jest bardzo łatwy w obsłudze.

30 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Niestety będę musiał instalować Kubuntu w virtualu, ja tego vi czy nano pod openwrt nie ogarniam, trochę mnie to przerasta.

31 Odpowiedź przez pepe2k

  • pepe2k
  • pepe2k
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-10-29
  • Posty: 5,028

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Zainstaluj sobie Notepad++ w Windowsie... masz tam opcję wybrania jaki ma stosować koniec linii i jest język polski.

32 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

No to przerobiłem ten plik pod linuxem, wkopiowałem na router we właściwe miejsce i wywołałem podane komendy i mam coś takiego:
root@ROUT:~# chmod 777 /etc/hotplug.d/usb/20-printer
root@ROUT:~# /etc/hotplug.d/usb/20-printer
root@ROUT:~#

Później restart drukarki, i komuniat z logów:
USB disconnect, device number 4
May  8 01:53:33 ROUT kern.info kernel: [13327.340000] usblp0: removed
May  8 01:53:38 ROUT kern.info kernel: [13331.920000] usb 1-1.2.1: new high-speed USB device number 9 using ehci-platform
May  8 01:53:38 ROUT kern.info kernel: [13332.050000] usblp0: USB Bidirectional printer dev 9 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
May  8 01:54:09 ROUT user.notice usb-modeswitch: 1-1.2.1:1.0: Manufacturer=Hewlett-Packard Product=HP_LaserJet_1020 Serial=JL3LEGY
May  8 01:54:13 ROUT user.notice /usr/lib/gargoyle/ping_watchdog.sh: WAN Restart
May  8 01:54:13 ROUT daemon.notice netifd: wan (1057): Trying to set mode


Wygląda trochę tak jakby nic się nie zadziało, bo drukarka dalej jest szara.

33 Odpowiedź przez Cezary

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

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Jak jeszcze nic ciekawego w logach nie ma. Czemu było odłączenie drukarki w trakcie działania routera?

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

Cezary's Strona

34 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Zrestartowałem ją bo po tej operacji z plikiem nic się nie zmieniło, więc sprawdziłem czy zadziała po ponownym włączeniu.
Ale tak jak pisałem wcześniej nic się nie zmieniło, co zatem teraz robić ?

35 Odpowiedź przez Cezary

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

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Nie możesz tak robić. O ile przeczytałeś skrypt to on tylko raz jedyny wysyła firmware później tego nie zrobi mimo odłączenia i przyłączenia drukarki. Więc teraz po prostu podłącz drukarkę i zrestartuj router. I później patrz w logi.

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

Cezary's Strona

36 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

OK, puszczam logi po restarcie routera, drukarka niestety dalej szara.

Jan  1 01:00:39 ROUT kern.debug kernel: [    0.340000] pci 0000:00:00.0: reg 10: [mem 0x00000000-0x0001ffff 64bit]
Jan  1 01:00:39 ROUT kern.debug kernel: [    0.340000] pci 0000:00:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
Jan  1 01:00:39 ROUT kern.debug kernel: [    0.340000] pci 0000:00:00.0: supports D1
Jan  1 01:00:39 ROUT kern.debug kernel: [    0.340000] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Jan  1 01:00:39 ROUT kern.info kernel: [    0.340000] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit]
Jan  1 01:00:39 ROUT kern.info kernel: [    0.340000] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref]
Jan  1 01:00:39 ROUT kern.info kernel: [    0.350000] pci 0000:00:00.0: using irq 40 for pin 1
Jan  1 01:00:39 ROUT kern.info kernel: [    0.350000] Switching to clocksource MIPS
Jan  1 01:00:39 ROUT kern.info kernel: [    0.360000] NET: Registered protocol family 2
Jan  1 01:00:39 ROUT kern.info kernel: [    0.360000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 01:00:39 ROUT kern.info kernel: [    0.360000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
Jan  1 01:00:39 ROUT kern.info kernel: [    0.370000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
Jan  1 01:00:39 ROUT kern.info kernel: [    0.370000] TCP: Hash tables configured (established 4096 bind 4096)
Jan  1 01:00:39 ROUT kern.info kernel: [    0.380000] TCP reno registered
Jan  1 01:00:39 ROUT kern.info kernel: [    0.380000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan  1 01:00:39 ROUT kern.info kernel: [    0.390000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan  1 01:00:39 ROUT kern.info kernel: [    0.390000] NET: Registered protocol family 1
Jan  1 01:00:39 ROUT kern.debug kernel: [    0.400000] PCI: CLS 0 bytes, default 32
Jan  1 01:00:39 ROUT kern.info kernel: [    0.410000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jan  1 01:00:39 ROUT kern.info kernel: [    0.420000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Jan  1 01:00:39 ROUT kern.info kernel: [    0.430000] msgmni has been set to 246
Jan  1 01:00:39 ROUT kern.info kernel: [    0.430000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
Jan  1 01:00:39 ROUT kern.info kernel: [    0.440000] io scheduler noop registered
Jan  1 01:00:39 ROUT kern.info kernel: [    0.440000] io scheduler deadline registered (default)
Jan  1 01:00:39 ROUT kern.info kernel: [    0.450000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Jan  1 01:00:39 ROUT kern.info kernel: [    0.480000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
Jan  1 01:00:39 ROUT kern.info kernel: [    0.490000] console [ttyS0] enabled, bootconsole disabled
Jan  1 01:00:39 ROUT kern.warn kernel: [    0.500000] m25p80 spi0.0: found en25q64, expected m25p80
Jan  1 01:00:39 ROUT kern.info kernel: [    0.500000] m25p80 spi0.0: en25q64 (8192 Kbytes)
Jan  1 01:00:39 ROUT kern.notice kernel: [    0.510000] 5 tp-link partitions found on MTD device spi0.0
Jan  1 01:00:39 ROUT kern.notice kernel: [    0.520000] Creating 5 MTD partitions on "spi0.0":
Jan  1 01:00:39 ROUT kern.notice kernel: [    0.520000] 0x000000000000-0x000000020000 : "u-boot"
Jan  1 01:00:39 ROUT kern.notice kernel: [    0.530000] 0x000000020000-0x00000010ef0c : "kernel"
Jan  1 01:00:39 ROUT kern.warn kernel: [    0.530000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Jan  1 01:00:39 ROUT kern.notice kernel: [    0.550000] 0x00000010ef0c-0x0000007f0000 : "rootfs"
Jan  1 01:00:39 ROUT kern.warn kernel: [    0.550000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Jan  1 01:00:39 ROUT kern.info kernel: [   31.360000] cfg80211: Calling CRDA to update world regulatory domain
Jan  1 01:00:39 ROUT kern.info kernel: [   31.370000] cfg80211: World regulatory domain updated:
Jan  1 01:00:39 ROUT kern.info kernel: [   31.380000] cfg80211:  DFS Master region: unset
Jan  1 01:00:39 ROUT kern.info kernel: [   31.380000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan  1 01:00:39 ROUT kern.info kernel: [   31.390000] cfg80211:   (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 3000 mBm)
Jan  1 01:00:39 ROUT kern.info kernel: [   31.400000] cfg80211:   (5140000 KHz - 5860000 KHz @ 40000 KHz), (N/A, 3000 mBm)
Jan  1 01:00:39 ROUT kern.info kernel: [   31.630000] NET: Registered protocol family 10
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.690000] ath: EEPROM regdomain: 0x0
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.690000] ath: EEPROM indicates default country code should be used
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.690000] ath: doing EEPROM country->regdmn map search
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.690000] ath: country maps to regdmn code: 0x3a
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.690000] ath: Country alpha2 being used: US
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.690000] ath: Regpair used: 0x3a
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.700000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.700000] Registered led device: ath9k-phy0
Jan  1 01:00:39 ROUT kern.info kernel: [   32.700000] ieee80211 phy0: Atheros AR9340 Rev:0 mem=0xb8100000, irq=47
Jan  1 01:00:39 ROUT kern.warn kernel: [   32.710000] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.720000] ath: EEPROM regdomain: 0x0
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.720000] ath: EEPROM indicates default country code should be used
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.720000] ath: doing EEPROM country->regdmn map search
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.720000] ath: country maps to regdmn code: 0x3a
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.720000] ath: Country alpha2 being used: US
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.720000] ath: Regpair used: 0x3a
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.730000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Jan  1 01:00:39 ROUT kern.debug kernel: [   32.730000] Registered led device: ath9k-phy1
Jan  1 01:00:39 ROUT kern.info kernel: [   32.730000] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb0000000, irq=40
Jan  1 01:00:39 ROUT kern.info kernel: [   32.740000] cfg80211: Calling CRDA for country: US
Jan  1 01:00:39 ROUT kern.info kernel: [   32.740000] cfg80211: Regulatory domain changed to country: US
Jan  1 01:00:39 ROUT kern.info kernel: [   32.750000] cfg80211:  DFS Master region: unset
Jan  1 01:00:39 ROUT kern.info kernel: [   32.760000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan  1 01:00:39 ROUT kern.info kernel: [   32.760000] cfg80211:   (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 3000 mBm)
Jan  1 01:00:39 ROUT kern.info kernel: [   32.770000] cfg80211:   (5140000 KHz - 5860000 KHz @ 40000 KHz), (N/A, 3000 mBm)
Jan  1 01:00:39 ROUT kern.info kernel: [   33.070000] RPC: Registered named UNIX socket transport module.
Jan  1 01:00:39 ROUT kern.info kernel: [   33.070000] RPC: Registered udp transport module.
Jan  1 01:00:39 ROUT kern.info kernel: [   33.080000] RPC: Registered tcp transport module.
Jan  1 01:00:39 ROUT kern.info kernel: [   33.080000] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan  1 01:00:39 ROUT kern.info kernel: [   33.510000] PPP generic driver version 2.4.2
Jan  1 01:00:39 ROUT kern.info kernel: [   33.620000] tun: Universal TUN/TAP device driver, 1.6
Jan  1 01:00:39 ROUT kern.info kernel: [   33.630000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan  1 01:00:39 ROUT kern.info kernel: [   33.730000] GRE over IPv4 demultiplexor driver
Jan  1 01:00:39 ROUT kern.info kernel: [   33.750000] GRE over IPv4 tunneling driver
Jan  1 01:00:39 ROUT kern.info kernel: [   34.040000] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jan  1 01:00:39 ROUT kern.info kernel: [   34.130000] ip_tables: (C) 2000-2006 Netfilter Core Team
Jan  1 01:00:39 ROUT kern.info kernel: [   34.590000] NET: Registered protocol family 24
Jan  1 01:00:39 ROUT kern.info kernel: [   34.710000] nf_conntrack version 0.5.0 (1978 buckets, 7912 max)
Jan  1 01:00:39 ROUT kern.info kernel: [   35.090000] PPTP driver version 0.8.5
Jan  1 01:00:39 ROUT kern.info kernel: [   35.790000] xt_time: kernel timezone is -0000
Jan  1 01:00:39 ROUT kern.info kernel: [   36.440000]     Hooked IMQ after mangle on PREROUTING
Jan  1 01:00:39 ROUT kern.info kernel: [   36.440000]     Hooked IMQ after nat on POSTROUTING
Jan  1 01:00:39 ROUT kern.info kernel: [   36.450000] IMQ driver loaded successfully. (numdevs = 2, numqueues = 1)
Jan  1 01:00:43 ROUT kern.info kernel: [   43.120000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan  1 01:00:43 ROUT user.notice root: Wyslano firmware do drukarki
Jan  1 01:00:44 ROUT kern.info kernel: [   44.340000] eth0: link up (1000Mbps/Full duplex)
Jan  1 01:00:44 ROUT kern.info kernel: [   44.360000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan  1 01:00:44 ROUT kern.info kernel: [   44.780000] eth0: link down
Jan  1 01:00:44 ROUT kern.info kernel: [   44.790000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan  1 01:00:44 ROUT kern.info kernel: [   44.800000] ADDRCONF(NETDEV_UP): eth0.1: link is not ready
Jan  1 01:00:44 ROUT kern.info kernel: [   44.800000] device eth0.1 entered promiscuous mode
Jan  1 01:00:44 ROUT kern.info kernel: [   44.810000] device eth0 entered promiscuous mode
Jan  1 01:00:44 ROUT kern.info kernel: [   44.810000] ADDRCONF(NETDEV_UP): br-lan: link is not ready
Jan  1 01:00:44 ROUT daemon.notice netifd: Interface 'lan' is now up
Jan  1 01:00:44 ROUT daemon.notice netifd: Interface 'loopback' is now up
Jan  1 01:00:44 ROUT kern.info kernel: [   44.820000] ADDRCONF(NETDEV_UP): wwan0: link is not ready
Jan  1 01:00:45 ROUT user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Jan  1 01:00:45 ROUT daemon.notice netifd: wan (971): Trying to set mode
Jan  1 01:00:46 ROUT kern.info kernel: [   46.350000] eth0: link up (1000Mbps/Full duplex)
Jan  1 01:00:46 ROUT kern.info kernel: [   46.360000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan  1 01:00:46 ROUT kern.info kernel: [   46.360000] br-lan: port 1(eth0.1) entered forwarding state
Jan  1 01:00:46 ROUT kern.info kernel: [   46.370000] br-lan: port 1(eth0.1) entered forwarding state
Jan  1 01:00:46 ROUT kern.info kernel: [   46.380000] ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
Jan  1 01:00:46 ROUT kern.info kernel: [   46.380000] ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Jan  1 01:00:48 ROUT kern.info kernel: [   48.370000] br-lan: port 1(eth0.1) entered forwarding state
Jan  1 01:00:48 ROUT user.notice usb-modeswitch: 1-0:1.0: Manufacturer=Linux_3.3.8_ehci_hcd Product=Generic_Platform_EHCI_Controller Serial=ehci-platform
Jan  1 01:00:49 ROUT daemon.notice netifd: wan (971): Trying to set mode
Jan  1 01:00:50 ROUT kern.info kernel: [   50.070000] cdc_ncm: wwan0: 150 mbit/s downlink 150 mbit/s uplink
Jan  1 01:00:50 ROUT kern.info kernel: [   50.080000] cdc_ncm: wwan0: network connection: connected
Jan  1 01:00:50 ROUT kern.info kernel: [   50.090000] ADDRCONF(NETDEV_CHANGE): wwan0: link becomes ready
Jan  1 01:00:50 ROUT kern.info kernel: [   50.390000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan  1 01:00:50 ROUT kern.info kernel: [   50.400000] device wlan0 entered promiscuous mode
Jan  1 01:00:50 ROUT kern.info kernel: [   50.610000] br-lan: port 2(wlan0) entered forwarding state
Jan  1 01:00:50 ROUT kern.info kernel: [   50.620000] br-lan: port 2(wlan0) entered forwarding state
Jan  1 01:00:50 ROUT kern.info kernel: [   50.620000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan  1 01:00:52 ROUT kern.info kernel: [   52.620000] br-lan: port 2(wlan0) entered forwarding state
Jan  1 01:00:53 ROUT daemon.notice netifd: wan (1264): udhcpc (v1.19.4) started
Jan  1 01:00:53 ROUT daemon.notice netifd: wan (1264): Sending discover...
May  8 20:00:01 ROUT daemon.notice netifd: wan (1264): Sending select for 100.91.0.61...
May  8 20:00:01 ROUT daemon.notice netifd: wan (1264): Lease of 100.91.0.61 obtained, lease time 518400
May  8 20:00:01 ROUT daemon.notice netifd: Interface 'wan' is now up
May  8 20:00:02 ROUT authpriv.info dropbear[1339]: Running in background
May  8 20:00:02 ROUT daemon.crit httpd_gargoyle[1363]: bind 0.0.0.0 - Address already in use
May  8 20:00:02 ROUT daemon.crit httpd_gargoyle[1363]: bind 0.0.0.0 - Address already in use
May  8 20:00:03 ROUT daemon.warn httpd_gargoyle[1364]: started as root without requesting chroot(), warning only
May  8 20:00:03 ROUT daemon.notice httpd_gargoyle[1364]: httpd_gargoyle/1.0 14mar2008 starting on ROUT, port 80
May  8 20:00:04 ROUT kern.warn kernel: [   56.880000] disktype: sending ioctl 5305 to a partition!
May  8 20:00:04 ROUT kern.warn kernel: [   56.880000] disktype: sending ioctl 5305 to a partition!
May  8 20:00:06 ROUT daemon.notice ntfs-3g[1488]: Version 2011.4.12 external FUSE 29
May  8 20:00:06 ROUT daemon.notice ntfs-3g[1488]: Mounted /dev/sdb1 (Read-Write, label "MEDIA", NTFS 3.1)
May  8 20:00:06 ROUT daemon.notice ntfs-3g[1488]: Cmdline options:
May  8 20:00:06 ROUT daemon.notice ntfs-3g[1488]: Mount options: allow_other,nonempty,atime,fsname=/dev/sdb1,blkdev,blksize=4096
May  8 20:00:06 ROUT daemon.notice ntfs-3g[1488]: Ownership and permissions disabled, configuration type 1
May  8 20:00:07 ROUT user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
May  8 20:00:07 ROUT user.notice dnsmasq: Allowing 127.0.0.0/8 responses
May  8 20:00:07 ROUT user.notice dnsmasq: Allowing RFC1918 responses for domain free.aero2.net.pl
May  8 21:33:12 ROUT daemon.info dnsmasq[1556]: started, version 2.66 cachesize 150
May  8 21:33:12 ROUT daemon.info dnsmasq[1556]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
May  8 21:33:12 ROUT daemon.info dnsmasq-dhcp[1556]: DHCP, IP range 182.182.182.100 -- 182.182.182.249, lease time 12h
May  8 21:33:12 ROUT daemon.info dnsmasq[1556]: using local addresses only for domain lan
May  8 21:33:12 ROUT daemon.info dnsmasq[1556]: reading /tmp/resolv.conf.auto
May  8 21:33:12 ROUT daemon.info dnsmasq[1556]: using nameserver 212.2.96.54#53
May  8 21:33:12 ROUT daemon.info dnsmasq[1556]: using nameserver 212.2.96.53#53
May  8 21:33:12 ROUT daemon.warn dnsmasq[1556]: ignoring nameserver 182.182.182.1 - local interface
May  8 21:33:12 ROUT daemon.info dnsmasq[1556]: using local addresses only for domain lan
May  8 21:33:12 ROUT daemon.info dnsmasq[1556]: read /etc/hosts - 3 addresses
May  8 21:33:12 ROUT daemon.info dnsmasq-dhcp[1556]: read /etc/ethers - 0 addresses
May  8 21:33:12 ROUT daemon.notice rpc.statd[1587]: Version 1.2.6 starting
May  8 21:33:12 ROUT daemon.notice sm-notify[1588]: Version 1.2.6 starting
May  8 21:33:12 ROUT daemon.err sm-notify[1588]: Failed to open directory sm.bak: No such file or directory
May  8 21:33:12 ROUT daemon.notice rpc.statd[1587]: Initializing NSM state
May  8 21:33:12 ROUT daemon.warn rpc.statd[1587]: Running as root.  chown /var/lib/nfs to choose different user
May  8 21:33:12 ROUT kern.warn kernel: [   63.700000] svc: failed to register lockdv1 RPC service (errno 124).
May  8 21:33:12 ROUT daemon.notice rpc.mountd[1603]: Version 1.2.6 starting
May  8 21:33:14 ROUT user.info sysinit: ERROR: No valid dynamic DNS service configurations defined
May  8 21:33:14 ROUT user.info sysinit: (Did you specify correct configuration file path?)
May  8 21:33:14 ROUT user.notice root: vsftpd init: mounted = 1
May  8 21:33:14 ROUT user.notice root: vsftpd init: got_lock = 1
May  8 21:33:15 ROUT user.info sysinit: setting up led USB1
May  8 21:33:15 ROUT user.info sysinit: setting up led USB2
May  8 21:33:15 ROUT user.info sysinit: setting up led WLAN2G
May  8 21:33:22 ROUT daemon.info hostapd: wlan0: STA 20:54:76:d0:b7:6d IEEE 802.11: authenticated
May  8 21:33:22 ROUT daemon.info hostapd: wlan0: STA 20:54:76:d0:b7:6d IEEE 802.11: associated (aid 1)
May  8 21:33:22 ROUT daemon.info hostapd: wlan0: STA 20:54:76:d0:b7:6d WPA: pairwise key handshake completed (RSN)
May  8 21:33:23 ROUT daemon.info dnsmasq-dhcp[1556]: DHCPREQUEST(br-lan) 182.182.182.239 20:54:76:d0:b7:6d
May  8 21:33:23 ROUT daemon.info dnsmasq-dhcp[1556]: DHCPACK(br-lan) 182.182.182.239 20:54:76:d0:b7:6d android-8333c6fc2c5a4610
May  8 21:33:25 ROUT user.notice firewall: Reloading firewall due to ifup of wan (wwan0)
May  8 21:33:41 ROUT daemon.info dnsmasq-dhcp[1556]: DHCPDISCOVER(br-lan) 00:21:ff:89:7c:dd
May  8 21:33:41 ROUT daemon.info dnsmasq-dhcp[1556]: DHCPOFFER(br-lan) 182.182.182.149 00:21:ff:89:7c:dd
May  8 21:33:41 ROUT daemon.info dnsmasq-dhcp[1556]: DHCPREQUEST(br-lan) 182.182.182.149 00:21:ff:89:7c:dd
May  8 21:33:41 ROUT daemon.info dnsmasq-dhcp[1556]: DHCPACK(br-lan) 182.182.182.149 00:21:ff:89:7c:dd HD6000
May  8 21:33:58 ROUT user.notice usb-modeswitch: 1-1:1.0: Manufacturer=? Product=USB2.0_Hub Serial=?
May  8 21:34:02 ROUT cron.err crond[1317]: time disparity of 94 minutes detected
May  8 21:34:16 ROUT kern.warn kernel: [  127.880000] ipt_bandwidth: timezone shift of 120 minutes detected, adjusting
May  8 21:34:16 ROUT kern.warn kernel: [  127.890000]                old minutes west=0, new minutes west=-120
May  8 21:34:59 ROUT user.notice usb-modeswitch: 1-1.2:1.0: Manufacturer=? Product=USB2.0_Hub Serial=?
May  8 21:36:00 ROUT user.notice usb-modeswitch: 1-1.2.1:1.0: Manufacturer=Hewlett-Packard Product=HP_LaserJet_1020 Serial=JL3LEGY
May  8 21:37:01 ROUT user.notice usb-modeswitch: 1-1.2.3:1.0: Manufacturer=HUAWEI_Technology Product=HUAWEI_Mobile Serial=?
Success

37 Odpowiedź przez Cezary

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

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

O drukarce to tu jeszcze nic nie ma.

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

Cezary's Strona

38 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

drukarka jest podpięta do routera za pośrednictwem aktywnego hub'a usb, nie wiem czy to może mieć jakieś znaczenie ?

39 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

nie, jest wpis:
Jan  1 01:00:43 ROUT user.notice root: Wyslano firmware do drukarki

40 Odpowiedź przez Cezary

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

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Więc to wszystko co masz zrobić.

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

Cezary's Strona

41 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Zabrzmiało tajemniczo, czy mam przez to rozumieć że podłączyć się z drukarką bezpośrednio do routera ?

42 Odpowiedź przez Cezary

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

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Skonfiguruj klienta i drukuj po prostu.

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

Cezary's Strona

43 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Jak się okazuje, nawet banalne działania mogą czasami okazać się nie doprzejścia. Na nowo dodałem drukarkę w systemie (WIN 8.1), i dalej nic. To znaczy puszczenie wydruku powoduję przedziwne zachowanie się wartości transferu wydruku do drukarki, cyfra transefu tańczy jak na dyskotece, maleje, rośnie, maleje, rośnie i to wszystko w bardzo szybkim tępie się odbywa, a finalnie i tak wydruk nie wychodzi.
Poniżej logi tego zdażenie widziane od strony routera:

May  8 22:06:43 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
May  8 22:08:19 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54904 accepted
May  8 22:08:19 ROUT lpr.notice p9100d[1343]: Finished job: 29265 bytes received, 0 bytes sent
May  8 22:08:35 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: authenticated
May  8 22:08:35 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: No WPA/RSN IE in association request
May  8 22:08:47 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: authenticated
May  8 22:08:47 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: No WPA/RSN IE in association request
May  8 22:08:59 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: authenticated
May  8 22:08:59 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: No WPA/RSN IE in association request
May  8 22:09:01 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54908 accepted
May  8 22:09:01 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:01 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54909 accepted
May  8 22:09:03 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:03 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54910 accepted
May  8 22:09:04 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:04 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54911 accepted
May  8 22:09:05 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:05 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54912 accepted
May  8 22:09:05 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:05 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54915 accepted
May  8 22:09:05 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:05 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54916 accepted
May  8 22:09:06 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:06 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54918 accepted
May  8 22:09:06 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:06 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54920 accepted
May  8 22:09:06 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:06 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54923 accepted
May  8 22:09:06 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:06 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54926 accepted
May  8 22:09:07 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:07 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54928 accepted
May  8 22:09:07 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:07 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54929 accepted
May  8 22:09:08 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:08 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54930 accepted
May  8 22:09:08 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:08 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54931 accepted
May  8 22:09:08 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:08 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54932 accepted
May  8 22:09:09 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:09 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54933 accepted
May  8 22:09:10 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:10 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54934 accepted
May  8 22:09:10 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:10 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54935 accepted
May  8 22:09:10 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:10 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54936 accepted
May  8 22:09:11 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:11 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: authenticated
May  8 22:09:11 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: No WPA/RSN IE in association request
May  8 22:09:11 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54937 accepted
May  8 22:09:11 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:11 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54938 accepted
May  8 22:09:12 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:12 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54939 accepted
May  8 22:09:12 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:12 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54940 accepted
May  8 22:09:13 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:13 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54941 accepted
May  8 22:09:13 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:13 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54942 accepted
May  8 22:09:13 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:13 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54943 accepted
May  8 22:09:14 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:14 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54944 accepted
May  8 22:09:14 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:14 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54945 accepted
May  8 22:09:15 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:15 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54946 accepted
May  8 22:09:15 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:15 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54947 accepted
May  8 22:09:16 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:16 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54948 accepted
May  8 22:09:16 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:16 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54949 accepted
May  8 22:09:17 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:17 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54950 accepted
May  8 22:09:17 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:17 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54951 accepted
May  8 22:09:18 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:18 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54952 accepted
May  8 22:09:19 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:19 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54953 accepted
May  8 22:09:20 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:20 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54955 accepted
May  8 22:09:21 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:21 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54956 accepted
May  8 22:09:22 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:22 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54957 accepted
May  8 22:09:22 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:22 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54958 accepted
May  8 22:09:23 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: authenticated
May  8 22:09:23 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: No WPA/RSN IE in association request
May  8 22:09:23 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:23 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54959 accepted
May  8 22:09:23 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:23 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54960 accepted
May  8 22:09:23 ROUT lpr.notice p9100d[1343]: Finished job: 63381 bytes received, 0 bytes sent
May  8 22:09:23 ROUT lpr.notice p9100d[1343]: Connection from ::ffff:182.182.182.105 port 54961 accepted
May  8 22:09:24 ROUT lpr.notice p9100d[1343]: Finished job: 63445 bytes received, 0 bytes sent
May  8 22:09:34 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: authenticated
May  8 22:09:34 ROUT daemon.info hostapd: wlan0: STA e0:63:e5:5f:96:fd IEEE 802.11: No WPA/RSN IE in association request
Success

44 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Dodam do powyższego że coś jednak się zmieniło, drukarka po tych wszystkich operacja w systemie nie wyświetla się już wyszarzona, prezentuje się jako on-line. Niestety nie drukuje, puszczane na nią wydruki giną gdzieś w nicości, dalej mam prośbę o pomoc, macie jakieś pomysły o co chodzi ?

45 Odpowiedź przez Orionator

  • Zarejestrowany: 2014-04-05
  • Posty: 20

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Jeszcze coś dodam, podstawowe testy wydruku robiłem na Win 8.1 Pro i wynik był taki jak wyżej opisano, dodatkowo zrobiłem jeszcze testy  z laptopa z Win XP HE, i niestety taka sama reakcja, stąd wnoszę że problem musi tkwić gdzieś w samym Openwrt lub zastosowanych skryptach.

46 Odpowiedź przez Cezary

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

Odp: Konfiguracja printservera w tplink tl-wr1043nd z gargoyle

Nic takiego nie ma. OpenWrt (czy raczej p910nd) jest tylko prostym mostem ip <> usb i nic ciekawego nie robi. Może ta drukarka nie będzie działać w tym trybie i tyle, nic nie będziesz w stanie zrobić poza instalacją cupsa.

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

Cezary's Strona