Date: Mon, 18 Dec 1995 09:06:23 -0600 (CST) From: Mark Tinguely <tinguely@plains.nodak.edu> To: partha@ipsilon.com, questions@FreeBSD.ORG Subject: Re: location for mtest utilities Message-ID: <199512181506.JAA21043@plains.nodak.edu>
next in thread | raw e-mail | index | archive | help
I am not familiar with mtest, but you might want to use the appliacations: mrinfo tells the information and status of the tunnels and physical interfaces. to use (as root): mrinfo YOUR.MBONE.ROUTER.DOMAIN and it responds somthing like: bash# mrinfo localhost 127.0.0.1 (localhost) [version 3.8,prune,genid,mtrace]: 134.129.125.191 -> 0.0.0.0 (local) [1/1/querier/leaf] 134.129.48.1 -> 0.0.0.0 (local) [1/1/querier/leaf] 134.129.125.191 -> 111.11.111.11 (our.provider.net) [1/64/tunnel] 134.129.125.191 -> 128.128.128.128 (made-up-host.somewher.com) [1/48/down] notice we have two interfaces on the mrouter machine and it serves both interfaces seperately. the tunnel to "made-up-host.somewher.com" is not connected, but the other tunnel to "our.provider.net" is connected. if your tunnel to your provider is working, then query the provider to see if the problem is upstream to you. you can look in /var/log/messages to see if there were any reason your mrouted did not start. you also start mrouted with a debug option greater than 0 to get more information about your tunnel. I also watch the network to see if multicast session broadcast are making it from the mrouted to the net by running as root: tcpdump net 224 The application map-mbone is a nice application to run, but it won't tell why your local tunnel is not working.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512181506.JAA21043>