![]() If your computer isn't running any service expecting traffic on port 9, then it's as good as closed. There is nothing insecure about ports themselves, it's all about the services which are listening for packets on those ports. However port forwarding is very insecure as the specified ports are always open. You want the static port forwarding rule to be always active. So if you want Wake-on-LAN or indeed any other service to work purely based on inbound requests, port-triggering is the completely wrong tool to use. There is no corresponding outbound traffic that would activate the port-triggering rule (after all the computer is asleep and cannot produce any packets of its own), so the rule will never activate. It's not actually sharing the whole port all the time, it just keeps re-assigning it to whichever host "requested" it last (and possibly for a limited time).īut no such thing happens when you're trying to send a wake packet from the outside. That's how it is able to "share" the same port number between hosts, too. The router temporarily opens the incoming port or ports that you specify in your rule, and forwards that incoming traffic to that destination. For outbound traffic from that port, the router saves the IP address of the computer that sent the traffic. With port triggering, the router monitors traffic to the Internet from an outbound "trigger" port that you specify. (For example, when your computer connects to IRC server X:6697, that activates a rule forwarding port 113 to the same computer.) Take a look at, for example, how Netgear describes it: 'Port Triggering' is named that way because it lets you create dynamic rules where some specific activity – some type of outgoing traffic – causes the router to add a temporary rule for incoming traffic. I know Remote Desktop Management feature can be used with Port Triggering, but waking devices seems to be alluding me. So if someone can help me it would be appreciated. UDP is also what I've set it for not TCP) At this point I'm not sure if I'm understanding how the Wake on WAN and Wake on LAN packets work. ![]() So ports 7 and ports 9 are not being triggered or forwarded (I've tried setting it for port 7 and when that didn't work changed the rule to use port 9. I've set up a rule for Port Triggering, removed all my port forwarding rules and I haven't gotten Wake on WAN to work at all while I'm at home using the method I described above to get a 100% success rate for Wake on WAN.Īlso Wake on LAN still works but I'm not even sure why it's working because I did a test after disabling port triggering. Also you can set a rule for a single port to be used by multiple devices unlike port forwarding where lets say port 2 will always be tied to a single IP address (device). ![]() I heard that with Port Triggering, when the port isn't used frequently the port is closed, but since it will save IP addresses of a device automatically when the ports are active and being used by a device. Now I usually have everything set up with Port Forwarding, however port forwarding is very insecure as the specified ports are always open. I have WiFi turned off on my phone and switch to connect to mobile data I get a 100% success rate to wake the pc. I've gotten 100% successful Wake on LAN for this PC when I'm connected to my home network and partial success for Wake on WAN when I am like in another state using mobile data. By the way Remote Management is turned off in the modem's administrator dashboard/UI. (My cell service is not comcast/xfinity). I use my galaxy s9+ with Verizon service to wake up the PC. ![]() So I have an old windows 7 machine from 2013 I believe the motherboard is also a MSI MPower Z77 for those who want specs. ![]()
0 Comments
Leave a Reply. |