You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even with all this problem client (my laptop) still can enjoy internet without problem, but the problem is Adguard unable to use upsream dns because it use name https://security.cloudflare-dns.com/dns-query and i must change to https://1.1.1.2/dns-query to make it work, and this is not because Adguard Home because this problem exist even before i'm installing Adguard Home.
Please help me so i can't ping and resolve dns name via wlan0, for detail information you can check below data, thank you.
Client Info (my laptop) :
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
# uname -rms
Linux 5.10.0-16-amd64 x86_64
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.110.232 0.0.0.0 UG 202 0 0 eth0
0.0.0.0 10.3.141.1 0.0.0.0 UG 303 0 0 wlan0
10.3.141.0 0.0.0.0 255.255.255.0 U 303 0 0 wlan0
192.168.110.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
Iptables
# ufw
-bash: ufw: command not found
# iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -i wlan0 -o eth0 -j ACCEPT
# iptables -L -v -n
Chain INPUT (policy ACCEPT 123K packets, 97M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 1 packets, 328 bytes)
pkts bytes target prot opt in out source destination
62823 69M ACCEPT all -- eth0 wlan0 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
47567 5025K ACCEPT all -- wlan0 eth0 0.0.0.0/0 0.0.0.0/0
Chain OUTPUT (policy ACCEPT 16374 packets, 4500K bytes)
pkts bytes target prot opt in out source destination
Ping problem :
# ping -I eth0 google.com -c 3
PING google.com (142.251.10.139) from 192.168.110.40 eth0: 56(84) bytes of data.
64 bytes from sd-in-f139.1e100.net (142.251.10.139): icmp_seq=1 ttl=57 time=28.5 ms
64 bytes from sd-in-f139.1e100.net (142.251.10.139): icmp_seq=2 ttl=57 time=28.4 ms
64 bytes from sd-in-f139.1e100.net (142.251.10.139): icmp_seq=3 ttl=57 time=28.4 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 28.385/28.427/28.450/0.029 ms
# ping -I eth0 142.251.10.101 -c 3
PING 142.251.10.101 (142.251.10.101) from 192.168.110.40 eth0: 56(84) bytes of data.
64 bytes from 142.251.10.101: icmp_seq=1 ttl=57 time=28.1 ms
64 bytes from 142.251.10.101: icmp_seq=2 ttl=57 time=28.0 ms
64 bytes from 142.251.10.101: icmp_seq=3 ttl=57 time=28.4 ms
--- 142.251.10.101 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 28.035/28.173/28.377/0.146 ms
Ping from INSIDE Raspberry BOX using wlan0 always Destination Host Unreachable
# ping -I wlan0 google.com -c 3
PING google.com (142.251.10.113) from 10.3.141.1 wlan0: 56(84) bytes of data.
From 10.3.141.1 (10.3.141.1) icmp_seq=1 Destination Host Unreachable
From 10.3.141.1 (10.3.141.1) icmp_seq=2 Destination Host Unreachable
From 10.3.141.1 (10.3.141.1) icmp_seq=3 Destination Host Unreachable
--- google.com ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2076ms
pipe 3
# ping -I wlan0 142.251.10.101 -c 3
PING 142.251.10.101 (142.251.10.101) from 10.3.141.1 wlan0: 56(84) bytes of data.
From 10.3.141.1 icmp_seq=1 Destination Host Unreachable
From 10.3.141.1 icmp_seq=2 Destination Host Unreachable
From 10.3.141.1 icmp_seq=3 Destination Host Unreachable
--- 142.251.10.101 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2065ms
pipe 3
Ping from INSIDE raspberry BOX using wlan0 to eth0 also not possible Destination Host Unreachable
# ping -I wlan0 192.168.110.40 -c 3
PING 192.168.110.40 (192.168.110.40) from 10.3.141.1 wlan0: 56(84) bytes of data.
From 10.3.141.1 icmp_seq=1 Destination Host Unreachable
From 10.3.141.1 icmp_seq=2 Destination Host Unreachable
From 10.3.141.1 icmp_seq=3 Destination Host Unreachable
--- 192.168.110.40 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2045ms
pipe 3
Ping to Raspberry Pi 2B Box FROM Client (LAPTOP)
# ping -I wlan0 10.3.141.1 -c 3
PING 10.3.141.1 (10.3.141.1) from 10.3.141.246 wlan0: 56(84) bytes of data.
64 bytes from 10.3.141.1: icmp_seq=1 ttl=64 time=3.73 ms
64 bytes from 10.3.141.1: icmp_seq=2 ttl=64 time=3.73 ms
64 bytes from 10.3.141.1: icmp_seq=3 ttl=64 time=3.66 ms
--- 10.3.141.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 3.662/3.708/3.734/0.032 ms
# ping -I wlan0 raspberrypi -c 3
ping: raspberrypi: Name or service not known
Service status
# systemctl status dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2022-08-06 02:57:00 BST; 1h 12min ago
Process: 1738 ExecStartPre=/etc/init.d/dnsmasq checkconfig (code=exited, status=0/SUCCESS)
Process: 1745 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS)
Process: 1753 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS)
Main PID: 1752 (dnsmasq)
Tasks: 1 (limit: 1598)
CPU: 1.012s
CGroup: /system.slice/dnsmasq.service
└─1752 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg>
Aug 06 02:56:59 raspberrypi systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
Aug 06 02:57:00 raspberrypi systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
# systemctl status hostapd.service
● hostapd.service - Access point and authentication server for Wi-Fi and Ethernet
Loaded: loaded (/lib/systemd/system/hostapd.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2022-08-06 01:26:31 BST; 2h 44min ago
Docs: man:hostapd(8)
Main PID: 834 (hostapd)
Tasks: 1 (limit: 1598)
CPU: 907ms
CGroup: /system.slice/hostapd.service
└─834 /usr/sbin/hostapd -B -P /run/hostapd.pid -B /etc/hostapd/hostapd.conf
Aug 06 04:07:35 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 WPA: pairwise key handshake completed (RSN)
Aug 06 04:07:57 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 IEEE 802.11: disassociated
Aug 06 04:08:30 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 IEEE 802.11: associated
Aug 06 04:08:30 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 RADIUS: starting accounting session 62DEFB4AF9C67D3B
Aug 06 04:08:30 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 WPA: pairwise key handshake completed (RSN)
Aug 06 04:09:20 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 IEEE 802.11: disassociated
Aug 06 04:09:53 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 IEEE 802.11: associated
Aug 06 04:09:53 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 RADIUS: starting accounting session D141E2053307285A
Aug 06 04:09:53 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 WPA: pairwise key handshake completed (RSN)
Aug 06 04:10:09 raspberrypi hostapd[834]: wlan0: STA e0:b9:a5:2d:a7:66 IEEE 802.11: disassociated
# systemctl status raspapd.service
● raspapd.service - RaspAP Service Daemon
Loaded: loaded (/lib/systemd/system/raspapd.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sat 2022-08-06 01:26:38 BST; 2h 44min ago
Main PID: 704 (code=exited, status=0/SUCCESS)
CPU: 417ms
Aug 06 01:26:27 raspberrypi systemd[1]: Starting RaspAP Service Daemon...
Aug 06 01:26:28 raspberrypi bash[704]: Stopping network services...
Aug 06 01:26:29 raspberrypi bash[704]: Changing RaspAP Daemon --interface to uap0
Aug 06 01:26:29 raspberrypi bash[704]: Disabling systemd-networkd
Aug 06 01:26:30 raspberrypi bash[704]: Starting network services...
Aug 06 01:26:38 raspberrypi bash[704]: RaspAP service start DONE
Aug 06 01:26:38 raspberrypi systemd[1]: raspapd.service: Succeeded.
Aug 06 01:26:38 raspberrypi systemd[1]: Finished RaspAP Service Daemon.
Is that normal for systemctl status raspapd.service Results Active: inactive (dead)
i cant still accessing raspap web interface even with raspapd status inactive.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Raspberry Pi B2 + RaspAP 2.8.5
Note :
Even with all this problem client (my laptop) still can enjoy internet without problem, but the problem is Adguard unable to use upsream dns because it use name
https://security.cloudflare-dns.com/dns-query
and i must change tohttps://1.1.1.2/dns-query
to make it work, and this is not because Adguard Home because this problem exist even before i'm installing Adguard Home.Please help me so i can't ping and resolve dns name via wlan0, for detail information you can check below data, thank you.
Client Info (my laptop) :
Gateway
Ping From Client to RaspAP BOX - i'm UNPLUG eth0 from laptop
Ping From Client to google.com - i'm UNPLUG eth0 from laptop
Raspberry 2B + RaspAP
RaspAP Hotspot Advanced settings :
Device Info
Networking Info
Gateway
Iptables
Ping problem :
Ping from INSIDE Raspberry BOX using wlan0 always
Destination Host Unreachable
Ping from INSIDE raspberry BOX using wlan0 to eth0 also not possible
Destination Host Unreachable
Ping to Raspberry Pi 2B Box FROM Client (LAPTOP)
Service status
Is that normal for
systemctl status raspapd.service
ResultsActive: inactive (dead)
i cant still accessing raspap web interface even with raspapd status
inactive
.Beta Was this translation helpful? Give feedback.
All reactions