You are not logged in.
Hello,
I'm attempting to install fresh from an Arch USB ISO, and can successfully boot into UEFI mode. My Ethernet interface (in this case named enp33s0) is failing to ping to devices outside of my network (College dorm network over ethernet). Pinging 8.8.8.8 and archlinux.org fails with no packets received.
I have confirmed the interface has received a dynamic IP address from the dorm's network, and can even ping devices on the network like my laptop and phone, and have also confirmed systemd-networkd and systemd-resolved are both running and have assigned a proper address. ip route outputs:
default via 10.150.12.1 dev enp33s0 proto dhcp src 10.150.14.86 metric 100
8.8.4.4 via 10.150.12.1 dev enp33s0 proto dhcp src 10.150.14.86 metric 100
8.8.8.8 via 10.150.12.1 dev enp33s0 proto dhcp src 10.150.14.86 metric 100
10.150.12.0/22 dev enp33s0 proto kernel scope link src 10.150.14.86 metric 100
10.150.12.1 dev enp33s0 proto dhcp scope link src 10.150.14.86 metric 100
Any help would be appreciated, thank you!
- Zeke
(Ezekiel Hernandez-Hall)
Offline
Does your college network use a captive portal that keeps you in a virtual jail until you log in?
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
Offline
Does your college network use a captive portal that keeps you in a virtual jail until you log in?
Not for the dorm's wired connection. I have been using this exact same connection for my Manjaro installation with no problems whatsoever.
- Zeke
(Ezekiel Hernandez-Hall)
Offline
default via 10.150.12.1 dev enp33s0 proto dhcp src 10.150.14.86 metric 100
8.8.4.4 via 10.150.12.1 dev enp33s0 proto dhcp src 10.150.14.86 metric 100
8.8.8.8 via 10.150.12.1 dev enp33s0 proto dhcp src 10.150.14.86 metric 100
10.150.12.0/22 dev enp33s0 proto kernel scope link src 10.150.14.86 metric 100
10.150.12.1 dev enp33s0 proto dhcp scope link src 10.150.14.86 metric 100
On most networks I'd expect just 2 lines , the default one and the 10.150.12.0/22 .
No idea what created them.
What is the output of
$ tracepath -4 95.217.163.246
$ tracepath -6 2a01:4f9:c010:6b1f::1
(those are the ipv4 & ipv6 addresses of archlinux.org)
Last edited by Lone_Wolf (2022-10-10 10:51:15)
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
Sorry for the late response, my output of
$ tracepath -4 95.217.163.246
$ tracepath -6 2a01:4f9:c010:6b1f::1
Is as follows:
1?: [LOCALHOST] pmtu 1500
1: no reply
2: no reply
A bunch of no-reply responses later...
30: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
As for IPv6, I get:
1: send failed
Resume: pmtu 128000
That help at all?
- Zeke
(Ezekiel Hernandez-Hall)
Offline
It kinda suggests the device at 10.150.12.1 is blocking lots of icmp protocols .
What Is the output of those commands on the manjaro install where things work ?
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
On my current Manjaro system, the output of
$ ip route
is:
default via 10.150.12.1 dev enp33s0 proto dhcp src 10.150.15.42 metric 100
default via 10.150.12.1 dev wlp35s0 proto dhcp src 10.150.14.87 metric 600
10.150.12.0/22 dev enp33s0 proto kernel scope link src 10.150.15.42 metric 100
10.150.12.0/22 dev wlp35s0 proto kernel scope link src 10.150.14.87 metric 600
While the outputs of
$ tracepath -4 95.217.163.246 && tracepath -6 2a01:4f9:c010:6b1f::1
are the exact same as the Arch ISO's execution. Funnily enough, I can't currently ping 8.8.8.8 from my Manjaro installation either, but I still have internet access...
- Zeke
(Ezekiel Hernandez-Hall)
Offline