Yes I did, after I put
screen becomes still and after about 2 minutes prompt line is returned. But still no net.
I tried it with different combinations like
ifconfig eht0 up 192.168.2.1
or with IP that I should be using that is 192.168.2.100, but net is still unreachable.
Though when I've used
ifconfig eth0 up 192.168.2.100
I could log into my router through links and I was able to ping it.
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.022 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.008 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.005 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.005 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=0.006 ms
64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=0.005 ms
64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=0.006 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.005 ms
--- 192.168.2.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 6996ms
rtt min/avg/max/mdev = 0.005/0.007/0.022/0.006 ms
I wasn't able to ping it though when I get eth0 up with 192.168.2.1 (my router).
I am confused mostly because I really don't know much about lan and networking...
One more thing, I have checked syslog and there is this:
Oct 21 12:36:49 aster dhcpcd: timed out waiting for a valid DHCP server response
Oct 21 12:37:20 aster dhcpcd: timed out waiting for a valid DHCP server response
I have browsed google for it, but haven't found anything usefull.