D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: timbradley on May 25, 2009, 02:37:59 AM

Title: Unexplained port blocking
Post by: timbradley on May 25, 2009, 02:37:59 AM

Hi All,

I have a DLink DIR-655 (Hardware v. A2, Firmware v. 1.21) hooked up to a Siemens SpeedStream 4200 (Optus Supplied) and am agonising over how to get into my webserver remotely.

The requests are making it to the router (the logs show them being blocked, but gives no reason), so it isn't the evil optus ppl doing it.

The modem is in bridge mode and the router is handling the negotiation.

I can get to the server if I specify it's IP in the DMZ. This is useable, but I really don't want to leave it hanging out there!

I have tried forwarding ports, and setting virtual server entries. Within the virtual server entries, I have also tried using alternative public ports (ie. public 9955 -> private 80).

I fail to see why using a DMZ entry will work when port forwarding will not!

Any help will be greatly appreciated...I'm tearing my hair out over this one!!!

Cheers

Tim Bradley

Title: Re: Unexplained port blocking
Post by: timbradley on May 25, 2009, 04:57:07 PM

OK - solved...Incredibly stupid on my behalf also - hadn't realised the checkboxes activated the forwards.

Still have a little problem.  Trying to get Wake on LAN to work over the net.  I know the 655 with the current firmware won't forward to x.x.x.255, so changed my subnet mask to 255.255.255.128 to alleviate that issue.

I have a packet sniffer on the PC I particularly want to wake up, but no sign of the magic packet reaching it when sent.

Any thoughts??

Title: Re: Unexplained port blocking
Post by: Demonized on May 26, 2009, 12:26:56 AM

Quote from: timbradley on May 25, 2009, 04:57:07 PM

OK - solved...Incredibly stupid on my behalf also - hadn't realised the checkboxes activated the forwards.

Still have a little problem.  Trying to get Wake on LAN to work over the net.  I know the 655 with the current firmware won't forward to x.x.x.255, so changed my subnet mask to 255.255.255.128 to alleviate that issue.

I have a packet sniffer on the PC I particularly want to wake up, but no sign of the magic packet reaching it when sent.

Any thoughts??

Any reasoning behind setting the subnet to 255.255.255.128 to alleviate the issue?

Title: Re: Unexplained port blocking
Post by: timbradley on May 26, 2009, 02:44:04 AM

Quote from: Demonized on May 26, 2009, 12:26:56 AM

Any reasoning behind setting the subnet to 255.255.255.128 to alleviate the issue?

Yep! Makes the Broadcast address 192.168.0.127, hence fooling the router out of blocking broadcasts :)