Właśnie o tym czytałem.
Ja szukam coś gotowego mocnego małego w obudowie z większą mocą i większą ilością pamięci niż dobre rutery abym mógł tam różne zabawki poinstalować sobie i pobawić się. Tryb AP zdecydowanie musi być.
Nie jesteś zalogowany. Proszę się zalogować lub zarejestrować.
eko.one.pl → Posty przez marcin.kasinski
Strony Poprzednia 1 2 3 4 Następna
Właśnie o tym czytałem.
Ja szukam coś gotowego mocnego małego w obudowie z większą mocą i większą ilością pamięci niż dobre rutery abym mógł tam różne zabawki poinstalować sobie i pobawić się. Tryb AP zdecydowanie musi być.
Jak dobrze znalazłem wifi to Intel Wireless-AC 3168
A na takim NUC pójdzie openwrt?
https://allegro.pl/oferta/mini-pc-intel … 8770049332
W szczególności pytam o WIFI, czy nie będzie problemów ze sterownikiem.
Dodatkowe pytanie.
Jak wygląda pobór prądu takiego NUC w porównaniu do lepszej klasy rutera?
Jeszcze nie zainstalowałeś sterowników. RTL8188CUS obsługuje chyba pakiet kmod-rtl8192cu (mówię od razu - weź coś na uspokojenie, bo jak zobaczysz jaka jest wydajność chipu 8188 to dostaniesz palpitacji serca). Zaś tplinka __może__ obsługiwać kmod-rtl8812au-ct ale on ostatnio nie działał w ogóle jak sprawdzaliśmy.
TL;DR kup sobie inne karty.
Możesz zaproponować jaki model mam kupić który działałby dobrze?
Najlepiej dwa modele najlepiej współpracujące jakby z pierwszym były problemy z dostępnością.
Tylko najlepiej jakby były dwuzakresowe.
Mam raspbery pi 2 na nim wgrałem openwrt
Poprzez usb mam podłaczone dwa adaptery wifi TP-LINK ARCHER T2U NANO i edimax n150
Oba są widoczne.
root@OpenWrt:~# lsusb
Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 005: ID 2357:011e TP-Link
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. SMC9512/9514 USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Mam zainstalowane pakiety:
root@OpenWrt:~# opkg list-installed | grep usb
brcmfmac-firmware-usb - 20190416-1
kmod-usb-core - 4.14.171-1
kmod-usb-hid - 4.14.171-1
kmod-usb-storage - 4.14.171-1
libusb-1.0-0 - 1.0.22-2
usbutils - 007-10
root@OpenWrt:~#
W konsoli openwrt nie widzę zupełnie sekcji WIFI.
Co powinienem zrobić aby te agaptery zaczęły współpracować z moim openwrt na raspberry pi 2?
Cześć.
Chodzi mi po głowie temat pobawienia się openwrt na jakimś terminalu PC.
Wymagania:
Chciałbym aby miał dwa porty lan, choć z jednym też dam radę.
Chciałbym aby był nowy.
Chciałbym na nim pobawić się AP i siecią 2,4 i 5.
Chciałbym aby był prosty i nie posiadał niepotrzebnych rzeczy aby prądu mało ciągnął
Chciałbym aby miał architekturę x64
Chciałbym aby mógł też czystego centosa pociągnąć
Nie wiem jakie powinien on spełniać wymagania, ile dysku, jaki moduł wifi itp.
Może ktoś podesłać linka z propozycją do takiego sprzętu z włąsnego doświadczenia?
Może ktoś podesłać sensownego linka z oisem wgrania openwr na taki terminał (Ja znalazłem https://openwrt.org/docs/guide-user/ins … nwrt_x86)?
Chyba nie po to wgrywasz openwrt żeby później wracać do oryginału. Bo jak tak chcesz na próbę to zainstaluj sobie openwrt na emulatorze żeby zobaczyć jak działa.
Oczywiście masz rację.
Ja zawsze chce mieć spokój i wiele możliwości.
Jakby openwrt mi nie działało najlepiej chciałbym mieć łatwość powrotu do oryginału.
Jakbym popsuł sobie tak totalnie openwrt , że leżałbym i płakał chciałbym mieć łatwość powrotu do oryginału.
itd.
Testowałem to z ruterami linksys acs i kilka razy mi się taka opcja przydała.
Tak: https://github.com/openwrt/openwrt/comm … 19085bfb9c
Tak: https://eko.one.pl/?p=openwrt-sta#mostbezprzewodowy
Dzięki.
Jedyne czego się boję to ewentualny powrót do oryginalnego firmware...
Cześć.
Zadziała mi openwrt na extenderze TP-LINK AC2600 RE650?
Pytam, bo nie mogę znaleźć informacji o tym.
Jest gdzieś ewentualnie uniwersalny opis konfiguracji extendera openwrt?
Witam.
Potrzebuje kupić router z możliwością zainstalowania openwrt.
Wymagania:
budżet: 300. No w porywach mógłbym dojść do 500
dwuzakresowy
pełne wsparcie openwrt
Rozważam Netgear R6220.
Czy to dobry wybór, czy coś bardziej sensownego znajdę z moimi wymaganiami?
Jest to opisane w poradniku: https://eko.one.pl/?p=openwrt-openvpntu … zaserwerem a ty tego nie zrobiłeś.
Wielkie dzięki.
Uznajmy, że jestem lama... ![]()
Witam.
Mam OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152)
Mam zainstalowane od zera openwrt i chce skonfigurować openvpn na podstawie opisu https://eko.one.pl/?p=openwrt-openvpntun
Robię zgodnie z opisem.
Jedyna różnica jest taka, że według instrukcji powinien wygenerować się plik dh2048.pem, a mi wygenerował się dh.pem
Mój problem jest taki, że pięknie się łączę z laptopa poprzez VPN, pinguje internet, ale nie widzę maszyn w LAN.
Nie wiem jak to teraz zweryfikować.
Mógłby ktoś pomóc ?
Network:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd64:e64a:9933::/48'
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
config interface 'wan'
option ifname 'eth1.2'
option proto 'static'
option ipaddr 'x.x.x.x'
option netmask 'x.x.x.x'
option gateway 'x.x.x.x.'
option dns 'x.x.x.x x.x.x.x x.x.x.x'
config interface 'wan6'
option ifname 'eth1.2'
option proto 'dhcpv6'
option auto '0'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 5t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
config interface 'vpn'
option ifname 'tun0'
option proto 'none'
openvpn:
config openvpn 'custom_config'
option enabled '0'
option config '/etc/openvpn/my-vpn.conf'
config openvpn 'sample_server'
option enabled '0'
option port '1194'
option proto 'udp'
option dev 'tun'
option ca '/etc/openvpn/ca.crt'
option cert '/etc/openvpn/server.crt'
option key '/etc/openvpn/server.key'
option dh '/etc/openvpn/dh1024.pem'
option server '10.8.0.0 255.255.255.0'
option ifconfig_pool_persist '/tmp/ipp.txt'
option keepalive '10 120'
option compress 'lzo'
option persist_key '1'
option persist_tun '1'
option user 'nobody'
option status '/tmp/openvpn-status.log'
option verb '3'
config openvpn 'sample_client'
option enabled '0'
option client '1'
option dev 'tun'
option proto 'udp'
list remote 'my_server_1 1194'
option resolv_retry 'infinite'
option nobind '1'
option persist_key '1'
option persist_tun '1'
option user 'nobody'
option ca '/etc/openvpn/ca.crt'
option cert '/etc/openvpn/client.crt'
option key '/etc/openvpn/client.key'
option compress 'lzo'
option verb '3'
config openvpn 'home'
option enabled '1'
option dev 'tun0'
option port '1194'
option proto 'udp'
option log '/tmp/openvpn.log'
option verb '3'
option ca '/etc/openvpn/ca.crt'
option cert '/etc/openvpn/serwer.crt'
option key '/etc/openvpn/serwer.key'
option server '10.8.0.0 255.255.255.0'
option dh '/etc/openvpn/dh.pem'
Firewall:
config defaults
option syn_flood '1'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'
config zone
option name 'lan'
list network 'lan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
config zone
option name 'wan'
list network 'wan'
list network 'wan6'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'
config forwarding
option src 'lan'
option dest 'wan'
config rule
option name 'Allow-DHCP-Renew'
option src 'wan'
option proto 'udp'
option dest_port '68'
option target 'ACCEPT'
option family 'ipv4'
config rule
option name 'Allow-Ping'
option src 'wan'
option proto 'icmp'
option icmp_type 'echo-request'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-IGMP'
option src 'wan'
option proto 'igmp'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-DHCPv6'
option src 'wan'
option proto 'udp'
option src_ip 'fc00::/6'
option dest_ip 'fc00::/6'
option dest_port '546'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-MLD'
option src 'wan'
option proto 'icmp'
option src_ip 'fe80::/10'
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Input'
option src 'wan'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
list icmp_type 'router-solicitation'
list icmp_type 'neighbour-solicitation'
list icmp_type 'router-advertisement'
list icmp_type 'neighbour-advertisement'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Forward'
option src 'wan'
option dest '*'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-IPSec-ESP'
option src 'wan'
option dest 'lan'
option proto 'esp'
option target 'ACCEPT'
config rule
option name 'Allow-ISAKMP'
option src 'wan'
option dest 'lan'
option dest_port '500'
option proto 'udp'
option target 'ACCEPT'
config include
option path '/etc/firewall.user'
config zone
option name 'vpn'
option input 'ACCEPT'
option forward 'ACCEPT'
option output 'ACCEPT'
option network 'vpn'
config forwarding
option src 'vpn'
option dest 'wan'
config rule
option name 'OpenVPN'
option target 'ACCEPT'
option src 'wan'
option proto 'udp'
option dest_port '1194'Problem rozwiązany.
Okazało się, że w konfiguracji rutera znajdował się plik openvpn-opkg
Jego zawartość poniżej.
Jakaś pozostałość po automatycznym upgrade, czy coś.
Po jego usunięciu wszystko znów działa.
package openvpn
#################################################
# Sample to include a custom config file. #
#################################################
config openvpn custom_config
# Set to 1 to enable this instance:
option enabled 0
# Include OpenVPN configuration
option config /etc/openvpn/my-vpn.conf
#################################################
# Sample OpenVPN 2.0 uci config for #
# multi-client server. #
#################################################
config openvpn sample_server
# Set to 1 to enable this instance:
option enabled 0
# Which local IP address should OpenVPN
# listen on? (optional)
# option local 0.0.0.0
# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
option port 1194
# TCP or UDP server?
# option proto tcp
option proto udp
# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
# option dev tap
option dev tun
# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
option ca /etc/openvpn/ca.crt
option cert /etc/openvpn/server.crt
# This file should be kept secret:
option key /etc/openvpn/server.key
# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
option dh /etc/openvpn/dh1024.pem
# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
option server "10.8.0.0 255.255.255.0"
# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
option ifconfig_pool_persist /tmp/ipp.txt
# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
# option server_bridge "10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100"
# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
# list push "route 192.168.10.0 255.255.255.0"
# list push "route 192.168.20.0 255.255.255.0"
# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).
# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
# option client_config_dir /etc/openvpn/ccd
# list route "192.168.40.128 255.255.255.248"
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.
# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
# option client_config_dir /etc/openvpn/ccd
# list route "10.9.0.0 255.255.255.252"
# list route "192.168.100.0 255.255.255.0"
# Then add this line to ccd/Thelonious:
# ifconfig-push "10.9.0.1 10.9.0.2"
# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
# option learn_address /etc/openvpn/script
# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# the TUN/TAP interface to the internet in
# order for this to work properly).
# CAVEAT: May break client's network config if
# client's local DHCP server packets get routed
# through the tunnel. Solution: make sure
# client's local DHCP server is reachable via
# a more specific route than the default route
# of 0.0.0.0/0.0.0.0.
# list push "redirect-gateway"
# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# list push "dhcp-option DNS 10.8.0.1"
# list push "dhcp-option WINS 10.8.0.1"
# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
# option client_to_client 1
# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
# option duplicate_cn 1
# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
option keepalive "10 120"
# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
# This file is secret:
# option tls_auth "/etc/openvpn/ta.key 0"
# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
# Blowfish (default):
# option cipher BF-CBC
# AES:
# option cipher AES-128-CBC
# Triple-DES:
# option cipher DES-EDE3-CBC
# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
option comp_lzo yes
# The maximum number of concurrently connected
# clients we want to allow.
# option max_clients 100
# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
option persist_key 1
option persist_tun 1
option user nobody
# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
option status /tmp/openvpn-status.log
# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
# option log /tmp/openvpn.log
# option log_append /tmp/openvpn.log
# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
option verb 3
# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
# option mute 20
##############################################
# Sample client-side OpenVPN 2.0 uci config #
# for connecting to multi-client server. #
##############################################
config openvpn sample_client
# Set to 1 to enable this instance:
option enabled 0
# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
option client 1
# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
# option dev tap
option dev tun
# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
# option proto tcp
option proto udp
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
list remote "my_server_1 1194"
# list remote "my_server_2 1194"
# Choose a random host from the remote
# list for load_balancing. Otherwise
# try hosts in the order specified.
# option remote_random 1
# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
option resolv_retry infinite
# Most clients don't need to bind to
# a specific local port number.
option nobind 1
# Try to preserve some state across restarts.
option persist_key 1
option persist_tun 1
option user nobody
# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
# retry on connection failures:
# option http_proxy_retry 1
# specify http proxy address and port:
# option http_proxy "192.168.1.100 8080"
# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
# option mute_replay_warnings 1
# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
option ca /etc/openvpn/ca.crt
option cert /etc/openvpn/client.crt
option key /etc/openvpn/client.key
# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". This is an
# important precaution to protect against
# a potential attack discussed here:
# http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server". The build_key_server
# script in the easy_rsa folder will do this.
# option ns_cert_type server
# If a tls_auth key is used on the server
# then every client must also have the key.
# option tls_auth "/etc/openvpn/ta.key 1"
# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
# option cipher x
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
option comp_lzo yes
# Set log file verbosity.
option verb 3
# Silence repeating messages
# option mute 20Witam.
Mam sobie openwrt i na nim VPN.
Zainstalowałem jakiś czas temu.
Używam niezbyt często.
Działało ostatnio (kilka miesięcy temu)
Dziś mam problem.
Niby łączę się z ruterem, niby wszystko OK.
Mam ruch do internetu.
Nie widzę niestety komputerów w mojej sieci.
Sprawdzam to pingując ip lokalne rutera i próbując wchodzić na konsolę rutera (192.168.1.1)
Nie wiem jak to zdebugować.
Niby nic nie było zmieniane na routerze i na kompie (tak mi się wydaje).
Jak się połączę z laptopa widzę IP VPN:
Ethernet adapter Ethernet 3:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.1.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :Konfiguracja VPN rutera:
config openvpn 'VPNserver'
option enabled '1'
# --- Protocol ---#
option dev 'tun'
option dev 'tun0'
option topology 'subnet'
option proto 'udp'
option port '1194'
#--- Routes ---#
option server '10.1.1.0 255.255.255.0'
option ifconfig '10.1.1.1 255.255.255.0'
#--- Client Config ---#
# option ccd_exclusive '1'
# option ifconfig_pool_persist '/etc/openvpn/clients/ipp.txt'
# option client_config_dir '/etc/openvpn/clients/'
#--- Pushed Routes ---#
list push 'route 192.168.1.0 255.255.255.0'
list push 'dhcp-option DNS 192.168.1.1'
list push 'dhcp-option WINS 192.168.1.1'
list push 'dhcp-option DNS 8.8.8.8'
list push 'dhcp-option DNS 8.8.4.4'
list push 'dhcp-option NTP 129.6.15.30'
#--- Encryption ---#
option cipher 'AES-256-CBC'
option dh '/etc/openvpn/dh2048.pem'
option 'ca' '/etc/openvpn/ca.crt'
option 'cert' '/etc/openvpn/server.crt'
option 'key' '/etc/openvpn/server.key'
option tls_auth '/etc/openvpn/ta.key 0'
#--- Logging ---#
option log '/tmp/openvpn.log'
option status '/tmp/openvpn-status.log'
option verb '7'
#--- Connection Options ---#
option keepalive '10 120'
option comp_lzo 'yes'
#--- Connection Reliability ---#
option client_to_client '1'
option persist_key '1'
option persist_tun '1'
#--- Connection Speed ---#
option sndbuf '393216'
option rcvbuf '393216'
option fragment '0'
option mssfix '0'
option tun_mtu '24000'
#--- Pushed Buffers ---#
list push 'sndbuf 393216'
list push 'rcvbuf 393216'
#--- Permissions ---#
option user 'nobody'
option group 'nogroup' Konfiguracja firewall.
config defaults
option syn_flood '1'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'
config zone
option name 'lan'
list network 'lan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
config zone
option name 'wan'
list network 'wan'
list network 'wan6'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'
config forwarding
option src 'lan'
option dest 'wan'
config rule
option name 'Allow-DHCP-Renew'
option src 'wan'
option proto 'udp'
option dest_port '68'
option target 'ACCEPT'
option family 'ipv4'
config rule
option name 'Allow-Ping'
option src 'wan'
option proto 'icmp'
option icmp_type 'echo-request'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-IGMP'
option src 'wan'
option proto 'igmp'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-DHCPv6'
option src 'wan'
option proto 'udp'
option src_ip 'fe80::/10'
option src_port '547'
option dest_ip 'fe80::/10'
option dest_port '546'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-MLD'
option src 'wan'
option proto 'icmp'
option src_ip 'fe80::/10'
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Input'
option src 'wan'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
list icmp_type 'router-solicitation'
list icmp_type 'neighbour-solicitation'
list icmp_type 'router-advertisement'
list icmp_type 'neighbour-advertisement'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Forward'
option src 'wan'
option dest '*'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config include
option path '/etc/firewall.user'
config rule
option src 'wan'
option dest 'lan'
option proto 'esp'
option target 'ACCEPT'
config rule
option src 'wan'
option dest 'lan'
option dest_port '500'
option proto 'udp'
option target 'ACCEPT'
config redirect
option target 'DNAT'
option src 'wan'
option dest 'lan'
option proto 'tcp'
option name 'kamerka salon admin'
option dest_ip '192.168.1.151'
option src_dport '9090'
option dest_port '9090'
config redirect
option target 'DNAT'
option src 'wan'
option dest 'lan'
option proto 'tcp'
option name 'kamerka salon stream'
option dest_ip '192.168.1.151'
option src_dport '9091'
option dest_port '9091'
config rule
option target 'ACCEPT'
option name 'VPN'
option src 'wan'
option proto 'udp'
option dest_port '1194'
config zone
option name 'vpn'
option input 'ACCEPT'
option forward 'ACCEPT'
option output 'ACCEPT'
option network 'vpn0'
config forwarding
option src 'vpn'
option dest 'lan'
config forwarding
option src 'lan'
option dest 'vpn'
Nie dam sobie nic uciąć, ale wydaje mi się , ze konfiguracja nie była zmieniana, więc to chyba nie to.
Może to coś z laptopem.
Tablica rutingu wygląda następująco:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.43.1 192.168.43.136 55
10.1.1.0 255.255.255.0 On-link 10.1.1.2 291
10.1.1.2 255.255.255.255 On-link 10.1.1.2 291
10.1.1.255 255.255.255.255 On-link 10.1.1.2 291
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.1.0 255.255.255.0 10.1.1.1 10.1.1.2 291
192.168.43.0 255.255.255.0 On-link 192.168.43.136 311
192.168.43.136 255.255.255.255 On-link 192.168.43.136 311
192.168.43.255 255.255.255.255 On-link 192.168.43.136 311
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.43.136 311
224.0.0.0 240.0.0.0 On-link 10.1.1.2 291
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.43.136 311
255.255.255.255 255.255.255.255 On-link 10.1.1.2 291
===========================================================================Tam coś kiedyś zmieniałem, ale nie widzę tu nic niepokojącego.
Ping 10.1.1.1 nie działa.
I najważniejsze ping do rutera 192.168.1.1 nie działa
Powyższe konfiguracje rutera z backupu, bo tak jak pisałem obecnie nie mogę tam się wbić
Macie jakiś pomysł co to może być i co jeszcze mogę sprawdzić ?
Zrobiłem mały test.
Do urządzenia GPON podłączyłem bezpośrednio laptop.
Efekt ten sam. Godzinę internet był. Po godzinie nie było. Restart laptopa i internet jest.
Wygląda więc , że to chyba problem urządzenia dostawcy internetu.
Cześć,
Mam taki dziwny problem.
Sprzętowo moja architektura wygląda następująca:
Urządzenie GPON dostawcy internetu-> Linksys WRT1900ACS (statyczne IP)-> inne urządzenia przez kabel lub wifi
Mam Linksys WRT1900ACS, a na nim aktualny openwrt Chaos Calmer 15.05.1.
Dziś mam taką sytuację, że mniej więcej co godzinę trace internet.
lokalnie na maszyny wszystkie mogę wejść, tylko internetu brak.
Jak tracę internet wchodzę ssh na router i sprawdzam, czy działa ping, aby potwierdzić, że problem jest na styku GPON -> WRT.
Ping oczywiście nie działa.
Ciekawostką jest, to, że jak wtedy dam fizycznie restart tylko router, lub na nim wykonam reboot wszystko wraca do normy.
Po godzinie sytuacja się powtarza.
Wiecie co to może być i jak to zdiagnozować ?
Czy jak restart routera wystarcza mogę założyć, że problem jest tylko i wyłącznie po stronie routera, czy należy brać pod uwagę, że coś jest nie tak po stronie dostawcy internetu ?
Z góry dzięki za pomoc.
Cześć,
Mam taki problem.
Raz na jakiś czas mam jakieś skoki napięcia powodujące, że router podłączony do WAN przestaje działać.
Wtedy muszę go wyłączyć i włączyć ponownie.
Problem jest taki, że po tej operacji drugi router podłączony do tego pierwszego kablem sam się nie odnajduje w sieci.
Wifi na drugim przestaje działać (urządzenia nie dostają IP).
Oba router mają statyczne IP, wpisane, nie dns z dns.
Moje pytanie :
1. Da się jakoś temat rozwiązać, aby na tym drugim sam powracał internet jak tylko pierwszy zrestartuje ?
Jakiś skrypt uruchamiany co jakiś czas i w przypadku braku internetu restart, czy coś ?
2. Jest jakieś urządzenie, które będzie niwelowało te skoki napięcia ?
Mam nadzieje, że jasno opisałem problem.
Witam.
Mam Xiaomi Youth.
Wgrałem na nim openwrt-15.05.1-ramips-mt7628-mt7628-squashfs-sysupgrade.bin.
Wszystko działa poza .... WIFI.
W luci nie widzę sekcji WIFI.
Niżej dmesg i logread.
Wiecie co jest nie tak ?
root@OpenWrt:~# dmesg
[ 0.000000] Linux version 3.18.23 (buildbot@builder1) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47269) ) #1 Sun Jan 31 14:12:49 CET 2016
[ 0.000000] Board has DDR2
[ 0.000000] Analog PMU set to hw control
[ 0.000000] Digital PMU set to hw control
[ 0.000000] SoC Type: MediaTek MT7628AN ver:1 eco:2
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 00019655 (MIPS 24KEc)
[ 0.000000] MIPS: machine is Mediatek MT7628AN evaluation board
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 02000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x01ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00000000-0x01ffffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x01ffffff]
[ 0.000000] On node 0 totalpages: 8192
[ 0.000000] free_area_init_node: node 0, pgdat 8031c290, node_mem_map 81000000
[ 0.000000] Normal zone: 64 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 8192 pages, LIFO batch:0
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
[ 0.000000] Kernel command line: console=ttyS0,57600 rootfstype=squashfs,jffs2
[ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Writing ErrCtl register=00029ed4
[ 0.000000] Readback ErrCtl register=00029ed4
[ 0.000000] Memory: 28748K/32768K available (2619K kernel code, 131K rwdata, 528K rodata, 168K init, 190K bss, 4020K reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:256
[ 0.000000] intc: using register map from devicetree
[ 0.000000] CPU Clock: 580MHz
[ 0.000000] clocksource_of_init: no matching clocksources found
[ 0.050000] Calibrating delay loop... 385.84 BogoMIPS (lpj=1929216)
[ 0.060000] pid_max: default: 32768 minimum: 301
[ 0.060000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.070000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.070000] pinctrl core: initialized pinctrl subsystem
[ 0.080000] NET: Registered protocol family 16
[ 0.090000] rt2880-pinmux pinctrl: try to register 47 pins ...
[ 0.090000] pinctrl core: registered pin 0 (io0) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 1 (io1) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 2 (io2) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 3 (io3) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 4 (io4) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 5 (io5) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 6 (io6) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 7 (io7) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 8 (io8) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 9 (io9) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 10 (io10) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 11 (io11) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 12 (io12) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 13 (io13) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 14 (io14) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 15 (io15) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 16 (io16) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 17 (io17) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 18 (io18) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 19 (io19) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 20 (io20) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 21 (io21) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 22 (io22) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 23 (io23) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 24 (io24) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 25 (io25) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 26 (io26) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 27 (io27) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 28 (io28) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 29 (io29) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 30 (io30) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 31 (io31) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 32 (io32) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 33 (io33) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 34 (io34) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 35 (io35) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 36 (io36) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 37 (io37) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 38 (io38) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 39 (io39) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 40 (io40) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 41 (io41) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 42 (io42) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 43 (io43) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 44 (io44) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 45 (io45) on rt2880-pinmux
[ 0.090000] pinctrl core: registered pin 46 (io46) on rt2880-pinmux
[ 0.090000] pinctrl core: add 2 pinmux maps
[ 0.090000] rt2880-pinmux pinctrl: found group selector 4 for i2c
[ 0.090000] rt2880-pinmux pinctrl: invalid group "jtag" for function "gpio"
[ 0.100000] mt7621_gpio 10000600.gpio: registering 32 gpios
[ 0.100000] mt7621_gpio 10000600.gpio: registering 32 gpios
[ 0.110000] mt7621_gpio 10000600.gpio: registering 32 gpios
[ 0.110000] Switched to clocksource MIPS
[ 0.120000] NET: Registered protocol family 2
[ 0.120000] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.120000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.130000] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.130000] TCP: reno registered
[ 0.140000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.140000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.150000] NET: Registered protocol family 1
[ 0.150000] PCI: CLS 0 bytes, default 32
[ 0.160000] alarmtimer alarmtimer: no of_node; not parsing pinctrl DT
[ 0.160000] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.170000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.180000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.190000] msgmni has been set to 56
[ 0.200000] io scheduler noop registered
[ 0.200000] io scheduler deadline registered (default)
[ 0.200000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.210000] serial8250 serial8250: no of_node; not parsing pinctrl DT
[ 0.210000] pinctrl core: add 1 pinmux maps
[ 0.210000] rt2880-pinmux pinctrl: found group selector 10 for uart0
[ 0.210000] rt2880-pinmux pinctrl: request pin 12 (io12) for 10000c00.uartlite
[ 0.210000] rt2880-pinmux pinctrl: request pin 13 (io13) for 10000c00.uartlite
[ 0.210000] console [ttyS0] disabled
[ 0.220000] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 28, base_baud = 2500000) is a 16550A
[ 0.230000] console [ttyS0] enabled
[ 0.240000] bootconsole [early0] disabled
[ 0.260000] pinctrl core: add 1 pinmux maps
[ 0.260000] rt2880-pinmux pinctrl: found group selector 8 for spi
[ 0.260000] rt2880-pinmux pinctrl: request pin 7 (io7) for 10000b00.spi
[ 0.260000] rt2880-pinmux pinctrl: request pin 8 (io8) for 10000b00.spi
[ 0.260000] rt2880-pinmux pinctrl: request pin 9 (io9) for 10000b00.spi
[ 0.260000] rt2880-pinmux pinctrl: request pin 10 (io10) for 10000b00.spi
[ 0.260000] spi-mt7621 10000b00.spi: sys_freq: 193333333
[ 0.280000] m25p80 spi32766.0: found w25q128, expected en25q64
[ 0.300000] m25p80 spi32766.0: w25q128 (16384 Kbytes)
[ 0.310000] m25p80 spi32766.0: using chunked io
[ 0.310000] 4 ofpart partitions found on MTD device spi32766.0
[ 0.330000] Creating 4 MTD partitions on "spi32766.0":
[ 0.340000] 0x000000000000-0x000000030000 : "u-boot"
[ 0.350000] 0x000000030000-0x000000040000 : "u-boot-env"
[ 0.360000] 0x000000040000-0x000000050000 : "factory"
[ 0.370000] 0x000000050000-0x000000800000 : "firmware"
[ 0.410000] 2 uimage-fw partitions found on MTD device firmware
[ 0.420000] 0x000000050000-0x00000016fac2 : "kernel"
[ 0.430000] 0x00000016fac2-0x000000800000 : "rootfs"
[ 0.440000] mtd: device 5 (rootfs) set to be root filesystem
[ 0.460000] 1 squashfs-split partitions found on MTD device rootfs
[ 0.470000] 0x000000340000-0x000000800000 : "rootfs_data"
[ 0.490000] ralink_soc_eth 10100000.ethernet: generated random MAC address 06:49:38:37:a7:85
[ 0.510000] ralink_soc_eth 10100000.ethernet eth0: ralink at 0xb0100000, irq 5
[ 0.520000] mt7621_wdt 10000120.watchdog: Initialized
[ 0.530000] TCP: cubic registered
[ 0.540000] NET: Registered protocol family 17
[ 0.550000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 0.570000] Bridge firewalling registered
[ 0.580000] 8021q: 802.1Q VLAN Support v1.8
[ 0.600000] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[ 0.620000] Freeing unused kernel memory: 168K (80336000 - 80360000)
[ 2.250000] init: Console is alive
[ 2.260000] init: - watchdog -
[ 3.180000] usbcore: registered new interface driver usbfs
[ 3.190000] usbcore: registered new interface driver hub
[ 3.210000] usbcore: registered new device driver usb
[ 3.220000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.230000] ehci-platform: EHCI generic platform driver
[ 3.440000] phy phy-usbphy.0: remote usb device wakeup disabled
[ 3.460000] phy phy-usbphy.0: UTMI 16bit 30MHz
[ 3.470000] ehci-platform 101c0000.ehci: EHCI Host Controller
[ 3.480000] ehci-platform 101c0000.ehci: new USB bus registered, assigned bus number 1
[ 3.490000] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
[ 3.520000] ehci-platform 101c0000.ehci: USB 2.0 started, EHCI 1.00
[ 3.530000] usb usb1: no of_node; not parsing pinctrl DT
[ 3.530000] hub 1-0:1.0: no of_node; not parsing pinctrl DT
[ 3.530000] hub 1-0:1.0: USB hub found
[ 3.540000] hub 1-0:1.0: 1 port detected
[ 3.550000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.560000] ohci-platform: OHCI generic platform driver
[ 3.570000] ohci-platform 101c1000.ohci: Generic Platform OHCI controller
[ 3.580000] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2
[ 3.600000] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000
[ 3.670000] usb usb2: no of_node; not parsing pinctrl DT
[ 3.670000] hub 2-0:1.0: no of_node; not parsing pinctrl DT
[ 3.670000] hub 2-0:1.0: USB hub found
[ 3.680000] hub 2-0:1.0: 1 port detected
[ 4.500000] init: - preinit -
[ 5.370000] rt305x-esw 10110000.esw: link changed 0x00
[ 5.550000] random: mktemp urandom read with 8 bits of entropy available
[ 8.790000] mount_root: jffs2 not ready yet, using temporary tmpfs overlay
[ 8.830000] procd: - early -
[ 8.840000] procd: - watchdog -
[ 8.890000] rt305x-esw 10110000.esw: link changed 0x04
[ 9.730000] procd: - ubus -
[ 10.750000] procd: - init -
[ 11.360000] NET: Registered protocol family 10
[ 11.380000] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 11.410000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 11.420000] nf_conntrack version 0.5.0 (451 buckets, 1804 max)
[ 11.470000] xt_time: kernel timezone is -0000
[ 11.490000] PPP generic driver version 2.4.2
[ 11.500000] NET: Registered protocol family 24
[ 15.260000] rt305x-esw 10110000.esw: link changed 0x00
[ 17.040000] device eth0.1 entered promiscuous mode
[ 17.050000] device eth0 entered promiscuous mode
[ 17.100000] br-lan: port 1(eth0.1) entered forwarding state
[ 17.110000] br-lan: port 1(eth0.1) entered forwarding state
[ 18.430000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
[ 18.580000] jffs2_build_filesystem(): unlocking the mtd device... done.
[ 18.590000] jffs2_build_filesystem(): erasing all blocks after the end marker...
[ 18.740000] rt305x-esw 10110000.esw: link changed 0x04
[ 19.110000] br-lan: port 1(eth0.1) entered forwarding state
[ 41.730000] done.
[ 41.730000] jffs2: notice: (932) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 78.800000] random: nonblocking pool is initialized
root@OpenWrt:~#
root@OpenWrt:~# logread
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 19 (io19) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 20 (io20) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 21 (io21) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 22 (io22) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 23 (io23) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 24 (io24) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 25 (io25) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 26 (io26) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 27 (io27) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 28 (io28) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 29 (io29) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 30 (io30) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 31 (io31) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 32 (io32) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 33 (io33) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 34 (io34) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 35 (io35) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 36 (io36) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 37 (io37) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 38 (io38) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 39 (io39) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 40 (io40) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 41 (io41) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 42 (io42) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 43 (io43) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 44 (io44) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 45 (io45) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: registered pin 46 (io46) on rt2880-pinmux
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] pinctrl core: add 2 pinmux maps
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.090000] rt2880-pinmux pinctrl: found group selector 4 for i2c
Sun Jan 31 13:07:19 2016 kern.err kernel: [ 0.090000] rt2880-pinmux pinctrl: invalid group "jtag" for function "gpio"
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.100000] mt7621_gpio 10000600.gpio: registering 32 gpios
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.100000] mt7621_gpio 10000600.gpio: registering 32 gpios
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.110000] mt7621_gpio 10000600.gpio: registering 32 gpios
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.110000] Switched to clocksource MIPS
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.120000] NET: Registered protocol family 2
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.120000] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.120000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.130000] TCP: Hash tables configured (established 1024 bind 1024)
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.130000] TCP: reno registered
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.140000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.140000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.150000] NET: Registered protocol family 1
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.150000] PCI: CLS 0 bytes, default 32
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.160000] alarmtimer alarmtimer: no of_node; not parsing pinctrl DT
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.160000] futex hash table entries: 256 (order: -1, 3072 bytes)
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.170000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.180000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.190000] msgmni has been set to 56
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.200000] io scheduler noop registered
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.200000] io scheduler deadline registered (default)
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.200000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.210000] serial8250 serial8250: no of_node; not parsing pinctrl DT
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.210000] pinctrl core: add 1 pinmux maps
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.210000] rt2880-pinmux pinctrl: found group selector 10 for uart0
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.210000] rt2880-pinmux pinctrl: request pin 12 (io12) for 10000c00.uartlite
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.210000] rt2880-pinmux pinctrl: request pin 13 (io13) for 10000c00.uartlite
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.210000] console [ttyS0] disabled
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.220000] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 28, base_baud = 2500000) is a 16550A
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.230000] console [ttyS0] enabled
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.240000] bootconsole [early0] disabled
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.260000] pinctrl core: add 1 pinmux maps
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.260000] rt2880-pinmux pinctrl: found group selector 8 for spi
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.260000] rt2880-pinmux pinctrl: request pin 7 (io7) for 10000b00.spi
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.260000] rt2880-pinmux pinctrl: request pin 8 (io8) for 10000b00.spi
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.260000] rt2880-pinmux pinctrl: request pin 9 (io9) for 10000b00.spi
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 0.260000] rt2880-pinmux pinctrl: request pin 10 (io10) for 10000b00.spi
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.260000] spi-mt7621 10000b00.spi: sys_freq: 193333333
Sun Jan 31 13:07:19 2016 kern.warn kernel: [ 0.280000] m25p80 spi32766.0: found w25q128, expected en25q64
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.300000] m25p80 spi32766.0: w25q128 (16384 Kbytes)
Sun Jan 31 13:07:19 2016 kern.warn kernel: [ 0.310000] m25p80 spi32766.0: using chunked io
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.310000] 4 ofpart partitions found on MTD device spi32766.0
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.330000] Creating 4 MTD partitions on "spi32766.0":
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.340000] 0x000000000000-0x000000030000 : "u-boot"
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.350000] 0x000000030000-0x000000040000 : "u-boot-env"
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.360000] 0x000000040000-0x000000050000 : "factory"
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.370000] 0x000000050000-0x000000800000 : "firmware"
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.410000] 2 uimage-fw partitions found on MTD device firmware
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.420000] 0x000000050000-0x00000016fac2 : "kernel"
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.430000] 0x00000016fac2-0x000000800000 : "rootfs"
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.440000] mtd: device 5 (rootfs) set to be root filesystem
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.460000] 1 squashfs-split partitions found on MTD device rootfs
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.470000] 0x000000340000-0x000000800000 : "rootfs_data"
Sun Jan 31 13:07:19 2016 kern.err kernel: [ 0.490000] ralink_soc_eth 10100000.ethernet: generated random MAC address 06:49:38:37:a7:85
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.510000] ralink_soc_eth 10100000.ethernet eth0: ralink at 0xb0100000, irq 5
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.520000] mt7621_wdt 10000120.watchdog: Initialized
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.530000] TCP: cubic registered
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.540000] NET: Registered protocol family 17
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.550000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 0.570000] Bridge firewalling registered
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.580000] 8021q: 802.1Q VLAN Support v1.8
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.600000] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 0.620000] Freeing unused kernel memory: 168K (80336000 - 80360000)
Sun Jan 31 13:07:19 2016 user.info kernel: [ 2.250000] init: Console is alive
Sun Jan 31 13:07:19 2016 user.info kernel: [ 2.260000] init: - watchdog -
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.180000] usbcore: registered new interface driver usbfs
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.190000] usbcore: registered new interface driver hub
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.210000] usbcore: registered new device driver usb
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.220000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.230000] ehci-platform: EHCI generic platform driver
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.440000] phy phy-usbphy.0: remote usb device wakeup disabled
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.460000] phy phy-usbphy.0: UTMI 16bit 30MHz
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.470000] ehci-platform 101c0000.ehci: EHCI Host Controller
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.480000] ehci-platform 101c0000.ehci: new USB bus registered, assigned bus number 1
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.490000] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.520000] ehci-platform 101c0000.ehci: USB 2.0 started, EHCI 1.00
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 3.530000] usb usb1: no of_node; not parsing pinctrl DT
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 3.530000] hub 1-0:1.0: no of_node; not parsing pinctrl DT
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.530000] hub 1-0:1.0: USB hub found
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.540000] hub 1-0:1.0: 1 port detected
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.550000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.560000] ohci-platform: OHCI generic platform driver
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.570000] ohci-platform 101c1000.ohci: Generic Platform OHCI controller
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.580000] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.600000] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 3.670000] usb usb2: no of_node; not parsing pinctrl DT
Sun Jan 31 13:07:19 2016 kern.debug kernel: [ 3.670000] hub 2-0:1.0: no of_node; not parsing pinctrl DT
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.670000] hub 2-0:1.0: USB hub found
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 3.680000] hub 2-0:1.0: 1 port detected
Sun Jan 31 13:07:19 2016 user.info kernel: [ 4.500000] init: - preinit -
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 5.370000] rt305x-esw 10110000.esw: link changed 0x00
Sun Jan 31 13:07:19 2016 kern.notice kernel: [ 5.550000] random: mktemp urandom read with 8 bits of entropy available
Sun Jan 31 13:07:19 2016 user.notice kernel: [ 8.790000] mount_root: jffs2 not ready yet, using temporary tmpfs overlay
Sun Jan 31 13:07:19 2016 user.info kernel: [ 8.830000] procd: - early -
Sun Jan 31 13:07:19 2016 user.info kernel: [ 8.840000] procd: - watchdog -
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 8.890000] rt305x-esw 10110000.esw: link changed 0x04
Sun Jan 31 13:07:19 2016 user.info kernel: [ 9.730000] procd: - ubus -
Sun Jan 31 13:07:19 2016 user.info kernel: [ 10.750000] procd: - init -
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 11.360000] NET: Registered protocol family 10
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 11.380000] ip6_tables: (C) 2000-2006 Netfilter Core Team
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 11.410000] ip_tables: (C) 2000-2006 Netfilter Core Team
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 11.420000] nf_conntrack version 0.5.0 (451 buckets, 1804 max)
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 11.470000] xt_time: kernel timezone is -0000
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 11.490000] PPP generic driver version 2.4.2
Sun Jan 31 13:07:19 2016 kern.info kernel: [ 11.500000] NET: Registered protocol family 24
Sun Jan 31 13:07:20 2016 kern.info kernel: [ 15.260000] rt305x-esw 10110000.esw: link changed 0x00
Sun Jan 31 13:07:21 2016 kern.info kernel: [ 17.040000] device eth0.1 entered promiscuous mode
Sun Jan 31 13:07:21 2016 kern.info kernel: [ 17.050000] device eth0 entered promiscuous mode
Sun Jan 31 13:07:21 2016 kern.info kernel: [ 17.100000] br-lan: port 1(eth0.1) entered forwarding state
Sun Jan 31 13:07:21 2016 kern.info kernel: [ 17.110000] br-lan: port 1(eth0.1) entered forwarding state
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'lan' is enabled
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'lan' is setting up now
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'lan' is now up
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'loopback' is enabled
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'loopback' is setting up now
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'loopback' is now up
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'wan6' is enabled
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Bridge 'br-lan' link is up
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'lan' has link connectivity
Sun Jan 31 13:07:21 2016 daemon.notice netifd: VLAN 'eth0.1' link is up
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Network device 'lo' link is up
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'loopback' has link connectivity
Sun Jan 31 13:07:21 2016 daemon.notice netifd: VLAN 'eth0.2' link is up
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'wan6' has link connectivity
Sun Jan 31 13:07:21 2016 daemon.notice netifd: Interface 'wan6' is setting up now
Sun Jan 31 13:07:22 2016 daemon.notice netifd: wan (906): udhcpc (v1.23.2) started
Sun Jan 31 13:07:22 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sun Jan 31 13:07:23 2016 daemon.notice netifd: wan (906): Sending discover...
Sun Jan 31 13:07:23 2016 daemon.err mount_root: no jffs2 marker found
Sun Jan 31 13:07:23 2016 kern.warn kernel: [ 18.430000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
Sun Jan 31 13:07:23 2016 kern.warn kernel: [ 18.580000] jffs2_build_filesystem(): unlocking the mtd device... done.
Sun Jan 31 13:07:23 2016 kern.warn kernel: [ 18.590000] jffs2_build_filesystem(): erasing all blocks after the end marker...
Sun Jan 31 13:07:23 2016 kern.info kernel: [ 18.740000] rt305x-esw 10110000.esw: link changed 0x04
Sun Jan 31 13:07:23 2016 kern.info kernel: [ 19.110000] br-lan: port 1(eth0.1) entered forwarding state
Sun Jan 31 13:07:26 2016 daemon.notice netifd: wan (906): Sending discover...
Sun Jan 31 13:07:29 2016 daemon.info dnsmasq[982]: started, version 2.73 cachesize 150
Sun Jan 31 13:07:29 2016 daemon.info dnsmasq[982]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Sun Jan 31 13:07:29 2016 daemon.info dnsmasq[982]: DNS service limited to local subnets
Sun Jan 31 13:07:29 2016 daemon.info dnsmasq-dhcp[982]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Sun Jan 31 13:07:29 2016 daemon.info dnsmasq[982]: using local addresses only for domain lan
Sun Jan 31 13:07:29 2016 daemon.warn dnsmasq[982]: no servers found in /tmp/resolv.conf.auto, will retry
Sun Jan 31 13:07:29 2016 daemon.info dnsmasq[982]: read /etc/hosts - 1 addresses
Sun Jan 31 13:07:29 2016 daemon.info dnsmasq[982]: read /tmp/hosts/dhcp - 1 addresses
Sun Jan 31 13:07:29 2016 daemon.notice netifd: wan (906): Sending discover...
Sun Jan 31 13:07:29 2016 daemon.info dnsmasq-dhcp[982]: read /etc/ethers - 0 addresses
Sun Jan 31 13:07:46 2016 kern.warn kernel: [ 41.730000] done.
Sun Jan 31 13:07:46 2016 kern.notice kernel: [ 41.730000] jffs2: notice: (932) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Sun Jan 31 13:07:46 2016 daemon.info mount_root: performing overlay whiteout
Sun Jan 31 13:07:47 2016 daemon.info procd: - init complete -
Sun Jan 31 13:07:56 2016 authpriv.info dropbear[1084]: Not backgrounding
Sun Jan 31 13:08:23 2016 kern.notice kernel: [ 78.800000] random: nonblocking pool is initialized
Sun Jan 31 13:09:23 2016 auth.info passwd: Password for root changed by root
Sun Jan 31 13:17:38 2016 authpriv.info dropbear[1999]: Child connection from 192.168.1.2:52666
Sun Jan 31 13:17:45 2016 authpriv.notice dropbear[1999]: Password auth succeeded for 'root' from 192.168.1.2:52666
root@OpenWrt:~#
Trochę stare, ale może ktoś odpowie:
Mówimy o tym:
http://www.ebay.com/itm/Wifi-Cell-Phone … 2330794802
Rozumiem, że jest tam własny openwrt i wystarczy tylko wgrać firmware openwrt dla TL-WR703N v1 i będzie tam czysty openwrt z ssh i luci ?
Ktoś wie ile pamięci jest na pokładzie ?
Cześć,
Problem cały czas występuję.
Minęło kilka dni, kilka restartów routera i WOL znów przestał działać.
Dodaje komp do arp:
ip neigh change 192.168.1.10 lladdr XX:XX:XX:XX:XX:XX nud permanent dev br-lan
ip neigh add 192.168.1.10 lladdr XX:XX:XX:XX:XX:XX nud permanent dev br-lan
Wywołuje WOL:
/usr/bin/etherwake -D -i "br-lan" "XX:XX:XX:XX:XX:XX"
NIC.
Między routerem, a kompem jest switch.
Teraz sprawdzam to szczegółowo , i co zauważyłem, że problemem nie jest sam reboot routera .
Wygląda tak jakby jak reboot zrobię w krótkim czasie od ostatniego użycia kompa (bez dodania wpisów do ARP), to po restarcie wol działa.
Nie działa po dłuższym czasie nieużywania.
Tak jakby router po dłuższym czasie nie używania zapominał o kompie.
Dłuższy czas jaki wcześniej zaobserwowałem to kilak dni.
Spróbuj dodać ten komputer do static DHCP leases, wtedy automatycznie doda się do tablicy ARP i wtedy zrób testy.
Problem jest taki, że ten komputer jest w static DHCP leases od dawna.
Już nie mam pomysłu co to jest i jak to zwalczyć.
Może niezbyt jasno się wypowiedziałem. Oczywiście wyłączam nie fizycznie, tylko shutdown -h now.
Jeszcze raz : WOL działa mi tyło wtedy jak fizycznie uruchomie komputer i automatycznie na routerze pojawi sie w ARP wpis dla tego komputera.
Test 1.
Włączam fizycznie komp.
Robię na kompie shutdown -h now . Wol działa
Test 2.
Włączam fizycznie komp.
Robię na kompie shutdown -h now . Robie restart routera. W arp wpisów nie ma więc je ręcznie dodaje. Wol nie działa.
To może jeszcze raz:
Wykonuje:
ip neigh change 192.168.1.10 lladdr XX:XX:XX:XX:XX:XX nud permanent dev br-lan
ip neigh add 192.168.1.10 lladdr XX:XX:XX:XX:XX:XX nud permanent dev br-lan
arp -a
IP address HW type Flags HW address Mask Device
...
192.168.1.10 0x1 0x6 XX:XX:XX:XX:XX:XX * br-lan
...
Adres jak widać jest w ARP
Dalej wywołuje WOL
/usr/bin/etherwake -D -i "br-lan" "XX:XX:XX:XX:XX:XX"
Nie wywołuje się.
Działą WOL tylko wtedy jak komputer włączę ręcznie i potem go wyłącze.
Nie działa po wpisaniu ręcznie rekordu do ARP i próbie WOL.
Zakładam, ze po ręcznym wprowadzeniu mac do apr WOL powinien działać.
Ma ktoś jakiś pomysł co jest nie tak z tym moim WOL ?
Strony Poprzednia 1 2 3 4 Następna
eko.one.pl → Posty przez marcin.kasinski
Forum oparte o PunBB, wspierane przez Informer Technologies, Inc