![]() Ip forward-protocol udp 7 or ip forward-protocol udp 9 ? (I tried 7, that didn't work.) So on the router, what I am missing, is either a (or both) On gi0/1.1, where the server/workstation is that sends the packet (ip addr 192.168.1.110) itended for waking up a machine with IP 192.168.2.117, the configuration is this: On the router, this is what the configuration for the interface with 192.168.2.0 looks like: Ip directed-broadcast I have 'ip directed-broadcast' on all interfaces that have hosts in the corresponding vlan that boot using dhcp (dhcp running on the 2900 router) From what I read some hardware uses 7/echo and some uses 9/discard? So shouldn't I use both, just in case? I alway thought that either 7 or 9 was used (I thought it was a broadcast though, so it wouldn't matter). Yes, 192.168.2.0 is the subnet for vlan2 (I am organizing stuff in separate subnets/vlans and associate .0 with vlan x, easier to keep track of that way.)) The next ste is that, of course, I would like to send a wake up packet from a different vlan to the same machine I want to wake up.Īre there some udp/broadcast settings that by default come with vlan1, but not necessarilly with other vlans? So what else is needed to be able to send a a WOL packet to a machine where the sender and receiver of the WOL packet are on a port configure like above. I moved the client the machine I want to wake up, to vlan 2, it being a native vlan on that port:Īnother machine on a port with the same settings as above, should be able to wake the machine up, since it is in the same vlan(s) correct? (Of course it doesn't else I'd wouldn't be writing this ost). I assume that just works, because the machines are both on vlan 1, the native untagged default vlan. I was able to remotely wake up a computer (using RHEL/Centos ether-wake). Therefor we built a custom action (of course your switches\routers need to handle the WOL-broadcast to push it to the target-subnet).I used to have a machine on a port with the "default settings" and also a work station, on a different (both 2960s) switch but also connected to a default port. for WOL to other VLANs WOL.exe needs the actual target subnet. You may also want to try setting up a custom action as suggested by VVB: Examples of how your proposed feature would be used in your environment are welcome. ![]() Send in an email to Outline the functionality you'd like to see within Lansweeper, the more information the better.However, for the most rapid response and most accurate tracking we recommend submitting feature requests as follows: ![]() The discussion this spawns can also be useful. We track all features submitted on the forum and will continue to do so. If you want this ability to be added, you may post to the Lansweeper wishlist forum or (the preferred way) send a suggestion email to the support team. I think Lansweeper does not support those options right now. In my case, there is no need to set up compatibility mode for wol.exe on Windows 10 Pro 20H2 to use WOL in Lansweeper. Where in LS do I setup "subnet" and "password" for WOL.exe ? When clicking link in LS asset page, no packet in WSĪfter changing WOL.exe to compatibiliti mode Windows8 (for all users), LS link also generates packets in WS When running WOL.exe I can see packet in WS Run wireshark -> start capture -> for filter enter "wol"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |