I have a raspberry with raspbian intstalled with no gui (I think its called jessie)
The first days it work exactly like I wanted it to work but since yesterday it has no internet even if the wlan cable is plugged in.
I've seen a couple of solutions but that is if you have a wireless conection with gui.
I dont think its my router because every other device works on there and the other days it also worked with that router
please help
thanks, Stephan
PS: Im sorry for my bad english, Im from the Netherlands and the ipconfig results are the same with no cable plugged in.
It was very simpel,
I just needed to
sudo dhcpcd
Because the service wouldnt start when it booted up.
Related
I have been trying to get Raknet up and running on my Raspberry Pi (2).
I am using a simple client server test program to connect from my windows machine to my raspberry pi. Using tshark on the Pi I can see that all message are arriving on the Pi. However, the server application does not seem to pick those up. As far as I can deduce all ports are open, the machines are on the same network, the code is correct (taken from some github repo with examples for raknet).
The frustrating thing is that a while back I though I solved this communication by starting my server app as root (sudo). However, in the meantime something has been changed in my setup which makes this no longer the case. Any help is appreciated.
I completely forgot about my question here. It actually had to do with privileges on the networks we use here. I had been testing on two different networks without realizing. Problem has been solved.
I recently bought a Raspberry Pi 3 Model B and started to set it up. I followed some tutorials and finally was able to access it remotely without having to plug it to a monitor, a keyboard, a mouse...
Everything is okay but it just bothers me a little bit that whenever I reboot it or I don't use it for some time I have to ping it on the computer before being able to control it remotely. If I don't ping it, connection fails.
It's not a big problem but is something I'd like to be solved. Thank you for your attention!
UPDATE: Just did a clean installation and now it works fine and can be accessed remotely at any time. Thanks to anybody that tried to help!
Let me start by saying that I have no experience with Linux and this is my first attempt at getting into the IoT with a raspberry pi3. My question is why can I connect via ssh to my pi when I use the ip address but not the hostname?
After getting everything set up at home, I tried to remote in via PuTTY from my laptop. (The laptop is less than 6 months old and if I need to provide the specs on it, I can. It is running windows 10 if that matters). It worked when I entered the ip address of the pi, but when I tried again with the host name (which is clearly defined in the raspberry pi configuration) it said host does not exist. I used hostname.local and still failed.
Today, I brought the whole setup to work to try a few more scenarios. From my work desktop, which is running windows 7 and not wireless, I could remote in via hostname.local. I then tried again on a different laptop running windows 7 and it worked too. Next attempt was on another new (less than 3 months old) laptop running windows 10 and it failed to remote in via the hostname.
This would tell me that there is nothing wrong with my home network or the network at work, and it also makes me think that this has nothing to do with the pi, since other computers can resolve the hostname to the ip address and successfully login. What the hell am I doing wrong or missing?
I spent 2 nights googling and browsing forums trying to find an answer for this but cant, so instead of bashing this post, please poke me for more information you think might be helpful for a solution.
EDIT I gave my computer and PI to my cousin to fix. He installed Samba, though I don't know what it does differently. After doing more research, it sounds like the problem I was having was a DNS issue. I don't know how it was resolved by downloading samba on the pi, but I can now connect via the hostname.
So if I understand correctly it would appear that there is some particular settings on that laptop preventing you from using SSH if that is the only thing you are changing? I think this is likely to be something to do with the security settings on the laptop but Windows isn't my thing sorry.
I want to make my raspberry pi (reaspbian) available from the internet via ssh.
Locally it is not a problem, but after asigning a public ip (router is thomson TG789vn) it does not work anymore.
also not from the local network. theres always a timeout error.
The strange thing is that i tried it some months ago and it worked and now i really don't know what to do to fix it.
Check your internet connection and the LED on the front. As well make sure it is configured correctly. Pi's are very barebones and do not have the comprehension that windows has to fix all the little problems.
I'm using Mac OS X and trying to SSH into my pi. I have the pi boot up in front of me, and I can see that the IP address is 192.168.0.13.
However, if I ping the router on the A Record address I assigned to it, it responds.
When I boot the Raspberry Pi up, it showed:
My IP address is 192.168.0.13
Raspian GNU/Linux 7 subdomain.domain.com tty1
subdomain login:
I was surprised that it showed the subdomain and domain on login (I'm a Linux newbie).
Ever since i set up the subdomain to go to my pi and set up the port forwarding and firewall exceptions on my router, I never really used the pi itself, I always SSH into it. It stopped working for the past week for some reason. There's nothing I installed recently except nginx, but that shouldn't affect it right?
Any troubleshooting advice? Can't seem to find anything newbie-friendly online.
Will be more than happy to provide more information, as I think I haven't provided enough here but don't know what else to add!
Many thanks in advance :)
EDIT: I was pinging the incorrect address! It's ...0.13 not ...1.13 :) Apologies!