Re: 350MHz IBM Intel Pentium II runs 5.9 fine

2016-12-01 Thread alexmcwhirter 

On 2016-12-01 22:01, Aaron Mason wrote:

I've got two Sun Netra X1s (400MHz ultraSPARC IIe, 2GB RAM, 2x40GB
drives) with 5.9 installed, they crash after awhile but I suspect
that's a cooling issue since these things run pretty hot.  I'd use
them as firewalls but I can't push any more than ~50Mbps through them
and I've got a 100/40 fibre connection coming once our house is built.

On Fri, Dec 2, 2016 at 12:19 PM,   wrote:
On a similar note, I have a Sun E6K (circa 1996, 30x 400Mhz CPU's 30GB 
of
RAM) running 6.0 like a dream, with some minor patches to support more 
than

8 disks in softraid 5.


Oddly enough i use netra X1's (500mhz) for routers. But mine routinely 
push ~100mb's without issue (no crashing either). ~100mbps seems to be 
pretty much the limit with them, mind you i have both nic's bonded with 
lacp into some cisco switch gear with public / private traffic split 
across vlans.

Re: 350MHz IBM Intel Pentium II runs 5.9 fine

2016-12-01 Thread Aaron Mason 
I've got two Sun Netra X1s (400MHz ultraSPARC IIe, 2GB RAM, 2x40GB
drives) with 5.9 installed, they crash after awhile but I suspect
that's a cooling issue since these things run pretty hot.  I'd use
them as firewalls but I can't push any more than ~50Mbps through them
and I've got a 100/40 fibre connection coming once our house is built.

On Fri, Dec 2, 2016 at 12:19 PM,   wrote:
> On a similar note, I have a Sun E6K (circa 1996, 30x 400Mhz CPU's 30GB of
> RAM) running 6.0 like a dream, with some minor patches to support more than
> 8 disks in softraid 5.



-- 
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse

Re: 350MHz IBM Intel Pentium II runs 5.9 fine

2016-12-01 Thread alexmcwhirter 
On a similar note, I have a Sun E6K (circa 1996, 30x 400Mhz CPU's 30GB 
of RAM) running 6.0 like a dream, with some minor patches to support 
more than 8 disks in softraid 5.

Re: 350MHz IBM Intel Pentium II runs 5.9 fine

2016-12-01 Thread Aaron Mason 
Could just be some garbage IBM machines of that era would spit out to
confuse anything not-Winders, as part of an agreement with Microshart.

Might pull out an old machine, give it some NICs and make it a
firewall.  Got an old Lacie 1U storage appliance with a VIA C7 mobo,
just needs an additional NIC and a couple of disks in raid1 and we're
laughing.  Will dmesg once I'm done.

On Thu, Dec 1, 2016 at 11:31 PM, Craig Skinner  wrote:
> Hi,
>
> On Wed, 30 Nov 2016 17:09:13 +0100 butresin wrote:
>> On 16.11.29Tue 14:12, Craig Skinner wrote:
>> >
>> > real mem  = 200740864 (191MB)
>> > avail mem = 184385536 (175MB)
>> ...
>> > spdmem0 at iic0 addr 0x50: 64MB SDRAM non-parity PC100CL3
>> > spdmem1 at iic0 addr 0x51: 64MB SDRAM non-parity PC100CL3
>> > spdmem2 at iic0 addr 0x52: 64MB SDRAM ECC PC100CL2
>> > spdmem3 at iic0 addr 0x55: 1GB DDR2 SDRAM PC2-5000CL5
>>
>> This is odd.
>>
>
> None of these IBM Pentium II machines have DDR memory installed.
> I don't think it was invented in 1999. The 3 slots are old DIMM.
>
> The other dmesg:
>
> spdmem0 at iic0 addr 0x50: 128MB SDRAM non-parity PC100CL3
> spdmem1 at iic0 addr 0x51: 64MB SDRAM non-parity PC100CL3
> spdmem2 at iic0 addr 0x52: 64MB SDRAM non-parity PC100CL3
> spdmem3 at iic0 addr 0x55: 448MB DDR2 SDRAM PC2-2500CL5
>
> Another identical machine, but with only 2 DIMM slots filled:
>
> spdmem0 at iic0 addr 0x50: 256MB SDRAM non-parity PC133CL2
> spdmem1 at iic0 addr 0x51: 256MB SDRAM non-parity PC133CL2
> spdmem2 at iic0 addr 0x55: 1GB DDR2 SDRAM PC2-6500CL5
>
> Being an ordinary user, I dunno what that means, but the boxes run fine.
>
> Cheers!
> --
> Craig Skinner | http://linkd.in/yGqkv7
>



