Foxtel V6510-1FXAUS

[dlscape]

Foxtel have recently upgraded me to a V6510-1FXAUS VDSL router. I've been trying to get it to let me use Wake On Lan but so far I've run into a brick wall.

I've tried talking to Foxtel but the tech guy clearly had no idea what WOL was. After he told me that he didn't have the information I needed, and I berated him for not being able to support the hardware they sell to their customers, he hung up on me 🙂

Soooo - here I am, looking for help. I have a dyndns pro account all set up correctly. I have ports 7 and 9 open on the router. I have the computer setup to Wake On Lan in the BIOS and Device Manager. For some reason though I can't get any computers on my home network (mac or windows) to actually wake up??

Does the V6510-1FXAUS actually support WOL? Or do I need to swap it out for a different router.

Thanks for any assistance,

James.

[antinode]

> [...] I have ports 7 and 9 open on the router.

   Actual copy+paste from the port-forwarding rules report (or whatever)
would be more informative/persuasive than that interpretation.

> [...] For some reason though I can't get any computers on my home
> network (mac or windows) to actually wake up??

   When you do what, exactly?  Can you do it from within the LAN?

   My Wake-on-LAN expertise is poor, but as I understand it, WoL
involves a broadcast message, which does not lend itself to port
forwarding.  Or are you specifying a broadcast address as the
destination?  I'd guess that you'd have a better chance with a single
(non-broadcast) destination than with whatever else you might have
tried.

> Does the V6510-1FXAUS actually support WOL?

   Depending on what "actually support" means to you, I don't know, but
WoL is generally a LAN-only thing, not something which gets routed.

      https://en.wikipedia.org/wiki/Wake-on-LAN

[dlscape]

Thanks for replying. I'll try answering you questions below;

---

antinode wrote:

> [...] I have ports 7 and 9 open on the router.

   Actual copy+paste from the port-forwarding rules report (or whatever)
would be more informative/persuasive than that interpretation.

>>I've gone throught the dyndns troubleshooting pages and one of those tests to see what ports you have open. It confirmed the the firewall incoming rules I'd created for both tcp and udp had opened ports 7 and 9.

> [...] For some reason though I can't get any computers on my home
> network (mac or windows) to actually wake up??

   When you do what, exactly?  Can you do it from within the LAN?

   My Wake-on-LAN expertise is poor, but as I understand it, WoL
involves a broadcast message, which does not lend itself to port
forwarding.  Or are you specifying a broadcast address as the
destination?  I'd guess that you'd have a better chance with a single
(non-broadcast) destination than with whatever else you might have
tried.

>>I can remote desktop into any of my conputers from outside my network using JumpDesktop. From within the home network I can easily RDP into the Windows machines using Microsoft Remote Desktop on my mac by just typing in the IP address. If I put the machines to sleep though no matter what I do, non of them will respond to WOL requests sent from my iphone running the iNet WOL app (although they used to a few years ago when I was using a differnet router). Doesn't matter if I try waking them locally or via dyndns from an external network 😞 

> Does the V6510-1FXAUS actually support WOL?

   Depending on what "actually support" means to you, I don't know, but
WoL is generally a LAN-only thing, not something which gets routed.

      https://en.wikipedia.org/wiki/Wake-on-LAN

---

>>I ask this as I'm baffled as to why nothing is working. I wouldn't put it past Foxtel to have the router they supply be lacking "non essential" feature to make it cheaper.

I'm staring to think it might be easier to build a remote controlled robot finger to simply press the "on" button when I dial in 🙂

James

[dlscape]

UPDATE

I've managed to get the windows 10 computer to wake up using iNetWOL from my iphone when using the home network 🙂

However. I still have had no luck getting it to work from outside my network. Even if I know what IP address my internet provider has dynamically allocated me, when I send the magic packet to the ip address and target the mac address of the windows 10 PC I get zip 😞  I'm guessing it's getting blocked by the router for some reason. Even thought the ports 7 and 9 are defintily open. Is there something else I need to open or allow on the V6510-1FXAUS?

Regards

James.

[dlscape]

The latest version - V2.2 release around a month ago.

I've also tried accessing my router using my dyndns hostname and again, from inside my network it goes straight to the router login, from outside it just times out. Even though the hostname is setup correctly and has the current IP address I've been assigned. It just looks like the router is blocking any attempt to access it from the internet 😞

James

[antinode]

> >>I've gone throught the dyndns troubleshooting pages and one of those
> tests to see what ports you have open. It confirmed the the firewall
> incoming rules I'd created for both tcp and udp had opened ports 7 and
> 9.

   Doesn't answer the question.

>    Actual copy+paste from the port-forwarding rules report (or whatever)
> would be more informative/persuasive than that interpretation.

   Still true.

   In my experience, people who talk about ports being "closed" or
"open" often don't understand the problem.  A port looks "closed" when
there's no server program (or device) listening at that port.  All the
port forwarding in the world won't help you if, at the end of the line,
no one is listening at that port number.

   In this case, with what's normally a broadcast message, I (still)
have no idea what you're asking the router to do with it.

> I've managed to get the windows 10 computer to wake up using iNetWOL
> from my iphone when using the home network [...]

   That's a start.  Note that the router should have approximately
nothing to do with LAN-LAN message traffic, only with WAN-LAN traffic.

> [...] I'm guessing it's getting blocked by the router for some reason.

   Knowing nothing (still) about your port-forwarding rule(s), I can
only try to imagine what the cause might be, because, based on no useful
information, I can't guess what you've asked the router to do.

> [...] Is there something else I need to open or allow on the
> V6510-1FXAUS?

   I can't tell what "else" might be needed, because, with my weak
psychic powers, I can't tell what you've done so far.

> [...] It just looks like the router is blocking any attempt to access
> it from the internet

   I don't know that it's a doomed effort, but it might be worth noting
that the feature is called Wake-on-_LAN_ (not "Wake-from-Anywhere) for a
reason.

[dlscape]

Thanks for the input everyone. I have finally managed to get it working. My fault as I wasn't setting up the portforwarding correctly.

Much appreciated 🙂

[antinode]

> [...] I wasn't setting up the portforwarding correctly.

   It's nice that you got something working.

   In the future, someone searching this forum for information on
Wake-on-LAN may find this thread, and will learn what from it?  That you
did something wrong, then you did something right, with nary a clue as
to what either was?

> >    Actual copy+paste from the port-forwarding rules report (or whatever)
> > would be more informative/persuasive than that interpretation.
>
>    Still true.

   Still true.