1

(660 odpowiedzi, napisanych Sprzęt / Hardware)

@Cezary - dziękuje uruchomiłem demona przy starcie systemu i jest ok.

2

(660 odpowiedzi, napisanych Sprzęt / Hardware)

lexmark3200 napisał/a:

WAN nie ma PoE przecież.
https://www.cudy.com/pl-pl/products/c200p-1-0#features

PoE masz na LAN. I jedynie po upgrad openWRT będziesz musiał jeszcze raz odpalić skrypt, bo brakuje mu dowiązań, a nie chciało mi się bawić w drugi skrypt.
No i zainstaluj usbutils, bo pewnie będzie Ci w log pluł błędem. Wg mnie binarka korzysta i sprawdza budżet pod PoE, czy masz coś po USB wpięte. Jeśli tak, to obniża moc na PoE, jeśli nie to masz pełną moc.

OK.
A błąd, który wyrzuca LUCI po instalacji paczki to:

RPCError

RPC call to pse/get_poe_status failed with error -32000: Object not found
  at handleCallReply (http://192.168.1.1/luci-static/resource … 99031:11:3)

To dlatego, ze nie mam podłączonego urządzania PoE?

3

(660 odpowiedzi, napisanych Sprzęt / Hardware)

@lexmark3200 rozpakowałem Twoją paczkę i w /pse/c200ppse/pse_daemon/etc/config jest plik pse w którym jest konfiguracja portów:

config port 'port_1'
    option enable '0'
    option port_id '0'

config port 'port_2'
    option enable '0'
    option port_id '1'

config port 'port_3'
    option enable '0'
    option port_id '2'

config port 'port_4'
    option enable '0'
    option port_id '3'

Według mnie brakuje jeszcze wpisu o porcie wan - dla obrazu, ktory pracuje jako switch - sprawdzałeś?

4

(660 odpowiedzi, napisanych Sprzęt / Hardware)

@Cezary dziękuje, działa - wgrałem oba obrazy.
Przejście pomiędzy nimi działa - wgywałem przez luci - użyłem force, bo "krzyczy" czy to na pewno dobry obraz.
Czy byłaby by szansa na obraz ze switchem pod 24.10?

5

(660 odpowiedzi, napisanych Sprzęt / Hardware)

@Cezary czy jak @Lexmark3200 podeślę Tobie zmienionego DTS tak, aby c200p pracował jako switch, bez wan, to czy będziesz mógł dodać do swoich źródeł i skompilować obraz w ten spsób?
Wówczas wszystkie porty są spięte i przewala Gb po LAN bez udziału CPU. Przy wyborze obrazu w firmware selector mogłyby być dwie pozycje.

6

(2 odpowiedzi, napisanych Oprogramowanie / Software)

Ok.

Skorzystam z https://firmware-selector.openwrt.org/? … erouter-6p

Dziękuje.

7

(2 odpowiedzi, napisanych Oprogramowanie / Software)

Cezary czy jest szansa na Twój obraz z Luci dla routera Ubiquiti EdgeRouter 6P?

Intel i5-7200u @ pfsense 2.7.2

[2.7.2-RELEASE][root@pfSense.localdomain]/root: iperf3 -s -D && iperf3 -c 127.0.0.1
Connecting to host 127.0.0.1, port 5201
[  5] local 127.0.0.1 port 18923 connected to 127.0.0.1 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  3.55 GBytes  30.5 Gbits/sec    0   2.01 MBytes
[  5]   1.00-2.00   sec  3.53 GBytes  30.3 Gbits/sec    0   2.01 MBytes
[  5]   2.00-3.00   sec  3.54 GBytes  30.4 Gbits/sec    0   2.01 MBytes
[  5]   3.00-4.00   sec  3.49 GBytes  30.0 Gbits/sec    0   2.01 MBytes
[  5]   4.00-5.00   sec  3.52 GBytes  30.2 Gbits/sec    0   2.01 MBytes
[  5]   5.00-6.00   sec  3.53 GBytes  30.4 Gbits/sec    0   2.01 MBytes
[  5]   6.00-7.00   sec  3.58 GBytes  30.7 Gbits/sec    0   2.01 MBytes
[  5]   7.00-8.00   sec  3.56 GBytes  30.6 Gbits/sec    0   2.01 MBytes
[  5]   8.00-9.00   sec  3.56 GBytes  30.6 Gbits/sec    0   2.01 MBytes
[  5]   9.00-10.00  sec  3.54 GBytes  30.4 Gbits/sec    0   2.01 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  35.4 GBytes  30.4 Gbits/sec    0             sender
[  5]   0.00-10.00  sec  35.4 GBytes  30.4 Gbits/sec                  receiver

9

(7 odpowiedzi, napisanych Sprzęt / Hardware)

ambrozy5 napisał/a:

po co pchać się w tak słabe procesory ? https://www.cpubenchmark.net/compare/In … 2005vs1839 , to zależy jaki vpn będzie miał, openvpn jest jednowątkowy więc trzeba postawić na pojedynczy wątek, wireguard za to wykorzysta wszystkie rdzenie jakie masz i będzie sporo szybszy , no i nie wykorzysta aes-ni bo szyfruje ChaCha20  pentium g2020 + jeden stick ramu +płyta  h61 intela + intel pro1000 dual port@ pico psu idlle na poziomie 18w a4-5000 na podobnej wartości ;p

Ok. A co powiesz na to:

https://pl.banggood.com/QOTOM-Mini-Pc-I … rehouse=CN

lub

https://www.banggood.com/QOTOM-Q355G4-M … rehouse=CN

10

(1,299 odpowiedzi, napisanych Oprogramowanie / Software)

Cezary napisał/a:

@n0rbi77

zobacz test fccid: https://fccid.io/TE7C7V2/RF-Exposure-In … 240767.pdf

C7 v2 na kanale 48 czyli częstotliwości 5240 ma niecałe 17dBm max. Mi nie musisz ufać, ale może zaufać instytucji która robiła certyfikację urządzenia. To co gui ci wyświetla to graniczenie narzucone przez ustawiony kraj.

Ok, dziękuje, wyrzucę z konfiguracji ustawiony kraj i przestawię kanał na inny!
Pozdrawiam!

11

(1,299 odpowiedzi, napisanych Oprogramowanie / Software)

Cezary napisał/a:
n0rbi77 napisał/a:
Cezary napisał/a:

Nie, od poprzedniej wersji nic się w sterownikach nie zmieniło. Po czym sądzisz że się zmieniło jakieś ograniczenie?

Załączam zrzut ekranu dla radia 5GHz.

radio5

Kraj ustawiony na US.

Wyniki poleceń

iw dev
iw list
uci show wireless

pokaż. Nie screenshoty z luci.

Proszę:

iw list
Wiphy phy1
        max # scan SSIDs: 4
        max scan IEs length: 2261 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Available Antennas: TX 0x7 RX 0x7
        Configured Antennas: TX 0x7 RX 0x7
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS
        Band 2:
                Capabilities: 0x11ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-23
                Frequencies:
                        * 5180 MHz [36] (22.0 dBm)
                        * 5200 MHz [40] (22.0 dBm)
                        * 5220 MHz [44] (22.0 dBm)
                        * 5240 MHz [48] (22.0 dBm)
                        * 5260 MHz [52] (23.0 dBm) (radar detection)
                        * 5280 MHz [56] (23.0 dBm) (radar detection)
                        * 5300 MHz [60] (23.0 dBm) (radar detection)
                        * 5320 MHz [64] (23.0 dBm) (radar detection)
                        * 5500 MHz [100] (23.0 dBm) (radar detection)
                        * 5520 MHz [104] (23.0 dBm) (radar detection)
                        * 5540 MHz [108] (23.0 dBm) (radar detection)
                        * 5560 MHz [112] (23.0 dBm) (radar detection)
                        * 5580 MHz [116] (23.0 dBm) (radar detection)
                        * 5600 MHz [120] (23.0 dBm) (radar detection)
                        * 5620 MHz [124] (23.0 dBm) (radar detection)
                        * 5640 MHz [128] (23.0 dBm) (radar detection)
                        * 5660 MHz [132] (23.0 dBm) (radar detection)
                        * 5680 MHz [136] (23.0 dBm) (radar detection)
                        * 5700 MHz [140] (23.0 dBm) (radar detection)
                        * 5745 MHz [149] (24.0 dBm)
                        * 5765 MHz [153] (24.0 dBm)
                        * 5785 MHz [157] (24.0 dBm)
                        * 5805 MHz [161] (24.0 dBm)
                        * 5825 MHz [165] (24.0 dBm)
        valid interface combinations:
                 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client                                                                                                                                                             , P2P-GO } <= 1, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match, radar de                                                                                                                                                             tect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Supported extended features:
                * [ RRM ]: RRM
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
Wiphy phy0
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS
        Band 1:
                Capabilities: 0x11ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                Frequencies:
                        * 2412 MHz [1] (26.0 dBm)
                        * 2417 MHz [2] (26.0 dBm)
                        * 2422 MHz [3] (26.0 dBm)
                        * 2427 MHz [4] (26.0 dBm)
                        * 2432 MHz [5] (26.0 dBm)
                        * 2437 MHz [6] (26.0 dBm)
                        * 2442 MHz [7] (26.0 dBm)
                        * 2447 MHz [8] (26.0 dBm)
                        * 2452 MHz [9] (26.0 dBm)
                        * 2457 MHz [10] (26.0 dBm)
                        * 2462 MHz [11] (26.0 dBm)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)
        valid interface combinations:
                 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client                                                                                                                                                             , P2P-GO } <= 1, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match, radar de                                                                                                                                                             tect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Supported extended features:
                * [ RRM ]: RRM
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs

iw dev
phy#1
        Interface wlan1
                ifindex 8
                wdev 0x100000002
                addr a0:63:91:7c:fd:e4
                ssid dom_14 5GHz
                type AP
                channel 48 (5240 MHz), width: 40 MHz, center1: 5230 MHz
                txpower 15.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                        0       0       1124    0       0       0       0       136092          1162
phy#0
        Interface wlan0-1
                ifindex 10
                wdev 0x3
                addr a2:63:91:7c:fd:e2
                ssid Guests
                type AP
                channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
                txpower 26.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                        0       0       0       0       0       0       0       0               0
        Interface wlan0
                ifindex 9
                wdev 0x2
                addr a0:63:91:7c:fd:e2
                ssid dom_14
                type AP
                channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
                txpower 26.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                        0       0       4248    4       0       0       0       675714          4467
uci show wireless

wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.hwmode='11g'
wireless.radio0.path='platform/ar934x_wmac'
wireless.radio0.channel='6'
wireless.radio0.htmode='HT40'
wireless.radio0.legacy_rates='1'
wireless.radio0.country='US'
wireless.radio0.txpower='26'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='lan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='siec'
wireless.default_radio0.encryption='psk2'
wireless.default_radio0.key='pass'
wireless.radio1=wifi-device
wireless.radio1.type='mac80211'
wireless.radio1.hwmode='11a'
wireless.radio1.path='pci0000:00/0000:00:00.0'
wireless.radio1.htmode='HT40'
wireless.radio1.country='US'
wireless.radio1.txpower='22'
wireless.radio1.channel='48'
wireless.default_radio1=wifi-iface
wireless.default_radio1.device='radio1'
wireless.default_radio1.network='lan'
wireless.default_radio1.mode='ap'
wireless.default_radio1.ssid='siec 5GHz'
wireless.default_radio1.encryption='psk2'
wireless.default_radio1.key='pass'
wireless.wifinet0=wifi-iface
wireless.wifinet0.device='radio0'
wireless.wifinet0.mode='ap'
wireless.wifinet0.ssid='Guests'
wireless.wifinet0.network='lan'
wireless.wifinet0.encryption='psk2'
wireless.wifinet0.key='pass'
wireless.wifinet0.isolate='1'

