Проблемы с GPRS-подключением


#104

Подключил minicom

aaaaaaaaat
OK
at+cops=?
+COPS: (2,"Beeline","Beeline","25099"),(1,"Beeline","Beeline","25099"),(1,"Mega)

OK
at+csq
+CSQ: 12,0

OK

Антенна вроде работает нормально - сигнал хороший.

Отправил СМС:

at+cmgf=?
+CMGF: (0,1)

OK
at+cmgf?
+CMGF: 0

OK
at+creg?
+CREG: 0,1

OK
at+cmgf=1
OK
at+cmgs=+79219438141
> test message
+CMGS: 0

OK

Дошло нормально!

Надо все-таки идти за симкой.


#105

Вроде по ppp0 IP-адрес получен. Попробуйте ping -I ppp0 8.8.8.8


#106

Команда ping -I ppp0 8.8.8.8
проходит!

root@wirenboard-AV6U5XZP:~# ping -I ppp0 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 10.224.44.227 ppp0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=2145 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=1087 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=99.4 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=115 time=91.6 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=115 time=86.4 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=115 time=1435 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=115 time=502 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=115 time=299 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=115 time=318 ms
^C
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9184ms
rtt min/avg/max/mdev = 86.430/674.096/2145.961/685.437 ms, pipe 3
root@wirenboard-AV6U5XZP:~#

Что это значит?
Не пойму, что за option -I ppp0 :frowning:

http://cloud.contactless.ru через GPRS молчит пока…


#107

Отправлять пинги через сетевой интерфейс ppp0, т.е. через модем. Без этой опции трафик идёт по стандартным правилам маршрутизации.

Покажите вывод route -n, скорее всего там что-то не то.


#108

Это все:

root@wirenboard-AV6U5XZP:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0

#109

Что бы исключить вопросы к симке, вчера взял МТС.
Поставил, поменял interfaces на mts
Ничего не изменилось, все симптомы остались на месте.


#110

Flagman, подскажите, как вы определяете, что облако недоступно через ppp0, но доступно как-то иначе?

Смотрите, когда поднимается интерфейс ppp0 и дефолтный маршрут (0.0.0.0) установлен через, скажем, eth0, то pppd не поднимет новый дефолтный маршрут через ppp0. Это особенность конфигурации по умолчанию.

Если вы имеете доступ к контроллеру из локальной сети или через отладочную консоль, удалите дефолтный маршрут командой
route del default
и задайте явно маршрут по умолчанию командой
route add default dev ppp0

Заработало?


#111

Сдвинулось!

root@wirenboard-AV6U5XZP:~# route del default
root@wirenboard-AV6U5XZP:~# route add default dev ppp0
root@wirenboard-AV6U5XZP:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 ppp0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0
root@wirenboard-AV6U5XZP:~#
root@wirenboard-AV6U5XZP:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=46 time=5593 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=46 time=4580 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=46 time=3548 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=46 time=2544 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=46 time=1512 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=46 time=533 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=46 time=3033 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=46 time=2774 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=46 time=1994 ms
^C
--- 8.8.8.8 ping statistics ---
13 packets transmitted, 9 received, 30% packet loss, time 12380ms
rtt min/avg/max/mdev = 533.617/2901.814/5593.534/1453.120 ms, pipe 6

Пинги пошли.
Проверяем cloud.wirenboard.ru:

root@wirenboard-AV6U5XZP:~# ping cloud.wirenboard.ru
PING contactless.ru (194.85.80.11) 56(84) bytes of data.
64 bytes from ip80-11.campus.mipt.ru (194.85.80.11): icmp_seq=1 ttl=52 time=5536 ms
64 bytes from ip80-11.campus.mipt.ru (194.85.80.11): icmp_seq=2 ttl=52 time=5434 ms
64 bytes from ip80-11.campus.mipt.ru (194.85.80.11): icmp_seq=3 ttl=52 time=5864 ms
64 bytes from ip80-11.campus.mipt.ru (194.85.80.11): icmp_seq=4 ttl=52 time=6042 ms
64 bytes from ip80-11.campus.mipt.ru (194.85.80.11): icmp_seq=5 ttl=52 time=6124 ms
64 bytes from ip80-11.campus.mipt.ru (194.85.80.11): icmp_seq=6 ttl=52 time=6364 ms
64 bytes from ip80-11.campus.mipt.ru (194.85.80.11): icmp_seq=7 ttl=52 time=6311 ms
64 bytes from ip80-11.campus.mipt.ru (194.85.80.11): icmp_seq=8 ttl=52 time=6569 ms
^C
--- contactless.ru ping statistics ---
14 packets transmitted, 8 received, 42% packet loss, time 13238ms
rtt min/avg/max/mdev = 5434.716/6031.063/6569.752/373.620 ms, pipe 7

Далее проверяем получение данных по запросу:

root@wirenboard-AV6U5XZP:~# mosquitto_sub -v -h contactless.ru -u wb_AV6U5XZP -P xxxxxxxxxxxxxxxx -t "/#"
/client/wb_AV6U5XZP/devices/network/controls/Ethernet 0 IP 192.168.1.35

/client/wb_AV6U5XZP/devices/network/controls/Ethernet 0 IP/meta/type text
/client/wb_AV6U5XZP/devices/network/controls/Ethernet 0 IP/meta/order 1
/client/wb_AV6U5XZP/devices/network/controls/Wi-Fi 0 IP/meta/type text
/client/wb_AV6U5XZP/devices/network/controls/Wi-Fi 0 IP/meta/order 4
/client/wb_AV6U5XZP/devices/network/controls/Ethernet 1 IP/meta/type text
/client/wb_AV6U5XZP/devices/network/controls/Ethernet 1 IP/meta/order 2
/client/wb_AV6U5XZP/devices/network/controls/Wi-Fi 1 IP/meta/type text
/client/wb_AV6U5XZP/devices/network/controls/Wi-Fi 1 IP/meta/order 5
/client/wb_AV6U5XZP/devices/network/controls/GPRS IP 10.219.43.158

/client/wb_AV6U5XZP/devices/network/controls/GPRS IP/meta/type text
/client/wb_AV6U5XZP/devices/network/controls/GPRS IP/meta/order 3
/client/wb_AV6U5XZP/devices/network/meta/name Network
/client/wb_AV6U5XZP/devices/system/controls/Current uptime 0d 0h 10m

/client/wb_AV6U5XZP/devices/system/controls/Current uptime/meta/type text
/client/wb_AV6U5XZP/devices/system/controls/Current uptime/meta/order 1
/client/wb_AV6U5XZP/devices/system/controls/DTS Version 61

/client/wb_AV6U5XZP/devices/system/controls/DTS Version/meta/type text
/client/wb_AV6U5XZP/devices/system/controls/DTS Version/meta/order 2
/client/wb_AV6U5XZP/devices/system/controls/Firmware version 201807100856

/client/wb_AV6U5XZP/devices/system/controls/Firmware version/meta/type text
/client/wb_AV6U5XZP/devices/system/controls/Firmware version/meta/order 3
/client/wb_AV6U5XZP/devices/system/controls/Reboot/meta/type pushbutton
/client/wb_AV6U5XZP/devices/system/controls/Reboot/meta/order 4
/client/wb_AV6U5XZP/devices/system/controls/Short SN AV6U5XZP

/client/wb_AV6U5XZP/devices/system/controls/Short SN/meta/type text
/client/wb_AV6U5XZP/devices/system/controls/Short SN/meta/order 5
/client/wb_AV6U5XZP/devices/system/meta/name System
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.82
/client/wb_AV6U5XZP/devices/power_status/controls/Vin/meta/type voltage
/client/wb_AV6U5XZP/devices/power_status/controls/Vin/meta/order 1
/client/wb_AV6U5XZP/devices/power_status/controls/working on battery 0
/client/wb_AV6U5XZP/devices/power_status/controls/working on battery/meta/type switch
/client/wb_AV6U5XZP/devices/power_status/controls/working on battery/meta/readonly 1
/client/wb_AV6U5XZP/devices/power_status/controls/working on battery/meta/order 2
/client/wb_AV6U5XZP/devices/power_status/meta/name Power status
/client/wb_AV6U5XZP/devices/wb-adc/controls/Vin 11.82
/client/wb_AV6U5XZP/devices/wb-adc/controls/5Vout 4.87
/client/wb_AV6U5XZP/devices/wb-adc/controls/A1 0.01
/client/wb_AV6U5XZP/devices/wb-adc/controls/A2 3.16
/client/wb_AV6U5XZP/devices/wb-adc/controls/A3 3.13
/client/wb_AV6U5XZP/devices/wb-adc/controls/A4 0.00
/client/wb_AV6U5XZP/devices/wb-w1/controls/28-041621a1f3ff 24.437
/client/wb_AV6U5XZP/devices/wb-w1/controls/28-041621bd3cff 24.375
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A3_OUT 0
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A4_IN 0
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A1_IN 1
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A1_OUT 1
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A2_OUT 0
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A2_IN 0
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A3_IN 1
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A4_OUT 0
/client/wb_AV6U5XZP/devices/CloudSend/controls/Auto 1
/client/wb_AV6U5XZP/devices/buzzer/controls/enabled 0
/client/wb_AV6U5XZP/devices/buzzer/controls/enabled/meta/type switch
/client/wb_AV6U5XZP/devices/buzzer/controls/enabled/meta/order 1
/client/wb_AV6U5XZP/devices/buzzer/controls/frequency 3000
/client/wb_AV6U5XZP/devices/buzzer/controls/frequency/meta/type range
/client/wb_AV6U5XZP/devices/buzzer/controls/frequency/meta/order 2
/client/wb_AV6U5XZP/devices/buzzer/controls/frequency/meta/max 7000
/client/wb_AV6U5XZP/devices/buzzer/controls/volume 10
/client/wb_AV6U5XZP/devices/buzzer/controls/volume/meta/type range
/client/wb_AV6U5XZP/devices/buzzer/controls/volume/meta/order 3
/client/wb_AV6U5XZP/devices/buzzer/controls/volume/meta/max 100
/client/wb_AV6U5XZP/devices/buzzer/meta/name Buzzer
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/meta/name T-Sensor 01-02
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Internal Temperature 24.5
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Internal Temperature/meta/type temperature
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Internal Temperature/meta/order 1
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/External Sensor 1 24.75
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/External Sensor 1/meta/type temperature
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/External Sensor 1/meta/order 2
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/External Sensor 2 24.625
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/External Sensor 2/meta/type temperature
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/External Sensor 2/meta/order 3
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.852
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage/meta/type voltage
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage/meta/readonly 1
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage/meta/order 4
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Serial NO 4276306540
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Serial NO/meta/type text
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Serial NO/meta/order 5
/client/wb_AV6U5XZP/devices/wbrules/controls/Rule debugging 0
/client/wb_AV6U5XZP/devices/wbrules/controls/Rule debugging/meta/type switch
/client/wb_AV6U5XZP/devices/wbrules/controls/Rule debugging/meta/order 1
/client/wb_AV6U5XZP/devices/wbrules/meta/name Rule Engine Settings
/client/wb_AV6U5XZP/devices/alarms/meta/name Alarms
/client/wb_AV6U5XZP/devices/alarms/controls/log/meta/type text
/client/wb_AV6U5XZP/devices/alarms/controls/log/meta/readonly 1
/client/wb_AV6U5XZP/devices/alarms/controls/log/meta/order 1
/client/wb_AV6U5XZP/config/rooms/room1/uid room1
/client/wb_AV6U5XZP/config/rooms/room1/name Гостиная
/client/wb_AV6U5XZP/config/dashboards/dashboard1/name Квартира
/client/wb_AV6U5XZP/config/dashboards/dashboard1/uid dashboard1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/controls/slot0/uid slot0
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/controls/slot0/topic/name External Sensor 1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/controls/slot0/topic/value 25.3125
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/controls/slot0/topic/topic /devices/T-Sensor 01-02/controls/External Sensor 1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/controls/slot0/topic/$$hashKey object:230
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/controls/slot0/topic/metaType temperature
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/controls/slot0/topic/metaOrder 2
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/uid widget1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/name Exterrnal sensor 1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/room room1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/template temperature
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget0/canEdit false
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/controls/slot0/uid slot0
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/controls/slot0/topic/name External Sensor 2
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/controls/slot0/topic/value 25.375
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/controls/slot0/topic/topic /devices/T-Sensor 01-02/controls/External Sensor 2
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/controls/slot0/topic/$$hashKey object:235
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/controls/slot0/topic/metaType temperature
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/controls/slot0/topic/metaOrder 3
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/uid widget2
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/name Exterrnal sensor 2
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/room room1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/template temperature
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget1/canEdit false
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/controls/slot0/uid slot0
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/controls/slot0/topic/name 28-041621a1f3ff
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/controls/slot0/topic/value 23.562
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/controls/slot0/topic/topic /devices/wb-w1/controls/28-041621a1f3ff
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/controls/slot0/topic/$$hashKey object:10
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/uid widget3
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/name ds18b20 T1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/room room1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget2/template sensor
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/controls/slot0/uid slot0
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/controls/slot0/topic/name 28-041621bd3cff
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/controls/slot0/topic/value 23.437
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/controls/slot0/topic/topic /devices/wb-w1/controls/28-041621bd3cff
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/controls/slot0/topic/$$hashKey object:13
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/uid widget4
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/name ds18b20 T2
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/room room1
/client/wb_AV6U5XZP/config/dashboards/dashboard1/widgets/widget3/template sensor
/client/wb_AV6U5XZP/config/widgets/widget1/controls/slot0/uid slot0
/client/wb_AV6U5XZP/config/widgets/widget1/controls/slot0/topic /devices/T-Sensor 01-02/controls/External Sensor 1
/client/wb_AV6U5XZP/config/widgets/widget1/name Exterrnal sensor 1
/client/wb_AV6U5XZP/config/widgets/widget1/room room1
/client/wb_AV6U5XZP/config/widgets/widget1/template temperature
/client/wb_AV6U5XZP/config/widgets/widget1/uid widget1
/client/wb_AV6U5XZP/config/widgets/widget2/controls/slot0/uid slot0
/client/wb_AV6U5XZP/config/widgets/widget2/controls/slot0/topic /devices/T-Sensor 01-02/controls/External Sensor 2
/client/wb_AV6U5XZP/config/widgets/widget2/name Exterrnal sensor 2
/client/wb_AV6U5XZP/config/widgets/widget2/room room1
/client/wb_AV6U5XZP/config/widgets/widget2/template temperature
/client/wb_AV6U5XZP/config/widgets/widget2/uid widget2
/client/wb_AV6U5XZP/config/widgets/widget3/controls/slot0/uid slot0
/client/wb_AV6U5XZP/config/widgets/widget3/controls/slot0/topic /devices/wb-w1/controls/28-041621a1f3ff
/client/wb_AV6U5XZP/config/widgets/widget3/name ds18b20 T1
/client/wb_AV6U5XZP/config/widgets/widget3/room room1
/client/wb_AV6U5XZP/config/widgets/widget3/template sensor
/client/wb_AV6U5XZP/config/widgets/widget3/uid widget3
/client/wb_AV6U5XZP/config/widgets/widget4/controls/slot0/uid slot0
/client/wb_AV6U5XZP/config/widgets/widget4/controls/slot0/topic /devices/wb-w1/controls/28-041621bd3cff
/client/wb_AV6U5XZP/config/widgets/widget4/name ds18b20 T2
/client/wb_AV6U5XZP/config/widgets/widget4/room room1
/client/wb_AV6U5XZP/config/widgets/widget4/template sensor
/client/wb_AV6U5XZP/config/widgets/widget4/uid widget4
/client/wb_AV6U5XZP/config/default_dashboard/uid dashboard1
/client/wb_AV6U5XZP/rpc/v1/db_logger/history/get_channels 1
/client/wb_AV6U5XZP/rpc/v1/db_logger/history/get_values 1
/client/wb_AV6U5XZP/rpc/v1/wbrules/Editor/List 1
/client/wb_AV6U5XZP/rpc/v1/wbrules/Editor/Load 1
/client/wb_AV6U5XZP/rpc/v1/wbrules/Editor/Remove 1
/client/wb_AV6U5XZP/rpc/v1/wbrules/Editor/Save 1
/client/wb_AV6U5XZP/rpc/v1/confed/Editor/List 1
/client/wb_AV6U5XZP/rpc/v1/confed/Editor/Load 1
/client/wb_AV6U5XZP/rpc/v1/confed/Editor/Save 1
/client/wb_AV6U5XZP/rpc/v1/confed/Editor/Load/contactless-PQpt3PE6T8/reply {"id":5,"result":{"configPath":"/etc/wb-mqtt-setpoints.conf","content":{"highHysteresis":0.5,"lowHysteresis":0.5,"rooms":[{"roomName":"Приемка 1","setPointDay":26,"setPointNight":15},{"roomName":"Приемка 2","setPointDay":26,"setPointNight":16},{"roomName":"Санузел","setPointDay":26,"setPointNight":15}],"startDay":"08:00","startNight":"20:00"},"schema":{"$schema":"http://json-schema.org/draft-04/schema#","configFile":{"path":"/etc/wb-mqtt-setpoints.conf","service":"wb-rules"},"definitions":{"room":{"format":"grid","headerTemplate":"{{i1}} : \"{{self.roomName}}\"","properties":{"roomName":{"default":"Помещение","description":"Наименование помещения","title":"Наименование","type":"string"},"setPointDay":{"default":25,"description":"Уставка температуры в помещении днём","title":"Температура дневная","type":"number"},"setPointNight":{"default":18,"description":"Уставка температуры в помещении ночью","title":"Температура ночная","type":"number"}},"required":["roomName","setPointDay","setPointNight"],"type":"object"}},"description":"Настройки для установки температуры в помещениях","format":"grid","properties":{"highHysteresis":{"description":"Верхний предел","maximum":2,"minimum":0.1,"propertyOrder":2,"title":"Гистерезис","type":"number"},"lowHysteresis":{"description":"Нижний предел","maximum":2,"minimum":0.1,"propertyOrder":1,"title":"Гистерезис","type":"number"},"rooms":{"items":{"$ref":"#/definitions/room"},"propertyOrder":3,"title":"ПОМЕЩЕНИЯ","type":"array"},"startDay":{"default":"08:00","description":"В формате 00:00","pattern":"^[0-9][0-9]:[0-9][0-9]$","propertyOrder":4,"title":"Начало рабочего дня","type":"string"},"startNight":{"default":"21:00","description":"В формате 00:00","pattern":"^[0-9][0-9]:[0-9][0-9]$","propertyOrder":5,"title":"Конец рабочего дня","type":"string"}},"title":"Установки температуры","type":"object"}}}
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.83
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.84
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.83
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.84
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.82
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.83
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.82
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.84
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.83
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.82
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.84
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.83
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.84
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.83
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.84
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.83
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.82
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.83
/client/wb_AV6U5XZP/devices/power_status/controls/Vin 11.84
/client/wb_AV6U5XZP/devices/wb-adc/controls/A3 3.15
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.737
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/External Sensor 2 24.9375
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A2_OUT 0
/client/wb_AV6U5XZP/devices/wb-adc/controls/A4 0.01
/client/wb_AV6U5XZP/devices/wb-adc/controls/Vin 11.72
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.738
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.737
/client/wb_AV6U5XZP/devices/wb-adc/controls/5Vout 4.89
/client/wb_AV6U5XZP/devices/wb-adc/controls/A1 0.01
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.736
/client/wb_AV6U5XZP/devices/wb-adc/controls/A2 3.17
/client/wb_AV6U5XZP/devices/wb-adc/controls/A3 3.15
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.733
/client/wb_AV6U5XZP/devices/wb-adc/controls/A4 0.01
/client/wb_AV6U5XZP/devices/wb-adc/controls/Vin 11.71
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.737
/client/wb_AV6U5XZP/devices/wb-adc/controls/5Vout 4.89
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.738
/client/wb_AV6U5XZP/devices/wb-adc/controls/A1 0.01
/client/wb_AV6U5XZP/devices/wb-adc/controls/A2 3.17
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.739
/client/wb_AV6U5XZP/devices/wb-adc/controls/A3 3.16
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.738
/client/wb_AV6U5XZP/devices/wb-adc/controls/A4 0.01
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.739
/client/wb_AV6U5XZP/devices/wb-adc/controls/Vin 11.72
/client/wb_AV6U5XZP/devices/wb-adc/controls/5Vout 4.89
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.738
/client/wb_AV6U5XZP/devices/wb-adc/controls/A1 0.01
/client/wb_AV6U5XZP/devices/wb-adc/controls/A2 3.16
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.739
/client/wb_AV6U5XZP/devices/wb-adc/controls/A3 3.16
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.738
/client/wb_AV6U5XZP/devices/wb-adc/controls/A4 0.01
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.74
/client/wb_AV6U5XZP/devices/wb-adc/controls/Vin 11.72
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.742
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/External Sensor 2 24.875
/client/wb_AV6U5XZP/devices/wb-gpio/controls/A2_OUT 0
/client/wb_AV6U5XZP/devices/wb-adc/controls/5Vout 4.89
/client/wb_AV6U5XZP/devices/wb-adc/controls/A1 0.01
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.743
/client/wb_AV6U5XZP/devices/wb-adc/controls/A2 3.17
/client/wb_AV6U5XZP/devices/wb-adc/controls/A3 3.14
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.74
/client/wb_AV6U5XZP/devices/wb-adc/controls/A4 0.01
/client/wb_AV6U5XZP/devices/wb-adc/controls/Vin 11.72
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.743
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.742
/client/wb_AV6U5XZP/devices/wb-adc/controls/5Vout 4.89
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.741
/client/wb_AV6U5XZP/devices/wb-adc/controls/A1 0.01
/client/wb_AV6U5XZP/devices/wb-adc/controls/A2 3.17
/client/wb_AV6U5XZP/devices/T-Sensor 01-02/controls/Input Voltage 11.738
/client/wb_AV6U5XZP/devices/wb-adc/controls/A3 3.15

На получение ответа ушло примерно 2-3 минуты.

Затем на странице Settings ввел UserId и Password как в bridge.conf и все заработало!


#112

После перезагрузки снова надо через терминал переназначать канал по умолчанию

		route del default
		route add default dev ppp0

Как и куда прописать, чтобы он при загрузке устанавливался?


#113

А оформите эти команды в виде исполняемого файла и положите его в \etc\ppp\ip-up.d\ , при поднятии ppp0 скрипт должен выполнится.


#114

Создал файл runppp

#!/bin/sh -e
route del default
route add default dev ppp0

дал права на исполнение /etc/ppp/ip-up.d# chmod +x runppp

Однако после перезагрузки все-равно

root@wirenboard-AROY5UJE:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
10.64.64.64 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0

Подкорректируйте пожалуйста что не так?
Или файл дайте пожалуйста чтобы ppp0 работал как канал в Интернет (и WiFi как точка доступа оставался)


#115

Добрый день! Извините за долгий ответ.

Давайте попробуем продиагностировать проблему детальнее. Поменяйте ваш скрипт на такой

#!/bin/sh
sleep 5
/bin/sh -c "/sbin/route -n > /tmp/ppp.log 2>/tmp/ppp.err || exit 0"
/bin/sh -c "/sbin/route del default >> /tmp/ppp.log 2>>/tmp/ppp.err || exit 0"
/bin/sh -c "/sbin/route -n > /tmp/ppp.log 2>>/tmp/ppp.err || exit 0"
/bin/sh -c "/sbin/route add  default dev ppp0 >> /tmp/ppp.log 2>>/tmp/ppp.err || exit 0"
/bin/sh -c "/sbin/route -n > /tmp/ppp.log 2>>/tmp/ppp.err || exit 0"

пришлите сюда содержимое /tmp/ppp.log и /tmp/ppp.err после перезагрузки.
В /var/log/messages нет ничего подозрительного?


#116

Скрипт поменял
в /tmp логи не появились после перезагрузки
В /var/log/messages есть информация о подключении

Oct 22 11:15:42 wirenboard-AV6U5XZP local2.info chat[1349]: timeout set to 5 seconds
Oct 22 11:15:42 wirenboard-AV6U5XZP local2.info chat[1349]: abort on (ERROR)
Oct 22 11:15:42 wirenboard-AV6U5XZP local2.info chat[1349]: abort on (BUSY)
Oct 22 11:15:42 wirenboard-AV6U5XZP local2.info chat[1349]: send (ATZ^M)
Oct 22 11:15:42 wirenboard-AV6U5XZP local2.info chat[1349]: expect (OK)
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   94.830078] usb 2-1.2: new high-speed USB device number 6 using ci_hdrc
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.011520] usb 2-1.2: New USB device found, idVendor=1e0e, idProduct=0020
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.018505] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.025968] usb 2-1.2: Product: SIMCOM_PRODUCT
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.030480] usb 2-1.2: Manufacturer: SIMCOM_VENDOR
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.035291] usb 2-1.2: SerialNumber: 004999010640000
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.110251] cdc_acm 2-1.2:1.0: ttyACM0: USB ACM device
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.128293] cdc_acm 2-1.2:1.2: ttyACM1: USB ACM device
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.146039] cdc_acm 2-1.2:1.4: ttyACM2: USB ACM device
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.167425] cdc_acm 2-1.2:1.6: ttyACM3: USB ACM device
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.187161] cdc_acm 2-1.2:1.8: ttyACM4: USB ACM device
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.205657] cdc_acm 2-1.2:1.10: ttyACM5: USB ACM device
Oct 22 11:15:44 wirenboard-AV6U5XZP user.info kernel: [   95.224069] cdc_acm 2-1.2:1.12: ttyACM6: USB ACM device
Oct 22 11:15:47 wirenboard-AV6U5XZP local2.info chat[1349]: alarm
Oct 22 11:15:47 wirenboard-AV6U5XZP local2.info chat[1349]: Failed
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: timeout set to 5 seconds
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: abort on (ERROR)
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: abort on (BUSY)
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: send (ATZ^M)
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: expect (OK)
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: ^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: RDY^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: ^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: +CFUN: 1^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: ^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: +CPIN: READY^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: ^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: Call Ready^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: ATZ^M^M
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: OK
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]:  -- got it
Oct 22 11:15:48 wirenboard-AV6U5XZP local2.info chat[1366]: send (^M)
Oct 22 11:15:59 wirenboard-AV6U5XZP local2.notice pppd[1387]: pppd 2.4.7 started by root, uid 0
Oct 22 11:15:59 wirenboard-AV6U5XZP daemon.err ntpdate[1397]: the NTP socket is in use, exiting
Oct 22 11:15:59 wirenboard-AV6U5XZP auth.info sshd[812]: Received SIGHUP; restarting.
Oct 22 11:15:59 wirenboard-AV6U5XZP daemon.err watchdog[985]: cannot open /var/run/sshd.pid (errno = 2 = 'No such file or directory')
Oct 22 11:15:59 wirenboard-AV6U5XZP auth.info sshd[812]: Server listening on 0.0.0.0 port 22.
Oct 22 11:15:59 wirenboard-AV6U5XZP auth.info sshd[812]: Server listening on :: port 22.
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]: timeout set to 5 seconds
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]: abort on (ERROR)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]: abort on (BUSY)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]: send (ATZ^M)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]: expect (OK)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]: ATZ^M^M
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]: OK
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]:  -- got it
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1439]: send (^M)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info pppd[1387]: Serial port initialized.
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: abort on (BUSY)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: abort on (NO ANSWER)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: abort on (NO CARRIER)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: abort on (ERROR)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: timeout set to 5 seconds
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: send (ATZ^M)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: expect (OK)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: ^M
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: ^MATZ^M^M
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: OK
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]:  -- got it
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: send (AT+CGDCONT=1,"IP","internet.mts.ru"^M)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: expect (OK)
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: ^M
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: AT+CGDCONT=1,"IP","internet.mts.ru"^M^M
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: OK
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]:  -- got it
Oct 22 11:16:00 wirenboard-AV6U5XZP local2.info chat[1441]: send (ATD*99***1#^M)
Oct 22 11:16:01 wirenboard-AV6U5XZP local2.info chat[1441]: expect (CONNECT)
Oct 22 11:16:01 wirenboard-AV6U5XZP local2.info chat[1441]: ^M
Oct 22 11:16:01 wirenboard-AV6U5XZP local2.info chat[1441]: ATD*99***1#^M^M
Oct 22 11:16:01 wirenboard-AV6U5XZP local2.info chat[1441]: CONNECT
Oct 22 11:16:01 wirenboard-AV6U5XZP local2.info chat[1441]:  -- got it
Oct 22 11:16:01 wirenboard-AV6U5XZP local2.info pppd[1387]: Serial connection established.
Oct 22 11:16:01 wirenboard-AV6U5XZP local2.info pppd[1387]: Using interface ppp0
Oct 22 11:16:01 wirenboard-AV6U5XZP local2.notice pppd[1387]: Connect: ppp0 <--> /dev/ttyGSM
Oct 22 11:16:02 wirenboard-AV6U5XZP authpriv.info CRON[1446]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 22 11:16:02 wirenboard-AV6U5XZP cron.info CRON[1450]: (root) CMD (/usr/share/wb-daemon-watchdogs/check_confed.sh 2>&1 | logger -t wb-daemon-watchdogs)
Oct 22 11:16:02 wirenboard-AV6U5XZP local2.warn pppd[1387]: kernel does not support PPP filtering
Oct 22 11:16:02 wirenboard-AV6U5XZP user.info kernel: [  112.383170] PPP BSD Compression module registered
Oct 22 11:16:02 wirenboard-AV6U5XZP user.info kernel: [  112.431671] PPP Deflate Compression module registered
Oct 22 11:16:05 wirenboard-AV6U5XZP local2.err pppd[1387]: not replacing default route to wlan0 [192.168.1.1]
Oct 22 11:16:05 wirenboard-AV6U5XZP local2.notice pppd[1387]: local  IP address 10.132.26.163
Oct 22 11:16:05 wirenboard-AV6U5XZP local2.notice pppd[1387]: remote IP address 10.132.26.163
Oct 22 11:16:05 wirenboard-AV6U5XZP local2.notice pppd[1387]: primary   DNS address 10.226.4.9
Oct 22 11:16:05 wirenboard-AV6U5XZP local2.notice pppd[1387]: secondary DNS address 10.226.3.9
Oct 22 11:16:05 wirenboard-AV6U5XZP daemon.info dnsmasq[859]: reading /etc/resolv.conf
Oct 22 11:16:05 wirenboard-AV6U5XZP daemon.info dnsmasq[859]: using nameserver 10.226.4.9#53
Oct 22 11:16:05 wirenboard-AV6U5XZP daemon.info dnsmasq[859]: using nameserver 10.226.3.9#53
Oct 22 11:16:06 wirenboard-AV6U5XZP daemon.info ntpd[841]: Listen normally on 7 ppp0 10.132.26.163:123
Oct 22 11:16:06 wirenboard-AV6U5XZP authpriv.info CRON[1446]: pam_unix(cron:session): session closed for user root

Проверяем

root@wirenboard-AV6U5XZP:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0

Все-равно ppp0 не поднялся автоматом.


#117

Странно, то есть интерфейс, я как понимаю, поднимается, но скрипт не выполняется. Вы пробовали этот скрипт запустить из командной строки? В /tmp что-то после этого появляется?


#118

вставляю в терминал эту строку, но реакции нет

root@wirenboard-AV6U5XZP:~#
.err || exit 0"-AV6U5XZP:~# /bin/sh -c "/sbin/route -n > /tmp/ppp.log 2>/tmp/ppp.
root@wirenboard-AV6U5XZP:~#

в /tmp пусто


#119

Наверное надо эту команду через терминал отправлять?

Но тоже реакции нет.

в списке интерфейсов ppp0 присутствует

root@wirenboard-AV6U5XZP:~# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether d8:80:39:e3:7f:b2  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether d8:80:39:e3:2c:9e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 148097  bytes 10509989 (10.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 148097  bytes 10509989 (10.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.132.26.163  netmask 255.255.255.255  destination 10.132.26.163
        ppp  txqueuelen 3  (Point-to-Point Protocol)
        RX packets 5  bytes 68 (68.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7  bytes 135 (135.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.6  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::56c9:dfff:feca:ecf3  prefixlen 64  scopeid 0x20<link>
        ether 54:c9:df:ca:ec:f3  txqueuelen 1000  (Ethernet)
        RX packets 19250  bytes 2252562 (2.1 MiB)
        RX errors 0  dropped 214  overruns 0  frame 0
        TX packets 20345  bytes 6014812 (5.7 MiB)
        TX errors 0  dropped 1 overruns 0  carrier 0  collisions 0

#120

Секунду, не очень понимаю.
Просто
/sbin/route -n
печатает таблицу маршрутизации в консоль, верно?
А /sbin/route -n > /tmp/ppp.log создает файл /tmp/ppp.log ?

Сейчас разберемся, что-то очень простое должно быть, не понимаю только, что.


#121

таблицу дает, а

/sbin/route -n > /tmp/ppp.log

лог не создает.

Права на /tmp:


#122

А touch /tmp/ppp.log тоже не создает файл в /tmp ?!


#123

С этим каталогом для меня непонятно.
Только-что создал ppp.log и ppp.err вручную через WnSCP - они появились в списке
теперь, чтобы проверить touch /tmp/ppp.log пытаюсь удалить их пишет

удаление тоже его не видит

root@wirenboard-AV6U5XZP:~# rm /tmp/ppp.log
rm: cannot remove '/tmp/ppp.log': No such file or directory
root@wirenboard-AV6U5XZP:~# cd /tmp
root@wirenboard-AV6U5XZP:/tmp# dir
root@wirenboard-AV6U5XZP:/tmp#