Print

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

[areel]

Hi

I have read the following thread

http://forums.dlink.com/index.php?topic=1888.0

and I can confirm that I have switched off SPI and set the NAT Endpoints to independent.
But I am still not able to ping my Global IP either via System Check web page or ping command.

A3 and latest 1.32 beta 2009/07/01

Regards

Aidan

[lizzi555]

Advanced/Advanced Network -> Enable WAN Ping Respond is enabled.

It is working here with 1.32b03 and Rev A2.

Router is connected to a modem only device or is your modem capable of own firewall/ NAT settings ?

[areel]

Hi

Thanks for the reply.

I had this setting set as well.

I am connected to a satellite router which I have been assured has all ports forwarded.

If I disconnect the router and plug my laptop direct then people external to my network can ping my Global IP. I cann't ping from the command line and cann't use the D-655 system check since it is now offline.

If I plug the router back in then people external can no longer ping the Global IP. I can not ping from the command line, same as before, but I can use the system check and it times out as in the other thread.

I have been told by the ISP helpdesk that I need to correct/set up a loopback on my wireless router.
Any advice on how to set up the loopback so I can ping the global IP from the command line (csh terminal on OSX 10.5.6) would also be appreciated.

Global IP -- 192.168.1.2 -- 192.168.1.1-- 192.168.0.1

Regards

Aidan

[Lycan]

Your numbers don't make any sense.
Please be more specific as to whats what.

[areel]

Your numbers don't make any sense.
Please be more specific as to whats what.

The Global IP is the IP given to me by my ISP, this is like google's public ip or msdn's public ip, I didn't want to make mine trollable so I just said Global IP, perhaps Public IP would have been more understandable.

192.168.1.2 and 192.168.1.1  are the WAN IP and Gateway (respectively), as displayed in Device Information.

192.168.0.1 is the LAN IP address, also displayed in Device Information.

So any artifact on the local network will have an IP of 192.168.0.XXX.

The diagram was trying to display the relationship between the various IP interfaces, starting with the Global IP down to the LAN IP.

So, I have a Satelllite Router with an external public IP (www.xxx.yyy.zzz), when I connect my DIR-655 router or MacBookPro to the Sat Router, it is given the internal IP of 192.168.1.2 with a gateway of 192.168.1.1, in the case of my router, it also has a LAN address  of  192.168.0.1 assigned, meaning that when I connect my MacBookPro to the DIR-655 the MBP will get an IP of 192.168.0.XXX with a Gateway of 192.168.1.1

Regards

Aidan

[areel]

I have just noticed my IP is displayed anyway as part of a footer on this forum, so much for trying to be careful 

[davevt31]

I have just noticed my IP is displayed anyway as part of a footer on this forum, so much for trying to be careful 

That is only seen by you, the public members don't see the actual numbers.  The Mods may see it too, but like I said regular members don't see the actual address.  Just look at some of the other postings to see.

[lizzi555]

You have two NAT routers in line and it seems your satelite router does not return the answers to your Ping command correctly to the WAN Port of the DIR-655.
As a ping command is an ICMP echo request it maybe treated in another way as normal TCP packets.
So maybe even if your loopback with ping doesn't work, it's most likely to work with a FTP or HTTP server if you configure the portforwarding in both routers correctly.

Easiest way is to put the WAN IP of the DIR into DMZ of your satelite router as only rule there.
So all incoming traffic is forwarded to the DIR and this is the only router you have to configure for applications.

[areel]

Thanks for the explanation.

I don't have access to the Sat Router, that is under the ISP's control. But they are ensuring me that their Sat router has been set up to forward all incoming traffic to the DIR.

They have said that the issue is with the setup of the DIR since they can ping the Public IP successfully when the MacBookPro is attached but not when the DIR is attached.

I appreciate any other suggestions, I will build up a list over this weekend and discuss them with the ISP on Monday.

Maybe I should explain what I want to achieve:

I have a process that I wish to connect to whilst away from home.
That process listens on a port, say 1234 and runs on 192.168.0.X.
While at home I can happily connect using local LAN address of 192.168.0.X:1234.
While at work I want to be able to connect using w.x.y.z:1234

It is getting w.x.y.z:1234  to work, at the moment all requests time out.






 

[lizzi555]

It is getting w.x.y.z:1234  to work, at the moment all requests time out.

And you've already forwarded port "1234" as a Virtual Server in the Advanced menu of the DIR to the internal IP address of the machine running your "process" ?
The internal IP of this machine has to be a static IP. Either assigned by the DIR with DHCP reservation or manually assigned in the properties of your Internet protocol on the machine.

[areel]

Yes tried that and tried port forwarding as well.

At this stage I think I could recite the various DIR pages and options within as a poem 

I just tried again to be absolutely correct and it times out with

 

The requested site did not respond to a connection request and the browser has stopped waiting for a reply.

I am certain the machine IPs are correct etc.

Regards

Aidan

[Demonized]

And the modem? Does it allow all traffic?

[areel]

I am not sure what you mean.

If you are asking if the modem forwards all traffic to the DIR, as far as the ISP people are concerned, it does.
I quote from an email from my ISP help desk

... confirmation from our networks team that all traffic has been forwarded from the Global IP (w.x.y.z) to the local IP (192.168.1.2).

[davevt31]

If your Sat Router is handing the DDIR-655 a 192.168.1.2 address, I think you may be running into a Double Nat'ing situation.

[areel]

This issue of double natting was the reason that the ISP went for forwarding everything to the DIR.
Before forwarding everything, they were forwarding just the port I had asked for but it wasn't working. In those days I could ping the Global/Public IP but the forwarding wasn't happening. I suggested that they just forward everything (no NAT functionality on their router), I suggested this after spotting some comments about double natting in the DIR help text.

Now I have to confess that I am out of my comfort zone when we move into double natting etc.

Regards

Aidan