ping: connect: Network is unreachable

Ivy2012 · 2012-09-26 17:22:36

Hi all,

I've been trying to connect to internet now for a serious long time.
Having a fresh install of Arch Linux.

Ping 8.8.8.8 gives me:
connect: Network is unreachable

I've tried many things.
It would be very nice if someone can point me in the right direction..

Here some output that might help.

ip a

inet 192.168.5.240/24 brd 192.168.5.255 scope global eth0

dhcpcd eth0 (after killing the process)

version 5.6.0 starting
eth0: sending IPv6 Router Solicitation
eth0: rebinding lease of 192.168.5.101
eth0: acknowledged 192.168.5.101 from 192.168.5.1
eth0: checking for 192.168.5.101
eth0: sending IPv6 Router Solicitation
eth0: leased 192.168.5.101 for 7200 seconds
forked to background, child pid 9885

vi /etc/resolve.conf

# Generated by dhcpcd
nameserver 8.8.8.8
# /etc/resolve.conf.tail can replace this line
(note: I putted the second line in a new file called /etc/resolve.conf.head)

vi /etc/rc.conf

...
# Network
interface="eth0"
address=
netmask=
gateway=
...

Again, it would be very nice with some tips..
I'm ready to respond right away.

Thanks
Ivy
PS Having a windows laptop on the side, same network. Works fine.

Last edited by Ivy2012 (2012-09-26 17:31:45)

luvfree · 2012-09-26 17:38:55

do you have dhcpcd enabled in systemd?
run this command and see what happens...
[ systemctl enable dhcpcd@eth0.service ]
reboot for it to take effect.

Last edited by luvfree (2012-09-26 17:43:45)

Ivy2012 · 2012-09-26 17:43:34

luvfree wrote:

do you have dhcpcd enabled in systemd?
run this command and see what happens...
systemctl enable dhcpcd@eth0.service
reboot for it to take effect.

systemctl command is not found.
Is there a different way I can do this?
Thanks for the quick response btw.

Strike0 · 2012-09-26 17:44:21

Hi Ivy,
Double-check the nameserver is in "/etc/resolv.conf" not in "resolve.conf"

luvfree · 2012-09-26 17:46:46

did you run it as superuser?
sudo systemctl enable dhcpcd@eth0.service
then enter your password.

Ivy2012 · 2012-09-26 17:48:06

Strike0 wrote:

Hi Ivy,
Double-check the nameserver is in "/etc/resolv.conf" not in "resolve.conf"

Hei. Thanks for the response.
Checked it. It is in /etc/resolv.conf.
resolv.conf does not exists, and when I "vi" it, it says I'm creating a new file.

Ivy2012 · 2012-09-26 17:52:16

luvfree wrote:

did you run it as superuser?
sudo systemctl enable dhcpcd@eth0.service
then enter your password.

Darn. I don't have sudo installed.
As said, it's a fresh install of Arch linux, so pretty clean (or: empty...)
Any work arounds for this?
Sorry if it all sounds hopeless.. trying to do what I can here.

luvfree · 2012-09-26 18:00:01

you can do this...
su root (hit enter)
enter the root password.
then enter the command without sudo.
systemctl enable dhcpcd@eth0.service (hit enter)
type "exit" when done to go back to regular user.

Ivy2012 · 2012-09-26 18:01:38

luvfree wrote:

you can do this...
su root (hit enter)
enter the root password.
then enter the command without sudo.
systemctl enable dhcpcd@eth0.service (hit enter)
type "exit" when done to go back to regular user.

Ouput:

bash: systemctl: command not found

jakobcreutzfeldt · 2012-09-26 18:09:34

luvfree wrote:

you can do this...
su root (hit enter)
enter the root password.
then enter the command without sudo.
systemctl enable dhcpcd@eth0.service (hit enter)
type "exit" when done to go back to regular user.

Protip: one needs Systemd to be installed in order to use Systemd commands

Last edited by jakobcreutzfeldt (2012-09-26 18:09:56)

luvfree · 2012-09-26 18:09:40

