• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Weird tracert from separate devices

V

VeeDubbs

Limp Gawd
Joined
Dec 9, 2005
Messages
398
Hi All -

Having some weird things happen that I can't figure out. Hopefully I can explain. I have three devices: my PC, an AP and my wireless controller.

  • PC - 10.200.0.99/16
  • AP - 10.5.16.11/24
  • Controller - 10.5.1.32/24

I'm having trouble getting my AP to adopt over L3. From my PC with a tracert I get:

Code: 
C:\Users\veedubbs>tracert 10.5.16.11

Tracing route to 10.5.16.11 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  10.200.0.1
  2     *        *        *     Request timed out.
  3     3 ms     3 ms     3 ms  10.255.70.2
  4     2 ms     4 ms    10 ms  10.5.16.11

Trace complete.

From my controller I get:

Code: 
VX9000-Primary#traceroute 10.5.16.11
traceroute to 10.5.16.11 (10.5.16.11), 30 hops max, 46 byte packets
 1  *  *  *
 2  *  *  *
 3  10.255.70.2 (10.255.70.2)  3.814 ms  2.627 ms  3.049 ms
 4  *  *  *

...

29  *  *  *
30  *  *  *

As you can see -- they both know to take the hop to 10.255.70.2, but the controller can't find the device beyond that hop.

I am also able to ping from my PC, but NOT from the controller.

The device is clearly on the network as I can ping it and see it in the ARP table:

Code: 
Johnson-1# show arp vlan 5

 IP ARP table - VLAN 5

  IP Address       MAC Address       Type    Port
  ---------------  ----------------- ------- ----
  10.5.16.11       00193b-82a98e     dynamic G2

It also seems like the routing is not problematic as they both take the appropriate hop. I feel like I am missing something terribly simple.

Hopefully I've given somewhat of a clear picture. Ideas?
 
I know you say it's not a routing problem, but your ICMP traffic might be getting to the end device, but echoes are not returning. Verify your routing.
 
Also ensure a firewall isn't blocking ICMP
 
* dont mean much any more, a lot of devices rate limit ICMP packets especially ISP's side of things.

do a tcp trace to get slightly better results.
 
You must log in or register to reply here.
Back
Top