FreeBSD Port: verlihub-0.9.8.e.r1,1
Hi all, after upgrading my verlihub to the latest version, the hub does not work anymore. Segmentation Fault. What´s happen to it ? And how may I help to solve the problem ? At the begging I snip gdb output, if it helps. # gdb /usr/local/bin/verlihub /usr/home/verlihub/verlihub.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `verlihub'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libverlihub.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libverlihub.so.0 Reading symbols from /usr/local/lib/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /usr/local/lib/mysql/libmysqlclient.so.15...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/mysql/libmysqlclient.so.15 Reading symbols from /lib/libz.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.4 Reading symbols from /usr/local/lib/libGeoIP.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libGeoIP.so.5 Reading symbols from /usr/lib/libssl.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libssl.so.5 Reading symbols from /lib/libcrypt.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.4 Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /lib/libcrypto.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.so.5 Reading symbols from /usr/local/etc/verlihub/plugins/libplug_pi.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/etc/verlihub/plugins/libplug_pi.so Reading symbols from /usr/local/etc/verlihub/plugins/libiplog_pi.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/etc/verlihub/plugins/libiplog_pi.so Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x458b08ec in ?? () [New Thread 0x28701040 (LWP 100126)] (gdb) Thank you for your help. Bye Stay d ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: mc-4.6.2 lynx-like motion forgot
Hi all, at the beginning I apologize for cross-mailling becuase I really don´t know which mailling list or mail address is the best one for sending my problem. I needed to set up lynx-like motion in configuration of mc. I did it and saved configuration. The application told me that it saved my configuration to ~/.mc/ini. Before I ended mc I tested new setted lynx-like motion and it worked. Next day I started mc again and lynx-like motion did not work at all. I checked my configuration menu and lynx-like motion was not enabled. Why ? I wanted to check it directly in ini file, but I didn´t found any .mc directory and of course any ini file. I tested this on another system where .mc directory and ini file were there. And it worked with lynx-like motion enabled well. I ended mc twice and it always worked again and again. So as I guess my problem is not actually lynx-like motion, but not being ini file. I checked ownership of my home directory and privileges and it were standard. The problem is the same for user and super-user account. I tested sh and bash command interpreter. No diffrence. Some important information about servers: [XYZ$ uname -a FreeBSD XYZ 7.2-STABLE-200906 FreeBSD 7.2-STABLE-200906 #0: Sun Jun 7 10:23:49 UTC 2009 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 or second server [ABC]$ uname -a FreeBSD ABC 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Wed Jun 24 00:57:44 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 mc-4.6.2Midnight Commander, a free Norton Commander Clone # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for mc-4.6.2 _OPTIONS_READ=mc-4.6.2 WITH_UTF8=true WITH_SLANG=true WITH_ICONV=true WITH_NLS=true WITH_EDIT=true WITHOUT_X11=true WITH_SUBSHELL=true WITH_SAMBA=true So what is wrong and where ? Daniel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: portupgrade-2.4.6,2
Hi, my portugrade does not upgrade my ports at all. I wanted to upgrade some ports with security risks. I upgraded my ports successfuly 2 months ago without any problem. server# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Tue Dec 23 20:09:45 CET 2008 to Thu Dec 25 12:30:47 CET 2008. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 97 patches.102030405060708090... done. Applying patches... done. Fetching 5 new ports or files... done. server# portversion -vL= GeoIP needs updating (port has 1.4.5_1) apacheneeds updating (port has 2.2.11) glib needs updating (port has 2.16.5_1) libexecinfo needs updating (port has 1.1_3) lsof needs updating (port has 4.82A,3) p5-HTML-Parserneeds updating (port has 3.59) p5-libwww needs updating (port has 5.822) php5 needs updating (port has 5.2.8) php5-bz2 needs updating (port has 5.2.8) php5-ctypeneeds updating (port has 5.2.8) php5-gd needs updating (port has 5.2.8) php5-mbstring needs updating (port has 5.2.8) php5-mcrypt needs updating (port has 5.2.8) php5-mysqlneeds updating (port has 5.2.8) php5-mysqli needs updating (port has 5.2.8) php5-openssl needs updating (port has 5.2.8) php5-session needs updating (port has 5.2.8) php5-simplexmlneeds updating (port has 5.2.8) php5-spl needs updating (port has 5.2.8) php5-xml needs updating (port has 5.2.8) php5-zlib needs updating (port has 5.2.8) phpMyAdminneeds updating (port has 3.1.1) quagganeeds updating (port has 0.99.11_1) samba needs updating (port has 3.0.32_2,1) smartmontools needs updating (port has 5.38_1) server# portupgrade -av --- Session started at: Thu, 25 Dec 2008 14:13:31 +0100 ** None has been installed or upgraded. --- Session ended at: Thu, 25 Dec 2008 14:14:31 +0100 (consumed 00:00:59) server# Why doesn´t portupgrade do its work when portversion thinks it should work ? And what can I do with it ? server# portupgrade -v quagga --- Session started at: Thu, 25 Dec 2008 14:18:40 +0100 ** None has been installed or upgraded. --- Session ended at: Thu, 25 Dec 2008 14:18:41 +0100 (consumed 00:00:00) server# Individual port does not work too. server#pkg_info ... portupgrade-2.4.6,2 FreeBSD ports/packages administration and management tool s ... quagga-0.99.10_3Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software ... Portupgrade is up to date. server# uname -a FreeBSD x.y.z 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun May 11 15:18:09 CEST 2008 a...@x.y.z:/usr/obj/usr/src/sys/SERVER i386 I can repeat this upgrading process on others system, they are 6.3-stable too and the same version of portupgrade, with the same failure. I tried to find something about this problem and I found one non-answered thread from October here: http://lists.freebsd.org/pipermail/freebsd-ports/2008-October/051187.html I think it is somehow connected with my problem. Thank you Dan Merry Xmas ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FW: FreeBSD Port: portupgrade-2.4.6,2
Ou ! You are right. I am so so sorry for disturbing all kind people here. 2 months and I completly forgot right command to execute portupgrade process. Dan Jerry mailto:freebsd-ports%40freebsd.org?Subject=FreeBSD%20Port%3A%20portupgrade-2.4.6%2C2In-Reply-To=79454A6D7BD64C0188EE0EB40A5E0794%40tocnet28.jspoj.czf gesbbb at yahoo.com Thu Dec 25 06:06:33 PST 2008 * Previous message: FreeBSD http://lists.freebsd.org/pipermail/freebsd-ports/2008-December/051907.html Port: portupgrade-2.4.6,2 * Messages sorted by: [ http://lists.freebsd.org/pipermail/freebsd-ports/2008-December/date.html#51908 date ] [ http://lists.freebsd.org/pipermail/freebsd-ports/2008-December/thread.html#51908 thread ] [ http://lists.freebsd.org/pipermail/freebsd-ports/2008-December/subject.html#51908 subject ] [ http://lists.freebsd.org/pipermail/freebsd-ports/2008-December/author.html#51908 author ] _ On Thu, 25 Dec 2008 14:37:03 +0100 Daniel Dvořák dandee at hellteam.net http://lists.freebsd.org/mailman/listinfo/freebsd-ports wrote: Hi, my portugrade does not upgrade my ports at all. I wanted to upgrade some ports with security risks. I upgraded my ports successfuly 2 months ago without any problem. server# portsnap fetch Shouldn't that be portsnap fetch update? At least that is what it seems to indicate on the 'man' page for portsnap assuming that you have used the extract command previously. -- Jerry gesbbb at yahoo.com http://lists.freebsd.org/mailman/listinfo/freebsd-ports Sometimes I simply feel that the whole world is a cigarette and I'm the only ashtray. -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081225/7094af57/signature.pgp _ From: Daniel Dvořák [mailto:dan...@hellteam.net] Sent: Thursday, December 25, 2008 2:37 PM To: 's...@freebsd.org' Cc: 'po...@freebsd.org' Subject: FreeBSD Port: portupgrade-2.4.6,2 Hi, my portugrade does not upgrade my ports at all. I wanted to upgrade some ports with security risks. I upgraded my ports successfuly 2 months ago without any problem. server# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Tue Dec 23 20:09:45 CET 2008 to Thu Dec 25 12:30:47 CET 2008. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 97 patches.102030405060708090... done. Applying patches... done. Fetching 5 new ports or files... done. server# portversion -vL= GeoIP needs updating (port has 1.4.5_1) apacheneeds updating (port has 2.2.11) glib needs updating (port has 2.16.5_1) libexecinfo needs updating (port has 1.1_3) lsof needs updating (port has 4.82A,3) p5-HTML-Parserneeds updating (port has 3.59) p5-libwww needs updating (port has 5.822) php5 needs updating (port has 5.2.8) php5-bz2 needs updating (port has 5.2.8) php5-ctypeneeds updating (port has 5.2.8) php5-gd needs updating (port has 5.2.8) php5-mbstring needs updating (port has 5.2.8) php5-mcrypt needs updating (port has 5.2.8) php5-mysqlneeds updating (port has 5.2.8) php5-mysqli needs updating (port has 5.2.8) php5-openssl needs updating (port has 5.2.8) php5-session needs updating (port has 5.2.8) php5-simplexmlneeds updating (port has 5.2.8) php5-spl needs updating (port has 5.2.8) php5-xml needs updating (port has 5.2.8) php5-zlib needs updating (port has 5.2.8) phpMyAdminneeds updating (port has 3.1.1) quagganeeds updating (port has 0.99.11_1) samba needs updating (port has 3.0.32_2,1) smartmontools needs updating (port has 5.38_1) server# portupgrade -av --- Session started at: Thu, 25 Dec 2008 14:13:31 +0100 ** None has been installed or upgraded. --- Session ended at: Thu, 25 Dec 2008 14:14:31 +0100 (consumed 00:00:59) server# Why doesn´t portupgrade do its work when portversion thinks it should work ? And what can I do with it ? server# portupgrade -v quagga --- Session started at: Thu, 25 Dec 2008 14:18:40 +0100 ** None has been installed or upgraded. --- Session ended at: Thu, 25 Dec 2008 14:18:41 +0100 (consumed 00:00:00) server# Individual port does not work too. server#pkg_info ... portupgrade-2.4.6,2 FreeBSD
FreeBSD Port: quagga-0.99.10_3
Hi Sergey, may the problem with lock pid_file messages be connected with running watchquagga daemon ? Here is what I have got in rc.conf file: quagga_enable=YES quagga_flags=-d quagga_daemons=zebra ospfd ospf6d bgpd Is this order okay ? quagga_extralibs_path= quagga_delay=10 watchquagga_enable=YES watchquagga_flags=-dz -R '/usr/local/sbin/zebra -d; /usr/local/sbin/ospfd -d; /usr/local/sbin/ospf6d -d; /usr/local/sbin/bgpd -d' zebra ospfd ospf6d bgpd I hope this syntax is right one. I did upgrading of quagga to the last one and restarting daemons. Error messages reappeared. Important! Watchquagga daemon was running at that time too. [EMAIL PROTECTED] 0.99.10 /]# egrep lock /var/log/quagga/* /var/log/quagga/ospfd.log:2008/07/01 13:57:21 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting /var/log/quagga/ospfd.log:2008/07/10 17:17:27 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting ^^ the last restarting /var/log/quagga/ospf6d.log:2008/07/01 13:57:21 errors: OSPF6: Could not lock pid_file /var/run/quagga/ospf6d.pid, exiting /var/log/quagga/ospf6d.log:2008/07/10 17:17:27 errors: OSPF6: Could not lock pid_file /var/run/quagga/ospf6d.pid, exiting ^^ the last restarting /var/log/quagga/zebra.log:2008/07/01 13:57:21 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting /var/log/quagga/zebra.log:2008/07/10 17:17:27 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting ^^ the last restarting [EMAIL PROTECTED] 0.99.10 /]# It is interesting that the bgp daemon runs without these errors. Important! After that, I stopped watchquagga daemon and I restarted quagga daemons, no wunder that error messages haven´t been appearing anymore. Voila! IMHO, the problem is connected with watchquagga daemon deffinitely. Daniel -Original Message- From: Daniel Dvořák [mailto:[EMAIL PROTECTED] Sent: Monday, July 07, 2008 4:44 PM To: 'Sergey Matveychuk' Cc: 'Boris Kovalenko'; '[EMAIL PROTECTED]' Subject: RE: FreeBSD Port: quagga-0.99.9_7 And do you use watchquagga in rc.conf ? I do. Daniel -Original Message- From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] Sent: Monday, July 07, 2008 4:21 PM To: [EMAIL PROTECTED] Cc: 'Boris Kovalenko'; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Daniel Dvořák wrote: VERSION 0.99.10# egrep lock /var/log/quagga/zebra.log ^^^ 2008/06/30 01:38:59 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting 2008/07/01 13:57:21 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting VERSION 0.99.10# egrep lock /var/log/quagga/ospfd.log 2008/06/30 01:38:59 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting 2008/07/01 13:57:21 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting VERSION 0.99.10# egrep lock /var/log/quagga/ospf6d.log 2008/07/01 13:57:21 errors: OSPF6: Could not lock pid_file /var/run/quagga/ospf6d.pid, exiting Looks like the daemons tried to run twice and fault. But I can see the problem on my boxes. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: monitord-0.4.1_2
Hi all, I needed to resolve the problem with verlihub, which refuses to properly run at the start of router. I tried using rcorder various tricks with orderring to run verlihub in the background of other processes. Nothing helped me. I have decided to use monitord, which monitors whether verlihub run at the start of router. For some time it worked well, although verlihub always in the first run snaps and the kernel recorded core file to filesystem as /monitord.core, but monitord always starts up verlihub at the second attempt. Monitord recently stopped work, and I do not know why. In addition, continuing the necessary facts and attached gdb backtraced output: [EMAIL PROTECTED] /]# /etc2/rc.d/monitord status monitord is not running. [EMAIL PROTECTED] /]# /etc2/rc.d/monitord start Starting monitord. [EMAIL PROTECTED] /]# /etc2/rc.d/monitord status monitord is not running. [EMAIL PROTECTED] /]# ls -l /monitord.core -rw--- 1 root wheel 495616 11 čvc 00:29 /monitord.core [EMAIL PROTECTED] /]# dmesg -a | grep monitord Starting monitord. pid 1460 (monitord), uid 0: exited on signal 11 (core dumped) pid 96607 (monitord), uid 0: exited on signal 11 (core dumped) pid 96625 (monitord), uid 0: exited on signal 11 (core dumped) pid 96697 (monitord), uid 0: exited on signal 11 (core dumped) pid 97330 (monitord), uid 0: exited on signal 11 (core dumped) pid 99878 (monitord), uid 0: exited on signal 11 (core dumped) [EMAIL PROTECTED] /]# [EMAIL PROTECTED] /]# cat /var/log/messages | grep monitord Jul 7 00:40:03 r kernel: pid 1460 (monitord), uid 0: exited on signal 11 (core dumped) Jul 7 00:40:03 r monitord: restarted verlihub using /etc2/rc.d/verlihub start Jul 9 21:45:30 r kernel: pid 1481 (monitord), uid 0: exited on signal 11 (core dumped) Jul 9 21:45:30 r monitord: restarted verlihub using /etc2/rc.d/verlihub start Jul 9 22:38:11 r kernel: pid 1459 (monitord), uid 0: exited on signal 11 (core dumped) Jul 9 22:38:12 r monitord: restarted verlihub using /etc2/rc.d/verlihub start Jul 9 22:49:25 r kernel: pid 1459 (monitord), uid 0: exited on signal 11 (core dumped) Jul 9 22:49:25 r monitord: restarted verlihub using /etc2/rc.d/verlihub start Jul 9 22:55:49 r kernel: pid 1460 (monitord), uid 0: exited on signal 11 (core dumped) Jul 9 22:55:49 r monitord: restarted verlihub using /etc2/rc.d/verlihub start Jul 11 00:19:26 r kernel: pid 96607 (monitord), uid 0: exited on signal 11 (core dumped) Jul 11 00:19:33 r kernel: pid 96625 (monitord), uid 0: exited on signal 11 (core dumped) Jul 11 00:20:21 r kernel: pid 96697 (monitord), uid 0: exited on signal 11 (core dumped) Jul 11 00:23:29 r kernel: pid 97330 (monitord), uid 0: exited on signal 11 (core dumped) Jul 11 00:29:51 r kernel: pid 99878 (monitord), uid 0: exited on signal 11 (core dumped) [EMAIL PROTECTED] /]# mount /dev/ad0s1a on / (ufs, NFS exported, local) devfs on /dev (devfs, local) /dev/ad0s1e on /jail (ufs, local, read-only) /dev/ad0s1d on /tmp (ufs, local, soft-updates) /dev/ad0s1g on /usr (ufs, NFS exported, local, soft-updates) /dev/ad0s1f on /var (ufs, NFS exported, local, soft-updates) procfs on /proc (procfs, local) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) [EMAIL PROTECTED] /]# gdb -c /monitord.core /usr/local/sbin/monitord GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `monitord'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28135d61 in strncpy () from /lib/libc.so.6 (gdb) backtrace #0 0x28135d61 in strncpy () from /lib/libc.so.6 #1 0x08049393 in ?? () #2 0xbfbfe4e0 in ?? () #3 0x in ?? () #4 0x0055 in ?? () #5 0x in ?? () #6 0x in ?? () #7 0x in ?? () #8 0x in ?? () #9 0x in ?? () #10 0x in ?? () #11 0x in ?? () #12 0x in ?? () #13 0x in ?? () #14 0x in ?? () #15 0x in ?? () #16 0x in ?? () #17 0x in ?? () #18 0x in ?? () #19 0x in ?? () #20 0x in ?? () #21 0x0001 in ?? () #22 0x0804d400 in ?? () #23 0x0804d000 in ?? () #24 0xbfbfdda0 in ?? () #25 0x in ?? () #26 0x0002 in ?? () #27 0x0002 in ?? () #28 0x0003 in ?? () #29 0x in ?? () #30 0x0001 in ?? () #31 0x0001 in ?? () #32 0x in ?? () #33 0x in ?? ()
RE: FreeBSD Port: quagga-0.99.9_7
Hi Sergey, I see your patch already in ports, so I needn´t use it for now. Am I right ? I did portupgrading of quagga yesterday and a functionality is back again. SYSTEM3# pkg_info | grep quagga quagga-0.99.10_3Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software SYSTEM3# /etc2/rc.d/quagga status zebra is running as pid 62557. ospfd is not running. ospf6d is running as pid 62571. Sleeping 10 seconds to obtain dynamic routing information... Thanks. Daniel P.S.: Boris, have you received my other mail about quagga or my reports is not new for you ? How can I help you with solving the problems, which I have described them last week ? -Original Message- From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] Sent: Sunday, July 06, 2008 1:22 AM To: [EMAIL PROTECTED] Cc: 'Boris Kovalenko'; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Daniel Dvořák wrote: It is new style. SYSTEM3: system3# pkg_info | grep quagga quagga-0.99.10_2Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system3# /etc2/rc.d/quagga status Sleeping 10 seconds to obtain dynamic routing information... system3# It is new broken style. :D Try the patch please. I'll commit it if it's OK. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
And do you use watchquagga in rc.conf ? I do. Daniel -Original Message- From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] Sent: Monday, July 07, 2008 4:21 PM To: [EMAIL PROTECTED] Cc: 'Boris Kovalenko'; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Daniel Dvořák wrote: VERSION 0.99.10# egrep lock /var/log/quagga/zebra.log ^^^ 2008/06/30 01:38:59 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting 2008/07/01 13:57:21 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting VERSION 0.99.10# egrep lock /var/log/quagga/ospfd.log 2008/06/30 01:38:59 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting 2008/07/01 13:57:21 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting VERSION 0.99.10# egrep lock /var/log/quagga/ospf6d.log 2008/07/01 13:57:21 errors: OSPF6: Could not lock pid_file /var/run/quagga/ospf6d.pid, exiting Looks like the daemons tried to run twice and fault. But I can see the problem on my boxes. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Hi Boris,
I am sorry for my late answer. I was on holidays.
I remember Makefile has ENABLE_VTY_GROUP knob, so You may use it. Is it what
You need?
egrep ENABLE_VTY_GROUP /usr/ports/net/quagga/Makefile
.if defined(ENABLE_VTY_GROUP)
CONFIGURE_ARGS+=--enable-vty-group=${ENABLE_VTY_GROUP}
@${ECHO} ENABLE_VTY_GROUP Specify group for vty socket ownership
But it seems it is not enabled, isn´t it ?
I'm not sure if this is it, but I would like to behave the quagga in Debian
(Linux) and FreeBSD consistently.
In contrast, FreeBSD, Linux also has a file named quagga in the directory
/etc/pam.d/.
This file is not in FreeBSD in directory /usr/local/etc/pam.d or /etc/pam.d,
which I would in the case of second option even understand.
Perhaps to FreeBSD is not needed, but then what exactly in the table the
options of quagga when compiling means the possibility of PAM PAM
authentication for vtysh ?
However, the aim is this:
I have an user XXX and I want him to give sufficient privileges to manipulate
the quagga. I do not want to give him permission through sudo or through su
commands. In addition, I want in order to when in the vtysh.conf file, the user
XXX is set with the possibility of nopassword, vtysh not ask me for a password
to the quagga.
Sh interpreter is preset to FreeBSD systems, so that the goal is for these
above-mentioned conditions, to run vtysh straight and asks for nothing.
So far, only what the user see the error message:
Vtysh
Exiting: failed to connect to any daemons.
I do not know how to do, to ask me, but the goal is identical behavior quagga
on FreeBSD to Linux systems and that´s all, not more and not less.
Thank you.
Regards,
Daniel
-Original Message-
From: Boris Kovalenko [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 5:45 AM
To: [EMAIL PROTECTED]
Subject: Re: FreeBSD Port: quagga-0.99.9_7
Hello, Daniel!
I remember Makefile has ENABLE_VTY_GROUP knob, so You may use it. Is it what
You need?
Hi Boris,
I would like to turn your attention on one little bug in quagga on
FreeBSD.
Why don´t we user groupname quaggavty from the beginning when the
quagga had been ported to FreeBSD ?
What do I mena ? I will show you the diffrence between quagga on
Debian and on our FreeBSD.
They use group quaggavty for command vtysh and they help themself with
pam.d/quagga file.
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ls -l /etc/pam.d/quagga
-rw-r--r-- 1 root root 162 2007-09-26 08:20 /etc/pam.d/quagga user$
cat /etc/pam.d/quagga # Any user may call vtysh but only those
belonging to the group quaggavty can # actually connect to the socket
and use the program.
auth sufficient pam_permit.so
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] whoami user [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ls -l /etc/quagga/vtysh.conf
-rw-rw 1 quagga quaggavty 63 2008-01-10 01:28
/etc/quagga/vtysh.conf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] cat
/etc/quagga/vtysh.conf username user nopassword username root
nopassword log syslog [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] egrep
quaggavty /etc/group quaggavty:x:106:user [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] vtysh Hello, this is Quagga (version 0.99.5).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
server# exit
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
So here it works, now FreeBSD:
whoami
resu
ls -l /etc/pam.d/quagga
ls: /etc/pam.d/quagga: No such file or directory
ls -l /usr/local/etc/pam.d/quagga
ls: /usr/local/etc/pam.d/quagga: No such file or directory
ls -l /usr/local/etc/quagga/vtysh.conf
-rw-rw-r-- 1 quagga quagga 129 10 led 01:52
/usr/local/etc/quagga/vtysh.conf
cat /usr/local/etc/quagga/vtysh.conf
username resu nopassword
username root nopassword
log syslog
pw group show quagga
quagga:*:101:resu
vtysh
Exiting: failed to connect to any daemons.
Is possible to repair it ? How can I assit you ?
It would be good if new version 0.99.10 will count with vtysh like on
Debian.
Thank you.
Bye.
Daniel
Regards,
Boris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) Hi Boris, The problem I haven´t solved since February, when I met with him again by chance in July when dealing with another problem, a new multicast api in FreeBSD 7. I will write another report the following e-mail on multicast. I found out that this strange number [: 34978: unexpected operator is not at all a number of lines of code, but it is PID! It is a PID of daemon, which was running, but for some reason has been terminated, for example by signal 11 and an integral condition is that in /var/run/ quagga is the rest of the daemon, the pid file is opened. So when a user runs /usr/local/etc/rc.d/quagga start|stop|restart so it just appears these nonsenses on some unexpected operators. I can not repeat it because I do not know how to simulate freezing process expediently. But I am sure that this is PID number, because in the list of running processes ps aux were two processes ospfd and one of them had the same number like the number in error message. When I was killed the process with the number from error message and restarted quagga, the error message suddenly disappeared, it would lead to think that, between February to July the error unexpected end of the process become, and that I am, of course, it could not even see, and finally that it is rare phenomenon. Respect, Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Hi Boris again, :) I would like to thank you retrospectively to that my proposal is realised, and if this view has ceased to function, so I have to respond. I am afraid that in the last two committed changes in quagga, the error occurred. I have three systems, where I have installed three different versions to the latest display completely ceased to function. SYSTEM1: system1# pkg_info | grep quagga quagga-0.99.9_7 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system1# /etc2/rc.d/quagga status quagga is running as pid 1116. quagga is running as pid 1122. quagga is running as pid 1128. Sleeping 10 seconds to obtain dynamic routing information... system1# It is old style. SYSTEM2: system2# pkg_info | grep quagga quagga-0.99.10 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system2# /etc2/rc.d/quagga status zebra is running as pid 1517. ospfd is running as pid 1523. ospf6d is running as pid 1529. bgpd is running as pid 1535. Sleeping 10 seconds to obtain dynamic routing information... system2# It is new style. SYSTEM3: system3# pkg_info | grep quagga quagga-0.99.10_2Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system3# /etc2/rc.d/quagga status Sleeping 10 seconds to obtain dynamic routing information... system3# It is new broken style. :D Respect, Daniel -Original Message- From: Daniel Dvořák [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 11:43 AM To: 'Boris Kovalenko' Cc: '[EMAIL PROTECTED]' Subject: RE: FreeBSD Port: quagga-0.99.9_7 Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, Question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: quagga-0.99.9_7
Hi Boris, I would like to turn your attention on one little bug in quagga on FreeBSD. Why don´t we user groupname quaggavty from the beginning when the quagga had been ported to FreeBSD ? What do I mena ? I will show you the diffrence between quagga on Debian and on our FreeBSD. They use group quaggavty for command vtysh and they help themself with pam.d/quagga file. [EMAIL PROTECTED] ls -l /etc/pam.d/quagga -rw-r--r-- 1 root root 162 2007-09-26 08:20 /etc/pam.d/quagga user$ cat /etc/pam.d/quagga # Any user may call vtysh but only those belonging to the group quaggavty can # actually connect to the socket and use the program. authsufficient pam_permit.so [EMAIL PROTECTED] whoami user [EMAIL PROTECTED] ls -l /etc/quagga/vtysh.conf -rw-rw 1 quagga quaggavty 63 2008-01-10 01:28 /etc/quagga/vtysh.conf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] cat /etc/quagga/vtysh.conf username user nopassword username root nopassword log syslog [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] egrep quaggavty /etc/group quaggavty:x:106:user [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] vtysh Hello, this is Quagga (version 0.99.5). Copyright 1996-2005 Kunihiro Ishiguro, et al. server# exit [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] So here it works, now FreeBSD: whoami resu ls -l /etc/pam.d/quagga ls: /etc/pam.d/quagga: No such file or directory ls -l /usr/local/etc/pam.d/quagga ls: /usr/local/etc/pam.d/quagga: No such file or directory ls -l /usr/local/etc/quagga/vtysh.conf -rw-rw-r-- 1 quagga quagga 129 10 led 01:52 /usr/local/etc/quagga/vtysh.conf cat /usr/local/etc/quagga/vtysh.conf username resu nopassword username root nopassword log syslog pw group show quagga quagga:*:101:resu vtysh Exiting: failed to connect to any daemons. Is possible to repair it ? How can I assit you ? It would be good if new version 0.99.10 will count with vtysh like on Debian. Thank you. Bye. Daniel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: denyhosts-2.6_1 (fwd)
Thank you. We will look forward for 2.7. Bye Dan -Original Message- From: Phil Schwartz [mailto:[EMAIL PROTECTED] Sent: Monday, March 17, 2008 2:41 PM To: Mohacsi Janos Cc: Daniel Dvořák Subject: Re: FreeBSD Port: denyhosts-2.6_1 (fwd) Hello, This will be fixed in 2.7. For now, simply place the following entry in your denyhosts.cfg file, save and then restart denyhosts: FAILED_ENTRY_REGEX7 = User (?Puser.*) .*from (?Phost.*?) not allowed because not listed in AllowUsers$ make sure that the entry appears on a single line. Regards, Phil Mohacsi Janos wrote: Corrected e-mail. Please help investigating. Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning and Projects NIIF/HUNGARNET, HUNGARY Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882 -- Forwarded message -- Date: Mon, 17 Mar 2008 10:29:43 +0100 (CET) From: Mohacsi Janos [EMAIL PROTECTED] To: Daniel Dvořák [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: FreeBSD Port: denyhosts-2.6_1 Dear Daniel, I have CC'ed the author of denyhosts he migth help. Best Regards, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning and Projects NIIF/HUNGARNET, HUNGARY Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882 On Mon, 17 Mar 2008, Daniel Dvořák wrote: Hi Janos, I have 2 servers with denyhosts and everytime I receive the security mail with many attempts to login to my systems and everytime I am surprised why that, if I have denyhosts. I have found out from this link (https://bugs.launchpad.net/ubuntu/feisty/+source/denyhosts/+bug/133569) that I am not alone with these regex errors. I use AllowUsers option in sshd.conf to speed up to deceide what is secured and what is ssh brute attack. But as I see, denyhosts has a problem to determine what to do with it. I suppose there is the same problem like in ubuntu/debian package and needs to be fixed. I could add in-depth report about regex pattern ( User (?Puser.*) not allowed because not listed in AllowUsers ) is missing 'host' group, if it is needed of course. Bye. Dan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: denyhosts-2.6_1
Hi Janos, I have 2 servers with denyhosts and everytime I receive the security mail with many attempts to login to my systems and everytime I am surprised why that, if I have denyhosts. I have found out from this link (https://bugs.launchpad.net/ubuntu/feisty/+source/denyhosts/+bug/133569) that I am not alone with these regex errors. I use AllowUsers option in sshd.conf to speed up to deceide what is secured and what is ssh brute attack. But as I see, denyhosts has a problem to determine what to do with it. I suppose there is the same problem like in ubuntu/debian package and needs to be fixed. I could add in-depth report about regex pattern ( User (?Puser.*) not allowed because not listed in AllowUsers ) is missing 'host' group, if it is needed of course. Bye. Dan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, I have 2 question to you. Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, I have 2 question to you. Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: cacti-0.8.7b
Thank you for your reactions. I look forward to test your cacti-pluginst port in FreeBSD. Bye Daniel -Original Message- From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 11:44 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: cacti-0.8.7b Daniel Dvořák wrote: On the 16th of December 2007, you wrote these sentences in UPDATING file about Plugin Architecture: Plugin support is dropped again and will not revive anymore in the port. A reason for that is the patch is unofficial and there are long time lags between a new cacti version released and time when the patch is adapted. It is very pitty for us, becuase we use weathermap plugin to monitor and visualize the current load of our network. With your commit and after restarting of mysql server, our weathemap plugin is gone, and people ask me why this nice tool is not working. They got used to this nice maps. On the 12th of February 2008, unofficial patch Plugin Architecture have been released as a version 2.0, and it is adjusted or adapted for 0.8.7b cacti, which we have in ports nowadays. Do you think that you could include this patch 2.0 to the cacti back again ? If you are not wellwisher for this, could you advise me how we can get plugins back to cacti ? Hi Daniel! As I already mention, cacti team don't support the plugin patch and a patch author not so fast how we'd like. So I'm between two users group, one ask me update cacti ASAP and another (a little one) ask me to keep plugins support. I can't satisfy them both. A good news is cacti team decide to include plugins support in future versions. Unfortunately it'll happen not so soon. But can add a new cacti-plugins port if you'll test it (I don't use the plugin support). -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: cacti-0.8.7b
Thank you for your reactions. I look forward to test your cacti-pluginst port in FreeBSD. Bye Daniel -Original Message- From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 11:44 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: cacti-0.8.7b Daniel Dvořák wrote: On the 16th of December 2007, you wrote these sentences in UPDATING file about Plugin Architecture: Plugin support is dropped again and will not revive anymore in the port. A reason for that is the patch is unofficial and there are long time lags between a new cacti version released and time when the patch is adapted. It is very pitty for us, becuase we use weathermap plugin to monitor and visualize the current load of our network. With your commit and after restarting of mysql server, our weathemap plugin is gone, and people ask me why this nice tool is not working. They got used to this nice maps. On the 12th of February 2008, unofficial patch Plugin Architecture have been released as a version 2.0, and it is adjusted or adapted for 0.8.7b cacti, which we have in ports nowadays. Do you think that you could include this patch 2.0 to the cacti back again ? If you are not wellwisher for this, could you advise me how we can get plugins back to cacti ? Hi Daniel! As I already mention, cacti team don't support the plugin patch and a patch author not so fast how we'd like. So I'm between two users group, one ask me update cacti ASAP and another (a little one) ask me to keep plugins support. I can't satisfy them both. A good news is cacti team decide to include plugins support in future versions. Unfortunately it'll happen not so soon. But can add a new cacti-plugins port if you'll test it (I don't use the plugin support). -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: cacti-0.8.7b
Thank you for your reactions. I look forward to test your cacti-pluginst port in FreeBSD. Bye Daniel -Original Message- From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 11:44 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: cacti-0.8.7b Daniel Dvořák wrote: On the 16th of December 2007, you wrote these sentences in UPDATING file about Plugin Architecture: Plugin support is dropped again and will not revive anymore in the port. A reason for that is the patch is unofficial and there are long time lags between a new cacti version released and time when the patch is adapted. It is very pitty for us, becuase we use weathermap plugin to monitor and visualize the current load of our network. With your commit and after restarting of mysql server, our weathemap plugin is gone, and people ask me why this nice tool is not working. They got used to this nice maps. On the 12th of February 2008, unofficial patch Plugin Architecture have been released as a version 2.0, and it is adjusted or adapted for 0.8.7b cacti, which we have in ports nowadays. Do you think that you could include this patch 2.0 to the cacti back again ? If you are not wellwisher for this, could you advise me how we can get plugins back to cacti ? Hi Daniel! As I already mention, cacti team don't support the plugin patch and a patch author not so fast how we'd like. So I'm between two users group, one ask me update cacti ASAP and another (a little one) ask me to keep plugins support. I can't satisfy them both. A good news is cacti team decide to include plugins support in future versions. Unfortunately it'll happen not so soon. But can add a new cacti-plugins port if you'll test it (I don't use the plugin support). -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, I have 2 question to you. Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, I have 2 question to you. Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, I have 2 question to you. Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: quagga-0.99.9_7
Hi Boris, I have 2 question to you. Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagga status [: 34978: unexpected operator strange quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: quagga-0.99.9
Hi all, today I wanted to upgrade my quagga ports in 4 diffrent systems and the upgrading process has failed with these messages below for all 4 systems the same: quagga-0.99.9 needs updating (port has 0.99.9_2) ... gmake[2]: Leaving directory `/usr/ports/net/quagga/work/quagga-0.99.9/watchquagga' Making all in vtysh gmake[2]: Entering directory `/usr/ports/net/quagga/work/quagga-0.99.9/vtysh' cc -DHAVE_CONFIG_H -DSYSCONFDIR=\/usr/local/etc/quagga/\ -I. -I.. -I.. -I../lib-O2 -pipe -march=athlon-xp -I/usr/local/include -MT vtysh_main.o -MD -MP -MF .deps/vtysh_main.Tpo -c -o vtysh_main.o vtysh_main.c mv -f .deps/vtysh_main.Tpo .deps/vtysh_main.Po cc -DHAVE_CONFIG_H -DSYSCONFDIR=\/usr/local/etc/quagga/\ -I. -I.. -I.. -I../lib-O2 -pipe -march=athlon-xp -I/usr/local/include -MT vtysh.o -MD -MP -MF .deps/vtysh.Tpo -c -o vtysh.o vtysh.c mv -f .deps/vtysh.Tpo .deps/vtysh.Po cc -DHAVE_CONFIG_H -DSYSCONFDIR=\/usr/local/etc/quagga/\ -I. -I.. -I.. -I../lib-O2 -pipe -march=athlon-xp -I/usr/local/include -MT vtysh_user.o -MD -MP -MF .deps/vtysh_user.Tpo -c -o vtysh_user.o vtysh_user.c vtysh_user.c:44: error: `PAM_CONV_FUNC' undeclared here (not in a function) vtysh_user.c:44: error: initializer element is not constant vtysh_user.c:44: error: (near initialization for `conv.conv') gmake[2]: *** [vtysh_user.o] Error 1 gmake[2]: Leaving directory `/usr/ports/net/quagga/work/quagga-0.99.9/vtysh' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/net/quagga/work/quagga-0.99.9' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/net/quagga. *** Error code 1 Stop in /usr/ports/net/quagga. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.24855.0 env make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! net/quagga(new compiler error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed Others 3 systems, the only diffrence: -O2 -pipe -march=pentium4 -O2 -pipe -march=pentium3 -O2 -pipe -march=athlon-tbird Something bad about vtysh ? I have a configured vtysh.conf file only. Any advise ? What could it be ? thx Dan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FW: FreeBSD Port: uptimed-0.3.7
I have no response, so I try to send to public.
_
From: Daniel Dvořák [mailto:[EMAIL PROTECTED]
Sent: Friday, August 03, 2007 11:09 PM
To: '[EMAIL PROTECTED]'
Subject: FreeBSD Port: uptimed-0.3.7
Hi Andy,
I ask you about updating uptimed to the last release 0.3.11.
Radek P. is my friend and I show him what the startting script in fbsd porttree
is, he was surprised a little bit about older our 0.3.7 release.
The main problem is with pid file and uptimed.sh script as whole.
See this:
# /etc2/rc.d/uptimed.sh stop
# /etc2/rc.d/uptimed.sh start
uptimeduptimed is already running.
# /etc2/rc.d/uptimed.sh stop
# ps aux | grep uptimed
root 91399 0,0 0,8 1564 948 p0 R+ 10:04od 0:00,03 grep uptimed
# /etc2/rc.d/uptimed.sh start
uptimeduptimed is already running.
# ps aux | grep uptimed
root 91406 0,0 0,7 1548 872 p0 R+ 10:05od 0:00,02 grep uptimed
I had to use „killall uptimed“ to really stop it.
This is our latest script:
#!/bin/sh
case $1 in
start)
echo -n ' uptimed'
/usr/local/sbin/uptimed
;;
stop)
;;
restart)
;;
*)
echo Usage: ${0##*/}: { start | stop | restart } 21
exit 65
;;
esac
And Radek has in his sources this much newer code with status. To be perfect it
should have rcvar option.
http://hg.podgorny.cz/uptimed/file/ccbad14594ae/etc/rc.uptimed
case $1 in
69 start)
70 start
71 ;;
72 stop)
73 stop
74 ;;
75 restart)
76 stop
77 start
78 ;;
79 createbootid)
80 createbootid
81 ;;
82 status)
83 showstatus
84 ;;
85 *)
86 echo $Usage: $0 {start|stop|restart|createbootid|status}
87 RETVAL=1
88esac
89exit $RETVAL
I think this code above is good point to start and adjust our modern uptimed
startting script with rc rules for our needs.
I ask you more than I could, becuse my contribution is almost none, but at
least new modern startting script with whole status and rcvar stuff under new
rc rules would be great.
Perhaps I do not bother you more than necessary.
Thanks
Bye
Dan
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: bash-3.2.17_2
Hi Obrien, portupgrading bash from 3.1.17 to 3.2.17_2 is finished with error about missing autoconf. It is interesting why bash needs autoconf while compiling and for the second I have autoconf package, but it is useless for that as you can see below. What can I do to fix it? Thanks Bye Dan configure: creating ./config.status config.status: creating Makefile config.status: creating builtins/Makefile config.status: creating lib/readline/Makefile config.status: creating lib/glob/Makefile config.status: creating lib/intl/Makefile config.status: creating lib/malloc/Makefile config.status: creating lib/sh/Makefile config.status: creating lib/termcap/Makefile config.status: creating lib/tilde/Makefile config.status: creating doc/Makefile config.status: creating support/Makefile config.status: creating po/Makefile.in config.status: creating examples/loadables/Makefile config.status: creating examples/loadables/perl/Makefile config.status: creating pathnames.h config.status: creating config.h config.status: executing default-1 commands config.status: creating po/POTFILES config.status: creating po/Makefile config.status: executing default commands === Building for bash-3.2.17_2 yacc -d ./parse.y yacc: 1 shift/reduce conflict touch parser-built cd . autoconf autoconf: not found *** Error code 127 Stop in /usr/ports/tmp/usr/ports/shells/bash/work/bash-3.2. *** Error code 1 Stop in /usr/ports/shells/bash. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.50881.0 en ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! shells/bash (unknown build error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed # # pkg_info autoconf-2.59_2 Automatically configure source code on many Un*x platforms bmon-2.1.0 Portable bandwidth monitor and rate estimator bsdstats-5.3_4 Monthly script for reporting anonymous statistics about you cvsup-without-gui-16.1h_3 General network file distribution system optimized for CVS db41-4.1.25_4 The Berkeley DB package, revision 4.1 gettext-0.16.1_3GNU gettext package glib-2.12.13Some useful routines of C programming (current stable versi gmake-3.81_2GNU version of 'make' utility gnu-watch-3.2.7 GNU watch command help2man-1.36.4_1 Automatically generating simple manual pages from program o ipfw2dshield-0.5A DShield client for ipfw logs isc-dhcp3-server-3.0.5_2 The ISC Dynamic Host Configuration Protocol server kismet-200701.r1802.11 layer2 wireless network detector, sniffer, and IDS libiconv-1.9.2_2A character set conversion library libtool-1.5.22_4Generic shared library support script lsof-4.79B Lists information about open files (similar to fstat(1)) m4-1.4.9GNU m4 mc-4.6.1_5 Midnight Commander, a free Norton Commander Clone net-snmp-5.3.1_3An extendable SNMP implementation openntpd-3.9p1_1,2 OpenBSD's Network Time Protocol daemon p5-gettext-1.05_1 Message handling functions perl-5.8.8 Practical Extraction and Report Language pkg-config-0.22 A utility to retrieve information about installed libraries portaudit-0.5.11Checks installed ports against a list of security vulnerabi portupgrade-2.3.1,2 FreeBSD ports/packages administration and management tool s quagga-0.99.7_2 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software ruby-1.8.6_2,1 An object-oriented interpreted scripting language ruby18-bdb-0.6.0Ruby interface to Sleepycat's Berkeley DB revision 2 or lat screen-4.0.3A multi-screen window manager sudo-1.6.9 Allow others to run commands as root trafshow-5.2.3,1Full screen visualization of network traffic uptimed-0.3.7 Rob Kaper's uptime daemon wget-1.10.2_1 Retrieve files from the Net via HTTP and FTP ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: quagga-0.99.7_2 - quagga restartting is broken ?
Hi Boris, I have a problem with restarting quagga by our script for a long time, I guess since that time when the script was moved from /etc/rc.d/ to /usr/local/etc/rc.d/. And before this major change each restarting of quagga was successful. I can swear on it. :) When I restart quagga, the router is unreachable at once, the last message before ssh client is kicked out: # /usr/local/etc/rc.d/quagga restart Stopping quagga. PuTTY (inactive) to be illustrative :) I can reach to the router from another host which is in the same network like my router fortunately. And what I see ? # /usr/local/etc/rc.d/quagga status quagga is running as pid 1164. quagga is running as pid 802. From ps aux: # ps aux | grep ospfd quagga 802 0.0 2.7 4704 3260 ?? Ss2:38AM 0:04.24 /usr/local/sbin/ospfd -d # ps aux | grep zebra quagga 1665 3.2 2.0 3868 2508 ?? Ss3:05AM 0:15.89 /usr/local/sbin/zebra -d So I begin to repeat restarting again: # /../rc.d/quagga restart Stopping quagga. Starting quagga. # /../rc.d/quagga status quagga is running as pid 1251. quagga is running as pid 802. # /../rc.d/watchquagga stop Stopping watchquagga. # /../rc.d/quagga restart Stopping quagga. Starting quagga. # /../rc.d/quagga status quagga is running as pid 1396. quagga is running as pid 802. So zebra daemon is definitely stopped and started. But something wrong is with ospfd, it has the same PID like before. When I do clean stop-status-start-status sequence, quagga works well again. # /usr/local/etc/rc.d/quagga stop Stopping quagga. Stopping quagga. # /usr/local/etc/rc.d/quagga status quagga is not running. quagga is not running. # /usr/local/etc/rc.d/quagga start Starting quagga. Starting quagga. # /usr/local/etc/rc.d/quagga status quagga is running as pid 1868. quagga is running as pid 1874. And for be sure: # /usr/local/etc/rc.d/quagga restart Stopping quagga. Waiting for PIDS: 1868. Starting quagga. # /usr/local/etc/rc.d/quagga status quagga is running as pid 2343. quagga is running as pid 1874. # ps aux | grep ospfd quagga 1874 0.0 2.7 4668 3264 ?? Ss3:17AM 0:00.64 /usr/local/sbin/ospfd -d root2368 0.0 0.8 1608 1012 p1 R+3:18AM 0:00.02 grep ospfd During this time, the routing table is half-empty or almost empty, unlike the time when quagga works well with 200 and more routes. So tell me please, what is wrong here ? Bye Dan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: ipfw2dshield-0.5
Hi Frank, I have some strange messages from cron daemon about ipfw2dshild. And what is more interesting it appears only on WRAP platform (PC ENGINE), not on other hardwares. This mail for root from Cron Daemon: Message 1: From [EMAIL PROTECTED] Sat Jan 1 00:03:07 2000 Date: Sat, 1 Jan 2000 00:03:01 +0100 (CET) From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED]/usr/local/sbin/ipfw2dshield X-Cron-Env: SHELL=/bin/sh X-Cron-Env: PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin X-Cron-Env: HOME=/var/log X-Cron-Env: LOGNAME=root X-Cron-Env: USER=root ipfw2dshield: Can't find 'strpdate' on this system. Do not look at the time, wrap doesn´t have a RTC. ls -al /usr/local/bin/strpdate -rwxr-xr-x 1 root wheel 3884 Jan 1 03:43 /usr/local/bin/strpdate X# /usr/local/bin/strpdate Usage: /usr/local/bin/strpdate -f fmt date So the file exists right there where it should be and it is fully executable. My /usr/local/etc/ipfw2dshild.rc configuration file is the generic one. Could you advise me, what it´s going on, please ? Thanks. Bye Dan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: phpMyAdmin-2.10.0.2
Can you try this small test to see if your php setup really does have broken support for ctype_digit() ? % php -r 'print ctype_digit(1234);' Yes, it returned 1. Should print '1'. If that doesn't work, then examine /usr/local/etc/php/extensions.ini -- does it contain the line extension=ctype.so ? Yes, it contains. Did you restart apache since installing the php5-ctype module? Perhaps, I didn´t. I restarted the daemon and the site works now again. Thank you. Dan Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: phpMyAdmin-2.10.0.2
In March there were reports about bad dependences for phpMyAdmin, specially missing php-ctype like this http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2007-March/114357.html It seems that the latest phpmyadmin-2.10.0.1 release now requires functions from the PHP ctype module. undefined function ctype_digit() /usr/local/www/phpMyAdmin/libraries/common.lib.php on line 2981 It seems that this was fixed between version 2.10.0.1 - 2.10.0.2 in Makefile. But today I did clean instalation of phpMyAdmin-2.10.0.2 port and after simple configuration through /scripts/setup.php with cookies auth-type instead of function phpMyAdmin site I saw this bug: Fatal error: Call to undefined function ctype_digit() in /usr/local/www/phpMyAdmin/libraries/common.lib.php on line 2993 It seems something wrong with php5-ctype ? What can I do with this ? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FW: kismet scanning deos not work for me
I can add new facts: # kismet -n Server options: -n Client options: none Starting server... Waiting for server to start before starting UI... Not logging any data Will drop privs to stayd (1001) gid 1001 No specific sources given to be enabled, all will be enabled. Enabling channel hopping. Disabling channel splitting. Source 0 (rik): Enabling monitor mode for radiotap_bsd_a source interface ath0 channel 100... FATAL: ath0: cannot set ifmedia: Device not configured # ifconfig -v ath0 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20b:6bff:fe35:509a%ath0 prefixlen 64 scopeid 0x1 inet 10.*.*.* netmask 0xfffc broadcast 10.40.192.19 ether 00:0b:6b:XX:YY:ZZ media: IEEE 802.11 Wireless Ethernet OFDM/24Mbps mode 11a flag0,adhoc (OFDM/24Mbps) status: associated ssid PtP channel 100 (5500) bssid 00:00:00:00:00:00 authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100 txpowmax 36 txpower 63 rtsthreshold 2346 mcastrate 1 fragthreshold 2346 bmiss 7 pureg protmode OFF wme burst roaming AUTO bintval 100 AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm kismet.conf is attached. rc.conf: ifconfig_ath0=inet 10.*.*.*/30 media OFDM/24Mbps mode 11a mediaopt flag0 mediaopt adhoc ssid PtP channel 100 pureg protmode off txpower 63 chanlist 100-140 wme up P.S.: mail me directly please. _ From: Daniel Dvořák [mailto:[EMAIL PROTECTED] Sent: Sunday, September 03, 2006 1:44 AM To: 'freebsd-ports@freebsd.org' Subject: kismet scanning deos not work for me Hi all, my config of kismet.conf is attached. I read the kismet manual from the begining to the end and Kismet does not work for me. Even when I manually reconfigure my card from ahdemo mode to monitor mode, after execute kismet -n command, these lines turn up at once: Waiting for channel control child 2842 to exit... Kismet exiting. Connected to Kismet server version 2006.04.R1 build 20050815211952 on localhost:2501 localhost:2501 TCP error: socket returned EOF, server has closed the connection. Is it known issue ? Thank you Daniel _ avast! Antivirus http://www.avast.com : Odchozi zprava cista. Virova databaze (VPS): 0635-5, 04.09.2006 Testovano: 5.9.2006 17:36:49 avast! - copyright (c) 1988-2006 ALWIL Software. # Kismet config file # Most of the static configs have been moved to here -- the command line # config was getting way too crowded and cryptic. We want functionality, # not continually reading --help! # Version of Kismet config version=2005.06.R1 # Name of server (Purely for organizational purposes) servername=Kismet # User to setid to (should be your normal user) suiduser=myuser # Sources are defined as: # source=sourcetype,interface,name[,initialchannel] # Source types and required drivers are listed in the README under the # CAPTURE SOURCES section. # The initial channel is optional, if hopping is not enabled it can be used # to set the channel the interface listens on. # YOU MUST CHANGE THIS TO BE THE SOURCE YOU WANT TO USE source=radiotap_bsd_a,ath0,1,100 #source=radiotap_bsd_a,ath1,2,108 # Comma-separated list of sources to enable. This is only needed if you defined # multiple sources and only want to enable some of them. By default, all defined # sources are enabled. # For example: # enablesources=prismsource,ciscosource # Do we channelhop? channelhop=true # How many channels per second do we hop? (1-10) channelvelocity=5 # By setting the dwell time for channel hopping we override the channelvelocity # setting above and dwell on each channel for the given number of seconds. #channeldwell=10 # Do we split channels between cards on the same spectrum? This means if # multiple 802.11b capture sources are defined, they will be offset to cover # the most possible spectrum at a given time. This also controls splitting # fine-tuned sourcechannels lines which cover multiple interfaces (see below) channelsplit=false # Basic channel hopping control: # These define the channels the cards hop through for various frequency ranges # supported by Kismet. More finegrain control is available via the # sourcechannels configuration option. # # Don't change the IEEE80211x identifiers or channel hopping won't work. # Users outside the US might want to use this list: # defaultchannels=IEEE80211b:1,7,13,2,8,3,14,9,4,10,5,11,6,12 #defaultchannels=IEEE80211b:1,6,11,2,7,3,8,4,9,5,10 # 802.11g uses the same channels as 802.11b... #defaultchannels=IEEE80211g
kismet scanning deos not work for me
Hi all, my config of kismet.conf is attached. I read the kismet manual from the begining to the end and Kismet does not work for me. Even when I manually reconfigure my card from ahdemo mode to monitor mode, after execute kismet -n command, these lines turn up at once: Waiting for channel control child 2842 to exit... Kismet exiting. Connected to Kismet server version 2006.04.R1 build 20050815211952 on localhost:2501 localhost:2501 TCP error: socket returned EOF, server has closed the connection. Is it known issue ? Thank you Daniel # Kismet config file # Most of the static configs have been moved to here -- the command line # config was getting way too crowded and cryptic. We want functionality, # not continually reading --help! # Version of Kismet config version=2005.06.R1 # Name of server (Purely for organizational purposes) servername=Kismet # User to setid to (should be your normal user) suiduser=myuser # Sources are defined as: # source=sourcetype,interface,name[,initialchannel] # Source types and required drivers are listed in the README under the # CAPTURE SOURCES section. # The initial channel is optional, if hopping is not enabled it can be used # to set the channel the interface listens on. # YOU MUST CHANGE THIS TO BE THE SOURCE YOU WANT TO USE source=radiotap_bsd_a,ath0,1,100 #source=radiotap_bsd_a,ath1,2,108 # Comma-separated list of sources to enable. This is only needed if you defined # multiple sources and only want to enable some of them. By default, all defined # sources are enabled. # For example: # enablesources=prismsource,ciscosource # Do we channelhop? channelhop=true # How many channels per second do we hop? (1-10) channelvelocity=5 # By setting the dwell time for channel hopping we override the channelvelocity # setting above and dwell on each channel for the given number of seconds. #channeldwell=10 # Do we split channels between cards on the same spectrum? This means if # multiple 802.11b capture sources are defined, they will be offset to cover # the most possible spectrum at a given time. This also controls splitting # fine-tuned sourcechannels lines which cover multiple interfaces (see below) channelsplit=false # Basic channel hopping control: # These define the channels the cards hop through for various frequency ranges # supported by Kismet. More finegrain control is available via the # sourcechannels configuration option. # # Don't change the IEEE80211x identifiers or channel hopping won't work. # Users outside the US might want to use this list: # defaultchannels=IEEE80211b:1,7,13,2,8,3,14,9,4,10,5,11,6,12 #defaultchannels=IEEE80211b:1,6,11,2,7,3,8,4,9,5,10 # 802.11g uses the same channels as 802.11b... #defaultchannels=IEEE80211g:1,6,11,2,7,3,8,4,9,5,10 # 802.11a channels are non-overlapping so sequential is fine. You may want to # adjust the list depending on the channels your card actually supports. defaultchannels=IEEE80211a:36,40,44,48,52,56,60,64,100,104,108,112,116,120,124,128,132,136,140,149,153,157,161,184,188,192,196,200,204,208,212,216 #defaultchannels=IEEE80211a:36,40,44,48,52,56,60,64 # Combo cards like Atheros use both 'a' and 'b/g' channels. Of course, you # can also explicitly override a given source. You can use the script # extras/listchan.pl to extract all the channels your card supports. #defaultchannels=IEEE80211ab:1,6,11,2,7,3,8,4,9,5,10,36,40,44,48,52,56,60,64 # Fine-tuning channel hopping control: # The sourcechannels option can be used to set the channel hopping for # specific interfaces, and to control what interfaces share a list of # channels for split hopping. This can also be used to easily lock # one card on a single channel while hopping with other cards. # Any card without a sourcechannel definition will use the standard hopping # list. # sourcechannels=sourcename[,sourcename]:ch1,ch2,ch3,...chN # ie, for us channels on the source 'prism2source' (same as normal channel # hopping behavior): # sourcechannels=prism2source:1,6,11,2,7,3,8,4,9,5,10 # Given two capture sources, prism2a and prism2b, we want prism2a to stay # on channel 6 and prism2b to hop normally. By not setting a sourcechannels # line for prism2b, it will use the standard hopping. # sourcechannels=prism2a:6 # To assign the same custom hop channel to multiple sources, or to split the # same custom hop channel over two sources (if splitchannels is true), list # them all on the same sourcechannels line: # sourcechannels=prism2a,prism2b,prism2c:1,6,11 # Port to serve GUI data tcpport=2501 # People allowed to connect, comma seperated IP addresses or network/mask # blocks. Netmasks can be expressed as dotted quad (/255.255.255.0) or as # numbers (/24) allowedhosts=127.0.0.1 # Address to bind to. Should be an address already configured already on # this host, reverts to INADDR_ANY if specified incorrectly. bindaddress=127.0.0.1 # Maximum number of concurrent GUI's maxclients=5 # Do we have a GPS? gps=false # Host:port that GPSD is
FreeBSD Port: arpwatch-2.1.a14
Hi all, let me ask you about arpwatch. The port under FreeBSD does not support the important switch -p, which we can find for example in Debian Linux. This switch is about don´t put to promisccuous mode, which is really needed for example wireless cards, where promisc kills usually the traffic on wi-fi. I am sorry I do not imagine how much work it is, I simple ask, is it possible to implement this switch (flag) ? In the Debian Linux, there are anothers useful flags, but of course -p is the most important one, here they are: (Debian) The -s flag is used to specify the path to the sendmail program. Any program that takes the option -odi and then text from stdin can be substituted. This is useful for redirecting reports to log files instead of mail. (Debian) The -p flag disables promiscuous operation. ARP broadcasts get through hubs without having the interface in promiscuous mode, while sav- ing considerable resources that would be wasted on processing gigabytes of non-broadcast traffic. OTOH, setting promiscuous mode does not mean getting 100% traffic that would concern arpwatch . YMMV. (Debian) -a By default, arpwatch reports bogons (unless -N is given) for IP addresses that are in the same subnet than the first IP address of the default interface. If this option is specified, arpwatch will report bogons about every IP addresses. (Debian) The -m option is used to specify the e-mail address to which reports will be sent. By default, reports are sent to root on the local machine. (Debian) The -u flag instructs arpwatch to drop root privileges and change the UID to username and GID to the primary group of username . This is recommended for security reasons, but username has to have write access to the default directory. (Debian) The -R flag instructs arpwatch to restart in seconds seconds after the interface went down. By default, in such cases arpwatch would print an error message and exit. This option is ignored if either the -r or -u flags are used. (Debian) The -Q flags prevents arpwatch from sending reports by mail. (Debian) The -z flag is used to set a range of ip addresses to ignore (such as a DHCP range). Netmask is specified as 255.255.128.0. Please, I just ask, do not shoot me, thanks :) Bye Daniel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