-- 
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse

Re: 350MHz IBM Intel Pentium II runs 5.9 fine

2016-12-01 Thread OpenBSD lists 

Craig Skinner wrote:

Hi,

On Wed, 30 Nov 2016 17:09:13 +0100 butresin wrote:

On 16.11.29Tue 14:12, Craig Skinner wrote:


real mem  = 200740864 (191MB)
avail mem = 184385536 (175MB)

...

spdmem0 at iic0 addr 0x50: 64MB SDRAM non-parity PC100CL3
spdmem1 at iic0 addr 0x51: 64MB SDRAM non-parity PC100CL3
spdmem2 at iic0 addr 0x52: 64MB SDRAM ECC PC100CL2
spdmem3 at iic0 addr 0x55: 1GB DDR2 SDRAM PC2-5000CL5


This is odd.



None of these IBM Pentium II machines have DDR memory installed.
I don't think it was invented in 1999. The 3 slots are old DIMM.

The other dmesg:

spdmem0 at iic0 addr 0x50: 128MB SDRAM non-parity PC100CL3
spdmem1 at iic0 addr 0x51: 64MB SDRAM non-parity PC100CL3
spdmem2 at iic0 addr 0x52: 64MB SDRAM non-parity PC100CL3
spdmem3 at iic0 addr 0x55: 448MB DDR2 SDRAM PC2-2500CL5

Another identical machine, but with only 2 DIMM slots filled:

spdmem0 at iic0 addr 0x50: 256MB SDRAM non-parity PC133CL2
spdmem1 at iic0 addr 0x51: 256MB SDRAM non-parity PC133CL2
spdmem2 at iic0 addr 0x55: 1GB DDR2 SDRAM PC2-6500CL5

Being an ordinary user, I dunno what that means, but the boxes run fine.

Cheers!

Looks like something is misinterpreting ID numbers form the EEPROM on 
the memory modules.  But I'd like to see what is physically there before 
making a call on what is going wrong, if you have any photos of the 
system's motherboard.


I'm thinking that perhaps the DDR2 modules might be for an integrated 
graphics chips but are reporting as part of main memory for some reason. 
 Older systems like that were a mess and many times buses would be 
wired together and whatever is attached to the IIC bus may be some 
random peripheral that just happens to have an ID that was later re-used 
for a DDR2 module.

Re: 5.8 EOL

2016-12-01 Thread OpenBSD lists 

Alessandro Baggi wrote:

Il 01/12/2016 17:01, Marko Cupać ha scritto:

On Thu, 1 Dec 2016 15:59:41 +0100
Alessandro Baggi  wrote:


Hi list,
I've installed some years ago OpenBSD 5.8 on apu with 3 nics.
I've tried to search but no look. What is the EOL for OpenBSD 5.8?

Thanks in advance.



https://www.openbsd.org/faq/faq5.html#Flavors

AFAIK Once 6.0 is out, 5.8 becomes unsupported (EOS). But it by no means
its life ends (EOL). I have just upgraded 2 boxes that were at 5.5,
but were quite alive and kicking :)

--
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/



Then, when 6.1 will be released,
Somewhere between March and May of next year.  Depends on when the code 
is in a releasable state.



5.9 will become unsupported.

Yep, it won't be getting patches anymore.


How do you provide to security patch for 5.5?
We don't.  Supporting a release that old would require quite a lot more 
volunteers to back-port and test every patch that would apply and we'd 
rather not waste resources on supporting the old stuff and use our time 
to move the project forward.  Upgrading is painless and major changes 
are very rare, so I can't think of any compelling reasons to stay on an 
old version (well, unless it is the last version your platform supports)

Re: 5.8 EOL

2016-12-01 Thread OpenBSD lists 

Alessandro Baggi wrote:

Hi list,
I've installed some years ago OpenBSD 5.8 on apu with 3 nics.
I've tried to search but no look. What is the EOL for OpenBSD 5.8?

Thanks in advance.



1 September 2016 when 6.0 was released.  The only support versions are 
the current and the immediately previous.


I'd recommend upgrading to 6.0 anyway, a lot of drivers for the AMD APUs 
were added/updated between 18 October 2015 when 5.8 was released and 
now.  Mostly newer graphics chips and USB 3.0 XHCI support.  Helped with 
some issues on an A6-5200 based system I use as my backup desktop box.


-Christopher Ahrens

Installer kernel shuts down root hub

2016-12-01 Thread Joseph Lawson 
Hello,

When I boot the installer it shuts down the root hub

Intel Compute Stick, Intel Atom z3735f (x86-64) Bay Trail

Obtained image from http://mirror.jmu.edu/pub/OpenBSD/6.0/amd64/install60.fs

Transferred to USB stick using Linux dd command. Also tried with windows32image 
writer.

Booted up and got this:

uhub0 at usb0 “Intel EHCI root hub” rev 2.00/1.00 addr1

uhub0: device problem, disabling port 1

I have photos of the dmesg if needed.

Is there anything I can do about this?


Sent from Mail for Windows 10

Announcing OSS-Fuzz: Continuous Fuzzing for Open Source Software

2016-12-01 Thread minek van 
Hello, 

https://testing.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html

OSS-Fuzz is launching in Beta right now, and will be accepting suggestions for 
candidate open source projects.

Apply here: https://github.com/google/oss-fuzz#accepting-new-projects


imho a great opportunity to get free audits :)

Who will apply "OpenBSD" and related projects?

Thanks!

Re: PCI Express wireless adapter supported under OpenBSD

2016-12-01 Thread Alex French 
> From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
> If you really want to use hostap and are having trouble finding a
> supported pcie card, it might be easier to find a supported athn or
> ral minipcie card and a pcie carrier, this sort of thing:
>
> http://www.banggood.com/Mini-WiFi-Wan-802_11n-PCI-e-to-PCI-e-Wireless-
> Expansion-Card-Adapter-Convertor-p-1013592.html
> https://www.amazon.co.uk/sourcingmap-Express-Wireless-Adapter-
> Antenna/dp/B0057UPNBE

That's the route I chose. I have a Ubiquiti SR71-E express card (Atheros
AR9280 XB92) in a PCIe adapter, and it seems to work well.

Re: long fat pipe problem

2016-12-01 Thread Stuart Henderson 
On 2016-11-29, gwes  wrote:
> I've got 2 6.0 systems: one in BOS one in LA. Transit
> time is about 100ms. There's adequate bandwidth end-to-end.
>
> I can only get 1.5 - 2.5 MB/sec due to the long fat
> pipe problem: the receiving system won't open the window
> large enough to let the sender put enough bytes in the pipe.

