I want to run a Node web server on my Pi, and connect to it via the Pi's wifi. The idea is that I can access the server when I am in the middle of nowhere and just plug the Pi to a 5V output and login the server through my phone. I just want to setup the pi as a LAN network.
Through past research and tests I managed to turn my Pi into an access point but I lost the ability to SSH to it.
At the moment I have a Node server running a webpage and I am able to connect to it as the Pi is connected to a wifi router.
I am wondering if I just need to turn my Pi into an AP or if I need to do some port forwarding too.
My current setup is a RaspberryPi4 with Raspbian and running Node.
Edited -
Added "I just want to setup the pi as a LAN network."
In the raspberrypi.org documentation has all the information, in the AC I recommend using a wifi adapter, but you can use the pi interface.
https://www.raspberrypi.org/documentation/configuration/wireless/access-point-routed.md
you do not need to configure dhcp, as the site may be located on localhost 127.0.0.1
and recommend to access by phone
https://www.raspberrypi.org/documentation/remote-access/ssh/
if you have any problems in the configuration process put it here
Related
I am trying to remotely gain access to the command line of a Raspberry Pi 3 from my windows laptop on the same network using ssh. I am using Putty as the tool.
Since both my laptop and Pi are connected using my home Internet wireless connection, they are on the same network. When I try to ping the Pi from my laptop, it says destination is not reachable. However, if I keep trying for 4-5 times, it finally works. I am able to use Putty and connect to my Pi and execute some commands. However, after few minutes, I lose the connection. When I try to ping the pi, I get the message destination is not reachable.
This issue is intermittent. I used the below link to set a static IP address.
http://www.modmypi.com/blog/how-to-give-your-raspberry-pi-a-static-ip-address-update
I am able to now always connect to my pi using a fixed IP address. However, the issue still exist. I am able to ping the pi after several attempts and then after few minutes the connection drops.
I am using the ADSL2+ internet connection at home and dont see any problem with that. In my Pi, I opened the file /etc/ssh/sshd_config file to confirm the port is 22. I use my Putty to connect to my Pi using port 22.
Thanks,
Murali
I am currently working on internet of things technology, in one of my scenarios I want to connect raspberry pi2 through the mobile network.
Please tell me is there any possibility to connect with raspberry pi2 through the mobile network.
Regards,
Pradeep
You can connect your Pi2 to a mobile network using either a USB 3G Dongle or a 3G Shield.
You will have to play around with the setup though to see how it works for you.
If you want to access your Pi2 from elsewhere while connected to a mobile network you will also need to setup dynamic ip resolution for your Pi if you do not have a fixed ip assigned by your mobile operator.
If, however you want to connect from a mobile device to your Pi2 which is located on a LAN, you will need to configure port forwarding on your router for the Pi2 to receive communication from the outside world. Once again, if your router does not have a fixed ip supplied by your ISP, you will need to setup a dynamic ip resolution (DDNS).
Hope this helps.
I installed LAMP on my raspberry pi and i can reach the default page at localhost from the pi. However, I can't reach the page from another computer in the LAN unless I'm on wifi.
If I am on ethernet, I just get a timeout. Any ideas why?
Firstly,here, I will mention all what I did to make raspberry pi as a web server or as a data cloud. But all the issues which were applied did not work. There are some problems in somewhere , but I dont know where, what , how.. ?
So let me start.
Firstly,I booted my raspberry pi with Raspian OS. It works in a best manner for sure.Then, I installed ntfs-3g to make it possible to read my hard drives by raspberry pi.
When I connected my hard drive (500 GB), raspberry pi went crazy,it freezed and so on.
I have two hypotheses. One of them , maybe hard drive could be so huge for raspberry pi to read and it could take lots of time to read.
But someone could do with 1TB hard drive. So this one is dead!
Another hypothesis is that hard drive is formatted with NTFS. Maybe it could be problem.
At first, I booted raspberry pi from a usb storage and when I connected that hard drive, raspberry tried to boot itself from hard drive, not from usb.That's why this is one another hypothesis. I havent disproved this yet. But i will and let you know.
Although I could not connect my hard drive to raspberry pi, I gave a break to that issue and I tried to create a connection from remote network to my raspberry pi.
I made raspberry's IP as a static. I could connect it from ssh and file zilla(ftp) LOCALLY. I disabled firewall of my router and observed my router's external IP. It has not changed for many days although I dont have a static external IP. Then, I arranged my port forwarding like these
"router_external_IP":8080 destination(raspberry's internal IP) is 22 (for SSH)
"router_external_IP":9000 destination(raspberry's internal IP) is 80 (for HTML)
"router_external_IP":8500 destination(raspberry's internal IP) is 3306(for mySql)
When SSH server and Mysql server ran on the raspberry pi, I tried to connect to raspberry pi
by SSH with "router_external_IP":8080 (from putty)
by browser with "router_external_IP":9000
by browser with "router_external_IP":8500
NO ONE WORKED :( ! [By the way, I installed web servers on it, but i did not mention]
Someone can say that "Are you sure about ports are open ?".
Yes I am sure I checked it out. But I am not sure on my router are forwarding these ports to raspberry pi or not . Also, I can not debug it.
Actually, I have 2 hypotheses on that also.
First one is that maybe router does not forward these ports to raspberry pi.
Second one is that maybe I am doing something wrong and that is why although router forwards all given ports to raspberry, raspberry can not respond.
I can not disprove these since I dont know how to debug.
I do not know what to do. I just got lost. Please help me on these issue.
An easy way to check if your router is forwarding your ports is to check them at: http://canyouseeme.org . If, as you say, all your ports are open on your internal network, if "canyouseeme" can't see your services then you know you need to tweak your router settings.
I'm trying to develop an interface to an application that doesn't run on Windows 8. Hence, I've created a VM with Windows 7 running the integration service and another service running on the Windows 8 host.
I have three Virtual Network scenarios configured for Hyper-V: Wireless, Shared and Internal. Where Wireless allows all VMs and the host to connect to a wireless network (External), Shared let's the VMs connect through the host via a VPN (Internal) and Internal creates a network within the host where the VMs don't have network access (Private).
When I'm in Wireless (External) mode and there's a wireless network to connect to, everything works fine as if I were testing using to physical PCs on a wireless network. However, today I had a situation where I wasn't connected to a network but still wanted to do some testing and I could not get the VM to see the host and vice-versa. This scenario was quite straight forward to create on VMware which I used before switching to Hyper-V...
Has anyone managed to make Client Hyper-V VMs and the host communicate without a network? Can you guide me how to set it up?
Wireless networking under Windows 8 Hyper V can not communicate with multiple VM the Wireless NIC is assign to only one Hyper V internet connection,
Meaning only one Hyper V can connect to the Internet preventing others from connecting unless you use multiple Nic's Wireless Network Cards or USB Wireless Network.
It is only after you restart or shut down your computer that Hyper-V problems start.
So if you can not connect any of your Hyper VMs then you problem could be due to a shutdown error that Hyper-v in counted Try restarting the whole computer then Hyper- VMs your problem should fix itself.
Might want to try this. I am having similar problems as you and all signs point to this particular solution working, but for me it is not. Might help you, though.
http://blogs.technet.com/b/doxley/archive/2008/07/07/disconnecting-hyper-v.aspx
The solution that DID end up working for me was this:
http://www.elmajdal.net/Win2k8/Enabling_Wireless_Network_For_Hyper_V_Virtual_Machine.aspx