Re: Browser access to file system on new install OpenBSD missing.
Actually, there is one major difference between the two systems that I had forgotten about. While both use the Calm window manager, the system that is experiencing problems with the browser file dialogs, uses PCManFM...
Re: Browser access to file system on new install OpenBSD missing.
On 7/11/22 17:53, Stuart Henderson wrote:
> I guess your locate database was last generated when firefox was
> installed but chromium was not
>
>> Wondering if something else is at play here...
> grep unveil /usr/local/share/doc/pkg-readmes/*
>
> ls /etc/*/*unveil*
$ grep unveil /usr/local/share/doc/pkg-readmes/*
/usr/local/share/doc/pkg-readmes/chromium:- each category of process
uses unveil(2) to limit filesystem access.
/usr/local/share/doc/pkg-readmes/chromium:Disabling pledge() or unveil()
is not recommended!
/usr/local/share/doc/pkg-readmes/chromium:- global unveil knob: invoke
chromium with --disable-unveil
/usr/local/share/doc/pkg-readmes/chromium:- specific unveil for specific
processes:
/usr/local/share/doc/pkg-readmes/chromium:/etc/chromium/unveil.*
/usr/local/share/doc/pkg-readmes/chromium:to /etc/chromium/unveil.main
and merge with changes in files in
/usr/local/share/doc/pkg-readmes/firefox:pledge(2) and unveil(2) Support
/usr/local/share/doc/pkg-readmes/firefox:Firefox on OpenBSD is secured
with pledge(2) and unveil(2) to limit
/usr/local/share/doc/pkg-readmes/firefox:following files to change the
pledge promises, unveil paths, and
/usr/local/share/doc/pkg-readmes/firefox:/etc/firefox/{unveil,pledge}.{main,content,gpu}
/usr/local/share/doc/pkg-readmes/firefox:As unveil() can't show
non-existing dirs, it is recommended to manually
/usr/local/share/doc/pkg-readmes/firefox:Due to unveil(2) limiting
filesystem access, special care has to be
/usr/local/share/doc/pkg-readmes/firefox:taken to unveil MIME handlers.
For example, to use the mupdf package
/usr/local/share/doc/pkg-readmes/firefox:And the corresponding binary
must be unveiled for it to appear as an
/usr/local/share/doc/pkg-readmes/firefox:line to /etc/firefox/unveil.main:
/usr/local/share/doc/pkg-readmes/firefox:/etc/firefox/unveil.main.
/usr/local/share/doc/pkg-readmes/firefox:To disable pledge and/or unveil
support when troubleshooting, set the
/usr/local/share/doc/pkg-readmes/firefox:corresponding pledge or unveil
file in
/usr/local/share/doc/pkg-readmes/firefox:/etc/firefox/{unveil,pledge}.{main,content,gpu}
to contain
$ ls /etc/*/*unveil*
/etc/chromium/unveil.gpu /etc/chromium/unveil.utility_audio
/etc/firefox/unveil.main
/etc/chromium/unveil.main
/etc/chromium/unveil.utility_network /etc/firefox/unveil.rdd
/etc/chromium/unveil.plugin /etc/chromium/unveil.utility_video
/etc/firefox/unveil.socket
/etc/chromium/unveil.renderer/etc/firefox/unveil.content
/etc/chromium/unveil.utility /etc/firefox/unveil.gpu
Re: Fanless amd64 sytem recommendations
On 7/11/22 1:13 AM, B. Atticus Grobe wrote: I've been running a Hewlett-Packard HP t620 Quad Core TC for a couple of years now in that role, with the AMD GX-415GA SOC in it. It's the bigger brother of that found in the APU systems. The stock configuration usually has 4GB of RAM in them, with a single re(4) 1GBps NIC, and a 16GB mSATA SSD. I haven't had any issues out of mine, which I got for I believe $50 on eBay. They seem to be fairly easy to acquire. Another $25 for a power brick (which amazingly has had no issues either), and you're good to go. These boxes have eDPI display outputs, and optionally have either an RS-232 serial port or VGA output, along with USB 2 and USB 3. They come with an embedded version Windows 10, but I've had no issues running OpenBSD 6.8-7.0 on it, 9front, or LInux. IIRC, it supports EFI booting, but I've only used legacy BIOS boot. If you get one from eBay, I would recommend opening it and verifying that all the internal screws are tight. I had some loose either from shipping or carelessness on the mSATA hold-down and a few other places. few notes on a HP T430 Thin Client...which probably apply to some other HP thin clients, definitely not others. HP T430: 16GB "disk", 2G RAM Intel N4000 dual core 1) OpenBSD requires the machine be in UEFI mode, which is a change from the HP linux which requires it be in legacy mode. If not in UEFI, you have no storage (for OpenBSD). 2) bsd.rd doesn't work without a monitor or fake monitor plug attached. Thus, if running headless, you can't do a "sysupgrade" (but can do a "remote upgrade" without bsd.rd/sysupgrade). Standard bsd.mp kernel works just fine. Friend of mine reports Linux does the same thing. 3) Rather than using a formal HP power pack, you can "fake it" with just about anything capable of putting out 12-20v and 0.75A or more. High value (100k-300k) resistor added between center pin and +V on the computer overrides the "Is this an HP power pack?" test. The higher the voltage, the lower the current draw. Hint: the parts are tiny, the workspace is cramped, not a good way to learn to solder. :) 4) Total power dissipation was 4w while compiling a kernel, which took 25 minutes. 2W when idle (according to a wattmeter that had a 1W granularity on its readings, so +/-1W on the reading). 5) X seems to just work. Have not used it extensively, though. 6) wired: re(4). Wireless (IF so equipped): iwm0 IF you happen to be in the Detroit, MI area and want one, I've got too many, contact me off-list. Probably cost less than Ebay "shipping". Nick. OpenBSD 7.1-current (GENERIC.MP) #0: Sun Jul 3 16:39:00 EDT 2022 n...@springboard.in.nickh.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1686781952 (1608MB) avail mem = 1618362368 (1543MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x6a8a7000 (23 entries) bios0: vendor AMI version "N41 v01.06" date 03/14/2019 bios0: HP HP t430 Thin Client acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI DBGP SSDT WDAT NHLT WSMT acpi0: wakeup devices SIO1(S3) HDAS(S3) XHC_(S4) XDCI(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) N4000 CPU @ 1.10GHz, 1096.97 MHz, 06-7a-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 24KB 64b/line 6-way D-cache, 32KB 64b/line 8-way I-cache, 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Celeron(R) N4000 CPU @ 1.10GHz, 1096.63 MHz, 06-7a-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
Re: Browser access to file system on new install OpenBSD missing.
> ... how to rectify it is beyond my capabilities as a new OpenBSD user. First of all, there is nothing to rectify. All was done to act like this and to serve a specific purpose. Much work and developers' efforts were poured into this, again with a specific great purpose ( hint: security related). As someone from development already said many times on this list, it is very irritating to see some user asking for help for or trying to circumvent those setups or even worse, seeing developers offering advice on how to disable those rules by common users. It is not forbidden to do that, but this must be left to people who know what they are doing, and for very very very very narrow field in which most users are not included. It is easier for you to store whatever you need access for it later in ~/Downloads and use the configuration it like it is shipped. Thank you.
Re: Browser access to file system on new install OpenBSD missing.
On 2022-07-11, Brian Durant wrote: > On 7/11/22 15:25, Stuart Henderson wrote: >> On 2022-07-11, Björn Gohla wrote: >>> >>> Brian Durant writes: >>> I have a problem with both Firefox and Chromium being unable to access the file system using the "open" dialog. The dialog appears, but no files or directories appear regardless of path. Things function >>> [...] >>> >>> This sounds like an unveil(2) issue. Only white-listed paths are >>> accessible, they are configured in /etc/firefox/unveil.* . >>> >>> ~/Downloads should be enabled by default though. >> >> only if present before the browser was started, also the file dialog boxes >> will often be blank and you need to either type a path by hand, or pick >> one of the predefined entries in the left-hand side; browsing the whole >> computer won't work with the default unveil restrictions >> >> > > ~/Downloads is indeed in /etc/firefox/unveil.main and > /etc/chromium/unveil.main. Interestingly, it doesn't appear that either > Thunderbird nor Midori have a similar unveil file. Interestingly (or > not) When running the following, Chromium doesn't appear at all: Thunderbird and Midori do not use this mechanism. > $ doas locate unveil.main > /etc/firefox/unveil.main > /usr/local/lib/firefox/browser/defaults/preferences/unveil.main > > Nor does it in: > > $ doas locate unveil > /etc/firefox/unveil.content > /etc/firefox/unveil.gpu > /etc/firefox/unveil.main > /etc/firefox/unveil.rdd > /etc/firefox/unveil.socket > /usr/local/lib/firefox/browser/defaults/preferences/unveil.content > /usr/local/lib/firefox/browser/defaults/preferences/unveil.gpu > /usr/local/lib/firefox/browser/defaults/preferences/unveil.main > /usr/local/lib/firefox/browser/defaults/preferences/unveil.rdd > /usr/local/lib/firefox/browser/defaults/preferences/unveil.socket > /usr/share/man/man2/unveil.2 > /usr/share/relink/kernel/GENERIC.MP/kern_unveil.o I guess your locate database was last generated when firefox was installed but chromium was not > Wondering if something else is at play here... grep unveil /usr/local/share/doc/pkg-readmes/* ls /etc/*/*unveil* -- Please keep replies on the mailing list.
Re: Browser access to file system on new install OpenBSD missing.
On 7/11/22 15:25, Stuart Henderson wrote: > On 2022-07-11, Björn Gohla wrote: >> >> Brian Durant writes: >> >>> I have a problem with both Firefox and Chromium being unable to access >>> the file system using the "open" dialog. The dialog appears, but no >>> files or directories appear regardless of path. Things function >> [...] >> >> This sounds like an unveil(2) issue. Only white-listed paths are >> accessible, they are configured in /etc/firefox/unveil.* . >> >> ~/Downloads should be enabled by default though. > > only if present before the browser was started, also the file dialog boxes > will often be blank and you need to either type a path by hand, or pick > one of the predefined entries in the left-hand side; browsing the whole > computer won't work with the default unveil restrictions > > ~/Downloads is indeed in /etc/firefox/unveil.main and /etc/chromium/unveil.main. Interestingly, it doesn't appear that either Thunderbird nor Midori have a similar unveil file. Interestingly (or not) When running the following, Chromium doesn't appear at all: $ doas locate unveil.main /etc/firefox/unveil.main /usr/local/lib/firefox/browser/defaults/preferences/unveil.main Nor does it in: $ doas locate unveil /etc/firefox/unveil.content /etc/firefox/unveil.gpu /etc/firefox/unveil.main /etc/firefox/unveil.rdd /etc/firefox/unveil.socket /usr/local/lib/firefox/browser/defaults/preferences/unveil.content /usr/local/lib/firefox/browser/defaults/preferences/unveil.gpu /usr/local/lib/firefox/browser/defaults/preferences/unveil.main /usr/local/lib/firefox/browser/defaults/preferences/unveil.rdd /usr/local/lib/firefox/browser/defaults/preferences/unveil.socket /usr/share/man/man2/unveil.2 /usr/share/relink/kernel/GENERIC.MP/kern_unveil.o Wondering if something else is at play here...
Re: Fanless amd64 sytem recommendations
Hi Stuart, Thanks very much for the suggestion! I was able to build and preliminary tests show that rclone on aarch64 is working with OpenBSD 7.1. I am able to do restore one of my backups from my GoogleDrive. FANTASTIC. Should I just send an email to the "Maintainer" to indicate that this can be changed? Trying to build it was my original thought but I've gone down the road of trying to fix broken ports before and it's led to a lot of pain because... they are marked "BROKEN" for a reason! People much smarter than me have tried to fix them :). In this case, I should have tried :( Thanks for the nudge. Cheers, Steve W. On Mon, Jul 11, 2022 at 4:51 AM Stuart Henderson wrote: > On 2022-07-11, Steve Williams wrote: > > First, I built a Raspberry Pi 4b system with a USB wired NIC and went to > > restore my backup from Google using rclone only to find that rclone isn't > > supported on arm64. :( > > Try removing the BROKEN-aarch64 and building from ports. > > It has been a while since the BROKEN markers were added for this and there > have been a number of updates, both to rclone itself, and to lang/go, in > the meantime. > > If it still fails then maybe there's some go build option that might help. > My initial reaction is that this is more likely to be a problem in go than > in rclone. > > >
Re: Browser access to file system on new install OpenBSD missing.
On 2022-07-11, Björn Gohla wrote: > > Brian Durant writes: > >> I have a problem with both Firefox and Chromium being unable to access >> the file system using the "open" dialog. The dialog appears, but no >> files or directories appear regardless of path. Things function > [...] > > This sounds like an unveil(2) issue. Only white-listed paths are > accessible, they are configured in /etc/firefox/unveil.* . > > ~/Downloads should be enabled by default though. only if present before the browser was started, also the file dialog boxes will often be blank and you need to either type a path by hand, or pick one of the predefined entries in the left-hand side; browsing the whole computer won't work with the default unveil restrictions -- Please keep replies on the mailing list.
Re: Browser access to file system on new install OpenBSD missing.
On 7/11/22 14:40, Björn Gohla wrote: > > Brian Durant writes: > >> I have a problem with both Firefox and Chromium being unable to access >> the file system using the "open" dialog. The dialog appears, but no >> files or directories appear regardless of path. Things function > [...] > > This sounds like an unveil(2) issue. Only white-listed paths are > accessible, they are configured in /etc/firefox/unveil.* . > > ~/Downloads should be enabled by default though. > > Read /usr/local/share/doc/pkg-readmes/firefox for all the details. Nothing in readmes that hit a note, except possibly dbus not running? I have two computers running the latest stable, but this problem is only on the one... The other thing that I have noticed is that $ uname -v returns GENERIC.MP#465 on the one, while the other responds GENERIC.MP#0. Otherwise, to my knowledge, both computer installs are exactly the same and of recent date (within two weeks) of each other. Thanks for your replies, but I am still confused... Brian
Re: Browser access to file system on new install OpenBSD missing.
Brian Durant writes: > I have a problem with both Firefox and Chromium being unable to access > the file system using the "open" dialog. The dialog appears, but no > files or directories appear regardless of path. Things function [...] This sounds like an unveil(2) issue. Only white-listed paths are accessible, they are configured in /etc/firefox/unveil.* . ~/Downloads should be enabled by default though. Read /usr/local/share/doc/pkg-readmes/firefox for all the details.
Re: Fanless amd64 sytem recommendations
On 2022-07-11, Steve Williams wrote: > First, I built a Raspberry Pi 4b system with a USB wired NIC and went to > restore my backup from Google using rclone only to find that rclone isn't > supported on arm64. :( Try removing the BROKEN-aarch64 and building from ports. It has been a while since the BROKEN markers were added for this and there have been a number of updates, both to rclone itself, and to lang/go, in the meantime. If it still fails then maybe there's some go build option that might help. My initial reaction is that this is more likely to be a problem in go than in rclone.
Re: Browser access to file system on new install OpenBSD missing.
On 2022-07-11, Brian Durant wrote: > I have a problem with both Firefox and Chromium being unable to access > the file system using the "open" dialog. The dialog appears, but no > files or directories appear regardless of path. Things function normally > however, with both Midori and Thunderbird. I assume that Firefox and > Chromium are experiencing a permissions issue, but what causes it and > how to rectify it is beyond my capabilities as a new OpenBSD user. > > Anyone out there that could help me out? : # pkg_add chromium : quirks-6.10 signed on 2022-07-09T19:41:21Z : chromium-103.0.5060.114: ok : Running tags: ok : New and changed readme(s): : /usr/local/share/doc/pkg-readmes/chromium See this file ^^ and the similar one for firefox. -- Please keep replies on the mailing list.
Re: Fanless amd64 sytem recommendations
I use 2 Fujitsu Futro S90, aftermarket quad core 4gb RAM. Slightly modified: mb fdd power connector modifier to provide sata ssd power supply (sata onboard) and low profile PCIE NIC added. It is actually terminal, small, very cheap, external power supply, fanless. VGA over DVI or Display Port, both embedded. Measured power peak under hi load less ten 15W, during idles about 8W. So far no troubles - filtreing bridge for small network, with few internal services enabled 24/7. Tomasz pon., 11 lip 2022, 06:47 użytkownik Steve Williams < st...@williamsitconsulting.com> napisał: > Hi, > > My pcengines APU system died on me catastrophically. It's my primary > router / email / web server. > > First, I built a Raspberry Pi 4b system with a USB wired NIC and went to > restore my backup from Google using rclone only to find that rclone isn't > supported on arm64. :( > > I have built an old Dell desktop into a replacement, but I would really > like a silent system (fanless) and rclone is instrumental to my backup > system so I need to stick to (likely) an amd64 compatible system. > > What recommendations do people have for a fanless AMD64 compatible system > that (ideally) has wired NIC's on it. > > Thanks, > Steve Williams >
Re: Fanless amd64 sytem recommendations
Le Sun, Jul 10, 2022 at 10:45:40PM -0600, Steve Williams a écrit : > Hi, > > My pcengines APU system died on me catastrophically. It's my primary > router / email / web server. > > First, I built a Raspberry Pi 4b system with a USB wired NIC and went to > restore my backup from Google using rclone only to find that rclone isn't > supported on arm64. :( > > I have built an old Dell desktop into a replacement, but I would really > like a silent system (fanless) and rclone is instrumental to my backup > system so I need to stick to (likely) an amd64 compatible system. > > What recommendations do people have for a fanless AMD64 compatible system > that (ideally) has wired NIC's on it. > I use Protectli devices : https://eu.protectli.com/
Re: Fanless amd64 sytem recommendations
Heho, I personally run a Dell 7030 micro for a similar purpose; There is basically a model from each 'big' vendor, and as outlined they are _really_ cheap as used units on ebay. There is a series called 'tiny mini micro' by "ServeTheHome" on our favorite non-free video site which goes over a range of these different devices. Something like the "Lenovo M90n-IoT" might also be worthwhile to look at (even though it comes with an Intel CPU). With best regards, Tobias -Original Message- From: owner-m...@openbsd.org On Behalf Of B. Atticus Grobe Sent: Monday, 11 July 2022 07:14 To: misc@openbsd.org Subject: Fanless amd64 sytem recommendations I've been running a Hewlett-Packard HP t620 Quad Core TC for a couple of years now in that role, with the AMD GX-415GA SOC in it. It's the bigger brother of that found in the APU systems. The stock configuration usually has 4GB of RAM in them, with a single re(4) 1GBps NIC, and a 16GB mSATA SSD. I haven't had any issues out of mine, which I got for I believe $50 on eBay. They seem to be fairly easy to acquire. Another $25 for a power brick (which amazingly has had no issues either), and you're good to go. These boxes have eDPI display outputs, and optionally have either an RS-232 serial port or VGA output, along with USB 2 and USB 3. They come with an embedded version Windows 10, but I've had no issues running OpenBSD 6.8-7.0 on it, 9front, or LInux. IIRC, it supports EFI booting, but I've only used legacy BIOS boot. If you get one from eBay, I would recommend opening it and verifying that all the internal screws are tight. I had some loose either from shipping or carelessness on the mSATA hold-down and a few other places. Good luck.
Re: Browser access to file system on new install OpenBSD missing.
Perhaps you run them in sandbox mode ? Kind regards Wim Brian Durant schreef op 11 juli 2022 08:46:21 CEST: >I have a problem with both Firefox and Chromium being unable to access the >file system using the "open" dialog. The dialog appears, but no files or >directories appear regardless of path. Things function normally however, with >both Midori and Thunderbird. I assume that Firefox and Chromium are >experiencing a permissions issue, but what causes it and how to rectify it is >beyond my capabilities as a new OpenBSD user. > >Anyone out there that could help me out? > >Thanks in advance. >
Browser access to file system on new install OpenBSD missing.
I have a problem with both Firefox and Chromium being unable to access the file system using the "open" dialog. The dialog appears, but no files or directories appear regardless of path. Things function normally however, with both Midori and Thunderbird. I assume that Firefox and Chromium are experiencing a permissions issue, but what causes it and how to rectify it is beyond my capabilities as a new OpenBSD user. Anyone out there that could help me out? Thanks in advance.
Re: Fanless amd64 sytem recommendations
Hi, I use Fujitsu esprimo Q920 it is small and very cheap. Even de poweradapter is build in. The BIOS is configurable to boot up or reboot on power. So if you have a power failure and power comes back it reboots. Just like a RPI. It is a laptop CPU so doesn't consume a lot of power. I just it with Linux as display server in our local Cinema, Movie theater ️ entrance to showcast all the movie trailers. Got like 10 running instances 16 hours a day never had an issue with. Kind regards Wim Steve Williams schreef op 11 juli 2022 06:45:40 CEST: >Hi, > >My pcengines APU system died on me catastrophically. It's my primary >router / email / web server. > >First, I built a Raspberry Pi 4b system with a USB wired NIC and went to >restore my backup from Google using rclone only to find that rclone isn't >supported on arm64. :( > >I have built an old Dell desktop into a replacement, but I would really >like a silent system (fanless) and rclone is instrumental to my backup >system so I need to stick to (likely) an amd64 compatible system. > >What recommendations do people have for a fanless AMD64 compatible system >that (ideally) has wired NIC's on it. > >Thanks, >Steve Williams
