searching a good MRTG/SNMP configuration
Hello misc@, hosting a lan party yesterday I started to play around with MRTG and SNMP, but I didn't quite get where I wanted. I guess somebody using OpenBSD already has a nice MRTG configuration showing: IN/OUT traffic [CPU] load memory usage some stuff about pf (states, blocks/pass) (using this patch: http://www.packetmischief.ca/openbsd/snmp/) Something similar to this: http://www.erde.co.jp/mrtg/index.html would be what I'm looking for. But with a better traffic report. Would this person be willing to share the configuration files (mrtg/snmp[/rrdtool]) with me and the rest of the OpenBSD community? While we are at it, how do you make the MRTG output accessible? My idea was to let every host create its own statistics and upload those to my central webserver, using pub-key scp/sftp with an unprivileged user account. The webserver would move all those reports to its www-chroot. If I need to I'll create one myself, but after fiddeling around with it for a couple of hours I thought about the reinvention of the wheel and its waste of time. Regards, ahb
Message deleted
Scanner: MailMonitor for SMTP v1.2.2 Problem description: Email data: MessageID: [EMAIL PROTECTED] From: misc@openbsd.org To: [EMAIL PROTECTED] Cc: Subject: Mail System Error - Returned Mail Scanning part [] Scanning part [document.zip] Attachment validity check: passed. Virus identity found: W32/MyDoom-O Virus identity found: W32/MyDoom-O Virus identity found: W32/MyDoom-O Virus identity found: W32/MyDoom-O
Re: searching a good MRTG/SNMP configuration
* Andreas Bihlmaier [EMAIL PROTECTED] [2007-02-04 14:04]: I guess somebody using OpenBSD already has a nice MRTG configuration showing: IN/OUT traffic [CPU] load memory usage some stuff about pf (states, blocks/pass) (using this patch: http://www.packetmischief.ca/openbsd/snmp/) save yourself the trouble and just go for ports/sysutils/symon/ -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: arptables: unable to enter address
John wrote: And, as far as getting the obsd box to talk to the modem was concerned, that's it! There is other stuff involved in getting the box to talk to the lan and v/v. I found it useful getting just the box to work with the modem, it's not clear in your message if that is also your situation. Thanks for trying to help, John. I'm able to get the OpenBSD machine to talk to the cable-modem box. Almost everything works fine. The only problem is this repeated log message every fifteen minutes: Feb 3 15:13:58 rock /bsd: arplookup: unable to enter address for 24.aaa.bbb.ccc (24.aaa.bbb.ccc is the WAN address of the cable-modem box.) I don't know if this is serious. If it is, I'd like to solve it; if not, I'd like to turn it off. J
apmd -f /dev/acpi?
Hi, I just downloaded cd40.iso from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots and installed openbsd on my laptop because I thought the kernel would be -current but when booting I tried bsd -c and then UKC enable acpi but nothing happened, so that I went to the site and downloaded bsd and bsd.mp, copied them to / with the names bsd.acpi and bsd.mp.acpi Then I rebooted (bsd.acpi -c and/or bsd.mp.acpi -c) and UKC said 385 acpi0 enabled and everything was looking fine (apart from the problem that I didn't get any dhcp offer?). I wait until it's up and then make sudo apmd -f /dev/acpi with the hope that I could get apm to work over acpi but when I type zzz or apm -S nothing happens... I know acpi is under development and I am not complaining at all. I just want to check out I did everything correctly or not. Do you see something wrong? I can provide you with dmesg if you wish but it looked fine to me. thanks, Pau
Re: apmd -f /dev/acpi?
On Sunday 04 February 2007 12:50, Pau Amaro-Seoane wrote: Hi, I just downloaded cd40.iso from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots and installed openbsd on my laptop because I thought the kernel would be -current but when booting I tried bsd -c and then UKC enable acpi but nothing happened, so that I went to the site and downloaded bsd and bsd.mp, copied them to / with the names bsd.acpi and bsd.mp.acpi I have seen many warnings from the developers and other knowledgeable people on this list to not mix the -current and snapshot, so may be that is your problem. Then I rebooted (bsd.acpi -c and/or bsd.mp.acpi -c) and UKC said 385 acpi0 enabled and everything was looking fine (apart from the problem that I didn't get any dhcp offer?). I wait until it's up and then make sudo apmd -f /dev/acpi with the hope that I could get apm to work over acpi but when I type zzz or apm -S nothing happens... I know acpi is under development and I am not complaining at all. I just want to check out I did everything correctly or not. Do you see something wrong? I find that ACPI and APM on OpenBSD works just like or probably better than it does on other OS'es and distros, for my purposes. I am not very knowledgeable about ACPI or APM but can provide you with what happens on my system (this is just a desktop -- I am going to try this on my laptop as soon as I get a chance). When I tried to do a boot -c, it did not work for me. Basically, the keyboard would not function, so even though I got the UKC prompt, I could not enter enable ACPI. So I did a config -ef /bsd from the root prompt, enabled acpi and rebooted. zzz and apm gave me the following . .. $ zzz Suspending system... $ $ apm Battery state: absent, 0% remaining, unknown life estimate A/C adapter state: not known Performance adjustment mode: manual (2412 MHz) Here is part of my dmesg that had stuff about apm and acpi. OpenBSD 4.0-current (GENERIC) #1351: Wed Jan 24 20:29:10 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (AuthenticAMD 686-class, 512KB L2 cache) 2.42 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16 real mem = 3488051200 (3406300K) avail mem = 3192864768 (3118032K) using 4256 buffers containing 174526464 bytes (170436K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+ BIOS, date 12/22/06, BIOS32 rev. 0 @ 0xf22f0, SMBIOS rev. 2.4 @ 0xf (76 entries) bios0: ASUSTeK Computer INC. M2N-SLI DELUXE apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 3.0 @ 0xf/0xdc44 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdb10/304 (17 entries) pcibios0: bad IRQ table checksum pcibios0: PCI BIOS has 17 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 5 10 11 pcibios0: no compatible PCI ICU found pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #7 is the last bus bios0: ROM list: 0xc/0xec00 0xd/0x2800! acpi0 at mainbus0: rev 2 acpi0: tables DSDT FACP HPET MCFG APIC acpitimer at acpi0 not configured acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (HUB0) acpibtn at acpi0 not configured acpitz at acpi0 not configured I can provide you with dmesg if you wish but it looked fine to me. thanks, Pau !DSPAM:1,45c63d9f148709730998309! -- Vijay Sankar ForeTell Technologies Limited 59 Flamingo Avenue, Winnipeg, MB, Canada R3J 0X6 Phone: +1 (204) 885-9535, E-Mail: [EMAIL PROTECTED]
Re: apmd -f /dev/acpi?
On 2007/02/04 19:50, Pau Amaro-Seoane wrote: I just downloaded cd40.iso from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots and installed openbsd on my laptop because I thought the kernel would be -current but when booting I tried bsd -c and then UKC enable acpi but nothing happened, ... Then I rebooted (bsd.acpi -c and/or bsd.mp.acpi -c) and UKC said 385 acpi0 enabled and everything was looking fine (apart from the problem that I didn't get any dhcp offer?). Sounds like you downloaded a snapshot cd40.iso, but then proceeded to install files from /pub/OpenBSD/4.0/... (i.e. 4.0 release). If so, you now have mismatched kernel and userland; at the boot prompt, type 'bsd.rd', then proceed with an upgrade install, making sure to set the ftp path to /pub/OpenBSD/snapshots/... I can provide you with dmesg if you wish but it looked fine to me. People don't just ask for a dmesg to see if 'it looks fine', it also shows: machine architecture, which kernel you're running, exact hardware in the machine (including version numbers of the hardware, BIOS version in some cases), IRQ routing, etc. These aren't always useful all the time, but the times when they are needed, having them right there in the first email saves a back-and-forth exchange to get necessary information.
Re: apmd -f /dev/acpi?
On Sun, 4 Feb 2007 19:50:26 +0100 Pau Amaro-Seoane [EMAIL PROTECTED] wrote: I just downloaded cd40.iso from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots and installed openbsd on my laptop because I thought the kernel would be -current but when booting I tried bsd -c and then UKC enable acpi but nothing happened, so that I went to the site and downloaded bsd and bsd.mp, copied them to / with the names bsd.acpi and bsd.mp.acpi Then I rebooted (bsd.acpi -c and/or bsd.mp.acpi -c) and UKC said 385 acpi0 enabled and everything was looking fine (apart from the problem that I didn't get any dhcp offer?). With problems like these a dmesg will make people be more interested in your problem. Without that advice is most likely a best guess. // nick
Re: apmd -f /dev/acpi?
On 2007 Feb 04 (Sun) at 19:50:26 +0100 (+0100), Pau Amaro-Seoane wrote: :I wait until it's up and then make sudo apmd -f /dev/acpi with the hope that I :could get apm to work over acpi but when I type zzz or apm -S nothing :happens... suspend is not yet supported in acpi. -- Horses are forbidden to eat fire hydrants in Marshalltown, Iowa.
Re: arptables: unable to enter address
On 2/4/07, J. Alfred Prufrock [EMAIL PROTECTED] wrote: John wrote: And, as far as getting the obsd box to talk to the modem was concerned, that's it! There is other stuff involved in getting the box to talk to the lan and v/v. I found it useful getting just the box to work with the modem, it's not clear in your message if that is also your situation. Thanks for trying to help, John. I'm able to get the OpenBSD machine to talk to the cable-modem box. Almost everything works fine. The only problem is this repeated log message every fifteen minutes: Feb 3 15:13:58 rock /bsd: arplookup: unable to enter address for 24.aaa.bbb.ccc (24.aaa.bbb.ccc is the WAN address of the cable-modem box.) I don't know if this is serious. If it is, I'd like to solve it; if not, I'd like to turn it off. It's curious that the outside interface address on the cable modem is showing up for any reason on the internal network. If your modem is configured as a routing device, there's no reason you should see that. You might use tcpdump or similar on your internal network to determine what kind of traffic it relates to. Note also that figuring this out is a bit harder if you don't understand the overall architecture of what things are set up like now and how you want them to be set up in the end. Might help if you diagram it out, indicate IP addresses and subnets, and so on. DS
Re: arptables: unable to enter address, TCPDUMP
Darren Spruell wrote: It's curious that the outside interface address on the cable modem is showing up for any reason on the internal network. Right, this is what first puzzled me too. You might use tcpdump or similar on your internal network to determine what kind of traffic it relates to. tcpdump -vv -x -l results attached below. Might help if you diagram it out, indicate IP addresses and subnets, and so on. The setup right now: WAN -- (WAN 24.aaa.bbb.ccc) SBG1000 cable-modem (LAN 192.168.0.1) -- (dc0: 192.168.0.10) OpenBSD (rock) (fxp0: 192.168.1.11) -- other machines, phone, etc. I hope the diagram above is clear. Basically, the WAN talks to the SBG1000, which talks to the OpenBSD box, which talks to the inside machines. The two IPs on each box show inward and outward addresses. (I assume I shouldn't show my real IP or MAC addresses in public.) The entire setup works; it just gives me the following message: Feb 4 19:14:03 rock /bsd: arplookup: unable to enter address for 24.aaa.bbb.ccc The SBG1000 does NAT and runs a DHCP server. I tried turning those off so that the OpenBSD box would get its IP address directly from the ISP's server, but that didn't fix the problem: I still got the same arptables message, but with a different IP address. I just ran tcpdump; here's the line at which I get the error/warning/log message: 19:14:03.562039 arp who-has rock tell 24.aaa.bbb.ccc [Note: 24.aaa.bbb.ccc is the cable-modem box's WAN address.] 0001 0800 0604 0001 000b 06bc 7b0e 1891 8674 c0a8 000a 1102 1fdc c0a8 6401 008a 00bb 2046 4445 19:14:03.562118 arp reply rock is-at 00:11:22:33:44:55 [Note: 00:11:22:33:44:55 is the OpenBSD box's outward-facing NIC's MAC address.] 0001 0800 0604 0002 0020 781f 00af c0a8 000a 000b 06bc 7b0e 1891 8674 1102 1fdc c0a8 6401 008a 00bb 2046 4445 Thanks for trying to help, guys. J
Re: arptables: unable to enter address, TCPDUMP
On Sunday 04 February 2007 18:37, J. Alfred Prufrock wrote: Darren Spruell wrote: It's curious that the outside interface address on the cable modem is showing up for any reason on the internal network. Right, this is what first puzzled me too. Possibly a silly question -- how are you connecting the cable modem to your OpenBSD server's external interface? Are they all plugged into a switch or hub or are you using a cable from the external interface directly to the cable modem? You might use tcpdump or similar on your internal network to determine what kind of traffic it relates to. tcpdump -vv -x -l results attached below. Might help if you diagram it out, indicate IP addresses and subnets, and so on. The setup right now: WAN -- (WAN 24.aaa.bbb.ccc) SBG1000 cable-modem (LAN 192.168.0.1) -- (dc0: 192.168.0.10) OpenBSD (rock) (fxp0: 192.168.1.11) -- other machines, phone, etc. I hope the diagram above is clear. Basically, the WAN talks to the SBG1000, which talks to the OpenBSD box, which talks to the inside machines. The two IPs on each box show inward and outward addresses. (I assume I shouldn't show my real IP or MAC addresses in public.) The entire setup works; it just gives me the following message: Feb 4 19:14:03 rock /bsd: arplookup: unable to enter address for 24.aaa.bbb.ccc The SBG1000 does NAT and runs a DHCP server. I tried turning those off so that the OpenBSD box would get its IP address directly from the ISP's server, but that didn't fix the problem: I still got the same arptables message, but with a different IP address. I just ran tcpdump; here's the line at which I get the error/warning/log message: 19:14:03.562039 arp who-has rock tell 24.aaa.bbb.ccc [Note: 24.aaa.bbb.ccc is the cable-modem box's WAN address.] 0001 0800 0604 0001 000b 06bc 7b0e 1891 8674 c0a8 000a 1102 1fdc c0a8 6401 008a 00bb 2046 4445 19:14:03.562118 arp reply rock is-at 00:11:22:33:44:55 [Note: 00:11:22:33:44:55 is the OpenBSD box's outward-facing NIC's MAC address.] 0001 0800 0604 0002 0020 781f 00af c0a8 000a 000b 06bc 7b0e 1891 8674 1102 1fdc c0a8 6401 008a 00bb 2046 4445 Thanks for trying to help, guys. J !DSPAM:1,45c689a494861220213263! -- Vijay Sankar ForeTell Technologies Limited 59 Flamingo Avenue, Winnipeg, MB, Canada R3J 0X6 Phone: +1 (204) 885-9535, E-Mail: [EMAIL PROTECTED]
Re: arptables: unable to enter address, TCPDUMP
On 2/4/07, J. Alfred Prufrock [EMAIL PROTECTED] wrote: tcpdump -vv -x -l results attached below. I just ran tcpdump; here's the line at which I get the error/warning/log message: 19:14:03.562039 arp who-has rock tell 24.aaa.bbb.ccc [Note: 24.aaa.bbb.ccc is the cable-modem box's WAN address.] 0001 0800 0604 0001 000b 06bc 7b0e 1891 8674 c0a8 000a 1102 1fdc c0a8 6401 008a 00bb 2046 4445 19:14:03.562118 arp reply rock is-at 00:11:22:33:44:55 [Note: 00:11:22:33:44:55 is the OpenBSD box's outward-facing NIC's MAC address.] 0001 0800 0604 0002 0020 781f 00af c0a8 000a 000b 06bc 7b0e 1891 8674 1102 1fdc c0a8 6401 008a 00bb 2046 4445 Grab that exchange again with the -n flag to tcpdump. Include the MAC address(es) of the cable modem if you can get them. DS
Re: arptables: unable to enter address, TCPDUMP
On 2/4/07, J. Alfred Prufrock [EMAIL PROTECTED] wrote: PS: I notice that when I reply-all to Vijay, Darren's and John's email addresses also show up. What's the etiquette here? Should I reply to just Vijay and misc, or to everyone whose address is included? Or will the list-manager automatically figure it out? Thanks. Depends on who you talk to. Some subscribers get really pissy when you email them on a mailing list reply because they're subscribed. But the list doesn't provide a Reply-To header either. I guess the assumption would be that the only reply needed can go to misc@ since everyone who needs to get it is subscribed, and if they're not they should be. DS
Re: arptables: unable to enter address, TCPDUMP
Vijay Sankar wrote: Possibly a silly question -- how are you connecting the cable modem to your OpenBSD server's external interface? Are they all plugged into a switch or hub or are you using a cable from the external interface directly to the cable modem? The external NIC connects directly to the cable modem. The internal NIC connects to a D-Link switch, and the inside machines (on the LAN, behind the OpenBSD box) also connect to the same switch. J PS: I notice that when I reply-all to Vijay, Darren's and John's email addresses also show up. What's the etiquette here? Should I reply to just Vijay and misc, or to everyone whose address is included? Or will the list-manager automatically figure it out? Thanks. The setup right now: WAN -- (WAN 24.aaa.bbb.ccc) SBG1000 cable-modem (LAN 192.168.0.1) -- (dc0: 192.168.0.10) OpenBSD (rock) (fxp0: 192.168.1.11) -- other machines, phone, etc. I hope the diagram above is clear. Basically, the WAN talks to the SBG1000, which talks to the OpenBSD box, which talks to the inside machines. The two IPs on each box show inward and outward addresses.
Re: arptables: unable to enter address, TCPDUMP
Darren Spruell wrote: Grab that exchange again with the -n flag to tcpdump. Include the MAC address(es) of the cable modem if you can get them. Here it is: 00:14:04.475261 arp who-has 192.168.0.10 tell 24.aaa.bbb.ccc 0001 0800 0604 0001 000b 06bc 7b0e 1891 8674 c0a8 000a 1102 2234 c0a8 6401 008a 00bb 2046 4445 00:14:04.475348 arp reply 192.168.0.10 is-at 0:20:78:1f:0:af 0001 0800 0604 0002 0020 781f 00af c0a8 000a 000b 06bc 7b0e 1891 8674 1102 2234 c0a8 6401 008a 00bb 2046 4445 Did you mean get the MAC addresses from tcpdump? I didn't see the cable modem box's MAC addresses in the dump file. MAC address of OpenBSD PC's external NIC: 00:20:78:1f:00:af Two MAC addresses listed in cable-modem box's admin screen: 00:0B:06:BC:7B:0A (labelled Self) 00:0B:06:BC:7B:0E (labelled Learned). From the way they're labelled, I'm guessing the former is the cable- modem box's external address and the latter its internal address. Not sure how to confirm that guess. J
Re: High Interrupt Load cased by pciide with sparc64 on SUN V210
The high interrupt load vanished after removing the CD-ROM drives from both V210, as suggested by Mark Kettenis. Now the CPU load is down to 0%, as one expects, and the systems are much more performant and responsive than before :-) # iostat -w 1 ttycd0 sd0 cpu tin tout KB/t t/s MB/s KB/t t/s MB/s us ni sy in id 0 21 0.00 0 0.00 8.18 2 0.01 3 0 0 36 61 0 172 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 57 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 57 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 57 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 57 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 57 0.00 0 0.00 16.00 2 0.03 0 0 0 0100 0 57 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 ^C # Thanks to Mark for his suggestion, Rolf
