D-Link Co.,_______________________________________________________________________ FAQ
FAQ: 25
> ip ping a.b.c.d (where a.b.c.d is the remote gateway IP
address)
(after the call stops)
> sys trcl disp
You will see the tracelog as well as the packet traces.
7.c
Can’t PING to or from the LAN on the Router
First check your physical LAN connection by checking the LAN LED
on the front panel; this should be on. Also check the other end
of this connection (to the hub).
Go to menu 3.2 and check that the Router is on the same
network/subnet as the other stations on the network.
Go to CI (menu 24.8)
> ip route stat
> ip ping w.x.y.z (where w.x.y.z is another station on the
network)
> ip route stat
By examining the routing table before and after the PING, you
should note that the ‘Use’ field for that route should have been
incremented by 3.
If not, then use
> ip route errcnt disp
to determine the cause.
If it has been incremented, then try
> lan cnt disp
to check if there is a hardware problem.
Finally, check for any filter sets that may have been implemented
that could prevent the PING packet from going through.
7.d
Workstations on the backbone LAN cannot access the remote node
Check that the Router has been connected to that remote node; use
menu 24.5 ‘Manual Call’. Try to PING from the Router to the
remote node.
Verify the LAN connection by trying to PING from the workstation
to the Router or vice versa.
If you want the Router to make a call every time the workstation
tries to send a packet to that remote node, check that the Call
Direction field is set to ‘Outgoing’ in menu 11.
Try to PING from the workstation to the remote node. This should
trigger the outcall.
If it does not trigger the outcall, check to see if there are any
filters blocking the packet.
Go to CI (menu 24.8) and check the routing table
