Hi,
I have arch installed on a Raspberry Pi2. Had a headless server configuration with with arch and the same Pi on the same network which worked, but I remember I had to change one line in a config file. Took me days to figure it out. Can't remember what it was hmm. One time I had network issues after upgrading but didn't have time to look into it. After months I did a fresh installation but could not get any Internet connection. I messed with some config files but can't recall in detail what I did. Didn't help.
So I just did another fresh installation to make sure everything is default.
I'm using a fritz.box as router. I can confirm the ethernet cable works and the ethernet port on the fritzbox also works. I also tried different ports and cables. I have no problems to SSH into the same Pi and to connect to the internet from a different network (at my girlfriends house).
However I can't SSH into the fresh installation on my home network. I have no option to use a monitor. I could however connect a keyboard and type commands blindly. I need a solution or further diagnostics that I can copy to the SD card and boot it up.
Any ideas? Thx so much.
Some details:
DHCP seems to work the fritz.box gave it IP address 192.168.1.6 and shows the hostname 'alarmpi'. It shows as status: "Connected to the fritz.box, but not to the internet"
The router is connected via IPv4 to the Internet. Somewhere I read that Fritz.Box runs it's own DNS server if DHCP is enabled. Fritz.Box also tells me that it's using 193.189.250.100 (currently used for standart requests) and 193.189.250.101 as DNS Nameservers.
resolv.conf of my laptop (kubuntu 16.10) which works just fine on this network is:
$this->bbcode_second_pass_code('', '
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1
search fritz.box
')
resolv.conf of the arch is (after the first boot):
$this->bbcode_second_pass_code('', '
# This file is managed by systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known DNS servers.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 2001:4860:4860::8888
# Too many DNS servers configured, the following entries may be ignored.
nameserver 2001:4860:4860::8844
')
Those are the errors I get when I try to connect:
$this->bbcode_second_pass_code('', '
$ ssh alarm@192.168.1.6
ssh: connect to host 192.168.1.6 port 22: No route to host
$ ssh alarmpi
ssh: Could not resolve hostname alarmpi: Name or service not known
$ ssh alarm@alarmpi.box
ssh: connect to host alarmpi.box port 22: Connection refused
$ $ ping 192.168.1.6
PING 192.168.1.6 (192.168.1.6) 56(84) bytes of data.
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
$ ping alarmpi.box
PING alarmpi.box (127.0.53.53) 56(84) bytes of data.
64 bytes from localhost (127.0.53.53): icmp_seq=1 ttl=64 time=0.037 ms
64 bytes from localhost (127.0.53.53): icmp_seq=2 ttl=64 time=0.065 ms
64 bytes from localhost (127.0.53.53): icmp_seq=3 ttl=64 time=0.072 ms
')