I feel like my last post was a little lacking in details so I thought I would give a full explanation of what I have done.
I had quagga installed with out qpimd but it looked like to me it had to be patched before it was made in order for it to work, so I did # apt-get remove quagga* * After which I started to follow the README directions on the following site: http://git.savannah.gnu.org/cgit/qpimd.git/tree/pimd/README?h=pim which were obtained from the qpmid site: http://nongnu.org/qpimd I downloaded the newest version of qpmid from here: http://download.savannah.gnu.org/releases/qpimd/ which after untarring looked like it was for Quagga 0.99.17 so I downloaded that version I followed the “BUILDING FROM QUAGGA TARBALL” instructions (after a failed attempt at the git instructions ) I followed the instructions as close as I could modifying version numbers as I went Changing the .13's to .17 1. Get the latest quagga tarball *# wget http://www.quagga.net/download/quagga-0.99.17.tar.gz* 2. Unpack the quagga tarball *# tar xzf quagga-0.99.17.tar.gz* 3. Apply qpimd patch into quagga source tree *# patch -p1 -d quagga-0.99.17 < pimd-0.162-quagga-0.99.17.patch* 4) Compile and install quagga*# cd quagga-0.99.17# ./configure --prefix=/usr/local/quagga --enable-pimd# make# sudo make install* note: I had to use sudo for the make install to work Then I got to the USAGE section. I copied the sample configurations over *# cp /usr/local/quagga/etc/zebra.conf.sample /usr/local/quagga/etc/zebra.conf* I then did the *# vi /usr/local/quagga/etc/zebra.conf* Although I wasn't sure what needed to be changed in it, and left it the default. I then ran zebra *# sudo /usr/local/quagga/sbin/zebra* Note: I had to use sudo again. I'm not sure if anything is expected to be displayed at this point but nothing was and it simply went to a new line on the terminal I copied the pimd.conf file over next *# cp /usr/local/quagga/etc/pimd.conf.sample /usr/local/quagga/etc/pimd.conf* and left it as default I then tried to run *# /usr/local/quagga/sbin/pimd* however this didn't work as I mentioned before I tried it at the - user level - with sudo - and as root (via sudo su) and none of them would work “ root@tom-laptop:/home/tom# sudo /usr/local/quagga/sbin/pimd 2011/08/18 14:34:38 PIM: Boot logging temporarily directed to stdout - begin 2011/08/18 14:34:38 PIM: Quagga 0.99.17 pimd 0.162 starting 2011/08/18 14:34:38 PIM: Boot logging temporarily directed to stdout - end 2011/08/18 14:34:38 PIM: Loading configuration - begin 2011/08/18 14:34:38 PIM: pim_if_add_vif: ifindex=0 < 1 on interface eth0 % Interface eth0 does not exist 2011/08/18 14:34:38 PIM: Loading configuration - end 2011/08/18 14:34:38 PIM: Can't create pid lock file /var/run/pimd.pid (Permission denied), exiting “ I was able to get it to run with sudo with the work around suggested earlier *# sudo /usr/local/quagga/sbin/pimd -i /tmp/pimd.pid * it would only work when I ran it with sudo and it kept outputting to the terminal “ tom@tom-laptop:~$ sudo /usr/local/quagga/sbin/pimd -i /tmp/pimd.pid2011/08/18 14:36:53 PIM: zclient_lookup_connect: FIXME blocking connect: zclient_socket_un() 2011/08/18 14:36:53 PIM: zclient_lookup_connect: failure connecting UNIX socket /var/run/zserv.api 2011/08/18 14:36:53 PIM: zclient_lookup_sched: zclient lookup connection scheduled for 10 seconds 2011/08/18 14:37:03 PIM: zclient_lookup_connect: FIXME blocking connect: zclient_socket_un() 2011/08/18 14:37:03 PIM: zclient_lookup_connect: failure connecting UNIX socket /var/run/zserv.api 2011/08/18 14:37:03 PIM: zclient_lookup_sched: zclient lookup connection scheduled for 10 seconds 2011/08/18 14:37:13 PIM: zclient_lookup_connect: FIXME blocking connect: zclient_socket_un() 2011/08/18 14:37:13 PIM: zclient_lookup_connect: failure connecting UNIX socket /var/run/zserv.api 2011/08/18 14:37:13 PIM: zclient_lookup_sched: zclient lookup connection scheduled for 10 seconds 2011/08/18 14:37:23 PIM: zclient_lookup_connect: FIXME blocking connect: zclient_socket_un() 2011/08/18 14:37:23 PIM: zclient_lookup_connect: failure connecting UNIX socket /var/run/zserv.api 2011/08/18 14:37:23 PIM: zclient_lookup_sched: zclient lookup connection scheduled for 10 seconds 2011/08/18 14:37:33 PIM: zclient_lookup_connect: FIXME blocking connect: zclient_socket_un() 2011/08/18 14:37:33 PIM: zclient_lookup_connect: failure connecting UNIX socket /var/run/zserv.api 2011/08/18 14:37:33 PIM: zclient_lookup_sched: zclient lookup connection scheduled for 10 seconds “ And then I'm not exactly sure what I would do to start quagga after this point. I used to start it by following this tutorial: http://openmaniak.com/quagga_tutorial.php but everything got installed in different directories and I wasn't sure what to do. I wouldn't mind documenting my attempt at getting it setup since it appears there is none in existence right now from the mailing list response... but I'm not sure what to do. On Thu, Aug 18, 2011 at 1:01 PM, Everton Marques <[email protected]>wrote: > On Thu, Aug 18, 2011 at 12:59 PM, Tom M <[email protected]> wrote: > > > > 2011/08/18 11:55:32 PIM: Can't create pid lock file /var/run/pimd.pid > > (Permission denied), exiting > > Any idea on what I'm doing wrong? > > The qpimd process lacks permission to create /var/run/pimd.pid. > You can work-around this by supplying a different location with the -i > command-line > switch. For instance: > /usr/local/quagga/sbin/pimd -i /tmp/pimd.pid > Though I guess the easiest way is to launch the pimd daemon as user root. > > > Are there any more detailed tutorials out there on using Quagga with > qpimd? > > AFAIK, no. > > Since pimd is a Quagga daemon, the basic usage is pretty similar to > other Quagga modules. > > A quick-and-dirty start guide for SSM with qpimd would look like this: > 1) Make sure your UNICAST routing is functional between your multicast > source and receiver. > 2) Make sure your zebra daemons know the correct UNICAST routes > towards the multicast source (S). > 3) Get pimd up and running on all PIM routers. > 4) Telnet to port 2611 of every PIM router to configure pimd. > 5) Enable "ip pim ssm" on all available interfaces. > 6) Enable "ip igmp" on interfaces attached to receivers. > 7) Make sure your source (S) is streaming multicast to multicast group G. > 8) Make sure your source (S) is issuing multicast packets with a > high-enough TTL to reach receivers. > 9) Tell you receiver to start receiving from the correct channel (S,G). > 10) If things are not working as expected, you should follow the > directions suggested in this post: > > http://lists.gnu.org/archive/html/qpimd-users/2009-04/msg00006.html > > > Is qpimd still being worked on? > > Since the current state is sufficient for my own SSM needs, and there > is not much time left for further heavy work, I currently perform only > resync with Quagga tree and am willing to fix defects. I don't plan to > add new features. Of course will merge contributions. :-) > > > How complete is the current version? > > It can fully perform the PIM SSM service model (including router-side > IGMPv3). > There are some known issues documented in the file pimd/CAVEATS. > > > Any good overviews of what PIM-SSM is that isn't a super technical paper? > > Sorry, I'm unaware of any. > > Best regards, > Everton >