OpenBSD up to and including 6.0 was limited to 256KB buffers, with
100ms RTT this limits you to 2.5Mbit/sec max (second form on
https://www.switch.ch/network/tools/tcp_throughput/).

Update both sides to -current, it has larger buffers and some other
changes to reduce the potential risk from the added kernel memory use.

The kernel is normally auto-tuning these days, if you want to force it
on a connection you can use setsockopt(). rsync gives an easy way to set
this, i.e. "--sockopts=SO_RCVBUF=262144".

Re: ftp(1) downloads a broken file; curl(1) doesn't

2016-12-01 Thread Stuart Henderson 
On 2016-11-29, Jan Vlach  wrote:
> this is unrelated to OpenBSD and is probably a bug in blocklist.php on server 
> side. (User agent processing? ...) You'd see this in tcpdump, if you had this 
> debugged properly.

> HTTP/1.1 200 OK
> Date: Tue, 29 Nov 2016 12:38:49 GMT
> Server: Apache/2
> X-Powered-By: PHP/5.5.9-1ubuntu4.20
> Content-Disposition: filename=zeus_badips.txt
> Strict-Transport-Security: max-age=15768000 ; includeSubDomains
> Vary: Accept-Encoding
> Cache-Control: max-age=2592000
> Expires: Thu, 29 Dec 2016 12:38:49 GMT
> X-Content-Type-Options: nosniff
> X-XSS-Protection: 1; mode=block, 1; mode=block
> X-Frame-Options: sameorigin
> Transfer-Encoding: chunked

The server is sending chunked transfer-encoding and ftp(1) cannot handle it.

> Content-Type: text/plain
>
> 971
> #
>

971 is the length of the following chunk.

> 0

And the 0 is the zero-length terminating chunk.

Re: PCI Express wireless adapter supported under OpenBSD

2016-12-01 Thread Stuart Henderson 
On 2016-11-30, C. L. Martinez  wrote:
> Hi all,
>
>  I would like to install OpenBSD on a HP Microserver Gen8 to act as a 
> firewall and hostap. I am searching what components I need and I have a doubt 
> about what wireless interface I need to buy to use it as a hostap under 
> OpenBSD.
>
>  I have found only these:
>
>  - Asus PCE-AC88 Wireless 5GHz PCI-E AC3100
>  - Asus PCE-AC68 PCI-E WiFi Dual-Band AC1900
>
>  Searching in ASUS's web, I didn't find any info about what chip use these 
> adapters. Are they supported under OpenBSD? Do you recommend any other 
> wireless adpater (PCI-e)?? Throughput needs to be 300 Mbps, at least.
>
> Thanks.
>

If you really want to use hostap and are having trouble finding a
supported pcie card, it might be easier to find a supported athn or
ral minipcie card and a pcie carrier, this sort of thing:

http://www.banggood.com/Mini-WiFi-Wan-802_11n-PCI-e-to-PCI-e-Wireless-Expansion-Card-Adapter-Convertor-p-1013592.html
https://www.amazon.co.uk/sourcingmap-Express-Wireless-Adapter-Antenna/dp/B0057UPNBE

Personally I'd use a dedicated AP instead and hang it on a separate
nic or vlan off an OpenBSD firewall.

Re: 5.8 EOL

2016-12-01 Thread Stuart Henderson 
On 2016-12-01, Alessandro Baggi  wrote:
> How do you provide to security patch for 5.5?

Patches to 5.5 are provided in the form of an upgrade to a current supported 
release.

Re: 5.8 EOL

2016-12-01 Thread Johan Mellberg 
Skickat från min "enhet" :-)
> 1 dec. 2016 kl. 15:59 skrev Alessandro Baggi :
>
> Hi list,
> I've installed some years ago OpenBSD 5.8 on apu with 3 nics.
> I've tried to search but no look. What is the EOL for OpenBSD 5.8?
>
> Thanks in advance.
>

Not sure that "end of life" is the way to put it, but OpenBSD developers
support the current and the previous releases (see picture on
http://www.openbsd.org/faq/faq5.html).  So 5.8 was "EOL:ed" when 6.0 was
released.
/Johan

Re: 5.8 EOL

2016-12-01 Thread Alessandro Baggi 

Il 01/12/2016 17:01, Marko Cupać ha scritto:

On Thu, 1 Dec 2016 15:59:41 +0100
Alessandro Baggi  wrote:


Hi list,
I've installed some years ago OpenBSD 5.8 on apu with 3 nics.
I've tried to search but no look. What is the EOL for OpenBSD 5.8?

Thanks in advance.



https://www.openbsd.org/faq/faq5.html#Flavors

AFAIK Once 6.0 is out, 5.8 becomes unsupported (EOS). But it by no means
its life ends (EOL). I have just upgraded 2 boxes that were at 5.5,
but were quite alive and kicking :)

--
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/



Then, when 6.1 will be released, 5.9 will become unsupported.
How do you provide to security patch for 5.5?

Re: trouble shooting print errors

2016-12-01 Thread Predrag Punosevac 
Anonymous coward wrote:

