[SOLVED] Direct connect to laptop via Ethernet problem

[dohuutamhuy]

Hi I'm still new to raspberry and linux . I'm trying to use the runeaudio via ethernet direct to laptop without network connection . I can connect to some OS (like Wheezy Raspian or Retropie ) through this way so i think this can work too but i've encoutered some problem . Here's what i did :
First : i connect the raspberry pi with runeaudio img to the router like normal .
Second : i change from DHCP IP to static IP (from 192.168.0.121 to 169.254.249.63) via GUI .
Third : i plug the ethernet cable directly to my laptop and use IP : 169.254.249.63 to access the rune . It worked
...
until i reboot the raspberry. After that i can't connect the the rune audio anymore even via the router nor direct to laptop . Anyone can help me or explain to me why this happened ? Tks very much guys.
P/S: my native language is not english so if anything's wrong plz correct me

[hondagx35]

[dohuutamhuy]

Hi hondagx35,
Tks for replying .
I tried your way but it didnt work . Here what i did :
First time :
- reflash the card and reinstall the image
- wired raspberry to router
- open ssh and put ur command
- access to runeaudio GUI and set the network interface from DHCP to static IP
- wired raspberry to my laptop ethernet
- access through the Local IP like I did before . Couldn't access
- reboot the raspberry then try again but still couldn't access

2nd time : this time i tried to change the IP first then put your command but still didn't work
- reflash the card and reinstall the image
- wired raspberry to router
- access to runeaudio GUI and set the network interface from DHCP to static IP
- open ssh and put ur command
- "systemctl enable netctl-ifplugd@eth0" everything still fine
- "systemctl start netctl-ifplugd@eth0" things started not working from here
- Then SSH stopped
- reboot the raspberry then try again but still couldn't access ...

conclusion : after put ur command and try to access through local IP like I did before, I can't connect to Rune GUI anymore .
EDIT 1 : Attach pictures

[cmh714]

unless something has changed in networking recently that I missed, I think what you are doing requires a cross-over cable not a normal straight-through cable.....

[MarkP]

The Pi has an auto-sensing ethernet port, so a cross-over cable should not be necessary.

When you connect directly to a PC, there will be no DHCP server active (unless you deliberately configure one). I think you are seeing it partially working as a result of cached IP addresses. If you want to connect like this, you should configure static IP addresses on both the PC and the Raspberry Pi, on a common subnet.

[dohuutamhuy]

Tks cmh714 and MarkP for replying .
Well i thinkn MarkP got the point . When I connect directly to my PC there's no DHCP active so that's why when i reset the Raspberry pi, things didn't work anymore .
P/S: sorry for the very late reply . My christmas was crazy X_x .