12

(1,299 odpowiedzi, napisanych Oprogramowanie / Software)

Cezary napisał/a:

Nie, od poprzedniej wersji nic się w sterownikach nie zmieniło. Po czym sądzisz że się zmieniło jakieś ograniczenie?

Załączam zrzut ekranu dla radia 5GHz.

radio5

Kraj ustawiony na US.

13

(1,299 odpowiedzi, napisanych Oprogramowanie / Software)

Cezary napisał/a:

Nie, po co ci stara wersja?

W poprzedniej wersji nie było ograniczenia mocy nadawania w sterowniku, dlatego o nią pytam.

14

(1,299 odpowiedzi, napisanych Oprogramowanie / Software)

Czy jest szansa na pobranie obrazu sysupgrade z 2019-09-15 LuCI OpenWrt 19.07-SNAPSHOT dla wndr4300?

15

(1,299 odpowiedzi, napisanych Oprogramowanie / Software)

Cezary a czy jest szansa na kompilacje 18.06 z luci i jądrem tak jak w Gargoyle - 4.14.151 - dla wndr4300?

16

(7 odpowiedzi, napisanych Sprzęt / Hardware)

Witam

Co sprzętowo wybrać pod łącze 400/100 z VPN?

Plan taki:

1. PC ENGINES APU.2D4 PLATFORMA 3XGIGABITLAN, 4GB RAM, AMD GX-412TC CPU + OpenWrt + WireGuard
2. Netgear XR500 ??
3. Netgear R7800 + Openwrt + WireGuard
4. Asus N86U + Merlin

Pozdrawiam

17

(4,519 odpowiedzi, napisanych Oprogramowanie / Software)

Gruberek napisał/a:

A ja bym nie brał r7800 ani nic na qca9984. VHT160 nie działa na openwrt. Nie wiem jak wypada z oryginalnym softem ale w końcu będę musiał sprawdzić. Kupiłem NBG6817, bo układy qualcomm zawsze były dobrze wspierane przez openwrt i niestety się zawiodłem. Minęło sporo czasu i nic się nie zmieniło.

Ok. To co byś wziął? Pozdrawiam

18

(4,519 odpowiedzi, napisanych Oprogramowanie / Software)

fido napisał/a:

Czy ten r6220 jest dużo lepszy od wndr4300 ? czy jest sens podmiany z wndr4300 na r6220

Cześć

Mam wndr4300 i zasięg wifi ma bardzo dobry, jeżeli nie potrzebujesz AC to bym nie zmieniał (miałem r6220 na testy).
Jak już to wziąłbym r7800 o ile możesz poświęcić tyle pieniędzy.
Pozdrawiam

19

(17 odpowiedzi, napisanych Oprogramowanie / Software)

Cezary napisał/a:

Wgrywa się przez tftp: https://git.openwrt.org/?p=openwrt/open … 7faa3f977f

Dziękuje, można na Ciebie liczyć! Śmiga!

20

(17 odpowiedzi, napisanych Oprogramowanie / Software)

Cześć

Otrzymałem asusa rt-n12+ i chciałem na niego wgrać OpenWRT+Luci, w dl.eko znajduje się wersja: luci-19.07-snapshot-r10532-cf3b50377e-ramips-mt7620-rt-n12p-squashfs-sysupgrade.bin
Cezary czy jest szansa na factory lub w jaki inny sposób zainstalować sysupgrade?

Pozdrawiam
Norbert

21

(4 odpowiedzi, napisanych Oprogramowanie / Software)

Dyziek napisał/a:

Na 18.06 na wifi mialem tak 120-130 mbit.
Na 19.07 mam 150-160 przy off-loading wlaczonym

Zasiegu nie porownywalem


Dziękuje za informacje, warto zmienić na 19.07.
Pozdr

22

(4 odpowiedzi, napisanych Oprogramowanie / Software)

Cezary napisał/a:

Są nowsze sterowniki od wifi, więc tak, istnieje taka szansa.


Dziękuje, sprawdzę!

23

(4 odpowiedzi, napisanych Oprogramowanie / Software)

Witam

Aktualnie używam wndr 4300 + Gargoyle PL 1.11. Czy na oprogramowaniu LuCI OpenWrt 19.07-SNAPSHOT będzie lepiej działać sieć wifi?

Pozdrawiam
Norbert

24

(8 odpowiedzi, napisanych Oprogramowanie / Software)

Skrypt 20-printer ręcznie uruchomiony działa.
logi:

Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4552 accepted
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4553 accepted
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4554 accepted
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4555 accepted
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:39 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:39 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4556 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4557 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4559 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4560 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4561 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4562 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4563 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4564 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4565 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4566 accepted
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:40 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:40 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4567 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 24673/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4568 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4569 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4570 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4571 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4572 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4573 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4574 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4575 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4576 accepted
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:41 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:41 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4577 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4578 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4579 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4580 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4581 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4582 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4583 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4584 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4585 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4586 accepted
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:42 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:42 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4587 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4588 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4589 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4590 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 24673/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4591 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4592 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4593 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4594 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4595 accepted
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Finished job: 28769/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:43 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:43 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4596 accepted
Fri Apr 27 21:47:44 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:44 2018 lpr.notice p9100d[6635]: Finished job: 24673/28949 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:44 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer
Fri Apr 27 21:47:44 2018 lpr.notice p9100d[6635]: Connection from 192.168.1.227 port 4597 accepted
Fri Apr 27 21:47:44 2018 lpr.err p9100d[6635]: read: Connection reset by peer
Fri Apr 27 21:47:44 2018 lpr.notice p9100d[6635]: Finished job: 55/64 bytes sent to printer, 0/0 bytes sent to network
Fri Apr 27 21:47:44 2018 lpr.err p9100d[6635]: copy_stream: Connection reset by peer

25

(8 odpowiedzi, napisanych Oprogramowanie / Software)

Skrypt wpisałem w vi, restart nie pomogło, nie wiem jak sprawdzić czy firware poszło do drukarki