Bsrgvty

Will the same JavaScript fetched by HTTP and HTTPS be cached separately by the browser?

My boss asked what number would keep me happy?

What to do with excess co-ax cable

Why are the Democrats & Republicans so homogeneous in their opinions of impeaching Trump?

Is it appropriate to ask for the text of a eulogy?

What was the first "Opening Repertoire" book?

Did a man complain that his Pontiac wouldn't start whenever the ice cream he picked up was vanilla?

What Lego set has the biggest box?

"Sack" data structure in C#

How to join many tables side by side?

make invisible depending on point of view

Is it appropriate to rewrite and republish another author's useful but very badly written paper?

Is it possible to kill parasitic worms by intoxicating oneself?

Why don't the absolute value functions in C accept const inputs?

If a problem is in P solved via dynamic programming, is it also in NP?

Can I decide to use the human trait variant before or after rolling stats?

Moon's unusual gravity

Hans Berliner and computers. Did he win the world ICCF championship using computer help?

How do I force `sudo` to ask for a password each time when a specific command is used?

What is the narrative difference between a Charisma and Wisdom saving throw?

Open a Folder in the File Manager by a Python Script

Is a board required by Scrum?

Could the barycenter orbit of our sun be greatly underestimated?

Is paying for portrait photos good for the people in the community you're photographing?

How can I use Wake-On-Lan on a server in a home network from anywhere on the Internet?

Remotely turning on computer?wakeonlan from remote hostWhich LAN card / module combinations proven to work with Wake on LANWake on demand (WOD, WOL)My website is accessible on my home network but nobody else can access it on the internetHow access openssh-server with external IP address from outside the Local Area Networkssh server unaccessible

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

1

2

I have a PC running Ubuntu Server 18.04.3 LTS and a laptop running Ubuntu Desktop 18.04.3 LTS.

Both are correctly configured to allow the client (laptop) to connect to the server (PC) via SSH on LAN/WLan and I've tested and used this many times before. I've also port forwarded with my home router (BTHomeHub6) to allow SSH via the server's ethernet port using it's public IP. Lastly, the server is configured to accept WOL magic packets (+port forwarding) so I can start it up from anywhere with an internet connection.

However, the issue is that when I'm not in range of my home network i.e at university and on mobile data/their network, sending magic packets doesn't appear to wake up the server and hence the following error is given when I try to SSH in.

ssh: connect to host [public ip of server] port 22: No route to host

Basically, nothing works as it does at home/in the vicinity of my home network (even if I'm on mobile data and using the public IP of the server instead of it's LAN IP it can still send the packets and initiate an SSH session) and I would really appreciate any help in fixing this.

Thanks, I hope I've explained it well enough

---

EDIT :

I'm using this command to send the magic packets (with the terminal package of wakeonlan):

wakeonlan -i [Public IP] -p [10009] [MAC ADDR]

I have two TCP/UDP port forward rules on my home router:

1. INTERNAL (Start/End = 22/22) to EXTERNAL (Start/End = 22/22). For SSH


2. INTERNAL (Start/End = 10009/10009) to EXTERNAL (Start/End = 10009/10009). For WOL

---

EDIT 2:

Having asked the same question on Reddit, I believe I have the solution now and will surely mark as solved if it works. Here is the link if anyone is interested / wants to know how it was fixed:

https://www.reddit.com/r/Ubuntu/comments/dbqitq/xpost_can_ssh_work_over_a_long_distance_providing/

Thanks for the help everyone!

networking server internet router wakeonlan

share|improve this question

edited Oct 1 at 22:48

ewebuntu

asked Oct 1 at 8:43

ewebuntuewebuntu

1144 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The title is misleading, the problem is not SSH but WOL. You should describe more in detail how the WOL packet are sent, and what you did to make sure that the magic packets are forwarded by your home router.
  
  – xenoid
  Oct 1 at 8:59
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Apologies, I've made the necessary edits now. Thanks
  
  – ewebuntu
  Oct 1 at 9:12
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Possible duplicate of Remotely turning on computer?
  
  – Melebius
  Oct 1 at 12:03
  

  
  
  
  

add a comment
 | 

1

2

I have a PC running Ubuntu Server 18.04.3 LTS and a laptop running Ubuntu Desktop 18.04.3 LTS.

Both are correctly configured to allow the client (laptop) to connect to the server (PC) via SSH on LAN/WLan and I've tested and used this many times before. I've also port forwarded with my home router (BTHomeHub6) to allow SSH via the server's ethernet port using it's public IP. Lastly, the server is configured to accept WOL magic packets (+port forwarding) so I can start it up from anywhere with an internet connection.

