You are not logged in.
Today I attempted to switch to the testing repos. Before switching, I performed a full system upgrade. Then I rebooted, made sure everything was working then switched to testing. On the switch, I upgraded the following packages:
binutils-2.28.0-3 blas-3.7.0-2 cblas-3.7.0-2 diffutils-3.6-1 file-5.31-1 fsharp-4.1.18-1 gcc-libs-multilib-7.1.1-2 gcc-multilib-7.1.1-2
glibc-2.25-2 krb5-1.15.1-1 lapack-3.7.0-2 lib32-gcc-libs-7.1.1-2 lib32-glibc-2.25-2 lib32-libdrm-2.4.81-1 lib32-libelf-0.169-1 lib32-libltdl-2.4.6-8
libdrm-2.4.81-1 libelf-0.169-1 libsystemd-233-4 libtool-2.4.6-8 libwbclient-4.6.3-1 pango-1.40.6+9+g92cc73c8-1 smbclient-4.6.3-1
systemd-233-4 systemd-sysvcompat-233-4
Upon reboot, I was unable to connect to the Internet via ethernet. I checked the status of the dhcpcd daemon, and that was running just fine. I was able to connect within my LAN, pinging other machines and load a web app on my home web server. However, I couldn't connect to the Internet outside of my LAN. I downgraded out of the testing repo shortly after.
Any ideas on where I can start looking to diagnose the problem? I'm not sure what packages could be causing the issue.
Offline
Try pinging by address, such as 138.201.81.199, an Arch Linux server.
I assume this is a wired LAN and the only networking service that is enabled is dhcpcd.service.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
I was able to ping that by address. Likely a DNS issue?
Offline
Yes. Sadly, DNS is not one of my strong points. We do know that drivers and stuff are all working.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
libsystemd-233-4 systemd-233-4 systemd-sysvcompat-233-4
core has systemd 232-8 , and some systemd parts play a big role in dns resolving.
I suggest checking systemd changelog if you want to investigate further.
Last edited by Lone_Wolf (2017-05-25 12:55:55)
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
Offline
paste your /etc/nsswitch.conf file
Offline
Here's /etc/nsswitch.conf (it was not changed when switching to the testing version of systemd):
# Begin /etc/nsswitch.conf
passwd: compat mymachines systemd
group: compat mymachines systemd
shadow: compat
publickey: files
hosts: files mymachines resolve mdns_minimal [NOTFOUND=return] [!UNAVAIL=return] dns myhostname
networks: files
protocols: files
services: files
ethers: files
rpc: files
netgroup: files
# End /etc/nsswitch.conf
Offline