При использование "opkg dns-override" на Peak 38B2 есть ошибка
ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
откат на 38B1 ее исправляет. Основной роутер подключенный к интернет. Так же на 38B2 не работает KeenDNS, на 38B1 проблем нет.
Описание 38B2
Скрытый текст
[I] May 21 16:54:23 ndnproxy: PID file: /var/ndnproxy_Policy2.pid.
[I] May 21 16:54:23 ndnproxy: stats. file: /var/ndnproxy_Policy2.stat.
[E] May 21 16:54:23 ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
[C] May 21 16:54:23 ndnproxy: can not bind to IPv4 address, aborted.
[I] May 21 16:54:23 ndnproxy: stopped.
[E] May 21 16:54:23 ndm: Service: "Dns::Proxy::Policy2": unexpectedly stopped.
[I] May 21 16:54:26 ndnproxy: NDM DNS Proxy, v1.3.0b45.
[I] May 21 16:54:26 ndnproxy: PID file: /var/ndnproxy_Policy1.pid.
[I] May 21 16:54:26 ndnproxy: stats. file: /var/ndnproxy_Policy1.stat.
[E] May 21 16:54:26 ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
[C] May 21 16:54:26 ndnproxy: can not bind to IPv4 address, aborted.
[I] May 21 16:54:26 ndnproxy: stopped.
[E] May 21 16:54:26 ndm: Service: "Dns::Proxy::Policy1": unexpectedly stopped.
[I] May 21 16:54:26 ndnproxy: NDM DNS Proxy, v1.3.0b45.
[I] May 21 16:54:26 ndnproxy: PID file: /var/ndnproxy_Policy2.pid.
[I] May 21 16:54:26 ndnproxy: stats. file: /var/ndnproxy_Policy2.stat.
[E] May 21 16:54:26 ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
[C] May 21 16:54:26 ndnproxy: can not bind to IPv4 address, aborted.
[I] May 21 16:54:26 ndnproxy: stopped.
....
[I] May 21 16:57:12 ndnproxy: NDM DNS Proxy, v1.3.0b45.
[I] May 21 16:57:12 ndnproxy: PID file: /var/ndnproxy_Policy1.pid.
[I] May 21 16:57:12 ndnproxy: stats. file: /var/ndnproxy_Policy1.stat.
[E] May 21 16:57:12 ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
[C] May 21 16:57:12 ndnproxy: can not bind to IPv4 address, aborted.
[I] May 21 16:57:12 ndnproxy: stopped.
[E] May 21 16:57:12 ndm: Service: "Dns::Proxy::Policy1": unexpectedly stopped.
[I] May 21 16:57:12 ndnproxy: NDM DNS Proxy, v1.3.0b45.
[I] May 21 16:57:12 ndnproxy: PID file: /var/ndnproxy_Policy2.pid.
[I] May 21 16:57:12 ndnproxy: stats. file: /var/ndnproxy_Policy2.stat.
[E] May 21 16:57:12 ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
[C] May 21 16:57:12 ndnproxy: can not bind to IPv4 address, aborted.
[I] May 21 16:57:12 ndnproxy: stopped.
[E] May 21 16:57:12 ndm: Service: "Dns::Proxy::Policy2": unexpectedly stopped.
[I] May 21 16:57:15 ndnproxy: NDM DNS Proxy, v1.3.0b45.
[I] May 21 16:57:15 ndnproxy: PID file: /var/ndnproxy_Policy1.pid.
[I] May 21 16:57:15 ndnproxy: stats. file: /var/ndnproxy_Policy1.stat.
[E] May 21 16:57:15 ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
[C] May 21 16:57:15 ndnproxy: can not bind to IPv4 address, aborted.
[I] May 21 16:57:15 ndnproxy: stopped.
[E] May 21 16:57:15 ndm: Service: "Dns::Proxy::Policy1": unexpectedly stopped.
[I] May 21 16:57:15 ndnproxy: NDM DNS Proxy, v1.3.0b45.
[I] May 21 16:57:15 ndnproxy: PID file: /var/ndnproxy_Policy2.pid.
[I] May 21 16:57:15 ndnproxy: stats. file: /var/ndnproxy_Policy2.stat.
[E] May 21 16:57:15 ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
[C] May 21 16:57:15 ndnproxy: can not bind to IPv4 address, aborted.
[I] May 21 16:57:15 ndnproxy: stopped.
<filename="temp:ndnproxymain.conf">
<![CDATA[
rpc_port = 54321
rpc_ttl = 10000
rpc_wait = 10000
timeout = 7000
proceed = 500
stat_file = /var/ndnproxymain.stat
stat_time = 10000
dns_server = 192.168.130.101 .
static_a = my.keenetic.net 78.47.125.180
norebind_ctl = on
norebind_ip4net = 192.168.130.101:24
norebind_ip4net = 255.255.255.255:32
set-profile-ip 127.0.0.1 0
set-profile-ip ::1 0
rpc_only = on
На 38B1
~ # netstat -ntulp | grep :53
tcp 0 0 192.168.130.101:53 0.0.0.0:* LISTEN 957/AdGuardHome
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 957/AdGuardHome
udp 0 0 0.0.0.0:53536 0.0.0.0:* 877/ndnproxy
udp 0 0 0.0.0.0:53290 0.0.0.0:* 876/ndnproxy
udp 0 0 0.0.0.0:53805 0.0.0.0:* 1025/ndnproxy
udp 0 0 192.168.130.101:53 0.0.0.0:* 957/AdGuardHome
udp 0 0 127.0.0.1:53 0.0.0.0:* 957/AdGuardHome
udp 0 0 0.0.0.0:53596 0.0.0.0:* 877/ndnproxy
udp 0 0 0.0.0.0:53859 0.0.0.0:* 877/ndnproxy
udp 0 0 0.0.0.0:53359 0.0.0.0:* 877/ndnproxy
udp 0 0 0.0.0.0:53125 0.0.0.0:* 1025/ndnproxy
udp 0 0 0.0.0.0:53906 0.0.0.0:* 878/ndnproxy
udp 0 0 0.0.0.0:53395 0.0.0.0:* 878/ndnproxy
udp 0 0 0.0.0.0:53934 0.0.0.0:* 1025/ndnproxy
udp 0 0 0.0.0.0:53454 0.0.0.0:* 878/ndnproxy
udp 0 0 0.0.0.0:53723 0.0.0.0:* 877/ndnproxy
udp 0 0 0.0.0.0:53468 0.0.0.0:* 878/ndnproxy
udp 0 0 0.0.0.0:53475 0.0.0.0:* 876/ndnproxy
udp 0 0 0.0.0.0:53477 0.0.0.0:* 877/ndnproxy
udp 0 0 0.0.0.0:53222 0.0.0.0:* 877/ndnproxy
udp 0 0 192.168.130.101:5351 0.0.0.0:* 2159/miniupnpd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 885/avahi-daemon
udp 0 0 0.0.0.0:5355 0.0.0.0:* 886/tsmb-server
udp 0 0 :::53249 :::* 876/ndnproxy
udp 0 0 :::53263 :::* 878/ndnproxy
udp 0 0 :::53007 :::* 877/ndnproxy
udp 0 0 :::53270 :::* 878/ndnproxy
udp 0 0 :::53789 :::* 877/ndnproxy
udp 0 0 :::53543 :::* 878/ndnproxy
udp 0 0 :::53318 :::* 878/ndnproxy
udp 0 0 :::53862 :::* 877/ndnproxy
udp 0 0 :::53879 :::* 876/ndnproxy
udp 0 0 :::53905 :::* 1025/ndnproxy
udp 0 0 :::53396 :::* 877/ndnproxy
udp 0 0 :::53909 :::* 876/ndnproxy
udp 0 0 :::53150 :::* 878/ndnproxy
udp 0 0 :::53922 :::* 878/ndnproxy
udp 0 0 :::53479 :::* 1025/ndnproxy
udp 0 0 :::5353 :::* 885/avahi-daemon
~ #
По настройкам IP роутера 101 на нем работает на 53 порту AdGuardHome так же он контролирует 127.0.0.1
ip name-server 192.168.130.101 "" on Home
ip name-server 192.168.130.101 "" on OpenVPN0
ip name-server 192.168.130.101 "" on Wireguard1
ip name-server 192.168.130.101 "" on GigabitEthernet0/Vlan9
ip name-server 192.168.130.101 "" on Wireguard0
ip policy Policy0
description Cloud
permit global Wireguard0
no permit global PPPoE0
no permit global GigabitEthernet0/Vlan9
no permit global GigabitEthernet0/Vlan2
no permit global Wireguard1
no permit global OpenVPN0
!
ip policy Policy1
description In-2
permit global PPPoE0
permit global GigabitEthernet0/Vlan9
no permit global GigabitEthernet0/Vlan2
ip policy Policy0
description Cloud
permit global Wireguard0
no permit global PPPoE0
no permit global GigabitEthernet0/Vlan9
!
ip policy Policy1
description In-2
permit global PPPoE0
permit global GigabitEthernet0/Vlan9
multipath
!
ip policy Policy2
description Anti
...
!
dns-proxy
rebind-protect auto
!
opkg disk D3-2:/
opkg initrc /opt/etc/init.d/rc.unslung
opkg dns-override
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
vasek00
При использование "opkg dns-override" на Peak 38B2 есть ошибка
ndnproxy: failed to bind to 0.0.0.0:53 reason: address in use.
откат на 38B1 ее исправляет. Основной роутер подключенный к интернет. Так же на 38B2 не работает KeenDNS, на 38B1 проблем нет.
Описание 38B2
По настройкам IP роутера 101 на нем работает на 53 порту AdGuardHome так же он контролирует 127.0.0.1
ip name-server 192.168.130.101 "" on Home ip name-server 192.168.130.101 "" on OpenVPN0 ip name-server 192.168.130.101 "" on Wireguard1 ip name-server 192.168.130.101 "" on GigabitEthernet0/Vlan9 ip name-server 192.168.130.101 "" on Wireguard0 ip policy Policy0 description Cloud permit global Wireguard0 no permit global PPPoE0 no permit global GigabitEthernet0/Vlan9 no permit global GigabitEthernet0/Vlan2 no permit global Wireguard1 no permit global OpenVPN0 ! ip policy Policy1 description In-2 permit global PPPoE0 permit global GigabitEthernet0/Vlan9 no permit global GigabitEthernet0/Vlan2 ip policy Policy0 description Cloud permit global Wireguard0 no permit global PPPoE0 no permit global GigabitEthernet0/Vlan9 ! ip policy Policy1 description In-2 permit global PPPoE0 permit global GigabitEthernet0/Vlan9 multipath ! ip policy Policy2 description Anti ... ! dns-proxy rebind-protect auto ! opkg disk D3-2:/ opkg initrc /opt/etc/init.d/rc.unslung opkg dns-override
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.