Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had discussed WOL stuff till in the deepest manner(get smacked by moderator), kinda easy if you know how to.
One thing that's in my mind that if we can turn one's computer on/off over the net, wouldn't it be a disaster then if one's can turn Fed's computer off.
One thing that's in my mind that if we can turn one's computer on/off over the net, wouldn't it be a disaster then if one's can turn Fed's computer off.
Hmm. I don't think that the ability to turn on or off the Fed's (or anyone else's) computers is as big a problem as what it implies. You cannot use wake-on-lan directly to turn on a computer from the internet, since it works using broadcast messages; rather you have to connect through SSH or other service to a computer on the local network of the computer to turn on, and execute the WoL from there. Being able to turn on their computers essentially means you've already hacked into their network.
Shutdown is different from WoL in that it's dependent on the OS and not the BIOS. In Linux we use the shutdown command which presumably accesses some kernel API to shutdown the computer; needless to say the user needs to be root (or sitting physically at the computer to send a CTRL-ALT-DEL). Same goes for Windows, except they also make use of something called a RPC (Remote Procedure Call), which allows for the system to be shutdown remotely. While this does use IP and so theoretically could be sent over the internet, it does require the username and password of a system admin. So once again, being able to do this means you already have access to their network.
Given that they have access to the network already, would you be more worried that some agents computer is being turned on/off, or the potential for data theft, etc. from said computer?
As a funny aside, I remember being in the computer lab once at my old university. Some kid realized he could connect to the schools server using putty (Windows SSH client). He thought he'd be a bad ass and restart the schools server by connecting through SSH and pressing CTRL-ALT-DEL. All he did was lose the paper he'd spent all day working on that off course he never thought to save.
Same issue here, however, I've got a router powered by Linux on ARM.
I was able to compile a wol tool for the router and I can telnet in to the router from the internet and issue the command. Perhaps a similar solution would fit you.
Or, you can buy a embedded Linux system that takes up hardly any power (like those gumpack sized computers), ssh in to that, and run wol.
What router do you have?
where can I find more info on compiling a wol tool and telneting to the router?
-----
for gumpack use putty to ssh to it?
can you recommend WOL software {name or link} to install on the gumpack?
I had discussed WOL stuff till in the deepest manner, kinda easy if you know how to.
It is... Some time ago with my last computer & router I gave it a try just while playing around... my laptop connected through dial-up and desktop on dsl router.
It never failed, same isp but still different connections, bellsouth, but by all means wol over internet worked.
At least a year later since I switched to comcast and have a different router and very much am confident all my settings are correct.. I understand the port forwarding and broadcast ip, etc etc and can make this function over the LAN..
There are too many variables to consider besides something I read about arp cache config or how the packet may be dropped by default while in transit since it can be mistaken for an attack attempt by some routers.
So chiefly I would like to get very simple brief but direct links, software titles, pointers as to getting the previously mentioned gumstix setup to work since it can be nothing more then counterproductive to not persue a direct controllable solution. The main dilemma being I am so new to linux its not even funny... So if setting up a gumstix to be able to connect to it and make that send a local wol packet is simple please include some specifics so I can consider this issue resolved..
As I understand that WOL over the internet is possible if you have complete access on the target computer.
Saying that, take for an example; IRC programs that can collects data from client computer or even shutdown your Buddy's computer.
Here's a simple fundamentals reference to WOL phenomenon;
As I understand that WOL over the internet is possible if you have complete access on the target computer.
Saying that, take for an example; IRC programs that can collects data from client computer or even shutdown your Buddy's computer.
Here's a simple fundamentals reference to WOL phenomenon;
Its great you put all these links and whatnot but if you consider they address the routing issues of certain hardware out there, to solve the WOL over internet issues people are having I will describe for you the following circumstance which myself besides many others of particular router hardware may find themselves..
In particular just consider for a moment everyone is a WOL expert at that for a moment. Consider that one of us very peculiarly cannot wakeup over internet. Thus router log is viewed.. the UPD shows it arrives and is blocked when the port forward for the particular udp is unchecked/deactivated, very consistently, and conversely nothing on the log, thus passed through, when the port forward is active.
This individual later came to speaking to the router mfg of a couple of companies and found out that certain model routers will NOT under any circumstance forward a broadcast packet from the internet as a mfg built-in safeguard. FULLSTOP.
With that understood.. you have one of the following options.
1. buying a router to compile your own firmware code on it
2. get a gumstix and use a simple collection of tools and best practices to connect to it and from it send a WOL packet, as formerly mentioned
or
3. buy a router with the WOL functionality allready built into the router.. I heard of someone that mentioned they had a "bulldog" router and its firmware had it build it... besides others..
I hope you understand that clarification of the WOL process is not needed for those that have routers that don't take broadcast packets from the internet.
Namely it would be nice to see a full BUT VERY concise elaboration of those 3 options to bring this thread to its full maturity..
I did a couple searches to try and provide some SPECIFIC and concise steps involved to resolve this issue by either of the first 2 means since I don't intend to buy another router or deal with open source, hacked, nor custom unstable firmware ... and quite frankly like my router very much... and yes I haven't ran across a single post specific to connecting to a gumstix and making it send a WOL packet.
So in other words quite frankly there is no real need for another demistification of WOL if there is no magic to it to begin with.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.