![]() ![]() It really is, the easiest, non-tech savvy way that i'm aware of) There are also other alternatives such as Afraid DNS ( Īnd even, Cisco's, Open DNS : could also be utilized (provided that this is not you're only client, i'd suggest you sign up for an umbrella account trial, take it for a spin and later sign-up for the real deal > they even got one of them GUI-like downloadable extensions which would automatically renew the the ddns hostname Free for 1-3 machines running on the same network(if im not mistaken, dont quote me here: its been a while since ive trusted any of these 'free' services. Head over to and signup for an account (it's, errr. You should really look into ddns services.Īs far as remotely being able to connect to a certain machine with dynamic ip address ddns is the most commonly used solution. This might mean your router not doing NAT at all, and my original ideas still being valid even behind a router. See, for example, - but in that case, shame on you for not mentioning it in your original post. Or, are you using IPV6? There are some configurations where a device keeps changing its IP to make it less easy to track. ![]() Give your server a fixed internal address. Or, it's the internal IP of the server that changes - in that case, something is severely broken with your DHCP. Did you set up a port forwarder within the router yourself. ![]() This port forwarding shouldn't break when the external IP changes (existing ssh connections will be dropped however), but maybe it's a rule that wasn't setup by you, but by some UPNP magic, with the router dropping UPNP forwards when it gets a new address, and sshd only invoking the rule when it restarts. You connect to the external address, and the router should a port-forwarding rule to the internal address. In this setup, the router has an external IP (which changes daily), and your internal devices should have some 10.x.y.z or .y addresses which shouldn't change. If one of these has the current server address, you'll need to either change it to 0.0.0.0 (make sure you know about the security implications), or update the rule/configuration whenever the IP changes.Īs the server is behind a router, the above ideas probably don't apply(*). To check the second case, do iptables -L -n and check if one of the rules in the INCOMING chain matches your server's IP and port 22. If it says 0.0.0.0:22, that's ok if it lists a specific IP, then check the sshd config file ( /etc/nf) for ListenAddress. To check the first case, do a netstat -nta | grep -w 22 | grep LISTEN. What I could imagine is the server not being behind a router and doing its own PPPoE connection, and a) the ssh server binding to the specific interface address at the point of server restart, b) a firewall on the machine that permits incoming ssh to just the server's IP with the firewall not updating when the IP changes. You might need to provide more information about the network topology to get a good answer. Unfortunately, the server getting a new IP should not be a problem in the standard setup where the ISP provides a router, the server has an internal address behind the router, and the router does the port forwarding. Once that happens, I'm no longer able to connect remotely even using the new IP addressĭDNS will help you find out the new IP address, but that doesn't seem to be the problem here. The other answers seem to have overlooked one thing in your question: Most people seem to think SSH should work as long as we know the new IP, so is this something unique to 18.04? I installed this server for the client recently, so all config settings are still default. I would like to know the root cause in hopes of finding a better solution. But I don't understand why I should have to do this. ![]() If I restart the SSH service on the target machine, I have remote access again. The problem is the server stops responding once the IP changes, even though I try to connect using the new IP address. To be clear, my problem is NOT finding the new IP address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |