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
Hello, sorry for the inconvenience. I wanted to ask for help with the following problem.
After a lot of effort I managed to connect the wifi of my banana pro board (many thanks to the user who recommended the brcm80211 driver), which uses Debian through an SD card.
Using the commands:
wpa_supplicant -c /etc/wpa_supplicant.conf -i wlan0 -B
#(to relate ssid and password to the wlan0 network)
dhclient Wlan0
#(to get an ip address)
I manage to connect to the Wi-Fi network and obtain an IP address.
In ifconfig everything seems to be correct and I can connect remotely to the board through SSH.
The issue is that I can't ping google.com or use apt update (when I need to download packages I connect a separate ethernet cable) but I can ping 1.1.1.1, 1.0.0.1, 8.8.4.4, 127.0.0.1, 208.67.222.222 and 208.67.220.220
When trying to ping google, 8.8.8.8 or linux: @Debian:~$ ping -c 6 linux.org
ping: linux.org: Temporary name resolution failure
ping -c 6 google.com
ping: google.com: Temporary name resolution failure
ping -c 6 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.3 icmp_seq=1 Destination Host Unreachable
From 192.168.1.2: icmp_seq=2 Redirect Host(New nexthop: 192.168.1.3)
From 192.168.1.3 icmp_seq=2 Destination Host Unreachable
From 192.168.1.3 icmp_seq=3 Destination Host Unreachable
From 192.168.1.3 icmp_seq=4 Destination Host Unreachable
From 192.168.1.3 icmp_seq=5 Destination Host Unreachable
From 192.168.1.3 icmp_seq=6 Destination Host Unreachable
I don't know if it helps anything but I tried doing the same pings with another PC with Linux and that is connected to the same network, it can ping Google but not 8.8.8.8 (I think this is the same for the entire network, although not I care as long as I can connect to the internet)
The resolv.conf files are the same on both pc:
etc/resolv.conf
nameserver 127.0.0.53
options edns0 trust-ad
I tried modifying it to:
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 1.0.0.1
but it didn't work either, I also find it difficult to modify this file since it is updated automatically when running dhclient Wlan0 or dhclientwlan0 -r, at the time I tried to solve it by modifying the /sbin/dhclient-script file and commenting on the resolv.conf update, until I realized that I could configure dhclient through /etc/dhcp/dhclient.conf. So I left the script as it was.
the etc/wpa_supplicant.conf file is this: (I censor my WiFi network data)
network={
ssid="xxxxx"
#psk="xxxxxxxxxxxxx"
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
}
There is a similar file in etc/wpa_supplicant/wpa_supplicant.conf:
ap_scan=1 # use the wpa_supplicant to scan and choose the AP
network={
ssid="xxxxx"
psk="xxxxxxxxxxxxx"
}
It may have been left over from when I was doing tests, I'm not sure if this is an interference
I did not find a file like etc/dhcp.conf as I read elsewhere, but I did find the file etc/dhcp/dhclient.conf:
Configuration file for /sbin/dhclient.
This is a sample configuration file for dhclient. See dhclient.conf's
man page for more information about the syntax of this file
and a more comprehensive list of the parameters understood by
dhclient.
Normally, if the DHCP server provides reasonable information and does
not leave anything out (like the domain name, for example), then
few changes must be made to this file, if any.
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
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
-
Hello, sorry for the inconvenience. I wanted to ask for help with the following problem.
After a lot of effort I managed to connect the wifi of my banana pro board (many thanks to the user who recommended the brcm80211 driver), which uses Debian through an SD card.
Using the commands:
wpa_supplicant -c /etc/wpa_supplicant.conf -i wlan0 -B
#(to relate ssid and password to the wlan0 network)
dhclient Wlan0
#(to get an ip address)
I manage to connect to the Wi-Fi network and obtain an IP address.
In ifconfig everything seems to be correct and I can connect remotely to the board through SSH.
The issue is that I can't ping google.com or use apt update (when I need to download packages I connect a separate ethernet cable) but I can ping 1.1.1.1, 1.0.0.1, 8.8.4.4, 127.0.0.1, 208.67.222.222 and 208.67.220.220
When trying to ping google, 8.8.8.8 or linux:
@Debian:~$ ping -c 6 linux.org
ping: linux.org: Temporary name resolution failure
ping -c 6 google.com
ping: google.com: Temporary name resolution failure
ping -c 6 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.3 icmp_seq=1 Destination Host Unreachable
From 192.168.1.2: icmp_seq=2 Redirect Host(New nexthop: 192.168.1.3)
From 192.168.1.3 icmp_seq=2 Destination Host Unreachable
From 192.168.1.3 icmp_seq=3 Destination Host Unreachable
From 192.168.1.3 icmp_seq=4 Destination Host Unreachable
From 192.168.1.3 icmp_seq=5 Destination Host Unreachable
From 192.168.1.3 icmp_seq=6 Destination Host Unreachable
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 5067ms
pipe 4
Notes:
I don't know if it helps anything but I tried doing the same pings with another PC with Linux and that is connected to the same network, it can ping Google but not 8.8.8.8 (I think this is the same for the entire network, although not I care as long as I can connect to the internet)
The resolv.conf files are the same on both pc:
etc/resolv.conf
nameserver 127.0.0.53
options edns0 trust-ad
I tried modifying it to:
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 1.0.0.1
but it didn't work either, I also find it difficult to modify this file since it is updated automatically when running dhclient Wlan0 or dhclientwlan0 -r, at the time I tried to solve it by modifying the /sbin/dhclient-script file and commenting on the resolv.conf update, until I realized that I could configure dhclient through /etc/dhcp/dhclient.conf. So I left the script as it was.
network={
ssid="xxxxx"
#psk="xxxxxxxxxxxxx"
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
}
There is a similar file in etc/wpa_supplicant/wpa_supplicant.conf:
ap_scan=1 # use the wpa_supplicant to scan and choose the AP
network={
ssid="xxxxx"
psk="xxxxxxxxxxxxx"
}
It may have been left over from when I was doing tests, I'm not sure if this is an interference
Configuration file for /sbin/dhclient.
This is a sample configuration file for dhclient. See dhclient.conf's
man page for more information about the syntax of this file
and a more comprehensive list of the parameters understood by
dhclient.
Normally, if the DHCP server provides reasonable information and does
not leave anything out (like the domain name, for example), then
few changes must be made to this file, if any.
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-routes, ntp-servers;
#send dhcp-client-identifier 1:0:xx:xx:xx:xx:xx;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;
#require subnet-mask, domain-name-servers;
#timeout 60;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/sbin/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.xx.xxx.xxx;
#alias {
interface "eth0";
fixed-address 192.x.x.xxx;
option subnet-mask 255.255.255.255;
#}
#lease {
interface "eth0";
fixed-address 192.xx.xxx.xxx;
medium "link0 link1";
option host-name "andare.swiftmedia.com";
option subnet-mask 255.255.255.0;
option broadcast-address 192.xx.xxx.xxx;
option routers 192.xx.xxx.xxxx;
option domain-name-servers 127.0.0.1;
renew 2 2000/1/12 00:00:01;
rebind 2 2000/1/12 00:00:01;
expire 2 2000/1/12 00:00:01;
#}
my operating system is debian old stable on an sd card
and my hardware is a banana pro board that has an integrated wifi module
use rfkill list and reskill unlock 0 to make sure there is no software-hardware lock
7)I have iw(config) installed
I still believe that the problem is in the DNS servers, if someone could explain to me why this happens I would appreciate it.
Beta Was this translation helpful? Give feedback.
All reactions