#Cant download wget using the terminal on debian. The base browser doesnt even open. (UTM, m1 mba)
solar folio
Try pinging repo. Maybe it's down
ping deb.debian.org
tawdry elk
Try pinging repo. Maybe it's down
```ping deb.debian.org```
"Temporary failure in name resolution"
solar folio
Can you ping other domains like google?
ping google.com
tawdry elk
in another dc they said its an internet problem..
tawdry elk
Can you ping other domains like google?
```ping google.com```
right after this command
so
assuming they were right, how can I fix that?
tawdry elk
Can you ping other domains like google?
```ping google.com```
temporary failure in name resolution
its doing this:
https://gyazo.com/951cab80434d7d4701eb9efe69ed5e25
I'm very new to linux and especially debian. I guess its searching for a wifi or?
solar folio
I'm very new to linux and especially debian. I guess its searching for a wifi or...
It can be DNS resolving
What's the output of
sudo nano /etc/resolv.conf
tawdry elk
nothing
tawdry elk
alr
solar folio
And then reload using
sudo systemctl restart systemd-resolved.service
tawdry elk
And then reload using
```sudo systemctl restart systemd-resolved.service```
and then write that in the terminal?
solar folio
and then write that in the terminal?
Yes
tawdry elk
Add to resolv.conf this
```nameserver 8.8.8.8```
well apparently I wrote that in the file, however, it didnt save it for some reasn
after putting the code in, there is no "save" option
solar folio
after putting the code in, there is no "save" option
Ctrl + S
Or
Crtl + X and then Y
tawdry elk
And then reload using
```sudo systemctl restart systemd-resolved.service```
okay got that one too
though it still doesnt spit out any code
and still says temporary failure in name resolution
tawdry elk
idk
lunar bloom
lspci -nnk
tawdry elk
will try later
tawdry elk
`lspci -nnk`
Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge [1b36:0008]
Subsystem: Red Hat, Inc. QEMU PCIe Host bridge [1af4:1100]
00:01.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000]
Subsystem: Red Hat, Inc. Virtio network device [1af4:0001]
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
00:02.0 Display controller [0380]: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01)
Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
00:03.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 01)
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:04.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 03)
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:05.0 USB controller [0c03]: Red Hat, Inc. QEMU XHCI Host Controller [1b36:000d] (rev 01)
Subsystem: Red Hat, Inc. QEMU XHCI Host Controller [1af4:1100]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:06.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block device [1af4:1001]
Subsystem: Red Hat, Inc. Virtio block device [1af4:0002]
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
00:07.0 Communication controller [0780]: Red Hat, Inc. Virtio console [1af4:1003]
Subsystem: Red Hat, Inc. Virtio console [1af4:0003]
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
00:08.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG [1af4:1005]
Subsystem: Red Hat, Inc. Virtio RNG [1af4:0004]
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
lunar bloom
Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge [1b36:0008]
Subsyste...
00:01.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000]
Subsystem: Red Hat, Inc. Virtio network device [1af4:0001]
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci
So it has ethernet, but is it configured? check ip address
tawdry elk
```
00:01.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af...
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: enp0s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 12:5e:9d:e1:6b:4d brd ff:ff:ff:ff:ff:ff
inet 10.148.44.97/22 brd 10.148.47.255 scope global dynamic noprefixroute enp0s1
valid_lft 571sec preferred_lft 571sec
inet6 fe80::105e:9dff:fee1:6b4d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
lunar bloom
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul...
Check if you can ping gateway and the said DNS server's IP address. The one by Neko Edges, #1074964802868351007 message
tawdry elk
Will try later. Sorry for skipping a day between the answers, I'm rather busy this week.
tawdry elk
Check if you can ping gateway and the said DNS server's IP address. The one by N...
so the 127.0.0.1/8? or the 10.148.47.255?
root@debian:~# ping 10.148.47.255
ping: Do you want to ping broadcast? Then -b. If not, check your local firewall rules
root@debian:~# -b
bash: -b: command not found
solar folio
root@debian:~# ping 10.148.47.255
ping: Do you want to ping broadcast? Then -b. ...
ping -b 8.8.8.8
lunar bloom
so the 127.0.0.1/8? or the 10.148.47.255?
Those aren't your IP addresses. The first one is a subnet mask in CIDR notation. The second is a broadcast IP hence you get that warning message in your subsequent message.
Do ip route show and one of them, most definitely starting with 10.148.x.y or at least 10.x.y.z should be your gateway address. You have routing issues if you can't reach a google public DNS server.
lunar bloom
Refer to your VM documentation. All guest machines within a VM should have networking set by default, with it pointing to VM host software's "router". The router acts as a NAT in which it masquerades packets as they traverse through the network, and onto their destination.
solar folio
Refer to your VM documentation. All guest machines within a VM *should* have net...
Bruh, it was VM
lunar bloom
Bruh, it was VM
What's that supposed to mean? I am aware it is a VM instance.
solar folio
What's that supposed to mean? I am aware it is a VM instance.
I thought that he had problems with a real machine, I already thought about Wi-Fi adapter. It turned out to be a virtual machine. Now I'm so embarrassed.
lunar bloom
I thought that he had problems with a real machine, I already thought about Wi-F...
To be fair, they did hint that it might be WiFi,
I'm very new to linux and especially debian. I guess its searching for a wifi or?
#1074964802868351007 message
That, and you weren't completely wrong. I mean, to err is human, and some of your troubleshooting suggestions weren't that far off either. I would always request for actual hardware information, in case there's any potential misunderstandings.