> I am getting "Broken Pipe" and or "Scheduler not responding" when
> attempting to print from a laser desk printer directly attached to usb.
> OpenBSD 6.0 recognizes the printer in dmesg and when plugged into the
> usb port.
> 
> I have been running OpenBSD for several years but never tried to attach
> a printer.
> 
> I also have downloaded a cups ppd driver for the printer and placed it
> in the cups ppd directory.
> 

PPD is not a driver! It is a PostScript Printer Description file created
by vendors to describe the entire set of features and capabilities
available for their PostScript printers. The real problem is that your
printer is not a PostScript printer which you could have found out by
reading page 3 of the product brochure

https://www.brother-usa.com/VirData/Content/en-US/Printers/ModelBrochures/HL2100Series_cat.pdf


which means that you really need a driver. Going back to the page three
of above brochure we see that you printer emulates HL-2:40 GD which is
proprietary language but also PCL 6 (Printer Command Language is in
generally open sourced). However based on the fact that Brother
recommends its own driver for Linux which contains binary blob I would
be tempted to declare the printer paperweight with a caveat. If you
printer is network capable you might be able to send the raw data to
port 9100. Please see again page 3 of the brochure. Your

/etc/printacap

# Remote printer must use jetdirect since foomatic-rip doesn't speak LPD
rp|HL-5250DN:\
:lp=9100@192.168.3.15:\
:if=/etc/foomatic-rip/script_brother.sh:\
:sh:sd=/var/spool/output/brother:\
:lf=/var/log/lpd-errs:

where script_brother.sh is an ugly work around foomatic filter which no
longer supports LPD spooling and it looks like 

#!/bin/sh

/usr/local/bin/a2ps -BRq --columns=1 -o - | \
/usr/local/bin/foomatic-rip -P HL-5250DN --ppd
/etc/foomatic-rip/direct/brother-hl-5250dn-postscript-brother.ppd


The printer you are attempting  to use cost about $20 here in U.S. The
one I use HL-5200 or its newer versions could be found for under $100
and it is a PostScript printer of superb quality in its price range
(also exceptionally low price per page). You might want to think about
it a bit before waisting your time with the printer you have.



> If someone can just point me where to research these errors I should be
> able to determine the cause and maybe get the brother HL2140 directly
> attached usb  printer working.
> 

I would expect from a  seasoned OpenBSD user to know to look for errors 
in the log files. Hint

/var/log/lpd-errs

I am guessing you are going to see nothing as your printer is just
paperwight. 

> I see no error messages in dmesg which relate to printing.

I would not expect to see any unless printer interface is so messed up
that generic usb driver can't attach to the device. 



Best,
Predrag




> Thanks in advance.

Re: 5.8 EOL

2016-12-01 Thread Marko Cupać 
On Thu, 1 Dec 2016 15:59:41 +0100
Alessandro Baggi  wrote:

> Hi list,
> I've installed some years ago OpenBSD 5.8 on apu with 3 nics.
> I've tried to search but no look. What is the EOL for OpenBSD 5.8?
>
> Thanks in advance.
>

https://www.openbsd.org/faq/faq5.html#Flavors

AFAIK Once 6.0 is out, 5.8 becomes unsupported (EOS). But it by no means
its life ends (EOL). I have just upgraded 2 boxes that were at 5.5,
but were quite alive and kicking :)

--
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/

5.8 EOL

2016-12-01 Thread Alessandro Baggi 

Hi list,
I've installed some years ago OpenBSD 5.8 on apu with 3 nics.
I've tried to search but no look. What is the EOL for OpenBSD 5.8?

Thanks in advance.

Re: OpenBSD 5.2 AutoFSCK at boot

2016-12-01 Thread Luescher Claude 

Hello All,

Thanks for the answers, I have gotten multiple good solutions here. Yes 
Indeed I have not provided some key details, well the OpenBSD 5.2 boxes 
were running in Vmware Server 2.X free until they were migrated to 
Vmware Workstation 8,9 and finally to Workstation 12 boxes.

HDD was set to IDE since that is what Vmware recommends for OpenBSD.

