[c-nsp] Something like MTR, but forced path

[Tuc at T-B-O-H.NET]

> 
> Tuc at T-B-O-H.NET wrote:
> 
> > Problem we have is a small wireless network is basically flat, not
> > networked. There are 10 pieces of equipment between 2 machines. However,
> > they are both on the same subnet, so it just looks like it only needs to 
> > hop once. Instead, it goes from the router, to a client antenna (IP'd),
> > to an Access Point (IP'd), to a switch (IP'd), to a backhaul (IP'd), to
> > another backhaul(IP'd)... You get the jist. I basically want to force the
> > system to believe my path, not what routed networking tells it.
> 
> traceroute shows a layer 3 path.  Your client antenna, access point etc. are 
> bridging - a layer 2 activity.
> 
> If you want to 'force' extra hops, you need to have each device decrement the 
> TTL of forwarded IP datagrams and correctly send ICMP unreachables.
> 
> There is some Layer 2 traceroute functionality built in to Cisco kit, useful to 
> trace paths through a network that may change due to Spanning Tree - but I have 
> to ask, what are you trying to achieve here?
> 
Hi,

	Sorry, I think I'm being seriously misunderstood. 

	Yes, I understand l3/l2.

	I'm not looking for something that will "autodetect the path" via any
sort of methods. I'm basically looking for something I can run on Unix and
give me a curses view of IPs I give it to ping at the same time. I was looking
on this list only because people here tend to either know or use the "kewl tools".
I found something that sort of does what I want, fping, but it doesn't have the
display part. Curses MTR bolds the lettering when it has a ping loss which I want
to catch my eye.

	As an FYI, the problem I have is I'm having connection losses between my
site and the wireless WISP's gateway. I think the packet is getting to the
backhaul link at the site here, but not to the other end of the backhaul here.
I want to run a set of pings basically that are :

1 - My router
2 - My antenna
3 - His AP at SiteC
4 - His switch at SiteC
5 - His BH at SiteC
6 - His BH at SiteB2C
7 - His switch at SiteB
8 - His BH at SiteB2A
9 - His BH at SiteA2B
10- His switch at SiteA
11- His router at SiteA

	I want something formalized since sending pings that just show
a loss somewhere in the middle don't mean anything.

		Thanks, Tuc