Japsser
September 13th, 2010, 10:36 AM
Hi,
I have a router that doesn't seem to support port forwarding to my complete home network using 192.168.1.255, I can only specify 1 ip. Am I missing something here or is there really no way around this.
Anyways, I figured I could maybe fix it changing settings on my ubuntu server. I started with specifying a static ip (192.168.1.8 ) , yet nothing changed.
Using wakeonlan -i 192.168.1.8 #MAC# won't boot the system.
this however; wakeonlan -i 192.168.1.255 #MAC# works perfectly.
Any other ideas that might be worth giving a shot?
Edit:
I have tried something similar like BkkBonanza suggested, I checked the source code of the router's port forwarding page and did this:
I set the netmask to 255.255.255.128
afterwards I executed javascript in the adress bar to make the port forwarding script think my netmask was still 255.255.255.0. Resulting in an accepted forward to the network broadcast adress 192.168.1.127.
http://i56.tinypic.com/2lvk17r.png
It's obviously still not working, so when I try
wakeonlan -i *MY IP* -p 44444 #MAC#
the server won't boot.
I tried a remote WOL website too, and I found this in my router's security logs
09/16/2010 16:08:41 **Probable ASCEND Probe** 208.77.98.204, 42402->> *MY IP*, 9 (from PPPoE1 Inbound)
09/16/2010 16:08:41 **UDP Loop** 208.77.98.204, 42402->> *MY IP*, 7 (from PPPoE1 Inbound)
09/16/2010 16:08:41 **UDP Loop** 208.77.98.204, 42402->> 192.168.1.127, 7 (from PPPoE1 Inbound)
I haven't got the slightest idea what they mean though.
I have a router that doesn't seem to support port forwarding to my complete home network using 192.168.1.255, I can only specify 1 ip. Am I missing something here or is there really no way around this.
Anyways, I figured I could maybe fix it changing settings on my ubuntu server. I started with specifying a static ip (192.168.1.8 ) , yet nothing changed.
Using wakeonlan -i 192.168.1.8 #MAC# won't boot the system.
this however; wakeonlan -i 192.168.1.255 #MAC# works perfectly.
Any other ideas that might be worth giving a shot?
Edit:
I have tried something similar like BkkBonanza suggested, I checked the source code of the router's port forwarding page and did this:
I set the netmask to 255.255.255.128
afterwards I executed javascript in the adress bar to make the port forwarding script think my netmask was still 255.255.255.0. Resulting in an accepted forward to the network broadcast adress 192.168.1.127.
http://i56.tinypic.com/2lvk17r.png
It's obviously still not working, so when I try
wakeonlan -i *MY IP* -p 44444 #MAC#
the server won't boot.
I tried a remote WOL website too, and I found this in my router's security logs
09/16/2010 16:08:41 **Probable ASCEND Probe** 208.77.98.204, 42402->> *MY IP*, 9 (from PPPoE1 Inbound)
09/16/2010 16:08:41 **UDP Loop** 208.77.98.204, 42402->> *MY IP*, 7 (from PPPoE1 Inbound)
09/16/2010 16:08:41 **UDP Loop** 208.77.98.204, 42402->> 192.168.1.127, 7 (from PPPoE1 Inbound)
I haven't got the slightest idea what they mean though.