apparently you don't have systemd installed.
did you install using the latest install medium 2012.09.07
if not I recommend starting over with the new media.

Last edited by luvfree (2012-09-26 18:19:03)

luvfree · 2012-09-26 18:10:47

jakobcreutzfeldt wrote:

luvfree wrote:
you can do this...
su root (hit enter)
enter the root password.
then enter the command without sudo.
systemctl enable dhcpcd@eth0.service (hit enter)
type "exit" when done to go back to regular user.
Protip: one needs Systemd to be installed in order to use Systemd commands

we're getting to that.
if she used the latest install media it should be there...

Last edited by luvfree (2012-09-26 18:20:36)

Ivy2012 · 2012-09-26 18:21:49

I installed a little while ago.
Running pacman -Q shows me:

...
archlinux-keyring 20120812-1
...

luvfree · 2012-09-26 18:24:42

that's the older install media.
one caught in the middle of a transitional period.
I strongly recommend starting over with the new media. (since this is a fresh install anyway)
it will simplify things in the long run.

Last edited by luvfree (2012-09-26 18:26:11)

Ivy2012 · 2012-09-26 18:33:36

luvfree wrote:

that's the older install media.
one caught in the middle of a transitional period.
I strongly recommend starting over with the new media. (since this is a fresh install anyway)
it will simplify things in the long run.

ok. Tnx for the tip.
Will do that, and call it a quit for tonight.
Thanks all of you, for the feedback

luvfree · 2012-09-26 18:36:15

Ivy2012 wrote:

luvfree wrote:
that's the older install media.
one caught in the middle of a transitional period.
I strongly recommend starting over with the new media. (since this is a fresh install anyway)
it will simplify things in the long run.
ok. Tnx for the tip.
Will do that, and call it a quit for tonight.
Thanks all of you, for the feedback

you're welcome Ivy and good luck with it.
I just did a fresh install with the new media and it makes things much smoother.
feel free to ask for help any time.

sysjumbledwords · 2018-06-11 22:50:25

luvfree wrote:

do you have dhcpcd enabled in systemd?
run this command and see what happens...
[ systemctl enable dhcpcd@eth0.service ]
reboot for it to take effect.

Thanks a lot. Years later your post helped me.

circleface · 2018-06-12 00:12:01

Please do not necrobump old threads, especially with an empty post.

jasonwryan · 2018-06-12 00:13:19

Indeed. https://wiki.archlinux.org/index.php/Co … bumping.22 and https://wiki.archlinux.org/index.php/Co … mpty_posts

Closing

Arch Linux

#1 2012-09-26 17:22:36

ping: connect: Network is unreachable

#2 2012-09-26 17:38:55

Re: ping: connect: Network is unreachable

#3 2012-09-26 17:43:34

Re: ping: connect: Network is unreachable

#4 2012-09-26 17:44:21

Re: ping: connect: Network is unreachable

#5 2012-09-26 17:46:46

Re: ping: connect: Network is unreachable

#6 2012-09-26 17:48:06

Re: ping: connect: Network is unreachable

#7 2012-09-26 17:52:16

Re: ping: connect: Network is unreachable

#8 2012-09-26 18:00:01

Re: ping: connect: Network is unreachable

#9 2012-09-26 18:01:38

Re: ping: connect: Network is unreachable

#10 2012-09-26 18:09:34

Re: ping: connect: Network is unreachable

#11 2012-09-26 18:09:40

Re: ping: connect: Network is unreachable

#12 2012-09-26 18:10:47

Re: ping: connect: Network is unreachable

#13 2012-09-26 18:21:49

Re: ping: connect: Network is unreachable

#14 2012-09-26 18:24:42

Re: ping: connect: Network is unreachable

#15 2012-09-26 18:33:36

Re: ping: connect: Network is unreachable

#16 2012-09-26 18:36:15

Re: ping: connect: Network is unreachable

#17 2018-06-11 22:50:25

Re: ping: connect: Network is unreachable

#18 2018-06-12 00:12:01

Re: ping: connect: Network is unreachable

#19 2018-06-12 00:13:19

Re: ping: connect: Network is unreachable

Board footer