media player with dlna support recommendation.
Hello, I'm currently playing with home stuff with OpenBSD, and i'm now looking for a media server with dlna support amongst package. Up to this day i was not able to find one, or at least to find how to enable and configure that. The OpenBSD based server side is ok and well supported (also tested with android and MacOs clients). Any ideas about my errors here ? Regards, Eric.
Re: media player with dlna support recommendation.
Eric Huiban wrote: > Hello, > > I'm currently playing with home stuff with OpenBSD, and i'm now looking > for a media server with dlna support amongst package. Up to this day i > was not able to find one, or at least to find how to enable and > configure that. > > The OpenBSD based server side is ok and well supported (also tested with > android and MacOs clients). > > Any ideas about my errors here ? > > Regards, > Eric. > > sorry for mistyping... i'm looking for the media player, not the server.
Re: i386 or amd64?
Thu, 22 Sep 2016 09:53:43 +0300 Mihai Popescu > Since the answer is done, I will dare to ask something in this thread: > are there some hints in choosing over Intel or AMD processors? > > I see many users do not comment that and I respect it. Sometimes, you > can see phrases in threads like "happy to run AMD again", etc. > Is there a preference over one manufacturer, even from the > documentation point of view? > > On the video section, is AMD prefered over Intel integrated video solutions? > > Thank you. > Hi Mihai, misc@, The simplest answer is, as always: it depends. On many factors, mostly what you want from the system as intended use, your budget, preference, and of course, special considerations. Like for example balancing your machine farm, power usage, testing and live machines, re-purpose roles. It also very much depends on the way you obtain the system whether it's new and you hand pick each component, or you salvage it from retirement or reuse some parts from other machines, or it's a refurbished laptop.. For me being on a very constrained budget for personal use, it's always been efficiency towards cost of ownership and longevity of the hardware but this may be a completely different story for you, even different in work compared to personal use, and different between consecutive tasks. For work I've always gone with ~even split, and special considerations. I would be willing to provide much more details on hardware choice from user point of view off list but I wouldn't insist details like CPU bugs or deep engineering specifics in the public air. I think this is being avoided for the risk of creating more stir than useful productive talks & furthermore, it may go completely off topic unrelated to OpenBSD use. Yet, I too would like to back you up with this request for more special details, as it's mostly interesting for me as well. Thanks for asking! P.S. If I was looking around for a laptop, I'd go for one that has both internal Intel video, and discrete Radeon video card, for more options. However, I am not interested in laptops any more since they became much more expensive than a real desktop/server machine & much lower quality. Looking forward to more interesting considerations for picking CPU/GPU. Kind regards, Anton
ARM64:s finally on the market, and flooding it. OpenBSD support?
The market is finally being flooded with ARM64:s. And some of them are inexpensive. I guess AllWinner A64/H64 will be the most ubiquitous one as the chip is/soon will be something like 5 USD. Boards should be on the market for 15 USD this year I think. If you need SATA or PCIe the same figure is something like 150 USD. See a listing below. What about running OpenBSD on these, do you have any idea when this should be possible? Thanks, Tinker * I suppose the AllWinner A64 (and the AllWinner H64 which is essentially the same chip) will be the very most popular. One board is https://www.pine64.org/ (15 USD for 512MB variant, 30 USD for 2GB variant), released fairly soon. Another upcoming is "Nobel64". 1x gigabit ethernet. No SATA. USB 2. No PCIe. http://linux-sunxi.org/A64 http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf * Amlogic S905 is one that's actually on the market already. The Odroid C2 (40 USD) deploys it, http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438 . Not sure how popular that one will be in the longer term though. 1x gigabit ethernet. No SATA. USB 2. No PCIe. http://dn.odroid.com/S905/DataSheet/S905_Public_Datasheet_V1.1.4.pdf * The Snapdragon 600 (and 410) is on the market also, here's a board: http://www.inforcecomputing.com/products/single-board-computers-sbc/qualcomm-snapdragon-600-inforce-6410plus-sbc , 150 USD. SATA. USB 2. PCIe. Ethernet.. by PCIe? https://developer.qualcomm.com/download/sd600/snapdragon-600-datasheet.pdf * Some more are Rockchip RK3368, Kirin 620, Marvell IAP140, Actions Semiconductor Actions S900, Samsung S5P6818.
Re: ARM64:s finally on the market, and flooding it. OpenBSD support?
2016-09-22 13:51 GMT+02:00 Tinker : > What about running OpenBSD on these, do you have any idea when this should > be possible? https://www.openbsd.org/armv7.html "A mailing list for ARM-based ports is available at a...@openbsd.org." The devs are looking forward to getting the boards you are sending them. Best Martin
kernel chmod
The /bsd kernel as installed by the installer has -rw-r--r-- 1 root wheel 10571887 Sep 22 16:27 /bsd The /bsd kernel recompiled and installed by make install has -rwxr-xr-x 1 root wheel 10572001 Sep 22 16:49 /bsd Not that I have any problem with it, but why is that? It it intentional? Jan
Re: kernel chmod
On Thu, 22 Sep 2016 16:51:28 +0200, Jan Stary wrote:
> The /bsd kernel as installed by the installer has
> -rw-r--r-- 1 root wheel 10571887 Sep 22 16:27 /bsd
>
> The /bsd kernel recompiled and installed by make install has
> -rwxr-xr-x 1 root wheel 10572001 Sep 22 16:49 /bsd
>
> Not that I have any problem with it,
> but why is that? It it intentional?
The execute bit is not relevant on the kernel. When you build your
own you get the mode that ld gave it. Since ld is generally used
to build executables, it sets the execute bit by default. The
install target in the kernel Makefile just used cp to install /bsd.
We could use ${INSTALL} and set the mode but historically that was
not available in the kernel Makefile (these days it is).
The short answer is that the mode is just cosmetic...
- todd
Re: ARM64:s finally on the market, and flooding it. OpenBSD support?
Tinker, do not touch el-cheapo undocumented SoCs/boards, IMHO this would be completely lost time. If you'd like to hack or buy hardware, better do with board/SoC which is/are fully documented. And no, datasheets are usually not good enough nor an advice to look into Linux sources...To make it completely clear, try to get some documentation for SoC you've listed, I would bet you will fail miserably. I've tried that in the past and all your choices were no go. In fact the only friendly vendor with full SoC/board developer/reference guide was Freescale/NXP of that time. Second was NVidia with their Tegra family, but this is again no-go due to missing GPU docs anyway... Good luck! And by the way, if you'd like to donate hardware, make that a bit meaningful by offering for example ThunderX or similar kind of machine or at least those fully documented Freescale/NXP boards which are good enough as routers/gateways. I guess such offer would be tempting even to OpenBSD devs and will not be thrown into the thrash easily. :-) And if you'd like to hack on those, post your patch(es) to tech@ -- for start I guess you may get some idea from bitrig's drahn_arm64 branch and/or from FreeBSD's source tree. Generally speaking I would guess you will need to start with in-tree LLVM and make that running for you... On Thu, Sep 22, 2016 at 2:07 PM, Martin Schröder wrote: > 2016-09-22 13:51 GMT+02:00 Tinker : >> What about running OpenBSD on these, do you have any idea when this should >> be possible? > > https://www.openbsd.org/armv7.html > "A mailing list for ARM-based ports is available at a...@openbsd.org." > > The devs are looking forward to getting the boards you are sending them. > > Best >Martin
Re: kernel chmod
Hello I thinks this is because your default "file creation" is 755 within umask / is a path like another one so... it works just like any other one. And this permit to modify it or recompile it again in case of issues this is not needed if we keep the original one, so I think this is why install script doesn't restrict the permissions after the build. > > From: Jan Stary > Sent: Thu Sep 22 16:51:28 CEST 2016 > To: > Subject: kernel chmod > > > The /bsd kernel as installed by the installer has > -rw-r--r-- 1 root wheel 10571887 Sep 22 16:27 /bsd > > The /bsd kernel recompiled and installed by make install has > -rwxr-xr-x 1 root wheel 10572001 Sep 22 16:49 /bsd > > Not that I have any problem with it, > but why is that? It it intentional? > > Jan > Cordialement Francois Pussault 10 chemin de négo saoumos apt 202 - bat 2 31300 Toulouse +33 6 17 230 820 fpussa...@contactoffice.fr
Re: Output Errors on VLAN interfaces
Hi Chris,
Sorry for the slow reply. Day job takes up most of my time.
Anyway, I finally added some logging into /usr/src/sys/net/if_vlan.c etc;
if (m == NULL) {
ifp->if_oerrors++;
printf("Output Error due to NULL mbuff\n");
continue;
}
}
if (if_enqueue(ifp0, m)) {
ifp->if_oerrors++;
printf("Output Error from if_enqueue\n");
continue;
}
ifp->if_opackets++;
Recompiled the kernel and rebooted onto it, and pushed traffic through it
(~50Mbps).
And sure enough every single instance of the VLAN Output drops is due
to "if_enqueue(ifp0,
m)" being TRUE. I edited if.c and again confirmed that IFQ_ENQUEUE does
return the error.
Traced it further back to ifq.c:ifq_enqueue_try(), and rv (from rv =
ifq->ifq_ops->ifqop_enq(ifq, m);) is 55 for every one of the VLAN output
drops.
Needed some help from a colleague to figure out what
ifq->ifq_ops->ifqop_enq(ifq,
m) calls.
We believe is should be calling ifq.c:priq_enq(). Still dont understand
that glue part yet :( But after adding some logging on "if (ifq_len(ifq) >=
ifq->ifq_maxlen)" it doesn't seem to be that? So have either made a mistake
or gone as far as my knowledge can go? Any _pointers_ guys? ;)
We do use HFSC (and have done since 5.0 without issues), but only on the
physical interface, not on the VLANs.
The reason for this is so that we can _share_ the whole of the 10Gig
interface root bandwidth across all of the VLANs on the same physical .1q
trunk. This has worked great for years without VLAN output errors. I think
this started after 5.8 or 5.9.
I increased the qlimits from the default but that made no difference.
queue trunk_root on $if_trunk bandwidth 4294M
queue qlocal on $if_trunk parent trunk_root bandwidth 4.1G
queue local_kern on $if_trunk parent qlocal bandwidth 8M min 8M
burst 8M for 1000ms
queue local_pri on $if_trunk parent qlocal bandwidth 150M min 150M
burst 200M for 2500ms qlimit 500
queue local_data on $if_trunk parent qlocal bandwidth 4G min 1G
qlimit 1000
queue qwan on $if_trunk parent trunk_root bandwidth 190M
queue wan_rt on $if_trunk parent qwan bandwidth 30M min 19M burst
38M for 5000ms
queue wan_int on $if_trunk parent qwan bandwidth 19M min 9M
queue wan_pri on $if_trunk parent qwan bandwidth 19M min 10M burst
25M for 2000ms
queue wan_vpn on $if_trunk parent qwan bandwidth 50M min 25M
queue wan_web on $if_trunk parent qwan bandwidth 29M min 10M burst
19M for 3000ms
queue wan_dflt on $if_trunk parent qwan bandwidth 19M min 10M burst
19M for 5000ms
queue wan_bulk on $if_trunk parent qwan bandwidth 20M max 100M
default
.
.
match out on INSIDE all received-on INSIDE queue (local_data,local_pri) set
prio (2,4)
So all traffic flowing from one VLAN to another (on the same trunk) are in
queues local_data and local_pri, however looking at the queue statistics
with systat queues 1, shows these large internal queues never drop a single
packet. Yet if_oerrors for the VLANs is still incrementing quite a lot for
most of our VLANs.
Hi Henning, whilst I have the code open, I am also going to have another go
at trying to find the missing 64bit counter/range check etc for the HFSC
queue size tomorrow (if I dont get dragged onto anything else).
Thanks for your time and help guys,
Kind regards, Andy Lemin
On Tue, Aug 9, 2016 at 2:48 AM, Chris Cappuccio wrote:
> Andy Lemin [a...@brandwatch.com] wrote:
> > The underlying trunk does not report any Rx or Tx errors at all.
> >
> > And the VLAN interfaces do not report any receive errors, only low rate
> > transmit errors.
> >
> > Also as a thought exercise, could anyone kindly explain/discuss how an
> > output error might even occur or be valid?
> >
>
> Look at /usr/src/sys/net/if_vlan.c, you'll find exactly two places where
> if_oerrors increments. Logically, both are in the vlan_start() routine.
> The first happens after vlan_inject fails. If vlan_inject returns a null
> mbuf, that appears to be a failure within m_prepend(), probably from
> failure to allocate memory for the new mbuf. Where's your dmesg? Are you
> using a card that does hw tagging? (If so, this isn't the codepath you're
> looking for.)
>
> If the failure is the new if_enqueue, it seems like ifq_enqueue would be
> calling priq_enq which would be returning a failure if the queue is full.
> Are you using hfsc?
>
> Chris
FW Hardware
There have been some good discussions lately about HW capable of running a lot of traffic, .. but this question is about the other end of the spectrum. Have a need for a small FW appliance that can be used to protect a single machine and provide a simple way to whitelist a single IP or two. Two HW ethernet ports, OBSD compatible, small form factor, low cost. Any recommendations? Thanks! Lee
Re: ARM64:s finally on the market, and flooding it. OpenBSD support?
Tinker [ti...@openmailbox.org] wrote: > The market is finally being flooded with ARM64:s. And some of them are > inexpensive. > > I guess AllWinner A64/H64 will be the most ubiquitous one as the chip > is/soon will be something like 5 USD. The Allwinner 64-bit parts are supported under 32-bit mode on armv7. Chris
Re: FW Hardware
On Donnerstag, 22. September 2016 12:58:37 PYT L. V. Lammert wrote: > There have been some good discussions lately about HW capable of running a > lot of traffic, .. but this question is about the other end of the > spectrum. > > Have a need for a small FW appliance that can be used to protect a single > machine and provide a simple way to whitelist a single IP or two. > > Two HW ethernet ports, OBSD compatible, small form factor, low cost. > > Any recommendations? > > Thanks! > > Lee PC Engines ALIX.2D2 System Board (i386) Interfaces: VIA VT6105M RhineIII I have been using that one for 3 1/2 years now as a router and FW - no complaints or for a little more you get PC Engines APU.2C2 which is amd64, has far more RAM and three Gigabit-ports. Interfaces: Realtek 8168 Look for a Bundle; it includes board, wallwart, memory-card and cabinet. Cabinet has lower profile than the one for ALIX, only 168 x 157 x 30 mm You're welcome Eike -- Eike Lantzsch ZP6CGE “Do you actually know what you are reading?” He said: “Really, how could I ever do so unless someone guided me?” ... (Acts 8:30, 31)
Re: FW Hardware
Like other have said, PC Engines might be your best bet. Edgerouter lite and PoE are another alternative. They run on Octeon [1]. They might be a bit less expensive with somewhat smaller form factor. They also should be easier to get, like $90 on amazon. Installation might be easier on PC Engines. You'll notice a lot of modal. I don't own either device, all the comments are second hand. [1] https://www.openbsd.org/octeon.html 2016-09-22 19:58 GMT+02:00 L. V. Lammert : > There have been some good discussions lately about HW capable of running a > lot of traffic, .. but this question is about the other end of the > spectrum. > > Have a need for a small FW appliance that can be used to protect a single > machine and provide a simple way to whitelist a single IP or two. > > Two HW ethernet ports, OBSD compatible, small form factor, low cost. > > Any recommendations? > > Thanks! > > Lee > -- Cordialement, Coues Ludovic +336 148 743 42
Re: FW Hardware
On 2016-09-22, Eike Lantzsch wrote: > PC Engines APU.2C2 > which is amd64, has far more RAM and three Gigabit-ports. > Interfaces: Realtek 8168 Actually, the APU2C2 has Intel i211AT interfaces, em(4). -- Christian "naddy" Weisgerber na...@mips.inka.de
Dual booting - can't boot OpenBSD from Windows 10 bootloader
I'm trying to dual boot windows 10 and OpenBSD 6.0 on Lenovo Thinkpad L560. I installed Windows 10 first then OpenBSD, copied pbr to windows (C:\openbsd.pbr) using: # dd if=/dev/rsd0a of=/mnt/openbsd.pbr bs=512 count=1 and run bcdedit as mentioned in FAQ. When i try to load OpenBSD it restarts, and black screen with a blinking cursor appears. When that happens I can't even reboot using CTRL+ALT+DEL, I must power down machine by pressing the power button. I can however boot into OpenBSD just fine using installation USB by runing: boot> boot sd1a:/bsd. I even tried using EasyBCD but the problem persists. # dmesg OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8341897216 (7955MB) avail mem = 8084606976 (7710MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xd7c58000 (64 entries) bios0: vendor LENOVO version "N1HET49W (1.13 )" date 03/23/2016 bios0: LENOVO 20F1S00T00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT UEFI SSDT SSDT HPET LPIT APIC MCFG WDAT SSDT\ SSDT SSDT SSDT SSDT SSDT DBGP DBG2 SSDT BOOT BATB SLIC SSDT SSDT MSDM ASF!\ FPDT UEFI acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) \ GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2694.65 MHz 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,\ DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC, \ FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT, \ PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-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 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2693.72 MHz 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, \ DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC, \ FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT, \ PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2693.72 MHz cpu2: 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, \ DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC, \ FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT, \ PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2693.73 MHz cpu3: 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT, \ DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC, \ FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT, \ PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus -1 (RP01) acpiprt5 at acpi0: bus -1 (RP02) acpiprt6 at acpi0: bus -1 (RP03) acpiprt7 at acpi0: bus 2 (RP04) acpiprt8 at acpi0: bus 5 (RP05) acpiprt9 at acpi0: bus 6 (RP06) acpiprt10 at acpi0: bus -1 (RP07) acpiprt11 at acpi0: bus -1 (RP08) acpiprt12 at acpi0: bus -1 (RP09) acpiprt13 at acpi0: bus -1 (RP10) acpiprt14 at acpi0: bus -1 (RP11) acpiprt15 at acpi0: bus -1 (RP12) acpiprt16 at acpi0: bus -1 (RP13) acpiprt17 at acpi0: bus -1 (RP14) acpiprt18 at acpi0: bus -1 (RP15) acpiprt19 at acpi0: bus -1 (RP16) acpiprt20 at acpi0: bus -1 (RP17) acpiprt21 at acpi0: bus -1 (RP18) acpiprt22 at acpi0: bus -1 (RP19) acpiprt23 at acpi0: bus -1 (RP20) acpiec0 at acpi0 a
Re: FW Hardware
On Donnerstag, 22. September 2016 20:17:28 PYT Christian Weisgerber wrote: > On 2016-09-22, Eike Lantzsch wrote: > > PC Engines APU.2C2 > > which is amd64, has far more RAM and three Gigabit-ports. > > Interfaces: Realtek 8168 > > Actually, the APU2C2 has Intel i211AT interfaces, em(4). my error, what I got here on my desk is an APU1 not APU2 Thank you for the correction