The crashes and filesystem corruptions never been OpenBSD's fault but 
outside circumstances (power outages, vm servers run out of memory froze 
the vms, disk DMA errors caused whole VMM to hang until reboot etc).


I have now successfully tested OpenBSD6.0's auto recovery in Vmware 12.0 
by copying bunch of small files from other machine through ftp and 
pulling the plug (killing the VMX pid), at start it always fixed all the 
errors so upgrading to 6.0 will be the solution I choose.


Good to see the clean and precise system engineering work which went 
into OpenBSD, hopefully it will never get corrupted by System(d) and 
alikes, in the future I should migrate even more servers to OpenBSD.


On 2016-11-28 12:36, Stuart Henderson wrote:

On 2016-11-24, Peter N. M. Hansteen  wrote:
As far as I can remember, OpenBSD does indeed run a file system check 
at
boot if there are indications that the system did not shut down 
cleanly.

I don't think the system has changed very much in that respect at all
for a very long time.


Correct. But /etc/rc uses fsck -p which only allows minor repairs
automatically and requires intervention for major repairs (which are
more likely to lose data).

On simple remote firewall boxes (where failing to boot is as big a 
problem

as a toasted filesystem) I modify this.


Next, look into what caused those file systems to go bad in the first
place.


Yes, very much this.

Re: trouble shooting print errors

2016-12-01 Thread Robert Klein 
Hi,

On Wed, 30 Nov 2016 07:56:16 -0600
f...@speednet.com wrote:

>   I am getting "Broken Pipe" and or "Scheduler not responding"
>   when attempting to print from a laser desk printer directly 
>   attached to usb.
>   OpenBSD 6.0 recognizes the printer in dmesg and when plugged
>   into the usb port.
> 
>   I have been running OpenBSD for several years but never tried
>   to attach a printer.

Did you try to read and
follow /usr/local/share/doc/pkg-readmes/cups-2.1.4 ?

> 
>   I also have downloaded a cups ppd driver for the printer and
>   placed it in the cups ppd directory.
> 
>   If someone can just point me where to research these errors
>   I should be able to determine the cause and maybe get the
>   brother HL2140 directly attached usb  printer working.
> 
>   I see no error messages in dmesg which relate to printing.
> 
> 
>   Thanks in advance.
> 

Best regards
Robert

Re: 350MHz IBM Intel Pentium II runs 5.9 fine

2016-12-01 Thread Craig Skinner 
Hi,

On Wed, 30 Nov 2016 17:09:13 +0100 butresin wrote:
> On 16.11.29Tue 14:12, Craig Skinner wrote:
> > 
> > real mem  = 200740864 (191MB)
> > avail mem = 184385536 (175MB)
> ...
> > spdmem0 at iic0 addr 0x50: 64MB SDRAM non-parity PC100CL3
> > spdmem1 at iic0 addr 0x51: 64MB SDRAM non-parity PC100CL3
> > spdmem2 at iic0 addr 0x52: 64MB SDRAM ECC PC100CL2
> > spdmem3 at iic0 addr 0x55: 1GB DDR2 SDRAM PC2-5000CL5
> 
> This is odd.
> 

None of these IBM Pentium II machines have DDR memory installed.
I don't think it was invented in 1999. The 3 slots are old DIMM.

The other dmesg:

spdmem0 at iic0 addr 0x50: 128MB SDRAM non-parity PC100CL3
spdmem1 at iic0 addr 0x51: 64MB SDRAM non-parity PC100CL3
spdmem2 at iic0 addr 0x52: 64MB SDRAM non-parity PC100CL3
spdmem3 at iic0 addr 0x55: 448MB DDR2 SDRAM PC2-2500CL5

Another identical machine, but with only 2 DIMM slots filled:

spdmem0 at iic0 addr 0x50: 256MB SDRAM non-parity PC133CL2
spdmem1 at iic0 addr 0x51: 256MB SDRAM non-parity PC133CL2
spdmem2 at iic0 addr 0x55: 1GB DDR2 SDRAM PC2-6500CL5

Being an ordinary user, I dunno what that means, but the boxes run fine.

Cheers!
-- 
Craig Skinner | http://linkd.in/yGqkv7