Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In my home network, I connect to the Internet through a router ( I also have another router (,, this one using OpenWRT, configured as a wireless client. One of my computers is connected to that router via an Ethernet cable, which is connected to my main router wirelessly.

Due to being connected through the OpenWRT router, my computer ( is on a different subnet. I have a static route set up on my main router for this. The destination network is set as, the subnet mask is, and the gateway is set as This computer can access both the Internet and other computers on the network without trouble.

Anyway, from a computer in subnet 192.168.1.x, I can ping and (both IP addresses of my OpenWRT router) just fine. However, when I try to ping, I get the following message:

PING ( 56(84) bytes of data.
From icmp_seq=1 Destination Port Unreachable

Clearly it's using the static route I assigned. The problem seems to be that the OpenWRT router doesn't know how to route packets to, which is strange because that IP is directly connected to that router.

What am I doing wrong?

share|improve this question

migrated from Apr 24 '13 at 12:30

This question came from our site for system and network administrators.

Is IP forwarding enabled on that router? – David Schwartz Apr 23 '13 at 18:43
I'm experiencing the same issue, two subnets and openwrt. Do you find out a solution? – jayatubi Jun 12 at 3:56

1 year late but your problem might be the OpenWRT firewall which seems to forbid ip forwarding on the LAN interface when the source&destination subnets aren't the same. retry pinging after this one : /etc/init.d/firewall stop

if it works, then u gonna have fun with the rules !

share|improve this answer
Should I create two zones with different lan interface and then add a new forward rule for them? Just like the default lan => wan? – jayatubi Jun 12 at 3:59

Might not be a solution, but did you check if your gateway is configured correctly? As the gateway is connected to both the systems, ping might be working just fine, but did you check if the gateway does the routing from 192.168.1.x to 192.168.2.x?

Do check the request and responses using Wireshark on the gateway.

share|improve this answer
I can SSH from 192.168.1.x to, but not from 192.168.1.x to Ping works in both cases though. I reconfigured the firewall to allow forwarding in all cases, but pinging from 192.168.1.x still doesn't work. It doesn't give me the destination port unreachable error anymore though. I checked with tcpdump and it is receiving the ping request for, but for whatever reason isn't responding. normally does respond to ping though, as I can ping it from – flarn2006 Apr 23 '13 at 20:25

Similar error fixed by opening good old dos window (search for "cmd"), and typing these 3 separate lines:

share|improve this answer
It would help to explain how these two commands solve the problem. – David Richerby May 30 '15 at 8:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .