I have a server on my local network which I cannot reach when connecting wirelessly. However, it's working fine when connecting directly via the network device the server is connected to.

When connecting wirelessly, I'm not connecting to the ASUS router, but a access point on that is connected to the ASUS router.

ASUS Router (

-> LAN1: Access point (

-> LAN2: ZyWALL ( -> Server (

Connecting directly to the ZyWALL through one of the LAN ports on it, the server is reached. When connecting via WIFI that goes via the access point it doesnt work.

The ASUS router has a configured static route to the server that looks like this:


Net Mask:


Metric: 2

Interface: LAN

When I ping the server while using wireless connectivity on my laptop i get the following results: Now when I ping the server i get the following result:

PING ( 56 data bytes
Request timeout for icmp_seq 0
92 bytes from router.asus.com ( Redirect Host(New addr:
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 0054 129f   0 0000  3f  01 f5b5 

The ping result looks like the server ip is attempted to be resolved by the access point, however there isn't a static route for that device telling that the server should be routed via the ZyWALL.

What am I doing wrong here?

  • Please verify the ping command output. It was mangled in your question. I tried to fix it, but may have gotten it wrong. Please use the Code Block feature when providing console output and text file contents of any kind (configuration, log, ...). – Daniel B Aug 11 '17 at 8:15
  • OK. Please clarify your network hierarchy. Especially what network segments are involved. Do you have two segments (both connected to “ASUS Router”) that have the network? – Daniel B Aug 11 '17 at 8:19
  • Sorry my bad. Yes both the AP and the ZyWALL is connected to each own LAN port on the ASUS router. – arqe3 Aug 11 '17 at 8:27

The route is correct. (Redirects are your router's way of saying "you can reach that gateway directly, without going through me" – but usually they are completely optional.)

Use tcpdump on the server to check whether ping requests actually arrive:

tcpdump -e -n -i eth0 icmp

It's possible that your server does not have a route back to the LAN, and therefore cannot reply back. It might need a similar static route via ZyWALL.

Though, if you can, also check whether the ZyWALL itself is receiving (and forwarding) the requests. (Depending on firmware, it might have Telnet → shtcpdump available.)

(Note that your Wi-Fi access point's address is usually completely irrelevant. The AP – well, if it's actually a AP – acts no different from an Ethernet switch, working at a layer below IP.)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.