Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[doug09]

Hi

I can't seem to get port forwarding to work on the DIR-655. Here's my setup:

Netgear WG824GT ADSL modem/router connected to the internet - private IP address = 192.168.11.1
DLink DIR 655 - public IP address 192.168.11.2, private IP address 192.168.111.1
Laptop - static IP address 192.168.111.10

I have successfully setup the netgear to forward port 48761 to 192.168.11.2. I have also tried to setup the DLink router to forward port 48761 to my laptop (192.168.111.10). But in the router logs I see:

"[INFO]   Wed Jul 15 00:11:46 2009   Blocked incoming TCP packet from 83.91.127.50:61369 to 192.168.11.2:48761 as PSH:ACK received but there is no active connection"

What does this mean?

I read it as there is no connection on that subnet with the address 192.168.11.2. Well that's probably because it's the router's public address.... I'm confused!

I have tried using both port forwarding and virtual server. Creating my own custom inbound filter and disabling SPI, but I still see numerous entries in the log as above.

Can someone help me please

Thanks

Andy

[Demonized]

tell us how your subnet config looks like

[doug09]

Router IP Address: 192.168.111.1

Subnet Mask: 255.255.255.0

[Demonized]

Try setting it to 255.255.0.0.

[doug09]

Nah setting the subnet address to 255.255.0.0 didn't work, got the following message:

[CRIT]   Wed Jul 15 00:41:23 2009   The addressing of the Internet side learnt thru DHCP conflicts with the addressing selected for the LAN side. Internet communications will be disabled until you have changed the LAN side addressing to resolve the problem.

Any other suggestions?

[Demonized]

You're connected through a LAn to the internet (192.168.11.1)?

[doug09]

You're connected through a LAn to the internet (192.168.11.1)?

Yes

It appears to me that the router is rejecting the packet based on the destination address not being on its subnet before checking the port against the forwarding rules. Could this be the case?

[jason1722x]

Hi

I can't seem to get port forwarding to work on the DIR-655. Here's my setup:

Netgear WG824GT ADSL modem/router connected to the internet - private IP address = 192.168.11.1
DLink DIR 655 - public IP address 192.168.11.2, private IP address 192.168.111.1
Laptop - static IP address 192.168.111.10

I have successfully setup the netgear to forward port 48761 to 192.168.11.2. I have also tried to setup the DLink router to forward port 48761 to my laptop (192.168.111.10). But in the router logs I see:

"[INFO]   Wed Jul 15 00:11:46 2009   Blocked incoming TCP packet from 83.91.127.50:61369 to 192.168.11.2:48761 as PSH:ACK received but there is no active connection"

What does this mean?

I read it as there is no connection on that subnet with the address 192.168.11.2. Well that's probably because it's the router's public address.... I'm confused!

I have tried using both port forwarding and virtual server. Creating my own custom inbound filter and disabling SPI, but I still see numerous entries in the log as above.

Can someone help me please

Thanks

Andy

Dose the Netgear WG824GT control the DHCP? If so is DHCP disabled on the Dir 655? You should not have a Lan Address connected (well trying to connect) to the internet. What is your Default Gateway address?
If the Netgear is a bridge then the Dir655 should grab the public (ISP) address.
Example:
Your D-Link router uses 192.168.0.1 for the IP address. You've assigned a computer that you want to designate as a Web server with a static IP address of 192.168.0.3. You've assigned another computer that you want to designate as an FTP server with a static IP address of 192.168.0.4. Therefore the starting IP address for your DHCP IP address range needs to be 192.168.0.5 or greater.
Example:
Suppose you configure the DHCP Server to manage addresses From 192.168.0.100 To 192.168.0.199. This means that 192.168.0.3 to 192.168.0.99 and 192.168.0.200 to 192.168.0.254 are NOT managed by the DHCP Server. Computers or devices that use addresses from these ranges are to be manually configured. Suppose you have a web server computer that has a manually configured address of 192.168.0.100. Because this falls within the "managed range" be sure to create a reservation for this address and match it to the relevant computer.

I'd say your outside of the scope of DHCP.

[doug09]

Right, I've tried disabling DHCP on the Netgear router and assigning it to address = 192.168.11.1. I then set the DLink router to use 192.168.11.2 with DHCP enabled using a pool of ip addresses from 192.168.11.10-100.

I can then connect wirelessly and get allocated 192.168.11.10 by the DLink. I can navigate to the DLinks web config on 192.168.11.2 but can't see Netgear's web config unless I connect the router via a ports 1-4 on the back of the router as opposed to the internet port.

Despite this I still can't connect to the web. I think I need to specify Netgear as default gateway on 192.168.11.1 so that addresses not found on the subnet are routed out to the web.

Is this right and how can I do this?

Thanks

[doug09]

FIXED - I had to disable DHCP on the DLink instead of the Netgear.... Doh! I was initially worried that as the DLink provided the wireless connection it had to also allocate IP addresses, but this is obviously not the case.

Works a treat now!

Thanks for the suggestions

[jason1722x]

FIXED - I had to disable DHCP on the DLink instead of the Netgear.... Doh! I was initially worried that as the DLink provided the wireless connection it had to also allocate IP addresses, but this is obviously not the case.

Works a treat now!

Thanks for the suggestions

Prolly many different ways to do that configuration, you just have to find what works for you.