Re: Nfsen and php problems...?
After nfsen -r live disappear First key message:
Mar 14 14:05:00 netflow /usr/local/bin/nfcapd[2154]: Ident:
'boldsoft_railcom' Flows: 70290, Packets: 688865, Bytes: 293528363, Sequence
Errors: 0, Bad Packets: 0
Mar 14 14:05:00 netflow /usr/local/bin/nfcapd[2148]: Ident: 'boldsoft_voip'
Flows: 918, Packets: 23094, Bytes: 16605621, Sequence Errors: 0, Bad
Packets: 0
Mar 14 14:05:00 netflow /usr/local/bin/nfcapd[2145]: Ident: 'boldsoft_tower'
Flows: 11400, Packets: 93012, Bytes: 48901004, Sequence Errors: 0, Bad
Packets: 0
Mar 14 14:05:10 netflow /usr/local/bin/nfcapd[2151]: Ident: 'boldsoft_dial'
Flows: 734, Packets: 7264, Bytes: 3251532, Sequence Errors: 0, Bad Packets:
0
Mar 14 14:05:15 netflow nfsen[2575]: 0 channels/alerts to profile
Mar 14 14:05:15 netflow nfsen[2575]: Update profile live in group .
Mar 14 14:05:17 netflow nfsen[3325]: Plugin Cycle: Time: 200803141400,
Profile: live, Group: ., Module: PortTracker,
Mar 14 14:05:29 netflow nfsen[2575]: Run expire at Fri Mar 14 14:05:00 2008
Mar 14 14:05:29 netflow nfsen[2575]: End expire at Fri Mar 14 14:05:00 2008
Balgaa
Richard Daemon wrote:
>
> Hi,
>
> I'm really stumped on this and any help would be greatly appreciated.
>
> When trying to load the nfsen/nfsen.php page I get:
>
> ERROR: nfsend connect() error: No such file or directory!
> ERROR: nfsend - connection failed!!
> ERROR: Can not initialize globals!
>
> I'm sure I have it configured properly and started properly as the
> documentation states, I've read over and over and over again...
>
> I've used the default ./etc/nfsen-dist.conf > ./etc/nfsen.conf (tried
> with and without changing HTMLDIR)
>
> I'm running httpd -u (non-chroot), php enabled, configured in
> httpd.conf and tested ok - httpd chrooted works less, for now.
>
> I did the mkdir /data then ran the ./install.pl etc/nfsen.conf
>
> Started it with: ./nfsen start and it starts ok.
>
> in nfsen.conf I tried with /var/www/nfsen and /var/www/htdocs/nfsen
> (same results)...
>
> %sources = (
> #'upstream1'=> { 'port'=> '9995', 'col' => '#ff',
> 'type' => 'netflow' },
> 'slacker'=> { 'port'=> '9995', 'col' => '#ff', 'type'
> => 'netflow' },
> #'peer1'=> { 'port'=> '9996', 'col' => '#ff' },
> );
>
> Then when I try http://slacker/nfsen/nfsen.php I get:
>
> ERROR: nfsend connect() error: No such file or directory!
> ERROR: nfsend - connection failed!!
> ERROR: Can not initialize globals!in red.
>
> pfflowd -d -n 192.168.0.10 running from remote host.
>
> I tried 1.3 and 1.3b, including nfsen -r live.
>
> I also get this in /var/log/messages:
> Feb 16 22:50:15 slacker nfsen[689]: Error reading channel stat
> information. Missing key 'first'
>
> $ netstat -anf inet |grep 995
> udp0 0 *.9995 *.*
>
> Running OpenBSD 4.2-stable.
>
> Did I miss anything? Am I doing something wrong?
>
> Any help is greatly appreciated!
>
>
>
--
View this message in context:
http://www.nabble.com/Nfsen-and-php-problems...--tp15526200p16045017.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Nfsen and php problems...?
Hello Peter,
After I nfsen -r live command, statistics table changed to like below.
Statistics timeslot Mar 14 2008 - 11:15
Channel: Flows: Packets: Traffic:
all: tcp: udp: icmp: other: all: tcp: udp: icmp: other: all: tcp: udp:
icmp: other:
boldsoft_railcom 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0
/s 0 b/s 0 b/s 0 b/s 0 b/s 0 b/s
boldsoft_dial 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s
0 b/s 0 b/s 0 b/s 0 b/s 0 b/s
boldsoft_voip 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s
0 b/s 0 b/s 0 b/s 0 b/s 0 b/s
boldsoft_tower 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s 0 /s
0 b/s 0 b/s 0 b/s 0 b/s 0 b/s
Display: Sum Rate
Any configuration problem?
Balgaa
Richard Daemon wrote:
>
> Hi,
>
> I'm really stumped on this and any help would be greatly appreciated.
>
> When trying to load the nfsen/nfsen.php page I get:
>
> ERROR: nfsend connect() error: No such file or directory!
> ERROR: nfsend - connection failed!!
> ERROR: Can not initialize globals!
>
> I'm sure I have it configured properly and started properly as the
> documentation states, I've read over and over and over again...
>
> I've used the default ./etc/nfsen-dist.conf > ./etc/nfsen.conf (tried
> with and without changing HTMLDIR)
>
> I'm running httpd -u (non-chroot), php enabled, configured in
> httpd.conf and tested ok - httpd chrooted works less, for now.
>
> I did the mkdir /data then ran the ./install.pl etc/nfsen.conf
>
> Started it with: ./nfsen start and it starts ok.
>
> in nfsen.conf I tried with /var/www/nfsen and /var/www/htdocs/nfsen
> (same results)...
>
> %sources = (
> #'upstream1'=> { 'port'=> '9995', 'col' => '#ff',
> 'type' => 'netflow' },
> 'slacker'=> { 'port'=> '9995', 'col' => '#ff', 'type'
> => 'netflow' },
> #'peer1'=> { 'port'=> '9996', 'col' => '#ff' },
> );
>
> Then when I try http://slacker/nfsen/nfsen.php I get:
>
> ERROR: nfsend connect() error: No such file or directory!
> ERROR: nfsend - connection failed!!
> ERROR: Can not initialize globals!in red.
>
> pfflowd -d -n 192.168.0.10 running from remote host.
>
> I tried 1.3 and 1.3b, including nfsen -r live.
>
> I also get this in /var/log/messages:
> Feb 16 22:50:15 slacker nfsen[689]: Error reading channel stat
> information. Missing key 'first'
>
> $ netstat -anf inet |grep 995
> udp0 0 *.9995 *.*
>
> Running OpenBSD 4.2-stable.
>
> Did I miss anything? Am I doing something wrong?
>
> Any help is greatly appreciated!
>
>
>
--
View this message in context:
http://www.nabble.com/Nfsen-and-php-problems...--tp15526200p16044913.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Nfsen and php problems...?
Hello Peter,
I saw that there no information on statistics table.
Statistics timeslot Mar 14 2008 - 01:35
Channel: Flows: Packets: Traffic:
all: tcp: udp: icmp: other: all: tcp: udp: icmp: other: all: tcp: udp:
icmp: other:
boldsoft_railcom x x x x x x x x x x x x x x x
boldsoft_dial x x x x x x x x x x x x x x x
boldsoft_voip x x x x x x x x x x x x x x x
boldsoft_tower x x x x x x x x x x x x x x x
Display: Sum Rate x: No Data available
Balgaa
Richard Daemon wrote:
>
> Hi,
>
> I'm really stumped on this and any help would be greatly appreciated.
>
> When trying to load the nfsen/nfsen.php page I get:
>
> ERROR: nfsend connect() error: No such file or directory!
> ERROR: nfsend - connection failed!!
> ERROR: Can not initialize globals!
>
> I'm sure I have it configured properly and started properly as the
> documentation states, I've read over and over and over again...
>
> I've used the default ./etc/nfsen-dist.conf > ./etc/nfsen.conf (tried
> with and without changing HTMLDIR)
>
> I'm running httpd -u (non-chroot), php enabled, configured in
> httpd.conf and tested ok - httpd chrooted works less, for now.
>
> I did the mkdir /data then ran the ./install.pl etc/nfsen.conf
>
> Started it with: ./nfsen start and it starts ok.
>
> in nfsen.conf I tried with /var/www/nfsen and /var/www/htdocs/nfsen
> (same results)...
>
> %sources = (
> #'upstream1'=> { 'port'=> '9995', 'col' => '#ff',
> 'type' => 'netflow' },
> 'slacker'=> { 'port'=> '9995', 'col' => '#ff', 'type'
> => 'netflow' },
> #'peer1'=> { 'port'=> '9996', 'col' => '#ff' },
> );
>
> Then when I try http://slacker/nfsen/nfsen.php I get:
>
> ERROR: nfsend connect() error: No such file or directory!
> ERROR: nfsend - connection failed!!
> ERROR: Can not initialize globals!in red.
>
> pfflowd -d -n 192.168.0.10 running from remote host.
>
> I tried 1.3 and 1.3b, including nfsen -r live.
>
> I also get this in /var/log/messages:
> Feb 16 22:50:15 slacker nfsen[689]: Error reading channel stat
> information. Missing key 'first'
>
> $ netstat -anf inet |grep 995
> udp0 0 *.9995 *.*
>
> Running OpenBSD 4.2-stable.
>
> Did I miss anything? Am I doing something wrong?
>
> Any help is greatly appreciated!
>
>
>
--
View this message in context:
http://www.nabble.com/Nfsen-and-php-problems...--tp15526200p16044807.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Nfsen and php problems...?
Hello Peter,
I installed Nfsen + Nfdump on Fedora Core 8 and it is working fine.
But I saw some message like:
Mar 14 13:35:00 netflow /usr/local/bin/nfcapd[2154]: Ident:
'boldsoft_railcom' Flows: 64080, Packets: 601491, Bytes: 259641123, Sequence
Errors: 0, Bad Packets: 0
Mar 14 13:35:00 netflow /usr/local/bin/nfcapd[2145]: Ident: 'boldsoft_tower'
Flows: 11400, Packets: 88151, Bytes: 23231888, Sequence Errors: 0, Bad
Packets: 0
Mar 14 13:35:02 netflow /usr/local/bin/nfcapd[2148]: Ident: 'boldsoft_voip'
Flows: 1436, Packets: 62183, Bytes: 37656718, Sequence Errors: 0, Bad
Packets: 0
Mar 14 13:35:10 netflow /usr/local/bin/nfcapd[2151]: Ident: 'boldsoft_dial'
Flows: 30, Packets: 2243, Bytes: 170321, Sequence Errors: 0, Bad Packets: 0
Mar 14 13:35:15 netflow nfsen[2575]: 0 channels/alerts to profile
Mar 14 13:35:15 netflow nfsen[2575]: Update profile live in group .
Mar 14 13:35:15 netflow nfsen[2575]: Error reading channel stat information.
Missing key 'first'
Mar 14 13:35:17 netflow nfsen[2575]:last message repeated 3 times
Mar 14 13:35:17 netflow nfsen[2707]: Plugin Cycle: Time: 200803141330,
Profile: live, Group: ., Module: PortTracker,
Mar 14 13:35:24 netflow nfsen[2575]: Run expire at Fri Mar 14 13:35:00 2008
Mar 14 13:35:24 netflow nfsen[2575]: End expire at Fri Mar 14 13:35:00 2008
I don't know "Error reading channel stat information. Missing key 'first'"
normal or not?
Balgaa
Richard Daemon wrote:
>
> Hi,
>
> I'm really stumped on this and any help would be greatly appreciated.
>
> When trying to load the nfsen/nfsen.php page I get:
>
> ERROR: nfsend connect() error: No such file or directory!
> ERROR: nfsend - connection failed!!
> ERROR: Can not initialize globals!
>
> I'm sure I have it configured properly and started properly as the
> documentation states, I've read over and over and over again...
>
> I've used the default ./etc/nfsen-dist.conf > ./etc/nfsen.conf (tried
> with and without changing HTMLDIR)
>
> I'm running httpd -u (non-chroot), php enabled, configured in
> httpd.conf and tested ok - httpd chrooted works less, for now.
>
> I did the mkdir /data then ran the ./install.pl etc/nfsen.conf
>
> Started it with: ./nfsen start and it starts ok.
>
> in nfsen.conf I tried with /var/www/nfsen and /var/www/htdocs/nfsen
> (same results)...
>
> %sources = (
> #'upstream1'=> { 'port'=> '9995', 'col' => '#ff',
> 'type' => 'netflow' },
> 'slacker'=> { 'port'=> '9995', 'col' => '#ff', 'type'
> => 'netflow' },
> #'peer1'=> { 'port'=> '9996', 'col' => '#ff' },
> );
>
> Then when I try http://slacker/nfsen/nfsen.php I get:
>
> ERROR: nfsend connect() error: No such file or directory!
> ERROR: nfsend - connection failed!!
> ERROR: Can not initialize globals!in red.
>
> pfflowd -d -n 192.168.0.10 running from remote host.
>
> I tried 1.3 and 1.3b, including nfsen -r live.
>
> I also get this in /var/log/messages:
> Feb 16 22:50:15 slacker nfsen[689]: Error reading channel stat
> information. Missing key 'first'
>
> $ netstat -anf inet |grep 995
> udp0 0 *.9995 *.*
>
> Running OpenBSD 4.2-stable.
>
> Did I miss anything? Am I doing something wrong?
>
> Any help is greatly appreciated!
>
>
>
--
View this message in context:
http://www.nabble.com/Nfsen-and-php-problems...--tp15526200p16044729.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: OpenBSD PRNG DNS Cache Poisoning and Predictable IP ID Weakness - fixed?
* Amarendra Godbole <[EMAIL PROTECTED]> [2008-03-14 08:37:18]: > DeepSight alert services (Symantec) notified me that OpenBSD has also > fixed the DNS cache poisoning and predictable IP ID weakness. I also > see PRNG related changes to 4.3. If my memory serves me right, my > impression was this was not an issue that bothered OBSD much, and as > such the developers had decided they won't (?) fix it. I would > appreciate to get an insight as to why this change in decision took > place (yeah, I am also okay if I get an answer like "some dev had some > time at hand". :)) > > My intention is not to question as to why this was fixed, but as to > why a change in decision from "not fix -> fix". Thanks. > > -Amarendra > 16 bits for a pseudo-random field that has a few constraints on it is pretty bad. That's why anybody would be reluctant to work out some new algorithm, because the problem is not in the algorithm, but in the implementations that need it. You'll probably see this problem crop up over and over and over. I believe what was changed in the Open tree came from / was inspired by DragonFly. -- Travers Buda
OpenBSD PRNG DNS Cache Poisoning and Predictable IP ID Weakness - fixed?
DeepSight alert services (Symantec) notified me that OpenBSD has also fixed the DNS cache poisoning and predictable IP ID weakness. I also see PRNG related changes to 4.3. If my memory serves me right, my impression was this was not an issue that bothered OBSD much, and as such the developers had decided they won't (?) fix it. I would appreciate to get an insight as to why this change in decision took place (yeah, I am also okay if I get an answer like "some dev had some time at hand". :)) My intention is not to question as to why this was fixed, but as to why a change in decision from "not fix -> fix". Thanks. -Amarendra
Re: Move hard disks in soft raid to new machine
klemen wrote: > Hello > > I have new computer in which I would like to have same things as on old > one (OpenBSD 4.2). In old one have software raid with two 500g ide drives. > How will raid "react" if I move both disks to new computer with > completely different hardware. depends how completely different you are talking about. :) If you are going from an amd64 system to a Sparc64, it won't work for a lot of reasons long before you get to RAID. However, I suspect by "completely different", you mean "80% the same", such as from an AMD64 to another AMD64 or i386 to another i386, (or even i386 to a newer amd64) in which case, it should just work, again having nothing to do with the (unspecified) software RAID system in use. Granted, since we are missing all specifics here, you win nothing for coming up with a wacked scenario that it won't work in (I can think of a few), but since the software RAID partition is just a partition of the disk, if the system boots (indicating the partitioning is good), RAID will usually "just work", and it will almost always boot when moving around on the same platform. Nick.
Problems with (em) on Nexcom NSA 1180
I have recently acquired, 3 * Nexcom NSA 1108 units - with the intention of using them as OpenBSD routers. Information about the unit can be found here :- http://www.nexcomuk.co.uk/product/productshow.jsp?iid=13&pid=692 The unit has the following onboard LAN chips :- PCI-E GbE: Intel. 82571EB PCI-32 GbE: Intel. 82541PI both of which are listed as being supported in the em manual page - despite this OpenBSD is having problems recognising 8 of the nic ports. The 2 fiber ports always detect fine, the remaining 8 copper ports issue errors in the dmesg. I have tried various things including 1) Updating to most recent bios 2) Disabling acpi, apm, usb 3) Disabling hyperthreading in the bios Whilst I get slightly different results on each test, the 8 copper nics still do not work. As the dmesg output is quite long I have put links to them here. The dmesg was carried out on an OpenBSD snapshot from two days ago. http://www.kgb.org.ru/nexcom/ Interestingly, all ports work fine in freebsd. I know a hardware developer at Nexcom in Taiwan who is keep to help and would be willing to assist OpenBSD developers with hardware documentation. I have used other Nexcom units with OpenBSD, including the NSA1086 and DNA840 - both make ideal routing platforms when used with bgp/ospf/ carp. Thanks, Jules
Re: jetway board sensors (Fintek F71805F)
On Thu, Mar 13, 2008 at 03:06:49AM -0400, Geoff Steckel wrote:
> Theo de Raadt wrote:
>> You really should show a dmesg of your machine.
although this was not addressed at myself.
> sure:
I second that one:
diff to previous (full dmesg below):
--- dmesg.foo Thu Mar 13 23:49:09 2008
+++ dmesg.fins Thu Mar 13 23:48:59 2008
@@ -1,10 +1,10 @@
-OpenBSD 4.2-current (GENERIC) #5: Sun Mar 9 10:26:16 CET 2008
+OpenBSD 4.2-current (GENERIC) #15: Thu Mar 13 23:39:59 CET 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class) 1.51 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3
cpu0: RNG AES AES-CTR SHA1 SHA256 RSA
real mem = 1005023232 (958MB)
-avail mem = 963772416 (919MB)
+avail mem = 963768320 (919MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 05/18/07, BIOS32 rev. 0 @ 0xfa0a0,
SMBIOS rev. 2.3 @ 0xf (34 entries)
bios0: vendor Phoenix Technologies, LTD version "6.00 PG" date 05/18/2007
@@ -89,7 +89,8 @@
midi0 at pcppi0:
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
-npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
+: Fintek F71805F
+fins0 at isa0 port 0x4e/2npx0 at isa0 port 0xf0/16: reported by CPUID; using
exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom0: console
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
There seems to be a small formating issue with the way fins prints
to dmesg, I was first shocked to see npx0 go until I had a closer look.
Otherwise it seems to work just fine
# sysctl hw:
hw.machine=i386
hw.model=VIA Esther processor 1500MHz ("CentaurHauls" 686-class)
hw.ncpu=1
hw.byteorder=1234
hw.physmem=1005023232
hw.usermem=1005019136
hw.pagesize=4096
hw.disknames=wd0,wd1,cd0
hw.diskcount=3
hw.sensors.fins0.temp0=30.00 degC (Temp1)
hw.sensors.fins0.temp1=39.00 degC (Temp2)
hw.sensors.fins0.temp2=127.00 degC (Temp3)
hw.sensors.fins0.fan0=6550 RPM (Fan1)
hw.sensors.fins0.volt0=3.31 VDC (+3.3V)
hw.sensors.fins0.volt1=1.07 VDC (Vtt)
hw.sensors.fins0.volt2=1.44 VDC (Vram)
hw.sensors.fins0.volt3=1.62 VDC (Vchips)
hw.sensors.fins0.volt4=5.13 VDC (+5V)
hw.sensors.fins0.volt5=11.88 VDC (+12V)
hw.sensors.fins0.volt6=1.10 VDC (Vcc 1.5V)
hw.sensors.fins0.volt7=1.47 VDC (VCore)
hw.sensors.fins0.volt8=4.88 VDC (Vsb)
hw.cpuspeed=1501
hw.product=CN700-8237
hw.uuid=Not Set
And temps/voltages do change and temp[01] seems to make sense
They rise a couple of degrees after doing a few minutes of
cat /dev/zero > /dev/null
After adding sensor(fins.temp*) to sym{on,ux}.conf they make nice and
steady graphs.
Thanks so far to Geoff Steckel, I'll this router with your diff for a
while to see if problems arise.
Regards,
ahb
OpenBSD 4.2-current (GENERIC) #15: Thu Mar 13 23:39:59 CET 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: VIA Esther processor 1500MHz ("CentaurHauls" 686-class) 1.51 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3
cpu0: RNG AES AES-CTR SHA1 SHA256 RSA
real mem = 1005023232 (958MB)
avail mem = 963768320 (919MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 05/18/07, BIOS32 rev. 0 @ 0xfa0a0, SMBIOS
rev. 2.3 @ 0xf (34 entries)
bios0: vendor Phoenix Technologies, LTD version "6.00 PG" date 05/18/2007
apm0 at bios0: Power Management spec V1.2 (slowidle)
apm0: AC on, battery charge unknown
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xf/0xc904
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc830/208 (11 entries)
pcibios0: bad IRQ table checksum
pcibios0: PCI BIOS has 11 Interrupt Routing table entries
pcibios0: PCI Exclusive IRQs: 5 10 11
pcibios0: PCI Interrupt Router at 000:17:0 ("VIA VT8237 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x1 0xd/0x800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA CN700 Host" rev 0x00
agp0 at pchb0: v3, aperture at 0xe800, size 0x1000
pchb1 at pci0 dev 0 function 1 "VIA CN700 Host" rev 0x00
pchb2 at pci0 dev 0 function 2 "VIA CN700 Host" rev 0x00
pchb3 at pci0 dev 0 function 3 "VIA PT890 Host" rev 0x00
pchb4 at pci0 dev 0 function 4 "VIA CN700 Host" rev 0x00
pchb5 at pci0 dev 0 function 7 "VIA CN700 Host" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8377 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "VIA S3 Unichrome PRO IGP" rev 0x01
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
xl0 at pci0 dev 8 function 0 "3Com 3c905C 100Base-TX" rev 0x74: irq 11, address
00:04:76:a1:cc:d1
bmtphy0 at xl0 phy 24: Broadcom 3C905C internal PHY, rev. 6
"VIA VT6306 FireWire" rev 0x80 at pci0 dev 10 function 0 not configured
re0 at pci0 dev 11 function 0 "Realtek 8169" rev 0x10: RTL8169/8110SCd
(0x1800), irq 5, address 00:30:18:a8:0f:cc
rgephy0
Re: dvmrpd dies when I add a vlan interface
Digging into this, I noticed that vlan0 has an ifindex of 39, which is greater than MAXVIFS (32). This causes the mfc.ttls[iface->ifindex] = 1 line in the IMSG_MFC_ADD clause of rde_dispatch_imsg to overflow the stack. I tried bumping MAXVIFS to 64, but it's originally defined in /usr/include/netinet/ip_mroute.h, so I'm not certain that will actually work. On 3/13/08, Matthew Dempsky <[EMAIL PROTECTED]> wrote: > I have an OpenBSD 4.2-stable machine with the following interfaces > (it's gross, I know :(): > > * bge1: connected to a OpenBSD 4.3 machine via leased line > * em1: connected to network switch > * vlan0: vlan on em1 > * gif0: tunnel to the 4.3 machine > * bridge0: bridging vlan0 and gif0 > > bge1, em1, and vlan0 are configured with IP addresses. > > If I run dvmrpd on just bge1 and em1, it works fine, and multicast > traffic is routed between subnets like I expect. However, if I also > add vlan0, dvmrpd prints this error to /var/log/daemon.log at startup: > > dvmrpd[1888]: mrt_add_vif: error adding VIF: Invalid argument > > and then exits ~72 seconds later after printing: > > dvmrpd[5569]: fatal in dvmrpe: pipe closed > dvmrpd[1888]: fatal in parent: pipe closed > > dvmrpd works fine on the 4.3 machine, but its interface setup isn't > quite as gross. It does correctly route multicast traffic from vlans > though. > > I'll put together a better bug report this weekend after I can look at > dvmrpd's code some more. I thought I'd mention this briefly in case > anyone more experienced could point out something obviously wrong. > > Thanks.
dvmrpd dies when I add a vlan interface
I have an OpenBSD 4.2-stable machine with the following interfaces (it's gross, I know :(): * bge1: connected to a OpenBSD 4.3 machine via leased line * em1: connected to network switch * vlan0: vlan on em1 * gif0: tunnel to the 4.3 machine * bridge0: bridging vlan0 and gif0 bge1, em1, and vlan0 are configured with IP addresses. If I run dvmrpd on just bge1 and em1, it works fine, and multicast traffic is routed between subnets like I expect. However, if I also add vlan0, dvmrpd prints this error to /var/log/daemon.log at startup: dvmrpd[1888]: mrt_add_vif: error adding VIF: Invalid argument and then exits ~72 seconds later after printing: dvmrpd[5569]: fatal in dvmrpe: pipe closed dvmrpd[1888]: fatal in parent: pipe closed dvmrpd works fine on the 4.3 machine, but its interface setup isn't quite as gross. It does correctly route multicast traffic from vlans though. I'll put together a better bug report this weekend after I can look at dvmrpd's code some more. I thought I'd mention this briefly in case anyone more experienced could point out something obviously wrong. Thanks.
Re: mfi(4) support for SAS8704ELP
Alexander Hall wrote: The man pages for mfi(4) does not mention that mfi supports SAS8704ELP, while the source seems to indicate so. I am about to buy new hardware and I just want to make sure that I do not buy anything non-supported or experimental, so cluesticks are appreciated. I've now ordered a server with an SAS8704ELP now and will report back when I've tested it. /Alexander
Re: sftp logging using chroot internal-sftp in -current
Damien, Thanks for the pointer. I believe the environment is now setup correctly, but I can not get DEBUG3 messages to appear from internal-sftp in authlog. I setup the log device file /ftp_jail/dev/log... [EMAIL PROTECTED]: ls -la /ftp_jail/dev/log srw-rw-rw- 1 root ftp 0 Mar 13 14:31 /ftp_jail/dev/log ...and syslogd points to /ftp_jail/dev/log syslogd -a /ftp_jail/dev/log -a /var/empty/dev/log When I sftp from 192.168.2.2 to the sftp server test0 I now get a line I did not see before, "subsystem request for sftp". As far as I can tell the log device is working correctly. This is the log of a sftp connection. As a test I switched directory, downloaded a test file and then disconnected. As you can see there is no mention in the logs. Mar 13 16:23:12 test0 sshd[24079]: Server listening on 0.0.0.0 port 22. Mar 13 16:23:25 test0 sshd[26118]: Connection from 192.168.2.2 port 48518 Mar 13 16:23:26 test0 sshd[26118]: Failed none for ftp from 192.168.2.2 port 48518 ssh2 Mar 13 16:23:26 test0 sshd[26118]: Failed publickey for ftp from 192.168.2.2 port 48518 ssh2 Mar 13 16:23:28 test0 sshd[26118]: Accepted password for ftp from 192.168.2.2 port 48518 ssh2 Mar 13 16:23:28 test0 sshd[10427]: Changed root directory to "/ftp_jail" Mar 13 16:23:28 test0 sshd[10427]: subsystem request for sftp Mar 13 16:23:44 test0 sshd[10427]: Connection closed by 192.168.2.2 Mar 13 16:23:44 test0 sshd[10427]: Closing connection to 192.168.2.2 This is my /etc/ssh/sshd_config if you can see anything wrong with it. I tried adding "ForceCommand internal-sftp -l DEBUG3" but this caused sshd to error. I appreciate the assistance. http://calomel.org/sftp_chroot.html ## /etc/ssh/sshd_config AllowTcpForwarding no ClientAliveCountMax 3 ClientAliveInterval 0 Compression delayed LoginGraceTime 60s LogLevel DEBUG3 MaxAuthTries 6 PasswordAuthentication yes PermitEmptyPasswords no PermitRootLogin no PermitTunnel no PermitUserEnvironment no Port 22 Protocol 2 StrictModes yes SyslogFacility AUTH TCPKeepAlive yes UseDNS no UsePrivilegeSeparation yes X11Forwarding no ## sftp directives Subsystem sftp internal-sftp -f AUTH -l DEBUG3 Match User ftp ForceCommand internal-sftp ChrootDirectory /ftp_jail http://calomel.org/sftp_chroot.html -- Calomel @ http://calomel.org Open Source Research and Reference On Thu, Mar 13, 2008 at 12:32:04PM +1100, Damien Miller wrote: >On Wed, 12 Mar 2008, Calomel wrote: > >> Is it possible to enable DEBUG logging for internal-sftp in sshd? >> >> Using -current (Mar 12, 2008) and enabling a chroot'd sftp server we can >> get sshd to log initial connections. But, we would also like to log sftp >> activity like uploads, downloads, and directory changes similar to what >> vsftpd does. >> >> The older sftp-server man page had a log facility (-f) and log level (-l) >> options, but those arguments might not have been carried over to >> internal-sftp. >> >> Perhaps the chroot environment keeps us from logging internal-sftp? > >Yes. You should be able to have syslogd(8) listen on /dev/log inside the >chroot to make messages from the internal sftp-server visible. > >-d
"arp info overwritten ..." log message
I would like to block these messages as they fill up /var/log/messages A MS windows server with a trunked interface sends packets with either of its two hardware addresses, causing these messages Regards
short _file in stdio -> fd leak
Hey, So at work we ran into a situation where a process had to fdopen more than 32K files, which lead to a file descriptor leak. The reason for this leak was that while regular fds are ints, _file is a short, so if fdopen got an fd larger than SHRT_MAX, it would get sign-extended and thus become invalid, causing the subsequent fclose to fail. This being FreeBSD, the fix was found and contributed back into FreeBSD's repository by John Baldwin in http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/stdio/fdopen.c.diff?r1=1.8 ;r2=1.9 (and other files; with surrounding discussion on http://docs.freebsd.org/mail/archive/2008/freebsd-arch/20080302.freebsd-arch. html). This fix was also added in NetBSD in http://mail-index.netbsd.org/source-changes/2008/03/13/msg003463.html . I believe this also affects OpenBSD and should probably be looked at. -Jan -- "When it's fall in New York, the air smells as if someone's been frying goats in it, and if you are keen to breathe the best plan is to open a window and stick your head in a building." [demime 1.01d removed an attachment of type application/pgp-signature]
ip(4) still says IP_MAX_MEMBERSHIPS is 20
ip(4) says that IP_MAX_MEMBERSHIPS is 20, but it was bumped to 4095 in rev 1.73 of netinet/in.h. Index: ip.4 === RCS file: /cvs/src/share/man/man4/ip.4,v retrieving revision 1.26 diff -p -u -r1.26 ip.4 --- ip.431 May 2007 19:19:50 - 1.26 +++ ip.413 Mar 2008 16:12:10 - @@ -310,7 +310,7 @@ programs running on multihomed hosts may join the same group on more than one interface. Up to .Dv IP_MAX_MEMBERSHIPS -(currently 20) memberships may be added on a +(currently 4095) memberships may be added on a single socket. .Pp To drop a membership, use:
Re: Howto route IP Broadcasts (255.255.255.255)
Paul de Weerd wrote: On Thu, Mar 13, 2008 at 11:55:53PM +1030, Damon McMahon wrote: On 13/03/2008, at 7:32 PM, Heinrich Rebehn wrote: Do i have to enable broadcasts explicitly ? I could not find anything in the manpages, and googling for "routing broadcasts" or similar yields only pages dealing with routing protocols. Broadcasts can't be routed - it's a violation of the Internet Protocol and so it's the OpenBSD IP stack which is dropping your packets, not pf(4). I guess if you absolutely need to route broadcast packets one option is to use NAT in pf.conf(5), e.g. (not tested) In addition to Damon's remarks, imagine what would happen if broadcasts *were* routed. While imagining this, please remember that a) I'm in no way interested in your (or other peoples) traffic and b) I have limited bandwidth I'd like to use for *MY OWN* traffic. You may want to look into multicast. Paul 'WEiRD' de Weerd Paul, My intention was to route between two *private* subnets, not to weirdnet.nl! No need to worry ;-) I started reading into multicast and found that it is overly complicated and overkill for our purposes. -Heinrich
Re: Possible discrepancy between sshd_config(5) and ssh-agent(1)
On Thu, Mar 13, 2008 at 02:07:57PM +0200, Lars Nood'en wrote:
> http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-agent&sektion=1
> ssh-agent(1)
>...
> -t life
> Set a default value for the maximum lifetime of
> identities added to the agent. The lifetime may
> be specified in seconds or in a time format
> specified in sshd_config(5). A lifetime
> specified for an identity with ssh-add(1)
> overrides this value. Without this option the
> default maximum lifetime is forever...
Both this reference and the quoted reference in ssh-add(1) refer to
a _time format_ defined in sshd_config(5), not a keyword. Look in
sshd_config(5) under TIME FORMATS.
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
Re: Sensors support on proliant DL380 G2
Unix Fan wrote: I did a search around and found something called "SmartStart", Apparently it's a bootable "configuration" utility for your system that configures various settings in NVRAM. You don't really need SmartStart for a DL380 G2, you can press F9 during boot to configure everything via firmware like a normal PC. SmartStart 5.5 is required for DL/ML G1 series machines and older Proliant servers (i.e. 1850, 6500, etc.) You can download SmartStart 5.5 from: ftp://ftp.hp.com/pub/products/servers/supportsoftware/ZIP/smartstart-5.50-0.zip
Re: Howto route IP Broadcasts (255.255.255.255)
On Thu, Mar 13, 2008 at 11:55:53PM +1030, Damon McMahon wrote: > On 13/03/2008, at 7:32 PM, Heinrich Rebehn wrote: >> Do i have to enable broadcasts explicitly ? I could not find anything in >> the manpages, and googling for "routing broadcasts" or similar yields only >> pages dealing with routing protocols. > > Broadcasts can't be routed - it's a violation of the Internet Protocol and > so it's the OpenBSD IP stack which is dropping your packets, not pf(4). I > guess if you absolutely need to route broadcast packets one option is to > use NAT in pf.conf(5), e.g. (not tested) In addition to Damon's remarks, imagine what would happen if broadcasts *were* routed. While imagining this, please remember that a) I'm in no way interested in your (or other peoples) traffic and b) I have limited bandwidth I'd like to use for *MY OWN* traffic. You may want to look into multicast. Paul 'WEiRD' de Weerd -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: dhcrelay on carp interface (above vlan)
Hi, I think a good solutions is to look if the given interface is a carp interface and to figure out the carpdev interface. Then this can be used to listen on. But my programming skills are really poor, else I would provide a patch... Regards, Falk
Re: Howto route IP Broadcasts (255.255.255.255)
Heinrich, On 13/03/2008, at 7:32 PM, Heinrich Rebehn wrote: Hi All, We have an OpenBSD 4.2-stable router which routes between 5 subnets. On 2 of those subnets we run an application that does "many to many" communication using UDP broadcasts to 255.255.255.255. Unfortunately, the router does not seem to forward these packets. They look like: [EMAIL PROTECTED] [~] # tcpdump -n -v -i vlan0 host 255.255.255.255 tcpdump: listening on vlan0, link-type EN10MB 09:55:04.622293 134.102.176.85.33094 > 255.255.255.255.60001: udp 331 (DF) (ttl 64, id 0, len 359) 09:55:04.696183 134.102.176.52.46247 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) 09:55:05.623102 134.102.176.85.33094 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) 09:55:05.623302 134.102.176.24.56807 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) 09:55:06.627005 134.102.176.24.56807 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) 09:55:07.627214 134.102.176.24.56807 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) Hosts on other subnets do not see the packets, neither do I see them on pflog0, so it seems the packet filter is not to blame. Do i have to enable broadcasts explicitly ? I could not find anything in the manpages, and googling for "routing broadcasts" or similar yields only pages dealing with routing protocols. Thanks for any help! -Heinrich Broadcasts can't be routed - it's a violation of the Internet Protocol and so it's the OpenBSD IP stack which is dropping your packets, not pf(4). I guess if you absolutely need to route broadcast packets one option is to use NAT in pf.conf(5), e.g. (not tested) nat on vlan0 inet udp from 134.102.176.0/24 to 255.255.255.255 port 60001 -> aaa.bbb.ccc.255 where aaa.bbb.ccc.255 is the broadcast address of your other subnet (assuming it's a /24). I've previously used a similar configuration to route NETBIOS Name Service broadcasts to/from MS Windows clients on different subnets, so I see no reason you can't do the same. Please accept my apologies if the syntax is incorrect, I'm sure brighter sparks on this list will correct me! best wishes, Damon
Move hard disks in soft raid to new machine
Hello I have new computer in which I would like to have same things as on old one (OpenBSD 4.2). In old one have software raid with two 500g ide drives. How will raid "react" if I move both disks to new computer with completely different hardware. thanks klemen
dhcrelay on carp interface (above vlan)
Hi, I run a firewall cluster with several vlans configured on one physical interface. On this vlans I have a carp interface. Same on a second firewall node, so failover is fine. To be able to install or boot servers from the network I set up an PXE boot server. But it's a little bit annoying to configure the switch port's vlan each time I want to use PXE boot. That's why I like to use dhcrelay on the firewall. But, there is a problem: dhcrelay can only be started on a numbered interface - as expected. Here this is the carp-interface. But the dhcp/ bootp requests are send via the vlan interface, as I can see with tcpdump. So dhcrelay won't forward any of these requests. Actualy I can have failover between the firewalls with carp, or dhcrelay without carp and only with vlans, but no redundandcy. What a pity. Is there a way to have both, failover and dhcrelay capabilities? Regards, Falk
Re: ftp-proxy and carp
On Wed, Mar 12, 2008 at 12:28:00PM +, Joe Warren-Meeks wrote: > Hey chaps, > > I have a pair of OpenBSD firewalls running CARP Thanks for your help guys. -- joe. Daddy, can we play a game of brinkmanship?
Re: Possible discrepancy between sshd_config(5) and ssh-agent(1)
On 2008-03-13, Lars Noodin <[EMAIL PROTECTED]> wrote: > The lifetime may > be specified in seconds or in a time format > specified in sshd_config(5). It's the *time format* which is specified in sshd_config(5), (in TIME FORMATS at the bottom).
Re: sftp: Umlauts and Spaces in filenames
>From someone who speaks a native language with several "extended characters": even non-unix systems (has Windows earned the "system" status already?) sucks with weird file names. > > That should work.. but, spaces and "extended characters" are so "unclean" in > the Unix world, it was never designed to use them.
Possible discrepancy between sshd_config(5) and ssh-agent(1)
sshd_config(5) does not appear to mention a keyword to set the maximum lifetime for identities. Which keyword does that and what is the syntax? According to the man page ssh-agent(1) the maximum lifetime for the agent to keep identities can be set as an option when running ssh-agent ssh-add, or via sshd_config. I presume I am missing the obvious in sshd_config(5). http://www.openbsd.org/cgi-bin/man.cgi?query=sshd_config&sektion=5 Neither 'lifetime' nor agent are mentioned. 'identity' is mentioned only once and in the context of the keyword KerberosAuthentication. The keyword PubkeyAuthentication appears to apply only to whether public key authentication is allowed, not the lifespan of the identities. Regards -Lars http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-agent&sektion=1 ssh-agent(1) ... -t life Set a default value for the maximum lifetime of identities added to the agent. The lifetime may be specified in seconds or in a time format specified in sshd_config(5). A lifetime specified for an identity with ssh-add(1) overrides this value. Without this option the default maximum lifetime is forever... http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-add&sektion=1 ssh-add(1) ... -t life Set a maximum lifetime when adding identities to an agent. The lifetime may be specified in seconds or in a time format specified in sshd_config(5)...
Re: FIPS 140-2
Theo, As am I, which was the point of the post :). Too many people, in my experience, spend time trying to certify just their solution, and don't take the interfacing systems into consideration. What good is certifying one part of a system when you have crap application code? All it means is that your "pwnage" takes place over a FIPS 140-2 certified secure channel. Too many people use that as an excuse to not do security elsewhere. Many of these people are trying to get Microsoft-based security solutions accredited, and use it as a check box on some spreadsheet to convince management that their solution is more secure just because of a certification that gets invalidated every time you patch the system (Patch Tuesday, anyone?), or change the system so that it doesn't match the baseline. I've seen too many people try to spread the FIPS or Common Criteria magic dust over bad code to get it certified. It doesn't matter what OS you run. Bad code is universal, and completely invalidates any security certification of the underlying system. Mitch -Original Message- From: Theo de Raadt [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 12:02 AM To: Mitch Parker Cc: Ryan McBride; misc@openbsd.org Subject: Re: FIPS 140-2 > What good is an OpenBSD system running with a FIPS 140-2 certified > cryptographic component handling SSL and SSH (using AES-256) if the > interfacing systems aren't also well-protected, and your applications > running on the system don't have safeguards against malicious usage? You're right -- better go back to Windows running FIPS 140-2 certified components I'm very very cynical about FIPS.
Howto route IP Broadcasts (255.255.255.255)
Hi All, We have an OpenBSD 4.2-stable router which routes between 5 subnets. On 2 of those subnets we run an application that does "many to many" communication using UDP broadcasts to 255.255.255.255. Unfortunately, the router does not seem to forward these packets. They look like: [EMAIL PROTECTED] [~] # tcpdump -n -v -i vlan0 host 255.255.255.255 tcpdump: listening on vlan0, link-type EN10MB 09:55:04.622293 134.102.176.85.33094 > 255.255.255.255.60001: udp 331 (DF) (ttl 64, id 0, len 359) 09:55:04.696183 134.102.176.52.46247 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) 09:55:05.623102 134.102.176.85.33094 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) 09:55:05.623302 134.102.176.24.56807 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) 09:55:06.627005 134.102.176.24.56807 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) 09:55:07.627214 134.102.176.24.56807 > 255.255.255.255.60001: [udp sum ok] udp 29 (DF) (ttl 64, id 0, len 57) Hosts on other subnets do not see the packets, neither do I see them on pflog0, so it seems the packet filter is not to blame. Do i have to enable broadcasts explicitly ? I could not find anything in the manpages, and googling for "routing broadcasts" or similar yields only pages dealing with routing protocols. Thanks for any help! -Heinrich Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax :-3341
Re: IP header compression status on OpenBSD
I mean rfc 3544, not rfc 3508 ... But who cares anyway... :-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 12. marts 2008 11:56 To: misc@openbsd.org Subject: IP header compression status on OpenBSD Hi, Does anyone know the status of IPHC over PPP as per RFC2507 and RFC3508 (TCP compression as described in RFC2507 is though not needed) on OpenBSD ? Thanks in advance. Mehdi
Re: jetway board sensors (Fintek F71805F)
Theo de Raadt wrote:
You really should show a dmesg of your machine.
sure:
Jan 10 21:54:31 lib /bsd: OpenBSD 4.2-current (fins) #11: Thu Jan 10
21:29:15 EST 2008
Jan 10 21:54:31 lib /bsd:
[EMAIL PROTECTED]:/doot/4.2snap/src/sys/arch/i386/compile/fins
Jan 10 21:54:31 lib /bsd: cpu0: VIA Esther processor 1500MHz
("CentaurHauls" 686-class) 1.51 GHz
Jan 10 21:54:31 lib /bsd: cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,APIC,SEP,MTRR,PGE,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,SSE3,EST,TM2
Jan 10 21:54:31 lib /bsd: cpu0: RNG AES AES-CTR SHA1 SHA256 RSA
Jan 10 21:54:31 lib /bsd: real mem = 1005023232 (958MB)
Jan 10 21:54:31 lib /bsd: avail mem = 963747840 (919MB)
Jan 10 21:54:31 lib /bsd: mainbus0 at root
Jan 10 21:54:31 lib /bsd: bios0 at mainbus0: AT/286+ BIOS, date
05/16/06, BIOS32 rev. 0 @ 0xfb570, SMBIOS rev. 2.3 @ 0xf (34 entries)
Jan 10 21:54:31 lib /bsd: bios0: vendor Phoenix Technologies, LTD
version "6.00 PG" date 05/16/2006
Jan 10 21:54:31 lib /bsd: apm0 at bios0: Power Management spec V1.2
(slowidle)
Jan 10 21:54:31 lib /bsd: apm0: AC on, battery charge unknown
Jan 10 21:54:31 lib /bsd: acpi at bios0 function 0x0 not configured
Jan 10 21:54:31 lib /bsd: pcibios0 at bios0: rev 2.1 @ 0xf/0xdc84
Jan 10 21:54:31 lib /bsd: pcibios0: PCI IRQ Routing Table rev 1.0 @
0xfdbb0/208 (11 entries)
Jan 10 21:54:31 lib /bsd: pcibios0: bad IRQ table checksum
Jan 10 21:54:31 lib /bsd: pcibios0: PCI BIOS has 11 Interrupt Routing
table entries
Jan 10 21:54:31 lib /bsd: pcibios0: PCI Exclusive IRQs: 5 10 11
Jan 10 21:54:31 lib /bsd: pcibios0: PCI Interrupt Router at 000:17:0
("VIA VT8237 ISA" rev 0x00)
Jan 10 21:54:31 lib /bsd: pcibios0: PCI bus #1 is the last bus
Jan 10 21:54:31 lib /bsd: bios0: ROM list: 0xc/0xfe00 0xd/0x5000!
Jan 10 21:54:31 lib /bsd: cpu0 at mainbus0
Jan 10 21:54:31 lib /bsd: cpu0: unknown Enhanced SpeedStep CPU, msr
0x08100f1308000f13
Jan 10 21:54:31 lib /bsd: cpu0: using only highest and lowest power states
Jan 10 21:54:31 lib /bsd: cpu0: Enhanced SpeedStep 1500 MHz (1004 mV):
speeds: 1500, 800 MHz
Jan 10 21:54:31 lib /bsd: pci0 at mainbus0 bus 0: configuration mode 1
(no bios)
Jan 10 21:54:31 lib /bsd: pchb0 at pci0 dev 0 function 0 "VIA CN700
Host" rev 0x00
Jan 10 21:54:31 lib /bsd: agp0 at pchb0: v3, aperture at 0xe800,
size 0x1000
Jan 10 21:54:31 lib /bsd: pchb1 at pci0 dev 0 function 1 "VIA CN700
Host" rev 0x00
Jan 10 21:54:31 lib /bsd: pchb2 at pci0 dev 0 function 2 "VIA CN700
Host" rev 0x00
Jan 10 21:54:31 lib /bsd: pchb3 at pci0 dev 0 function 3 "VIA PT890
Host" rev 0x00
Jan 10 21:54:31 lib /bsd: pchb4 at pci0 dev 0 function 4 "VIA CN700
Host" rev 0x00
Jan 10 21:54:31 lib /bsd: pchb5 at pci0 dev 0 function 7 "VIA CN700
Host" rev 0x00
Jan 10 21:54:31 lib /bsd: ppb0 at pci0 dev 1 function 0 "VIA VT8377 AGP"
rev 0x00
Jan 10 21:54:31 lib /bsd: pci1 at ppb0 bus 1
Jan 10 21:54:31 lib /bsd: vga1 at pci1 dev 0 function 0 "VIA S3
Unichrome PRO IGP" rev 0x01
Jan 10 21:54:31 lib /bsd: wsdisplay0 at vga1 mux 1: console (80x25,
vt100 emulation)
Jan 10 21:54:31 lib /bsd: wsdisplay0: screen 1-5 added (80x25, vt100
emulation)
Jan 10 21:54:31 lib /bsd: re0 at pci0 dev 8 function 0 "Realtek 8169"
rev 0x10: RTL8169S (0x0400), irq 11, address 00:08:54:d1:c7:eb
Jan 10 21:54:31 lib /bsd: rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 0
Jan 10 21:54:31 lib /bsd: "VIA VT6306 FireWire" rev 0x80 at pci0 dev 10
function 0 not configured
Jan 10 21:54:31 lib /bsd: pciide0 at pci0 dev 15 function 0 "VIA VT6420
SATA" rev 0x80: DMA
Jan 10 21:54:31 lib /bsd: pciide0: using irq 11 for native-PCI interrupt
Jan 10 21:54:31 lib /bsd: wd0 at pciide0 channel 1 drive 0:
Jan 10 21:54:31 lib /bsd: wd0: 16-sector PIO, LBA48, 152627MB, 312581808
sectors
Jan 10 21:54:31 lib /bsd: wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA
mode 5
Jan 10 21:54:31 lib /bsd: pciide1 at pci0 dev 15 function 1 "VIA
VT82C571 IDE" rev 0x06: ATA133, channel 0 configured to compatibility,
channel 1 configured to compatibility
Jan 10 21:54:31 lib /bsd: wd1 at pciide1 channel 0 drive 0:
Jan 10 21:54:31 lib /bsd: wd1: 16-sector PIO, LBA48, 76319MB, 156301488
sectors
Jan 10 21:54:31 lib /bsd: wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA
mode 5
Jan 10 21:54:31 lib /bsd: pciide1: channel 1 disabled (no drives)
Jan 10 21:54:31 lib /bsd: uhci0 at pci0 dev 16 function 0 "VIA VT83C572
USB" rev 0x81: irq 10
Jan 10 21:54:31 lib /bsd: uhci1 at pci0 dev 16 function 1 "VIA VT83C572
USB" rev 0x81: irq 10
Jan 10 21:54:31 lib /bsd: uhci2 at pci0 dev 16 function 2 "VIA VT83C572
USB" rev 0x81: irq 11
Jan 10 21:54:31 lib /bsd: uhci3 at pci0 dev 16 function 3 "VIA VT83C572
USB" rev 0x81: irq 11
Jan 10 21:54:31 lib /bsd: ehci0 at pci0 dev 16 function 4 "VIA VT6202
USB" rev 0x86: irq 5
Jan 10 21:54:31 lib /bsd: ehci0: timed out waiting for BIOS
Jan 10 21:54:31 lib /bsd: usb0 at ehci0: USB revision 2.0
Jan 10 21:54:31 lib /bsd: uhub0 at usb0 "VIA EHCI root hub" rev
2.00/1.00 addr 1
Jan 10 21:54:31 lib
