![]() ![]() VPN is initiated from the device to cloud, so you can close 22 port if needed for inbound connections.Īs a bonus in both tools you also get monitoring and more. - desktop app that maps any port to the remote, so you can open connections to both devices and your local computer act like a bridgeįor both tools NAT is not an issue.There are plenty tools for that, some of them are free to use. If you want to ssh from local network, use ssh -p 222 192.168.0.33. Physical machine will give that connection to port 22 of virtual machine (provided that VM is running). If you want to have SSH access and If your devices are connected to the internet you could build a VPN connections to them and access them via SSH or web remote console. Now if you know your routers IP, you can ssh to your routers IP, and it will be automatically forwarded to port 2222 of your physical machine. You do not have to play around with the fixed IP If you want to send small amount of data between devices - you can use some free cloud MQTT providers and both devices just connect to it. On the side of the inbound SSH connection, the router needs a port forwarding configured: from the internet-side of the router, a TCP port of your choice needs to be forwarded to the static private IP of the destination RPi.You might even find a free dynamic DNS service for your region sometimes. If the public IP is non-static (as usual for consumer-grade internet connections), using a dynamic DNS service to assign a static DNS name for it is usually cheaper than getting a static IP address, and then you'll be able to connect by DNS name, even if the IP address will vary. An SSH tunnel is another method of rerouting some or all traffic from one location (like your local computer) through another (your remote server). But you don't really need a static public IP for the router at the inbound SSH connection side, but a known public IP. Getting a really static IP tends to have a cost, and is not always possible for home consumer internet connections.You need the internet provider on the inbound ssh connection side to be not using Carrier-grade NAT (CGNAT) and not firewalling all inbound connections.You don't need anything specific on the outbound ssh connection side.Strictly speaking, that is off topic for Unix&Linux.SE. ![]() The rest of your question is basically asking for general home networking advice, nothing specific to Unix or Linux. DHCP offers from 192.168.1.10 to 192.168.1.127) then you could just pick one address from outside the DHCP range but within the subnet (say, 192.168.1.200) and just configure it to the RPi as a static IP address. 192.168.1.254) but only uses DHCP on some subset of them (e.g. Or if your router provides a particular private subnet (e.g. usually wired connections don't randomize MAC addresses by default, but WiFi connections might) and always assign it a particular private IP. Getting a static private IP address is entirely between the RPi and its router.įor example, you could configure the router to identify the RPi by MAC address (after ensuring any MAC address randomization features on the RPi OS are switched off. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |