Re: Unable to complete secure online login

2022-09-14 Thread Stuart Henderson
On 2022/09/13 08:36, Alton Shaw wrote:
>     I am no longer able to log into to my bank using Firefox, Firefox-ESR,
> or Chromium on OpenBSD.  After entering my username and password the
> website responds "/We’re currently having technical issue Please try again
> later./"  The bank's technical supports says that they are not even seeing
> a login attempt at their end. This only happens with the OpenBSD as I am
> able to successfully login on both Windows 10 and Debian regardless of
> browser.  As recently as September 3rd this was not a problem.  I
> regularly run syspatch and pkg_add -u.  Per /var/syspatch the following
> packages were updated on September 3rd: xserver, cron, bgpd, and zlib.

Some websites are fussy about the client user-agent string and won't
let you login (or sometimes access the site at all) with the default ones
used by OpenBSD packages. Try a user-agent switcher extension with various
options (usually best to change the presented OS and not the type of
browser) and see if it helps.



Re: httpd+slowcgi sometimes wrongly interpret next request

2022-09-14 Thread Alexey Vatchenko
> 15 Sep 2022 р. о 13:41 Alexey Vatchenko  wrote:
> 
>> On 12 Aug 2022, at 14:37, Alexey Vatchenko  wrote:
>> 
>>> On 12 Aug 2022, at 13:12, Claudio Jeker  wrote:
>>> 
>>> On Thu, Aug 11, 2022 at 02:00:39PM +0300, Alexey Vatchenko wrote:
 
 I’m getting complains that the problem returned.
 
 But I haven’t applied patch for slowcgi. Is it mandatory? I believe it 
 shouldn’t.
 
 As I mentioned earlier, sometime the client is fast enough to make new 
 request before slowcgi daemon closes connection triggering 
 server_file_error() with EOF (or server_fcgi_error() in your case). So, 
 our goal to get to server_read_http() with reset client structure.
>>> 
>>> I think you need this diff on top of all what is in -current.
>> 
>> Applied on prod again. Waiting :)
> 
> Still complains.

All patches applied don’t fix my issue. I applied my old patch to stop whining.
So if you have something to test, I’m ready. Thank you!

iwx-firmware-20211101.tgz drivers not working with Intel Wireless AC-9560 NIC

2022-09-14 Thread Adam Szewczyk
After installing drivers I have many errors like this:
iwm0: fw chunk addr 0x404000 len 712 failed to load

I saw that similar issue was fixed on freebsd

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249287

BR Adam Szewczyk


re(4) drivers not working

2022-09-14 Thread Adam Szewczyk
After configuring re0 inteface in installer I'm spammed by :
re0: watchdog timeout
messages. Ethernet also won't work. It looks like it is a known problem
also in other bsds.

When cable isn't connected to interface messages error messages not
appearing.

BR Adam Szewczyk


Re: Unable to complete secure online login

2022-09-14 Thread Alton Shaw

You can give username Phineas_T, password b@rnum-1810 a try :-)

On 2022-09-13 19:47, joshua stein wrote:

I don't have an account with them to test, can you provide me your
username and password so I can look into this problem?


Re: Unable to complete secure online login

2022-09-14 Thread Alton Shaw
Thank you Stuart for your suggestion. I tried logging in using the 
add-on /User-Agent Switcher and Manager/ within Firefox set to Windows 
10/Edge but I've received the same response.


Note that I've been able to login in to another banking website with 
OpenBSD/Firefox without issues.


I don't know anything about anything but could it be something related 
to bgpd?  I would like to test the previous version but don't know how 
to rollback a package without blowing up my system.



On 2022-09-14 01:47, Stuart Henderson wrote:

On 2022/09/13 08:36, Alton Shaw wrote:

     I am no longer able to log into to my bank using Firefox, Firefox-ESR,
or Chromium on OpenBSD.  After entering my username and password the
website responds "/We’re currently having technical issue Please try again
later./"  The bank's technical supports says that they are not even seeing
a login attempt at their end. This only happens with the OpenBSD as I am
able to successfully login on both Windows 10 and Debian regardless of
browser.  As recently as September 3rd this was not a problem.  I
regularly run syspatch and pkg_add -u.  Per /var/syspatch the following
packages were updated on September 3rd: xserver, cron, bgpd, and zlib.

Some websites are fussy about the client user-agent string and won't
let you login (or sometimes access the site at all) with the default ones
used by OpenBSD packages. Try a user-agent switcher extension with various
options (usually best to change the presented OS and not the type of
browser) and see if it helps.



Re: Unable to complete secure online login

2022-09-14 Thread Sonic
Probably not your issue but a mistake I made once caused a similar issue.
The ISP provided a /29, the outside interface was configured with all
5 available addresses (4 as aliases). Which could allow me to use
different addresses for different purposes. But in one case I had
natted, in pf, to the interface itself instead of just one address.
Everything worked except for one banking site. Drove me nuts but when
I finally natted to just one address the site worked fine.
My guess is that the round-robin nat nature caused secondary
connections to use a different outbound IP address than the primary
connection creating the failure.
Note to self: don't do this.

Chris

On Wed, Sep 14, 2022 at 10:06 AM Otto Moerbeek  wrote:
>
> On Wed, Sep 14, 2022 at 05:48:22AM -0700, Alton Shaw wrote:
>
> > Thank you Stuart for your suggestion. I tried logging in using the add-on
> > /User-Agent Switcher and Manager/ within Firefox set to Windows 10/Edge but
> > I've received the same response.
> >
> > Note that I've been able to login in to another banking website with
> > OpenBSD/Firefox without issues.
> >
> > I don't know anything about anything but could it be something related to
> > bgpd?  I would like to test the previous version but don't know how to
> > rollback a package without blowing up my system.
>
> Nah, its very unlikely it's bgpd.
>
> What you can try is logging in after clearing cookies and site storage
> or using a private browser window. I have seen browsers adding a
> zillion cookies and generating requests headers that are very big and
> won't make it past the companies firewall unharmed.
>
> Another posibility is that the login process needs third party
> cookies. Try playing with the firefox settings in that area: should be
> under "Privacy and Security".
>
> -Otto
>
> >
> >
> > On 2022-09-14 01:47, Stuart Henderson wrote:
> > > On 2022/09/13 08:36, Alton Shaw wrote:
> > > >  I am no longer able to log into to my bank using Firefox, 
> > > > Firefox-ESR,
> > > > or Chromium on OpenBSD.  After entering my username and password the
> > > > website responds "/We’re currently having technical issue Please try 
> > > > again
> > > > later./"  The bank's technical supports says that they are not even 
> > > > seeing
> > > > a login attempt at their end. This only happens with the OpenBSD as I am
> > > > able to successfully login on both Windows 10 and Debian regardless of
> > > > browser.  As recently as September 3rd this was not a problem.  I
> > > > regularly run syspatch and pkg_add -u.  Per /var/syspatch the following
> > > > packages were updated on September 3rd: xserver, cron, bgpd, and zlib.
> > > Some websites are fussy about the client user-agent string and won't
> > > let you login (or sometimes access the site at all) with the default ones
> > > used by OpenBSD packages. Try a user-agent switcher extension with various
> > > options (usually best to change the presented OS and not the type of
> > > browser) and see if it helps.
> > >
>



Re: Unable to complete secure online login

2022-09-14 Thread Stuart Henderson
On 2022/09/14 05:48, Alton Shaw wrote:
> Thank you Stuart for your suggestion. I tried logging in using the add-on
> /User-Agent Switcher and Manager/ within Firefox set to Windows 10/Edge but
> I've received the same response.

as I said, "usually best to change the presented OS and not the type of browser"

because if the browser name in the user-agent doesn't match other
characteristics of the browser, that may trip the bank's snake oil defences
too.

but it might be that you'll just never get it to work. the person you're
talking to at the bank probably doesn't know the details of this either.

> I don't know anything about anything but could it be something related to
> bgpd?

no.



re(4) drivers not working

2022-09-14 Thread John Verne
A reminder of how to report problems: https://www.openbsd.org/report.html

Specifically, folks here want to see at least a dmesg. But, honestly,
a report that "re isn't working" is (at best) going to be ignored.



Re: Unable to complete secure online login

2022-09-14 Thread Alton Shaw
I suspect you are absolutely correct Crystal as the bank's online 
service tech said he didn't even see a login attempt at their end when I 
gave it a try while we were speaking on the phone.


On 2022-09-14 02:54, Crystal Kolipe wrote:
The error that the OP reports suggests that the login process is 
failing before that.

In our experience, banks sometimes check odd aspects of http requests in a 
misguided
attempt at security.  For example, I'm aware of one that checks for the 
presence of
an accept-encoding: gzip header on the login request, and if it's missing, 
returns a
generic error message.  Took me about five minutes to work that out.

We also know of a bank that has what seems like a backdoor, (or just a plain 
bug), to
bypass their two-factor authentication in some cases, which took about 15 
minutes to
find.


re(4) drivers not working

2022-09-14 Thread Adam Szewczyk
After installation of OpenBSD as HVM on Qubes OS with passed through
Realtek NIC driver starts to spamming with "re0: watchdog timeout" message
and not working. Attaching dmesg.

OpenBSD 7.1 (GENERIC.MP) #465: Mon Apr 11 18:03:57 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1040183296 (991MB)
avail mem = 991436800 (945MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfc10 (12 entries)
bios0: vendor Xen version "4.14.5" date 08/24/2022
bios0: Xen HVM domU
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP APIC HPET WAET SSDT SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 48 pins, remapped
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2593.27 MHz, 06-9e-0a
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2592.03 MHz, 06-9e-0a
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
acpihpet0 at acpi0: 6250 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpipci0 at acpi0 PCI0
acpicmos0 at acpi0
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
cpu0: using VERW MDS workaround (except on vmm entry)
pvbus0 at mainbus0: Xen 4.14
xen0 at pvbus0: features 0x2705, 2048 grant table frames, event channel 1
xbf0 at xen0 backend 0 channel 6: disk
scsibus1 at xbf0: 1 targets
sd0 at scsibus1 targ 0 lun 0: 
sd0: 10240MB, 512 bytes/sector, 20971520 sectors
xbf1 at xen0 backend 0 channel 7: disk
scsibus2 at xbf1: 1 targets
sd1 at scsibus2 targ 0 lun 0: 
sd1: 2048MB, 512 bytes/sector, 4194304 sectors
xbf2 at xen0 backend 0 channel 8: disk
scsibus3 at xbf2: 1 targets
sd2 at scsibus3 targ 0 lun 0: 
sd2: 10240MB, 512 bytes/sector, 20971520 sectors
xnf0 at xen0 backend 113 channel 9: address 00:16:3e:5e:6c:00
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel
0 wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: SMBus
disabled
xspd0 at pci0 dev 2 function 0 "XenSource Platform Device" rev 0x01
vga1 at pci0 dev 3 function 0 "Bochs VGA" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ehci0 at pci0 dev 4 function 0 "Intel 82801DB USB" rev 0x10: apic 1 int 35
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
re0 at pci0 dev 6 function 0 "Realtek 8168" rev 0x15: RTL8168H/8111H
(0x5400), msi, address 98:fa:9b:11:d0:cf
rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet"
rev 2.00/0.00 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 3 buttons, Z dir
wsmouse1 at ums0 mux 0
vscsi0 at root
scsibus4 at vscsi0: 256 targets
softraid0 at root
scsibus5 at softraid0: 256 targets
root on sd0a (e12f8a03b72580b6.a) swap on sd0b dump on sd0b
fd0 at fdc0 drive 1: density unknown
re0: watchdog timeout
re0: watchdog timeout
re0: watchdog timeout


Re: Unable to complete secure online login

2022-09-14 Thread Alton Shaw
Thanks for everyone's suggestions.  I have to admit I only understand a 
small portion of Chris' comments ("natted" & /29 ?) but I'll look at 
that separately.


To further my debugging efforts I started Firefox, turned off all 
add-ons other than Agent Switcher, cleared absolutely everything, opened 
a Private Window, closed the original window, set Agent Switcher to 
Firefox R100.0/Windows 10 and attempted to login but doing so did not 
resolve the issue.


I next installed surf and pointed it to 
https://secure.royalbank.com/statics/login-service-ui/index#/full/signin?LANGUAGE=ENGLISH 
and I was able to login without any problems.


I have no idea what that means in that Firefox, Firefox-ESR, & Chromium 
won't work but surf does other than perhaps I need to fiddle with third 
party cookies & security settings as suggested by Otto.


Thoughts and suggestions are all appreciated.

Alton

On 2022-09-14 08:27, Stuart Henderson wrote:

On 2022/09/14 05:48, Alton Shaw wrote:

Thank you Stuart for your suggestion. I tried logging in using the add-on
/User-Agent Switcher and Manager/ within Firefox set to Windows 10/Edge but
I've received the same response.

as I said, "usually best to change the presented OS and not the type of browser"

because if the browser name in the user-agent doesn't match other
characteristics of the browser, that may trip the bank's snake oil defences
too.

but it might be that you'll just never get it to work. the person you're
talking to at the bank probably doesn't know the details of this either.


I don't know anything about anything but could it be something related to
bgpd?

no.



Re: Unable to complete secure online login

2022-09-14 Thread Alton Shaw
Thanks Crystal.  I'm thinking my next step is to pkg_delete each of the 
browsers except surf and then pkg_add mozilla-firefox and give it a try 
with the as-installed default settings. At least surf provides me a work 
around which is appreciated when it comes time to pay the bills :-]


On 2022-09-14 14:57, Crystal Kolipe wrote:

On Wed, Sep 14, 2022 at 12:05:02PM -0700, Alton Shaw wrote:

I next installed surf and pointed it 
tohttps://secure.royalbank.com/statics/login-service-ui/index#/full/signin?LANGUAGE=ENGLISH
and I was able to login without any problems.

Glad that worked :-).


I have no idea what that means in that Firefox, Firefox-ESR, & Chromium
won't work but surf does

Basically, it means that the bank is not overly fussy about which browser you
are using, and what settings you are using, (which is what I expected).

In other words, they are not 'blocking all browsers except for a specific few',
but rather for some reason your particular configuration is tripping them up.

So it should be fixable.


other than perhaps I need to fiddle with third
party cookies & security settings as suggested by Otto.

If surf works in it's default configuration, then you do NOT need third party
cookies enabled, as surf does not enable them by default.


Re: re(4) drivers not working

2022-09-14 Thread Jonathan Gray
On Wed, Sep 14, 2022 at 10:23:32PM +0200, Adam Szewczyk wrote:
> After installation of OpenBSD as HVM on Qubes OS with passed through
> Realtek NIC driver starts to spamming with "re0: watchdog timeout" message
> and not working. Attaching dmesg.

Try without xen.  It may be messing up interrupts.

> 
> OpenBSD 7.1 (GENERIC.MP) #465: Mon Apr 11 18:03:57 MDT 2022
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 1040183296 (991MB)
> avail mem = 991436800 (945MB)
> random: good seed from bootblocks
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfc10 (12 entries)
> bios0: vendor Xen version "4.14.5" date 08/24/2022
> bios0: Xen HVM domU
> acpi0 at bios0: ACPI 4.0
> acpi0: sleep states S3 S4 S5
> acpi0: tables DSDT FACP APIC HPET WAET SSDT SSDT
> acpi0: wakeup devices
> acpitimer0 at acpi0: 3579545 Hz, 32 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 48 pins, remapped
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2593.27 MHz, 06-9e-0a
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 100MHz
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 2592.03 MHz, 06-9e-0a
> cpu1:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> acpihpet0 at acpi0: 6250 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpipci0 at acpi0 PCI0
> acpicmos0 at acpi0
> "ACPI0007" at acpi0 not configured
> "ACPI0007" at acpi0 not configured
> acpicpu0 at acpi0: C1(@1 halt!)
> acpicpu1 at acpi0: C1(@1 halt!)
> cpu0: using VERW MDS workaround (except on vmm entry)
> pvbus0 at mainbus0: Xen 4.14
> xen0 at pvbus0: features 0x2705, 2048 grant table frames, event channel 1
> xbf0 at xen0 backend 0 channel 6: disk
> scsibus1 at xbf0: 1 targets
> sd0 at scsibus1 targ 0 lun 0: 
> sd0: 10240MB, 512 bytes/sector, 20971520 sectors
> xbf1 at xen0 backend 0 channel 7: disk
> scsibus2 at xbf1: 1 targets
> sd1 at scsibus2 targ 0 lun 0: 
> sd1: 2048MB, 512 bytes/sector, 4194304 sectors
> xbf2 at xen0 backend 0 channel 8: disk
> scsibus3 at xbf2: 1 targets
> sd2 at scsibus3 targ 0 lun 0: 
> sd2: 10240MB, 512 bytes/sector, 20971520 sectors
> xnf0 at xen0 backend 113 channel 9: address 00:16:3e:5e:6c:00
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
> pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel
> 0 wired to compatibility, channel 1 wired to compatibility
> pciide0: channel 0 disabled (no drives)
> pciide0: channel 1 disabled (no drives)
> piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: SMBus
> disabled
> xspd0 at pci0 dev 2 function 0 "XenSource Platform Device" rev 0x01
> vga1 at pci0 dev 3 function 0 "Bochs VGA" rev 0x02
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> ehci0 at pci0 dev 4 function 0 "Intel 82801DB USB" rev 0x10: apic 1 int 35
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
> 2.00/1.00 addr 1
> re0 at pci0 dev 6 function 0 "Realtek 8168" rev 0x15: RTL8168H/8111H
> (0x5400), msi, address 98:fa:9b:11:d0:cf
> rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
> isa0 at pcib0
> isadma0 at isa0
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet"
> rev 2.00/0.00 addr 2
> uhidev0: iclass 3/0
> ums0 at uhidev0: 3 buttons, Z dir
> wsmouse1 at ums0 mux 0
> vscsi0 at root
> scsibus4 at vscsi0: 256 targets
> softraid0 at root
> scsibus5 at softraid0: 256 targets
> root on sd0a