I can't connect to internet (via ethernet) from Manjaro NET Install ISO
ManjaroThis forum is for the discussion of Manjaro Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can't connect to internet (via ethernet) from Manjaro NET Install ISO
Hi there
I got a new computer and want to install manjaro net edition on it, but I can't connect to internet from it.
I know the NIC and cables are working fine because I can connect to internet from a Debian installation on the same computer (On Debian I had to edit a little bit /etc/network/interfaces file to get it working)
My dhcpcd.conf file looks like this: https://hastebin.com/raw/warocaqeda
I tried running dhcpcd and dhclient -4 -v but they return
Code:
dev: loaded udev
DUID 00:01:00:01:20:0e:92:da:40:8d:5c:18:90:27
enp5s0: IAID 5c:18:90:27
enp5s0: soliciting an IPv6 router
enp5s0: soliciting a DHCP lease
enp5s0: using IPv4LL address 169.254.180.236
enp5s0: adding route to 169.254.0.0/16
forked to background, child pid 1730`
and
Code:
Internet Systems Consortium DHCP Client 4.3.4
Copyright 2004-2016 Internet Systems Consortium.
All rigts reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/enp5s0/40:8d:5c:18:90:27
Sending on LPF/enp5s0/40:8d:5c:18:90:27
Sending on Socket/fallback
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
respectively, and, after that, ping 8.8.8.8 returns Destination Host Unreachable
In your first post you said the output of dhcpcd returned what I quoted in my initial response, which seems to indicate that it received a lease from your router. What is the output of
That Is the output of dhcpd, but, it never says that it received a lease :O , it just says that is using IPv4LL address 169.254.180.236 (which is useless :P).
'ip a' output is
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
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: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 40:8d:5c:18:90:27 brd ff:ff:ff:ff:ff:ff
inet 164.254.180.236/16 brd 169.254.255.255 scope global enp5s0
valid_lft forever preferred_lft forever
inet6 fe80::48f9:5417:28cb:8d63/64 scope link
valid_lft forever preferred_lft forever
That's strange. Is it still assigning a link local address even with that option? You might try putting it in your dhcp.conf and see if that makes a difference. If it's still assigning it a link local address, it seems for some reason must not be reading dhcp.conf
Hmmm... need to 'dig out' the 'hidden clue' here (but I don't have definitive way, sorry)
Manjaro is usually 'pretty good' (I VBox'ed manjaro-net-16.06.1-i686.iso per early LQ recomendation)
To clarify, what is running (&your output posted from) is the .iso (not a 'modified' install), I assume.
What [exact] "edit a little bit" was needed to make Debian work? Any ISP details relevant?
(when my 'unfriendly' wifi ISP refuses to 'lease' me a 192.168.6.x, I get [random?] 169.254..)
Can you run [either] dhcpClient with more/max verbose debugging? Extreme: tcpdump?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.