Re: quirks "unsigned package," "Can't find CONTENTS"
>Your package path points to 6.0- release. But your error messages > indicate you've installed a snapshot of -current, the development > breach. Use snapshot packages, or install the release. Thanks! You're right, I had intended to install 6.0 from release, but ended up getting a snapshot ISO. I'll get them back in sync.
quirks "unsigned package," "Can't find CONTENTS"
I'm installing OpenBSD i386 on a fresh new hard drive, I've set PKG_PATH, and I can't add packages- my tries give errors about quirks. Trying a bare "pkg_add quirks" tells me: # pkg_add quirks Error from http://mirrors.mit.edu/pub/OpenBSD/6.0/packages/i386/quirks-2.241.tgz unsigned package Can't find CONTENTS from http://mirrors.mit.edu/pub/OpenBSD/6.0/packages/i386/quirks-2.241.tgz Error from http://mirrors.mit.edu/pub/OpenBSD/6.0/packages/i386/quirks-2.241.tgz unsigned package Can't find CONTENTS from http://mirrors.mit.edu/pub/OpenBSD/6.0/packages/i386/quirks-2.241.tgz --- quirks-2.241 --- Can't install quirks-2.241: bad package Can't install quirks-2.241: bad package # uname -a OpenBSD elided.example.org 6.0 GENERIC.MP#2172 i386 Turning up the verbosity with -vvv it shows another error, "Can't load quirk: Can't load OpenBSD/Quirks.pm in @INC" I feel like I'm missing something very basic. Any ideas on debugging, fixing pkg_add on this install? -y
use of divert-packet and table insertion
I need to use dns blacklisting on incoming email. Spamd caused a user revolt because of its unpredictable delay. smtpd maintainers have more urgent projects than working on filter-dnsbl. What I'd like to do is: in pf.conf pass in on ingress from to any port smtp pass in on ingress from to any port smtp \ divert-to [spamd-port] pass in on ingress from to any port smtp \ #insert proper action here = pass on or send to spamd pass in from any to any port smtp divert-packet \ no-state in dnsbld: bind to divert socket parallel loop: receive syn packet for smtp connection initiate dnsbl lookup good reply: insert address into bad reply: insert address into timeout: insert address into reinject syn packet in dnsbld-cleaner: maintain lists of expiry times and remove entries from the pf tables appropriately What I'd like to happen is that the first syn packet will go to dnsbld. By inserting entries into pf tables, when the syn is finally reinjected or retry syn packets arrive, they will match a table thus creating a state . Subsequent packets of that connection wouldn't go to the divert socket. dnsbld should only see syn packets, usually only one if the dns lookup is quick. What I don't want to do is interpose dnsbld for the entire smtp connection. Is this likely to work? My reading of the code suggests it should but pf is pretty intricate. I don't know if the pf rule optimizer would rearrange things detrimentally. thanks Geoff Steckel
Re: APU2 Internal USB Headers Not Working
> > $ dmesg | egrep -i 'hci|hub|usb' > > Please don't trim things. Full dmesg, full pcidump (preferably -vxx). > Or better, run sendbug as root which includes acpi tables in the mail > it produces (the latter is not presently working in -current, but since > you're running 6.0 you won't run into that). Sorry. I was trying to keep the noise down and wasn’t sure that it qualified as a bug. Will know for next time. Full report posted just now using sendbug. Thanks Stuart, Sam
Re: tfdpd doesn't deliver pxeboot file
> On Oct 6, 2016, at 7:24 AM, Peer Janssen wrote: > > But I realized that there must be something in the dhcpd options and/or > something related to arp resolution, which I didn't grok. So I read some > more RFCs about pxebooting in relation to dhcp and arp, but finally > abandoned this problem for now, because it was taking way too much time > for my current local situation. So, I just happened across my notes for setting up a PXE server from scratch, and thought I’d send this for the benefit of anyone trying to set up a PXE server on OpenBSD 6.0. Granted, this was written to boot an Alix.2d13 using a VMware Fusion OpenBSD VM instance on a MacBook Pro, but it shows the important steps for tftpd and dhcpd. There are bunches of places on the web that talk about this (usually using a Linux instance for setting up PXE), but I was amazed that I basically could go from a freshly installed OBSD6.0 to PXE server in about 5 minutes (depending, really, on how fast I typed). I particularly like this set up for testing builds (I build on the Mac in a VM, use the USB port on the Mac to talk to the alix board’s console, and use the Mac ethernet port for installation). And, again, these were my own notes, not really meant for publication, but I wanted to show how simple it was to set up an OpenBSD PXE server. Sean # # Setting up the PXE Server # # # These notes assume a FRESHLY installed OpenBSD 6.0 system, with no modifications. # Primary NIC is connected (bridged) to another network just to get the sets loaded on it. * Set up httpd — You need to do this unless you put a router/gateway on the network. /etc/httpd.conf: chroot “/var/www" server "default" { listen on * port 80 } * Add the sets to the httpd server mkdir /var/www/htdocs/release Populate /var/www/htdocs/release/OPENBSD_X_Y (from the release server) * Set up dhcpd /etc/dhcpd.conf: subnet 192.168.100.0 netmask 255.255.255.0 { option router 192.168.100.1; range 192.168.100.32 192.168.100.127; filename "pxeboot"; next-server 192.168.100.1; } * Set up tftpd mkdir -p /path/to/tftpdir/etc echo "set tty com0" > /path/to/tftpdir/etc/boot.conf echo "boot bsd.rd" >> /path/to/tftpdir/etc/boot.conf cp /path/to/www/htdpcs/release/OPENBSD_X_Y/bsd.rd /path/to/tftpdir cp /path/to/www/htdpcs/release/OPENBSD_X_Y/pxeboot /path/to/tftpdir * Set up vic1 * vic1 is an added NIC, Bridged to Ethernet. The Ethernet port * is plugged into a switch that the Alix is also plugged into /etc/hostname.vic1: inet 192.168.100.1 255.255.255.0 192.168.100.255 description "PXE Net" chmod 640 /etc/hostname.vic1 * Enable httpd rcctl enable httpd * Enable dhcpd rcctl enable dhcpd rcctl set dhcpd flags vic1 * Turn on tftpd rcctl enable tftpd rcctl set tftpd flags /path/to/tftpdir * Reboot VM (just to verify everything was set up correctly, not really necessary; * you can just bring vic1 up if instead (when you set it up)) * Boot the Alix board, set it to PXE boot (S on startup) and set the board rate to 9600 or whatever speed you want. * It should boot into bsd.rd
Re: Booting BSD on a Libreboot system - documentation needed
Look. Please leave the drama off the lists. Any discussion against drama is also drama. Can my mail be the last on the topic please? People who have jumped onto this list from the outside without respecting our community are the most disrespectful of all. It should be all about code. If it works, it'll be used by people. If it doesn't work, it won't be used by people. That's it. Don't try to upsell a process by politicizing it, it really does not work. > To be clear, it's not "the libreboot side" but rather "The Leah Rowe side" > - to date she has not offered any evidence of her accusations. > From my viewpoint it seems VERY doubtful that the FSF would be bigoted > towards trans people and i'm inclined not to believe the accusation. > > Leah: I also have to ask why you are only now looking into supporting the > BSDs better. The GNU project is not anti-BSD as you seem to believe. > > Remember that GRUB contains code to load BSD kernels - in fact the last > time I installed OpenBSD I did so by loading bsd.rd from GRUB. > > Leah - you might remember me as GarethTheGreat on freenode. I had a lot of > respect for your efforts with libreboot and gluglug and hoped to buy > a laptop from you at some point. I will no longer do so as I am a proud > supporter of the FSF and can see you actively slandering some good people. > > I'd rather not drag the OpenBSD mailing lists into such drama so I will not > comment further. > > > --- > âLanie, Iâm going to print more printers. Lots more printers. One for > everyone. Thatâs worth going to jail for. Thatâs worth anything.â - > Printcrime by Cory Doctrow > > Please avoid sending me Word or PowerPoint attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > > On Thu, Oct 6, 2016 at 1:09 PM, wrote: > > > On Thu, 6 Oct 2016 15:05:04 +1100 > > Aaron Mason wrote: > > > > > Holy frijole, just reading some of the responses from the some people > > > in GNU - I'm at the point where I'm not entirely convinced that GNU > > > isn't a cult, with Stallman as the high almighty leader. > > > > I am suspicious of both sides. Libreboot's team talks about > > "transgender discrimination" of employees at GNU, without actually > > explaining what went on over at GNU that was anything serious, or > > anything "transgender" related. > > > > The Libreboot side claims some people got fired just for being > > transgender. I could not see anything more than just that claim, and a > > list of employees who were "discriminated" against. > > > > However, all the GNU side responses, as cult-ish as they are, are > > somewhat valid if Leah and co have set the copyright to the FSF, in > > which case there is no easy way out other than a fork. Leah and co have > > to be careful, because have a look at this: > > http://www.guidestar.org/FinDocuments/2007/412/165/ > > 2007-412165986-036368a0-9.pdf > > > > As of writing this message, we are in the 2010's, where anyone and > > everyone uses "(trans)gender discrimination" or "racial discrimination" > > to avoid accountability. A little suspicion, cynicism, and scepticism > > could reduce potential embarrassment.
Re: Booting BSD on a Libreboot system - documentation needed
Do any of you mind to drop the off topic, pretty please? it's a thread about booting BSD on hardware with the libreboot BIOS/UEFI. Not... whatever you are doing here. 2016-10-06 23:15 GMT+02:00 Gareth Nelson : > To be clear, it's not "the libreboot side" but rather "The Leah Rowe side" > - to date she has not offered any evidence of her accusations. > From my viewpoint it seems VERY doubtful that the FSF would be bigoted > towards trans people and i'm inclined not to believe the accusation. > > Leah: I also have to ask why you are only now looking into supporting the > BSDs better. The GNU project is not anti-BSD as you seem to believe. > > Remember that GRUB contains code to load BSD kernels - in fact the last > time I installed OpenBSD I did so by loading bsd.rd from GRUB. > > Leah - you might remember me as GarethTheGreat on freenode. I had a lot of > respect for your efforts with libreboot and gluglug and hoped to buy > a laptop from you at some point. I will no longer do so as I am a proud > supporter of the FSF and can see you actively slandering some good people. > > I'd rather not drag the OpenBSD mailing lists into such drama so I will not > comment further. > > > --- > “Lanie, I’m going to print more printers. Lots more printers. One for > everyone. That’s worth going to jail for. That’s worth anything.” - > Printcrime by Cory Doctrow > > Please avoid sending me Word or PowerPoint attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > > On Thu, Oct 6, 2016 at 1:09 PM, wrote: > >> On Thu, 6 Oct 2016 15:05:04 +1100 >> Aaron Mason wrote: >> >> > Holy frijole, just reading some of the responses from the some people >> > in GNU - I'm at the point where I'm not entirely convinced that GNU >> > isn't a cult, with Stallman as the high almighty leader. >> >> I am suspicious of both sides. Libreboot's team talks about >> "transgender discrimination" of employees at GNU, without actually >> explaining what went on over at GNU that was anything serious, or >> anything "transgender" related. >> >> The Libreboot side claims some people got fired just for being >> transgender. I could not see anything more than just that claim, and a >> list of employees who were "discriminated" against. >> >> However, all the GNU side responses, as cult-ish as they are, are >> somewhat valid if Leah and co have set the copyright to the FSF, in >> which case there is no easy way out other than a fork. Leah and co have >> to be careful, because have a look at this: >> http://www.guidestar.org/FinDocuments/2007/412/165/ >> 2007-412165986-036368a0-9.pdf >> >> As of writing this message, we are in the 2010's, where anyone and >> everyone uses "(trans)gender discrimination" or "racial discrimination" >> to avoid accountability. A little suspicion, cynicism, and scepticism >> could reduce potential embarrassment. > -- Cordialement, Coues Ludovic +336 148 743 42
Re: Booting BSD on a Libreboot system - documentation needed
To be clear, it's not "the libreboot side" but rather "The Leah Rowe side" - to date she has not offered any evidence of her accusations. >From my viewpoint it seems VERY doubtful that the FSF would be bigoted towards trans people and i'm inclined not to believe the accusation. Leah: I also have to ask why you are only now looking into supporting the BSDs better. The GNU project is not anti-BSD as you seem to believe. Remember that GRUB contains code to load BSD kernels - in fact the last time I installed OpenBSD I did so by loading bsd.rd from GRUB. Leah - you might remember me as GarethTheGreat on freenode. I had a lot of respect for your efforts with libreboot and gluglug and hoped to buy a laptop from you at some point. I will no longer do so as I am a proud supporter of the FSF and can see you actively slandering some good people. I'd rather not drag the OpenBSD mailing lists into such drama so I will not comment further. --- âLanie, Iâm going to print more printers. Lots more printers. One for everyone. Thatâs worth going to jail for. Thatâs worth anything.â - Printcrime by Cory Doctrow Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html On Thu, Oct 6, 2016 at 1:09 PM, wrote: > On Thu, 6 Oct 2016 15:05:04 +1100 > Aaron Mason wrote: > > > Holy frijole, just reading some of the responses from the some people > > in GNU - I'm at the point where I'm not entirely convinced that GNU > > isn't a cult, with Stallman as the high almighty leader. > > I am suspicious of both sides. Libreboot's team talks about > "transgender discrimination" of employees at GNU, without actually > explaining what went on over at GNU that was anything serious, or > anything "transgender" related. > > The Libreboot side claims some people got fired just for being > transgender. I could not see anything more than just that claim, and a > list of employees who were "discriminated" against. > > However, all the GNU side responses, as cult-ish as they are, are > somewhat valid if Leah and co have set the copyright to the FSF, in > which case there is no easy way out other than a fork. Leah and co have > to be careful, because have a look at this: > http://www.guidestar.org/FinDocuments/2007/412/165/ > 2007-412165986-036368a0-9.pdf > > As of writing this message, we are in the 2010's, where anyone and > everyone uses "(trans)gender discrimination" or "racial discrimination" > to avoid accountability. A little suspicion, cynicism, and scepticism > could reduce potential embarrassment.
Re: Setting flags on /dev/audio
On 10/06/16 22:44, ludovic coues wrote: misc strip attachment. Please send your diff inline or start a new thread on dev Thanks forthe pointer Ludovic, sys/dev/audio.c: @@ -1537,6 +1537,11 @@ case FIONBIO: /* All handled in the upper FS layer. */ break; +case FIOASYNC: +/* No async mode, so set is an error, unset is a noop. */ +if (*(int *)addr) +error = EINVAL; +break; case AUDIO_GETPOS: mtx_enter(&audio_lock); ap = (struct audio_pos *)addr; test program: #include #include int main(void) { int fd, flags; if ((fd = open("/dev/audio", O_RDWR | O_NDELAY, 0)) < 0) { perror("can't open file"); return fd; } if ((flags = fcntl(fd, F_GETFL)) < 0) perror("can't get flags!\n"); else if (fcntl(fd, F_SETFL, flags & ~(O_NDELAY)) < 0) perror("can't set flags"); else printf("good!\n"); close(fd); return 0; } 2016-10-06 2:15 GMT+02:00 Tobias Brodel : Somehow sent the inverse of the intended diff, all apologies. Please find the proper diff attached. toby/ On 10/06/16 11:07, Tobias Brodel wrote: Hi, I've been working on porting an audio application which uses the OSS compatibility layer. It was throwing warnings at runtime about not being able to set flags on /dev/audio. After searching around I found a diff written by Steven McDonald in the misc@ archives: http://openbsd-archive.7691.n7.nabble.com/perl-fctnl-woes-td276032.html Apparently the issue lies with the removal of the FIOASYNC ioctl(2). I've applied the diff on -CURRENT and it has solved my issues - please find the diff and a test program attached. toby/ [demime 1.01d removed an attachment of type text/x-patch which had a name of sys_dev_audio_c.diff]
autoinstall (eg: disklabel -T) doesn't support templates that specify partition sizes in sectors?
Experimenting with autoinstall(8) and predefined partition layout templates, I was a little surprised to find that disklabel(8) apparently does not support specifying partition sizes givin in sectors, only in units (b,c,k,m,g,t) and/or percentages? Am I missing out on something obvious here? My use case is the need to make autoinstallations that would be installed onto (large) HDD/SSD's but with sector sized boundries such that the installations could fit *exactly* onto, lets say 4 or 8GB flash media. Not the end of the world, of course. I will survive wasting a few kilo- or megabytes. But I got curious as to why templates cannot be specified in sectors? This is OpenBSD 6.0. Cheers, Erling
Re: SPARC64: input/output error on softraid 5 with more than 8 disks
On 2016-10-06 11:34, Kenneth Westerback wrote: 1) Why do you say >8 but only give an example using 10 disks? 2) fdisk and disklabels for all the disks you test would be useful, as would the verbatum output from newfs. 3) The size of the disks would also be useful (although the information above would contain this). 4) To eliminate the size of the resulting volume being a problem and possibly eliminating ffs2 vs ffs issues trying to create a volume with smaller chunks (say 100MB) on each disk would be another useful data point. Ken 1. That was a bit of an assumption on my part, just tested 9 disks and it works fine. My raid arrays have even disk spacing, so using odd numbered arrays is not ideal so i never tested it before hand. I can verify that 10 disk arrays, 11 disk arrays, and 12 disk arrays are broken in the same manner however. 2. To make testing a bit easier i decided to start doing debugging on my Sun T5120 at home. I only have 2 disks, but have setup 10 ~100MB partitions on sd0. # disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST914602SSUN146G duid: 82bafda60ea79f65 flags: vendor bytes/sector: 512 sectors/track: 848 tracks/cylinder: 24 sectors/cylinder: 20352 cylinders: 14089 total sectors: 286739329 boundstart: 0 boundend: 286739329 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 2238720RAID b: 223872 223872RAID c:2867393290 unused d: 223872 447744RAID e: 223872 671616RAID f: 223872 895488RAID g: 223872 1119360RAID h: 223872 1343232RAID i: 223872 1567104RAID j: 223872 1790976RAID k: 223872 2014848RAID #dd After that i setup raid 5 between all of these partitions... # bioctl -c 5 -l sd0a,sd0b,sd0d,sd0e,sd0f,sd0g,sd0h,sd0i,sd0j,sd0k softraid0 sd2 at scsibus2 targ 1 lun 0: SCSI2 0/direct fixed sd2: 981MB, 512 bytes/sector, 2009088 sectors softraid0: RAID 5 volume attached as sd2 # Then add a disklabel to sd2 and format it... # disklabel sd2 # /dev/rsd2c: type: SCSI disk: SCSI disk label: SR RAID 5 duid: 9388bbda6be53605 flags: vendor bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 125 total sectors: 2009088 boundstart: 0 boundend: 2009088 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 20081250 4.2BSD 2048 163841 c: 20090880 unused # # newfs sd2a /dev/rsd2a: 980.5MB in 2008124 sectors of 512 bytes 5 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each super-block backups (for fsck -b #) at: 32, 414688, 829344, 1244000, 1658656, # And now we mount it and try to write data to it... # mount /dev/sd2a /mnt # cd /mnt # dd if=/dev/zero of=test bs=1m count=128 dd: test: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 0.112 secs (0 bytes/sec) # I plan on building a debug kernel tonight see if i can get anything out more out of it.
Re: Large datasize - how to limit physical memory?
Raimo Niskanen wrote: > On Wed, Oct 05, 2016 at 12:34:42PM -0400, Ted Unangst wrote: > > If somebody writes a C program that demonstrates the problem, I'm happy to > > take a look. I'm not installing erlang. > > It has been ages since I wrote a C program from scratch, but here goes: Thanks. That wasn't so bad, was it? :) > And the symptom would be that the ulimit -m limit is not immediately > enforced. The question is if that is a problem? Or rather if I can use > the ulimit -m limit to prevent a process from taking all memory since I > need to set a large ulimit -d size to do clever address comparision tricks > in the Erlang VM. Ah, indeed. So ulimit -m doesn't do anything any more. I'm not sure when it stopped, but the man page reflects ancient history. Sorry about that. Unfortunately, it's not easy to make PROT_NONE stop counting. After all, it may have been mapped read/write, and modified, then mapped none, but we can't discard the page.
security(8) question - how to skip a single file?
I have RTFMed and googled, but I still canât figure out how to do one simple thing: make security(8) ignore a single file that changes on a daily basis, where that file is otherwise monitored due to /etc/mtree/4.4BSD.dist. The file in question is /var/unbound/db/root.key, which I have auto-updating. Yes, I understand why this file is important, but on this particular system, being lulled into complacency by a daily false-positive security(8) report is more of a danger than someone managing to hack the root DNS key. Suggestions or pointers or interpretation of the docs appreciated. Thanks, -Adam
Re: security(8) question - how to skip a single file?
On Thu, Oct 06, 2016 at 08:17:02AM -0500, Adam Thompson wrote: > I have RTFMed and googled, but I still can???t figure out how to do one simple > thing: make security(8) ignore a single file that changes on a daily basis, > where that file is otherwise monitored due to /etc/mtree/4.4BSD.dist. > > > > The file in question is /var/unbound/db/root.key, which I have auto-updating. > > > > Yes, I understand why this file is important, but on this particular system, > being lulled into complacency by a daily false-positive security(8) report is > more of a danger than someone managing to hack the root DNS key. > > > > Suggestions or pointers or interpretation of the docs appreciated. Edit /etc/changelist, see changelist(5). > > > Thanks, > > -Adam
Re: serial input line not working [solved]
Am 22.09.2016 um 04:47 schrieb Philip Guenther: > Backing up to the beginning... > > On Wed, Sep 21, 2016 at 2:39 PM, Peer Janssen wrote: >> I updated an alix.3c3 box from OpenBSD 4.6 release to 6.0 release >> recently via bsd.rd install kernel. >> This went very smoothly, except that now I can't get a serial stream via >> the DB9 serial connector. > Ah, you accessed it under OpenBSD 4.6. That raises two questions: > 1) What was the dmesg when this box ran 4.6? > 2) What was the exact command line you used then Since I riskily upgraded in-place, no chance to get back to a dmesg of the installation which was already history. >> But on that alix box, nothing seems to arrive at the serial line. > The 6.0 dmesg you included doesn't include any "com" drivers that I > recognize, so it doesn't surprise me that nothing seems to work...and > thus the query about what 4.6 reported and what worked there. That was indeed the problem. The solution was to switch a setting in the BIOS which enabled the com0 port. Duh! It was there from the beginning to see, but I didn't know certain OpenBSD terminology yet to understand how the different levels of access to the port were named and interact. E.g. what precisely "configured" (as in "Device not configured") referred to, namely that it's not me who had to do that configuring manually in whatever securelevel etc. of the fine OpenBSD software, but that it should have been the autoconf mecanism of the kernel which should have done it, so I searched around without realizing, what is now obvious to me, too, that the configuration had to take place -- manually indeed -- before OpenBSD even got it's chance to do it's own configuration. So, more RTFM cleared things up, and now I got a better grip on the system. This also enabled me to get gpio working on that and other boards. Great fun! Thanks to all who helped! Great software! Peer -- Peer Janssen - p...@pjk.de
Re: tfdpd doesn't deliver pxeboot file
Am 29.09.2016 um 14:05 schrieb Stuart Henderson: > On 2016-09-28, Peer Janssen wrote: >> # tftpd -d /tftpboot >> >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: Operation timed out >> tftpd: 192.168.0.81: read request for 'pxeboot' >> tftpd: 192.168.0.81: Operation timed out > Check your firewall rules. The packets where the file is actually > transferred come from a high numbered source port: > > Request $high_port_A -> port 69 > First file packet $high_port_B -> $high_port_A > Ack $high_port_A -> $high_port_B > Second file packet $high_port_B -> $high_port_A > etc. > > I suspect you might not be allowing the return packets. Adding "log" > to any "block" rules that you have and watch "tcpdump -neipflog0" > probably gives you some clues. Thank you for this hint. Frankly, I find it generally enthusing to realize the power of the tools you OpenBSD ecosystem create. The pflog0 live tcpdump log revealed that no packets at all were dropped, and even turning off pf completely didn't change the behavior. But I realized that there must be something in the dhcpd options and/or something related to arp resolution, which I didn't grok. So I read some more RFCs about pxebooting in relation to dhcp and arp, but finally abandoned this problem for now, because it was taking way too much time for my current local situation. That alix2d13 is now working fine, although I finally installed it via CF-Disk, now that I got that reader. (I'm not working in my home lab, so I didn't have that part handy, what made my try using pxeboot in the first place.) Maybe I'll try pxebooting again later, either just to get to the bottom of it, or using it for installing a row of servers, because I still like the idea of that method. Peer -- Peer Janssen - p...@pjk.de
Re: OpenBSD 6.0 bsd.rd doesn't boot on soekris net4801 [wrap up]
Wrap-up: The net4801 is now working as expected. (Before reading his post,) I did exactly what Nick suggested. This worked well. Lesson learned: mixing bootloader and kernel from different releases doesn't necessarily work. Another lesson: An intuition told me that I might have had to sync after dd'ing an image to the new CF card before taking it out of the zillion-in-1 adapter (before any automatic sync occured, that is). A log confirmed that I indeed forgot that sync. The reinstallation then should have solved any of these. Thanks to all who helped, or encouraged me by contributing their comparative working or failing cases! Peer Am 02.10.2016 um 17:54 schrieb Peer Janssen: > Goal: Upgrade a working soekris net4801 from OpenBSD 4.6 to 6.0. > > First I copied the complete 256 MB SiliconDrive CF-Disk to a newer > SanDisk 8 GB Ultra one and rebootet, which worked smoothly and fine. > > I took the bsd.rd from an OpenBSD 6.0 i386 machine: > > # ls -l /bsd.rd > -rw-r--r-- 1 root wheel 7173390 Sep 20 19:17 /bsd.rd > # md5 /bsd.rd > MD5 (/bsd.rd) = 191559b8c5907ca34c144462366b021a > # dmesg > OpenBSD 6.0 (GENERIC) #1917: Tue Jul 26 12:48:33 MDT 2016 > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC > cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" > 586-class) 499 MHz > cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW > > [snip] > > put it in / of a working soekris net4801 with OpenBSD 4.6 in order to > jump-upgrade the system, but it doesn't boot the 6.0 bsd.rd install image: > > $ cu -l /dev/ttyS0 -s 19200 > Connected. > 1 > Using drive 0, partition 3. > Loading... > probing: pc0 com0 com1 pci mem[639K 255M a20=on] > disk: hd0+ >>> OpenBSD/i386 BOOT 3.02 > switching console to com0 > >> OpenBSD/i386 BOOT 3.02 > boot> stty com0 19200 > > com0: 19200 baud > boot> set tty com0 > switching console to com0 >>> OpenBSD/i386 BOOT 3.02 > boot> boot bsd.rd > booting hd0a:bsd.rd: 3211188+1318224+2061312+0+442368 > [72+298576+282894]=0x744144 > entry point at 0x2000d4 > cu: Got hangup signal > > Disconnected. > ==> So here is where it brakes. Immediate reconnect: > > $ cu -l /dev/ttyS0 -s 19200 > Connected. > > [snip: more empty lines] > ==> it goes into a reboot like this: > > comBIOS ver. 1.28 20050529 Copyright (C) 2000-2005 Soekris Engineering. > > net4801 > > 0256 Mbyte MemoryCPU Geode 266 Mhz > > Pri Mas SDCFHS-008G LBA Xlt 974-255-63 7831 Mbyte > > Slot Vend Dev ClassRev Cmd Stat CL LT HT Base1Base2 Int > --- > 0:00:0 1078 0001 0600 0107 0280 00 00 00 > 0:06:0 100B 0020 0200 0107 0290 00 3F 00 E101 A000 10 > 0:07:0 100B 0020 0200 0107 0290 00 3F 00 E201 A0001000 10 > 0:08:0 100B 0020 0200 0107 0290 00 3F 00 E301 A0002000 10 > 0:10:0 104C AC23 06040002 0107 0210 08 3F 01 > 0:18:2 100B 0502 01018001 0005 0280 00 00 00 > 0:19:0 0E11 A0F8 0C031008 0117 0280 08 38 00 A0003000 11 > 1:00:0 100B 0020 0200 0107 0290 00 3F 00 D001 A400 05 > 1:01:0 100B 0020 0200 0107 0290 00 3F 00 D101 A4001000 11 > 1:02:0 100B 0020 0200 0107 0290 00 3F 00 D201 A4002000 05 > 1:03:0 100B 0020 0200 0107 0290 00 3F 00 D301 A4003000 11 > > 1 Seconds to automatic boot. Press Ctrl-P for entering Monitor. > > comBIOS Monitor. Press ? for help. > [snip] > ==> For comparison and giving machine details, booting into the working > OpenBSD 4.6: >> boot > Using drive 0, partition 3. > Loading... > probing: pc0 com0 com1 pci mem[639K 255M a20=on] > disk: hd0+ >>> OpenBSD/i386 BOOT 3.02 > switching console to com0 > >> OpenBSD/i386 BOOT 3.02 > boot> > booting hd0a:/bsd: 6563548+1052072 [52+345584+327881]=0x7e7ce8 > entry point at 0x200120 > > [ using 673892 bytes of bsd ELF symbol table ] > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2009 OpenBSD. All rights reserved. > http://www.OpenBSD.org > > OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009 > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC > cpu0: Geode(TM) Integrated Processor by National Semi ("Geode by NSC" > 586-class) 267 MHz > cpu0: FPU,TSC,MSR,CX8,CMOV,MMX > real mem = 268005376 (255MB) > avail mem = 250331136 (238MB) > mainbus0 at root > bios0 at mainbus0: AT/286+ BIOS, date 20/50/29, BIOS32 rev. 0 @ 0xf7840 > pcibios0 at bios0: rev 2.0 @ 0xf/0x1 > pcibios0: pcibios_get_intr_routing - function not supported > pcibios0: PCI IRQ Routing information unavailable. > pcibios0: PCI bus #1 is the last bus > bios0: ROM list: 0xc8000/0x9000 > cpu0 at mainbus0: (uniprocessor) > cpu0: TSC disabled > pci0 at mainbus0 bus 0: configuration mode 1 (bios) > pchb0 at pci0 dev 0 function 0 "Cyrix GXm PCI" rev 0
Re: W^X issues running valgrind
On Thu, Oct 06, 2016 at 12:57:43PM +0100, Stuart Henderson wrote: > On 2016/10/06 13:23, David Coppa wrote: > > On Thu, Oct 6, 2016 at 12:50 PM, Andreas Kusalananda Kähäri > > wrote: > > > Hi, > > > > > > Let me know if this should be on ports rather than here. > > > > > > I'm following OpenBSD current on amd64, updating the system a couple of > > > times a week, and I'm using valgrind from ports to check a C program for > > > memory leaks. However, since recently (sorry, can't specify closer, > > > within the last couple of months) I get a W^X violation when I try it. > > > > devel/valgrind is missing the USE_WXNEEDED=Yes marker. > > valgrind works by preloading an .so file and wrapping library functions > to override with its own versions. > > You will at least need to link the program under test with -Wl,-z,wxneeded > but you might need to do more than this. > Adding USE_WXNEEDED=Yes to the valgrind port cuts down the error from valgrind to just valgrind: mmap(0x108000, 4550656) failed in UME with error 12 (Cannot allocate memory). ... and a notification of a W^X violation from the kernel as before. Adding "-Wl,-z,wxneeded" when linking my application makes no difference. I'm still trying to run it under /home with wxneeded added to the mount flags as before. Is there anything else I could try? -- Andreas Kusalananda Kähäri Bioinformatics Developer NBIS, Uppsala University http://www.nbis.se/ [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: netsnmpd Fails to Start on Current
On 2016-10-04, Theodore Wynnychenko wrote: > # /usr/local/sbin/snmpd -L e > kvm_openfiles: Operation not permitted > kvm_openfiles: /dev/mem: Operation not permitted Kernel virtual memory access is no longer permitted by the kernel on a normally running system. The relevant parts of net-snmp will need to be disabled or rewritten.
Re: Booting BSD on a Libreboot system - documentation needed
On Thu, 6 Oct 2016 15:05:04 +1100 Aaron Mason wrote: > Holy frijole, just reading some of the responses from the some people > in GNU - I'm at the point where I'm not entirely convinced that GNU > isn't a cult, with Stallman as the high almighty leader. I am suspicious of both sides. Libreboot's team talks about "transgender discrimination" of employees at GNU, without actually explaining what went on over at GNU that was anything serious, or anything "transgender" related. The Libreboot side claims some people got fired just for being transgender. I could not see anything more than just that claim, and a list of employees who were "discriminated" against. However, all the GNU side responses, as cult-ish as they are, are somewhat valid if Leah and co have set the copyright to the FSF, in which case there is no easy way out other than a fork. Leah and co have to be careful, because have a look at this: http://www.guidestar.org/FinDocuments/2007/412/165/2007-412165986-036368a0-9.pdf As of writing this message, we are in the 2010's, where anyone and everyone uses "(trans)gender discrimination" or "racial discrimination" to avoid accountability. A little suspicion, cynicism, and scepticism could reduce potential embarrassment.
Re: W^X issues running valgrind
On 2016/10/06 13:23, David Coppa wrote: > On Thu, Oct 6, 2016 at 12:50 PM, Andreas Kusalananda Kähäri > wrote: > > Hi, > > > > Let me know if this should be on ports rather than here. > > > > I'm following OpenBSD current on amd64, updating the system a couple of > > times a week, and I'm using valgrind from ports to check a C program for > > memory leaks. However, since recently (sorry, can't specify closer, > > within the last couple of months) I get a W^X violation when I try it. > > devel/valgrind is missing the USE_WXNEEDED=Yes marker. valgrind works by preloading an .so file and wrapping library functions to override with its own versions. You will at least need to link the program under test with -Wl,-z,wxneeded but you might need to do more than this.
Re: W^X issues running valgrind
On Thu, Oct 6, 2016 at 12:50 PM, Andreas Kusalananda Kähäri wrote: > Hi, > > Let me know if this should be on ports rather than here. > > I'm following OpenBSD current on amd64, updating the system a couple of > times a week, and I'm using valgrind from ports to check a C program for > memory leaks. However, since recently (sorry, can't specify closer, > within the last couple of months) I get a W^X violation when I try it. devel/valgrind is missing the USE_WXNEEDED=Yes marker. Ciao! David
W^X issues running valgrind
Hi, Let me know if this should be on ports rather than here. I'm following OpenBSD current on amd64, updating the system a couple of times a week, and I'm using valgrind from ports to check a C program for memory leaks. However, since recently (sorry, can't specify closer, within the last couple of months) I get a W^X violation when I try it. $ pwd /home/kk/Work/Development/MrBayes $ valgrind src/mb --80065:0:aspacem <<< SHOW_SEGMENTS: out_of_memory (21 segments, 0 segnames) --80065:0:aspacem0: RSVN 00-0003ff 64m - SmFixed --80065:0:aspacem1: 000400-0037ff832m --80065:0:aspacem2: ANON 003800-003835 3538944 r-x-- --80065:0:aspacem3: 003836-003845efff 1044480 --80065:0:aspacem4: FILE 003845f000-00384f4fff 614400 r d=0x000 i=0 o=3534848 (-1) --80065:0:aspacem5: 00384f5000-00385f4fff 1048576 --80065:0:aspacem6: FILE 00385f5000-00385fdfff 36864 rw--- d=0x000 i=0 o=4149248 (-1) --80065:0:aspacem7: ANON 00385fe000-00385fefff4096 rw--- --80065:0:aspacem8: 00385ff000-00386fdfff 1044480 --80065:0:aspacem9: FILE 00386fe000-00386fefff4096 rw--- d=0x000 i=0 o=4186112 (-1) --80065:0:aspacem 10: ANON 00386ff000-003a150fff 26m rw--- --80065:0:aspacem 11: 003a151000-0332374fff 12162m --80065:0:aspacem 12: ANON 0332375000-0332375fff4096 r-x-- --80065:0:aspacem 13: 0332376000-0801ff 19708m --80065:0:aspacem 14: RSVN 080200-0802000fff4096 - SmFixed --80065:0:aspacem 15: 0802001000-0f 32735m --80065:0:aspacem 16: RSVN 10-7f7ffdff9fff 130495g - SmFixed --80065:0:aspacem 17: ANON 7f7ffdffa000-7f7fffbf9fff 28m - --80065:0:aspacem 18: ANON 7f7fffbfa000-7f7f8fff 4190208 rw--- --80065:0:aspacem 19: ANON 7f7f9000-7f7f9fff4096 - --80065:0:aspacem 20: RSVN 7f7fa000- 16383e - SmFixed --80065:0:aspacem >>> --80065-- core:0/ 0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/ 0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 8 rzB --80065-- dinfo :0/ 0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/ 0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 8 rzB --80065-- (null) :0/ 0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/ 0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 0 rzB --80065-- demangle:0/ 0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/ 0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 8 rzB --80065-- ttaux :0/ 0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/ 0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 8 rzB --80065-- translate:fast SP updates identified: 0 ( --%) --80065-- translate: generic_known SP updates identified: 0 ( --%) --80065-- translate: generic_unknown SP updates identified: 0 ( --%) --80065-- tt/tc: 0 tt lookups requiring 0 probes --80065-- tt/tc: 0 fast-cache updates, 0 flushes --80065-- transtab: new0 (0 -> 0; ratio 0:10) [0 scs] --80065-- transtab: dumped 0 (0 -> ??) --80065-- transtab: discarded 0 (0 -> ??) --80065-- scheduler: 0 event checks. --80065-- scheduler: 0 indir transfers, 0 misses (1 in 0) --80065-- scheduler: 0/0 major/minor sched events. --80065--sanity: 0 cheap, 0 expensive checks. ==80065== ==80065== Valgrind's memory management: out of memory: ==80065==newSuperblock's request for 4194304 bytes failed. ==80065==64700416 bytes have already been allocated. ==80065== Valgrind cannot continue. Sorry. ==80065== ==80065== There are several possible reasons for this. ==80065== - You have some kind of memory limit in place. Look at the ==80065== output of 'ulimit -a'. Is there a limit on the size of ==80065== virtual memory or address space? ==80065== - You have run out of swap space. ==80065== - Valgrind has a bug. If you think this is the case or you are ==80065== not sure, please let us know and we'll try to fix it. ==80065== Please note that programs can take substantially more memory than ==80065== normal when running under Valgrind tools, eg. up to twice or ==80065== more, depending on the tool. On a 64-bit machine, Valgrind ==80065== should be able to make use of up 32GB memory. On a 32-bit ==80065== machine, Valgrind should be able to use all the memory available ==80065== to a single process, up to 4GB if that's how you have your ==80065== kernel configured. Most 32-bit Linux setups allow a maximum of ==80065== 3GB per process. ==80065== ==80065== Whatever the reason, Valgrind cannot continue. Sorry. $ dmesg | tail vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at r
Re: Large datasize - how to limit physical memory?
On Wed, Oct 05, 2016 at 12:34:42PM -0400, Ted Unangst wrote: > If somebody writes a C program that demonstrates the problem, I'm happy to > take a look. I'm not installing erlang. It has been ages since I wrote a C program from scratch, but here goes: #include #include #include int main() { size_t len = 0; void *p1, *p2; printf("Pid: %ld\n", (long) getpid()); /* 12 GB PROT_NONE [anon] */ p1 = mmap(NULL, ((size_t)12) << 30, PROT_NONE, MAP_ANON, -1, 0); /* 200 MB read/write [anon] */ p2 = mmap(NULL, ((size_t)200) << 20, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0); printf("p1: %p, p2: %p\n", p1, p2); fgetln(stdin, &len); } $ ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 16777216 stack(kbytes)8192 lockedmem(kbytes)2612782 memory(kbytes) 1 nofiles(descriptors) 1024 processes1024 $ ./a.out Pid: 56334 p1: 0x1bcb4718, p2: 0x1bca5f10 # procmap 56334 : 1BCA5F10 204800K read/write [ anon ] : 1BCB4718 12582912K [ anon ] : And the symptom would be that the ulimit -m limit is not immediately enforced. The question is if that is a problem? Or rather if I can use the ulimit -m limit to prevent a process from taking all memory since I need to set a large ulimit -d size to do clever address comparision tricks in the Erlang VM. / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: APU2 Internal USB Headers Not Working
On 2016-10-06, Sam Vaughan wrote: > $ dmesg | egrep -i 'hci|hub|usb' Please don't trim things. Full dmesg, full pcidump (preferably -vxx). Or better, run sendbug as root which includes acpi tables in the mail it produces (the latter is not presently working in -current, but since you're running 6.0 you won't run into that).
Re: State of IPsec, iked (OpenIKED) and redundancy (CARP)
Hello Jasper, I wanted to use iked in a redundant configuration too and wasn't sure whether iked and sasyncd play nice together. I contacted Reyk Floeter (the main developer of iked) and it turns out there is room for improvement. We use OpenBSD for the Muniam managed firewalls and need redundant iked for our customers. We will be sponsoring Reyk's work to improve iked redundancy. I expect that Reyk will have something soon but the timing depends on him. Daniel Jasper Siepkes wrote on 28-9-2016 11:07: Hi everyone @ misc! I'm trying to determine what the state is of using iked (OpenIKED) with redundancy (with CARP). Should such a setup work in OpenBSD 6.0? The iked.conf (5) man page implies that using CARP for redundancy is a supported configuration: "This option is used for setups using sasyncd(8) and carp(4) to provide redundancy.". However after some digging I'm leaning towards it was something that used to work but doesn't work anymore (at least not in 6.0). The issue I bumped into; I'm using OpenBSD 6.0 (fully patched) and CARP and iked by themselves work fine. The problems start when trying to have iked use the CARP IP address instead of the IP of the host it self. iked says in it's logs that it uses the CARP IP as source IP in the messages it sends but in reality (checked with tcpdump) it doesn't. It uses the IP of the interface with the default route. After some digging I found someone on the list who encountered the same problem: "IKED/carp/sasyncd: Wrong source ip address/No IKEv2 response" [1]. The response is: "iked generates some packets before binding, so they have whatever source address is on the interface that holds the outgoing route to the destination.". I also found a post in the list called "iked+CARP/ active, passive"[2] which implies that iked + CARP actually does work. But since that post is from 2011 I'm guessing it broke somewhere between 2011 and 2016. If the current state is indeed that using CARP with iked is not an working option perhaps we should modify the iked.conf (5) man page to clearly state that? On a related note; I got bitten by the bug fixed in the patch: "Fix an infinite loop in iked"[3]. I manually patched my build with it but perhaps it's a good candidate for inclusion in the 6.0 patch branch? Regards, Jasper [1] https://marc.info/?l=openbsd-misc&m=145924380931352&w=2 [2] https://marc.info/?l=openbsd-misc&m=131850193524708&w=2 [3] https://marc.info/?l=openbsd-tech&m=147348976311128&w=2