However, the issue is that when I'm not in range of my home network i.e at university and on mobile data/their network, sending magic packets doesn't appear to wake up the server and hence the following error is given when I try to SSH in.

ssh: connect to host [public ip of server] port 22: No route to host

Basically, nothing works as it does at home/in the vicinity of my home network (even if I'm on mobile data and using the public IP of the server instead of it's LAN IP it can still send the packets and initiate an SSH session) and I would really appreciate any help in fixing this.

Thanks, I hope I've explained it well enough

---

EDIT :

I'm using this command to send the magic packets (with the terminal package of wakeonlan):

wakeonlan -i [Public IP] -p [10009] [MAC ADDR]

I have two TCP/UDP port forward rules on my home router:

1. INTERNAL (Start/End = 22/22) to EXTERNAL (Start/End = 22/22). For SSH


2. INTERNAL (Start/End = 10009/10009) to EXTERNAL (Start/End = 10009/10009). For WOL

---

EDIT 2:

Having asked the same question on Reddit, I believe I have the solution now and will surely mark as solved if it works. Here is the link if anyone is interested / wants to know how it was fixed:

https://www.reddit.com/r/Ubuntu/comments/dbqitq/xpost_can_ssh_work_over_a_long_distance_providing/

Thanks for the help everyone!

networking server internet router wakeonlan

share|improve this question

edited Oct 1 at 22:48

ewebuntu

asked Oct 1 at 8:43

ewebuntuewebuntu

1144 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The title is misleading, the problem is not SSH but WOL. You should describe more in detail how the WOL packet are sent, and what you did to make sure that the magic packets are forwarded by your home router.
  
  – xenoid
  Oct 1 at 8:59
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Apologies, I've made the necessary edits now. Thanks
  
  – ewebuntu
  Oct 1 at 9:12
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Possible duplicate of Remotely turning on computer?
  
  – Melebius
  Oct 1 at 12:03
  

  
  
  
  

add a comment
 | 

I have a PC running Ubuntu Server 18.04.3 LTS and a laptop running Ubuntu Desktop 18.04.3 LTS.

Both are correctly configured to allow the client (laptop) to connect to the server (PC) via SSH on LAN/WLan and I've tested and used this many times before. I've also port forwarded with my home router (BTHomeHub6) to allow SSH via the server's ethernet port using it's public IP. Lastly, the server is configured to accept WOL magic packets (+port forwarding) so I can start it up from anywhere with an internet connection.

However, the issue is that when I'm not in range of my home network i.e at university and on mobile data/their network, sending magic packets doesn't appear to wake up the server and hence the following error is given when I try to SSH in.

ssh: connect to host [public ip of server] port 22: No route to host

Basically, nothing works as it does at home/in the vicinity of my home network (even if I'm on mobile data and using the public IP of the server instead of it's LAN IP it can still send the packets and initiate an SSH session) and I would really appreciate any help in fixing this.

Thanks, I hope I've explained it well enough

---

EDIT :

I'm using this command to send the magic packets (with the terminal package of wakeonlan):

wakeonlan -i [Public IP] -p [10009] [MAC ADDR]

I have two TCP/UDP port forward rules on my home router:

1. INTERNAL (Start/End = 22/22) to EXTERNAL (Start/End = 22/22). For SSH


2. INTERNAL (Start/End = 10009/10009) to EXTERNAL (Start/End = 10009/10009). For WOL

---

EDIT 2:

Having asked the same question on Reddit, I believe I have the solution now and will surely mark as solved if it works. Here is the link if anyone is interested / wants to know how it was fixed:

https://www.reddit.com/r/Ubuntu/comments/dbqitq/xpost_can_ssh_work_over_a_long_distance_providing/

Thanks for the help everyone!

networking server internet router wakeonlan

share|improve this question

edited Oct 1 at 22:48

ewebuntu

asked Oct 1 at 8:43

ewebuntuewebuntu

1144 bronze badges

wakeonlan -i [Public IP] -p [10009] [MAC ADDR]

share|improve this question

edited Oct 1 at 22:48

ewebuntu

asked Oct 1 at 8:43

ewebuntuewebuntu

1144 bronze badges

share|improve this question

edited Oct 1 at 22:48

ewebuntu

asked Oct 1 at 8:43

ewebuntuewebuntu

1144 bronze badges

asked Oct 1 at 8:43

ewebuntuewebuntu

1144 bronze badges

asked Oct 1 at 8:43

ewebuntuewebuntu

1144 bronze badges