You are not logged in.
Pages: 1
Hi,
I installed arch this weekend, I am used to arch and I have done dual boots several times so I'm confident in what I've done.
Though something is obviously wrong because when I try to connect to the wifi using wpa_supplicant or iwctl, iwconfig tells me that I'm connected to the wifi but I have not internet connection (ping not working, pacman neither).
some infos:
$ iwconfig:
wlan0     IEEE 802.11  ESSID:"Ile-Falkland"  
          Mode:Managed  Frequency:5.54 GHz  Access Point: 30:93:BC:87:CD:14   
          Bit Rate=433.3 Mb/s   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=70/70  Signal level=-38 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:15   Missed beacon:0
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether d8:d0:90:06:04:e7 brd ff:ff:ff:ff:ff:ff
5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 98:2c:bc:3a:14:6b brd ff:ff:ff:ff:ff:ff
$ ip route show:
default via 192.168.1.254 dev wlan0 proto dhcp src 192.168.1.40 metric 305 mtu 1500 
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.40 metric 305 mtu 1500
$ ping archlinux.org
ping: archlinux.org: Temporary failure in name resolutionI have a dell, I have the same packages as the arclinux iso.
I mainly tried :
This thread
and this one
but got nothing out of it
EDIT:
found the solution >> systemd-networkd and systemd-resolved were not running.
Last edited by EinhardOmpredus (2020-07-15 07:47:47)
Offline

I have not internet connection (ping not working, pacman neither)
It's definitely possible you're right about not having an internet connection, but the outputs you posted could 'just' be a name resolution issue.
More info is needed to verify whether your connection works or not.
please post outputs of
$ ip addr
$ ping -4 192.168.1.254
$ ping -4 138.201.81.199  # ipv4 address of archlinux.org
$ ping 2a01:4f8:172:1d86::1 # ipv6 address of  archlinux.orgWhat are you using to manage network connections (dhcpcd , dhclient , systemd-networkd , NetworkManager to name a few) ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
 Try clean chroot manager by graysky
Offline
I can't send you the outputs right now, I will ASAP. If I understood what I did, I'm using systemd-network, but I will check just in case.
I don't know if that changes anything but I tried different adresses like google.fr , it didn't work either.
Offline

I can't send you the outputs right now
Well just tell us if you can ping the IP addresses then. If you can then you need to configure /etc/resolv.conf as per resolv.conf(5). See also https://wiki.archlinux.org/index.php/Do … resolution
If you can't ping the IP addresses then please post all of the relevant configuration files and also the output of
ls -lR /etc/systemd/systemJin, Jîyan, Azadî
Offline
So I could only ping the IPV6 address, the others gave me
ping: connect: Network is unreachablea correction about what I said, I'm using iwd.
about the configuration files I did only what was in the installation guide. So except from hostname and hosts I changed nothing. I don't really know which files are relevant.
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d8:d0:90:06:04:e7 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 98:2c:bc:3a:14:6b brd ff:ff:ff:ff:ff:ff
    inet6 2001:861:3d81:f200:9a2c:bcff:fe3a:146b/64 scope global dynamic mngtmpaddr 
       valid_lft 84633sec preferred_lft 12633sec
    inet6 fe80::9a2c:bcff:fe3a:146b/64 scope link 
       valid_lft forever preferred_lft forever
$ ls -lR /etc/systemd/system
/etc/systemd/system:
total 8
drwxr-xr-x 2 root root 4096 Jul 12 21:27 getty.target.wants
drwxr-xr-x 2 root root 4096 Jul 12 21:57 multi-user.target.wants
/etc/systemd/system/getty.target.wants:
total 0
lrwxrwxrwx 1 root root 38 Jul 12 21:27 getty@tty1.service -> /usr/lib/systemd/system/getty@.service
/etc/systemd/system/multi-user.target.wants:
total 0
lrwxrwxrwx 1 root root 35 Jul 12 21:57 iwd.service -> /usr/lib/systemd/system/iwd.service
lrwxrwxrwx 1 root root 40 Jul 12 21:27 remote-fs.target -> /usr/lib/systemd/system/remote-fs.targetOffline
thanks to this post I found a solution by renewing my IP address but as the guy says I don't know if it's permanent
## Actually it didn't work
Last edited by EinhardOmpredus (2020-07-14 09:01:42)
Offline

So I could only ping the IPV6 address
So populate /etc/resolv.conf with an IPv6-capable nameserver.
Jin, Jîyan, Azadî
Offline

EDIT:
found the solution >> systemd-networkd and systemd-resolved were not running.
That indicates the problem was you didn't have a dhcp client / dns resolver running.
The systemd-networkd / systemd-resolved is just one of the available choices and has its own share of problems.
Pleaee prepend [Solved] to the thread title (edit first post) .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
 Try clean chroot manager by graysky
Offline
Pages: 1