Re: umsm0: this device is not using CDC notify message in intr pipe. HP Compaq dc5750
On 6/29/19, Chris Cappuccio wrote: > Kihaguru Gathura [pqscr...@gmail.com] wrote: >> Hello, >> >> Huawei E303 modem now detaches in OpenBSD 6.5 This works fine on >> OpenBSD 6.2 same machine. >> > > There's a remote chance that this is fixed in 6.5-current. Some USB work > has been going on. But if that doesn't work, you'll have to try more > kernels > to figure out when this stopped working. Try 6.5-current first, then 6.4, > and then 6.3 to see which are broken. > This was working up and until OpenBSD 6.4 amd64.
Re: umsm: sparc64
On 7/4/19, Claudio Jeker wrote: > On Thu, Jul 04, 2019 at 12:52:15PM +0300, Kihaguru Gathura wrote: >> Hereby attached the new multiprocessor kernel with umsm working ok. >> >> The error message appears for each connection made to cuaU. This might >> potentially populate dmesg logs over time. >> >> Error message: >> umsm0: this device is not using CDC notify message in intr pipe. >> Please send your dmesg to , thanks. >> umsm0: intr buffer 0xc1 0x1 0x3 0x0 0x0 0x0 0x0: > > Can you try this USB device on a different OpenBSD machine (e.g. an amd64 > one). I wonder if this is the device just sending a bad message along the > way. The first byte should be 0xa1 (UCDC_NOTIFICATION) and not 0xc1. The device works well without errors on OpenBSD 6.4 amd64 (IBM Thinkpad T60) and OpenBSD 6.5 arm64 ( Raspberry Pi 3 Model B V1.2) The device detaches and has error (umsm2: this device is not using CDC notify message in intr pipe.) on OpenBSD 6.5 amd64 (HP dc5750 MT) of which i already sent email to b...@openbsd.org. Thanks. >> Kihaguru. >> >> www# dmesg >> console is /pci@83,4000/isa@7/su@0,3f8 >> Copyright (c) 1982, 1986, 1989, 1991, 1993 >> The Regents of the University of California. All rights >> reserved. >> Copyright (c) 1995-2019 OpenBSD. All rights reserved. >> https://www.OpenBSD.org >> >> OpenBSD 6.5 (WWW.MP) #0: Thu Jul 4 08:43:43 EAT 2019 >> kihag...@www.datastore.ke:/usr/src/sys/arch/sparc64/compile/WWW.MP >> real mem = 17179869184 (16384MB) >> avail mem = 16862576640 (16081MB) >> mpath0 at root >> scsibus0 at mpath0: 256 targets >> mainbus0 at root: Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V >> cpu0 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz >> cpu0: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K >> external (64 b/l) >> cpu1 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz >> cpu1: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K >> external (64 b/l) >> psycho0 at mainbus0 addr 0xfffb2000: SUNW,psycho, impl 0, version 4, ign >> c0 >> psycho0: bus range 0-0, PCI bus 0 >> psycho0: dvma map fe00-, STC0 enabled >> pci0 at psycho0 >> ebus0 at pci0 dev 1 function 0 "Sun PCIO EBus2" rev 0x01 >> "FJSV,scfc" at ebus0 addr 21-210085, 22-220031, 26-260001, >> 27-28 ivec 0x23 not configured >> "FJSV,flashprom" at ebus0 addr 0-3f not configured >> clock1 at ebus0 addr 25-251fff: mk48t59 >> "FJSV,panel" at ebus0 addr 210011-210011 ivec 0x25 not configured >> ebus1 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 >> com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo >> com0: console >> com1 at ebus1 addr 2e8-2ef ivec 0x2b: ns16550a, 16 byte fifo >> hme0 at pci0 dev 1 function 1 "Sun HME" rev 0x01: ivec 0xe1, address >> 00:0b:5d:f3:a7:5c >> nsphyter0 at hme0 phy 1: DP83843 10/100 PHY, rev. 0 >> mpi0 at pci0 dev 2 function 1 "Symbios Logic 53c1030" rev 0x07: ivec 0xe0 >> mpi0: 0, firmware 1.0.12.0 >> scsibus1 at mpi0: 16 targets, initiator 7 >> sym0 at scsibus1 targ 0 lun 0: SCSI2 >> 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR >> sd0 at scsibus0 targ 0 lun 0: SCSI2 >> 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR >> sd0: 70007MB, 512 bytes/sector, 143374738 sectors >> sym1 at scsibus1 targ 1 lun 0: SCSI2 >> 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL >> sd1 at scsibus0 targ 1 lun 0: SCSI2 >> 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL >> sd1: 70007MB, 512 bytes/sector, 143374738 sectors >> mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 >> mpi0: target 1 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 >> pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: >> DMA, channel 0 configured to native-PCI, channel 1 configured to >> native-PCI >> pciide0: using ivec 0xe4 for native-PCI interrupt >> atapiscsi0 at pciide0 channel 0 drive 0 >> scsibus2 at atapiscsi0: 2 targets >> cd0 at scsibus2 targ 0 lun 0: ATAPI >> 5/cdrom removable >> cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 >> pciide0: channel 1 disabled (no drives) >> ohci0 at pci0 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec >> 0xe9, version 1.0, legacy support >> usb0 at ohci0: USB revision 1.0 >> uhub0 at usb0 configuration 1 interface 0 "Acer Labs OHCI root hub" >> rev 1.00/1.00 addr 1 >> psycho1 at mainbus0 addr 0xfff9e000: SUNW,psycho, impl 0, version 4, ign >> c0 >> psycho1: bus range 128-128, PCI bus 128 >> psycho1: dvma map fe00-, STC0 enabled, STC1 enabled >> pci1 at psycho1 >> bge0 at pci1 dev 1 function 0 "Fujitsu PRIMEPOWER250/450 LAN" rev >> 0x02, BCM5702/5703 A2 (0x1002): ivec 0xc0, address 00:0b:5d:f4:27:5c >> brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 >> "counter-timer" at mainbus0 addr 0xfff8bc00 not configured >> umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI HUAWEI >> Mobile" rev 2.00/1.02 addr 2 >> ucom0 at umsm0 >> umsm1 at
Re: ed(1) man page doesn't mention use of single / and ?
To add to Ian's reference. "Ed Mastery" is the only book I know specific to ed(1). Mo On Thu, 4 Jul 2019, 6:54 pm ropers Do I understand correctly that this is in reference to these parts of man > 1 ed: > > > /re/ > >The next line containing the regular expression re. The search wraps > to the beginning of the buffer and continues down to the current line, if > necessary. “//” repeats the last search. > > > ?re? > >The previous line containing the regular expression re. The search > wraps to the end of the buffer and continues up to the current line, if > necessary. “??” repeats the last search. > > and: > > > (1,$)g/re/command-list > >Applies command-list to each of the addressed lines matching a > regular expression re. The current address is set to the line currently > matched before command-list is executed. At the end of the g command, the > current address is set to the last line affected by command-list. If no > lines were matched, the current line number remains unchanged. > > > >Each command in command-list must be on a separate line, and every > line except for the last must be terminated by a backslash (‘\’). Any > commands are allowed, except for g, G, v, and V. A newline alone in > command-list is equivalent to a p command. > > > If yes, then the corresponding parts of ed.1 are: > > .It / Ns Ar re Ns / > The next line containing the regular expression > .Ar re . > The search wraps to the beginning of the buffer and continues down to the > current line, if necessary. > .Qq // > repeats the last search. > .It Pf ? Ar re ? > The previous line containing the regular expression > .Ar re . > The search wraps to the end of the buffer and continues up to the > current line, if necessary. > .Qq ?? > repeats the last search. > > and: > > .It Xo > .Pf (1,$) Ic g No / > .Ar re No / Ar command-list > .Xc > .Sm on > Applies > .Ar command-list > to each of the addressed lines matching a regular expression > .Ar re . > The current address is set to the line currently matched before > command-list is executed. > At the end of the > .Ic g > command, the current address is set to the last line affected by > command-list. > If no lines were matched, > the current line number remains unchanged. > .Pp > Each command in > .Ar command-list > must be on a separate line, > and every line except for the last must be terminated by a backslash > .Pq Sq \e . > Any commands are allowed, except for > .Ic g , > .Ic G , > .Ic v , > and > .Ic V . > A newline alone in command-list is equivalent to a > .Ic p > command. > .Sm off > > I'm not actually sure how to rewrite that. Would this call for > separate /re, ?re and (1,$)g/re entries, or would it suffice to say > that the second question mark or slash can be omitted if immediately > followed by a newline? > > Does anyone else have any ideas? > > NB: In case people haven't seen it, here's an excellent ed(1) > tutorial: https://sanctum.geek.nz/arabesque/actually-using-ed/ > I just thought I'd mention that. > > Ian > > On 03/07/2019, mazoc...@disroot.org wrote: > > Hi! > > > > I am not good at explaining something shortly and clearly to fit into > > proper documentation, so I'll just describe my experience here. > > > > Terminating regular expressions with / or ? is necessary only if they > > are followed by commands, otherwise the following are legal in both > > OpenBSD ed, Plan 9 ed and GNU ed: > > /something > > / > > ? > > g/ing > > > > I hope I made life of many ed users easier :) > > > > > >
Re: ed(1) man page doesn't mention use of single / and ?
Do I understand correctly that this is in reference to these parts of man 1 ed: > /re/ >The next line containing the regular expression re. The search wraps to > the beginning of the buffer and continues down to the current line, if > necessary. “//” repeats the last search. > ?re? >The previous line containing the regular expression re. The search wraps > to the end of the buffer and continues up to the current line, if necessary. > “??” repeats the last search. and: > (1,$)g/re/command-list >Applies command-list to each of the addressed lines matching a regular > expression re. The current address is set to the line currently matched > before command-list is executed. At the end of the g command, the current > address is set to the last line affected by command-list. If no lines were > matched, the current line number remains unchanged. > >Each command in command-list must be on a separate line, and every line > except for the last must be terminated by a backslash (‘\’). Any commands are > allowed, except for g, G, v, and V. A newline alone in command-list is > equivalent to a p command. If yes, then the corresponding parts of ed.1 are: .It / Ns Ar re Ns / The next line containing the regular expression .Ar re . The search wraps to the beginning of the buffer and continues down to the current line, if necessary. .Qq // repeats the last search. .It Pf ? Ar re ? The previous line containing the regular expression .Ar re . The search wraps to the end of the buffer and continues up to the current line, if necessary. .Qq ?? repeats the last search. and: .It Xo .Pf (1,$) Ic g No / .Ar re No / Ar command-list .Xc .Sm on Applies .Ar command-list to each of the addressed lines matching a regular expression .Ar re . The current address is set to the line currently matched before command-list is executed. At the end of the .Ic g command, the current address is set to the last line affected by command-list. If no lines were matched, the current line number remains unchanged. .Pp Each command in .Ar command-list must be on a separate line, and every line except for the last must be terminated by a backslash .Pq Sq \e . Any commands are allowed, except for .Ic g , .Ic G , .Ic v , and .Ic V . A newline alone in command-list is equivalent to a .Ic p command. .Sm off I'm not actually sure how to rewrite that. Would this call for separate /re, ?re and (1,$)g/re entries, or would it suffice to say that the second question mark or slash can be omitted if immediately followed by a newline? Does anyone else have any ideas? NB: In case people haven't seen it, here's an excellent ed(1) tutorial: https://sanctum.geek.nz/arabesque/actually-using-ed/ I just thought I'd mention that. Ian On 03/07/2019, mazoc...@disroot.org wrote: > Hi! > > I am not good at explaining something shortly and clearly to fit into > proper documentation, so I'll just describe my experience here. > > Terminating regular expressions with / or ? is necessary only if they > are followed by commands, otherwise the following are legal in both > OpenBSD ed, Plan 9 ed and GNU ed: > /something > / > ? > g/ing > > I hope I made life of many ed users easier :) > >
Re: ssh-keygen specify max keysize for ed25519
On 2019-07-03, jungle boogie wrote: > $ ssh-keygen -t ed25519 -b 1000 > Bits has bad value 1000 (too large) That's fine, that's a generic argument parsing error. > $ ssh-keygen -t ed25519 -b 2 > key bits exceeds maximum 16384 That error makes no sense. ED25519 keys have a fixed length, and 16384 is the limit for RSA keys. Looks like an error path that dates back to when only DSA and RSA were supported and that wasn't updated when additional key types were added. I'll send a tweak to tech@. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: OT: hardware war with manufacturers (espionage claims)
On 04/07/2019, cho...@jtan.com wrote: > ropers writes: >> ::I put on my robe and tinfoil hat.:: > >> ... Wow. The things you guys come up with ... > > I mean yeah, I guess, in theory maybe? > > Of course in order to achieve this level of evil you need highly competent > governments and corporations but that's no problem right? > > Matthew Remember, you can have the effects of conspiracy without there being a conspiracy, so long as the preconditions exist and things and people lean a certain way. (after A. Goldman) Honestly, with some of the stuff I just mentioned, and with "smart" features soon to be included in just about any type of product by default, I expect that sooner or later, **transistor pollution** will become a real problem. I could go on if people wanted to hear it, though this is OT. Toodles. Ian
Re: DNS Race Condition on Boot
Aren’t new version enabling (some.host) to not race ? On Thu, Jul 4, 2019 at 7:26 AM Andy Lemin wrote: > Hey guys. > > Thanks for the ideas. Sadly I cannot use static IPs as we don’t control > the domains. > > I think I’ll use Otto’s suggestion as I am already doing that to provide a > black hole table for the spamhaus drop list. So I’ll just enhance that > script to manage some more tables > > After all, the current fqdns in pf.conf can still go out of date (pf only > resolves dns -> IP once during rule apply). So this solves that too. > > Cheers, Andy. > > > > Sent from a teeny tiny keyboard, so please excuse typos > > > On 4 Jul 2019, at 09:18, Otto Moerbeek wrote: > > > >> On Thu, Jul 04, 2019 at 09:14:19AM +0100, Andy Lemin wrote: > >> > >> Hi guys, > >> > >> Is anyone else aware of the Unbound and PF race condition that exists > when FQDNs are used in pf.conf with a local Unbound server? > > > > Yes, it's an obvious one isn't it? > > > >> > >> The issue occurs when pf starts before unbound, but where pf fails to > start as it cannot resolve some DNS names.. and so unbound also fails to > work when it is started later in the boot because pf failed to start.. > >> > >> The only solution I’ve found so far is to add some commands to > /etc/rc.local (run end of boot) to temporarily disable (the failed) pf, > restart unbound, and restart pf again now unbound is working. > >> > >> Just wondering if anyone knows of a cleaner workaround? PS; Using an > external DNS server in resolv.conf is not an option in this scenario. > > > > Do not use DNS names in pf.conf. Use a IP addresses or a table filled > > from a file. Run some script to update the file periodically. If it > > changed kick pf. > > > >-Otto > > > > -- -- - Knowing is not enough; we must apply. Willing is not enough; we must do
Re: AESGCM supported in IKEv1 phase 2 but not in phase 1
On 2019-07-04, Daniel Polak wrote: > Just tried to configure an IKEv1 VPN connection with AESGCM but isakmpd > only supports that in phase 2 but not in phase 1. > See https://marc.info/?l=openbsd-cvs=128516335103833=2 for the commit. > > Is there any special reason why AESGCM has not been implemented for > phase 1 as well? AFAIK AES-GCM isn't in the spec for IKEv1 phase 1. See e.g. https://tools.ietf.org/html/rfc4543#section-5.1
Re: DNS Race Condition on Boot
Hey guys. Thanks for the ideas. Sadly I cannot use static IPs as we don’t control the domains. I think I’ll use Otto’s suggestion as I am already doing that to provide a black hole table for the spamhaus drop list. So I’ll just enhance that script to manage some more tables After all, the current fqdns in pf.conf can still go out of date (pf only resolves dns -> IP once during rule apply). So this solves that too. Cheers, Andy. Sent from a teeny tiny keyboard, so please excuse typos > On 4 Jul 2019, at 09:18, Otto Moerbeek wrote: > >> On Thu, Jul 04, 2019 at 09:14:19AM +0100, Andy Lemin wrote: >> >> Hi guys, >> >> Is anyone else aware of the Unbound and PF race condition that exists when >> FQDNs are used in pf.conf with a local Unbound server? > > Yes, it's an obvious one isn't it? > >> >> The issue occurs when pf starts before unbound, but where pf fails to start >> as it cannot resolve some DNS names.. and so unbound also fails to work when >> it is started later in the boot because pf failed to start.. >> >> The only solution I’ve found so far is to add some commands to /etc/rc.local >> (run end of boot) to temporarily disable (the failed) pf, restart unbound, >> and restart pf again now unbound is working. >> >> Just wondering if anyone knows of a cleaner workaround? PS; Using an >> external DNS server in resolv.conf is not an option in this scenario. > > Do not use DNS names in pf.conf. Use a IP addresses or a table filled > from a file. Run some script to update the file periodically. If it > changed kick pf. > >-Otto >
Re: Full Disk Encryption and (U)pgrade via snapshot installer?
Thank you for the tip there Maksym! I'll be sure to remember it. On Thu, Jul 04, 2019 at 12:59:37PM +0300, Maksym Sheremet wrote: > In -current you should create sd0 manually. > > # cd /dev && sh MAKEDEV sd0 > > And then use bioctl as usual. > > On Thu, Jul 04, 2019 at 02:02:39AM +, Chris Humphries wrote: > > Hello, > > > > I have full disk encryption active on my machine. I would like to > > follow -current, and the FAQ[1] said to grab an install image for a > > snapshot and (U)pgrade. > > > > The problem is, I'm not sure how to manually get my FDE disk live via > > shell from the installer. > > > > I tried doing disklabel on likely candidates, but disklabel claims wd0 > > device not configured and sd0 doesn't exist. I didn't see anything > > obvious on the -current FAQ. > > > > Is it possible to do an upgrade from the installer for a FDE disk? > > > > Thank you! > > > > 1: https://www.openbsd.org/faq/current.html > > > > > > -- > > Chris Humphries > > 5223 9548 E1DE DE87 F509 1888 8141 8451 6338 DD29 > > > > -- > MS
Re: umsm: sparc64
On 2019/07/04 12:52, Kihaguru Gathura wrote: > Hereby attached the new multiprocessor kernel with umsm working ok. > > The error message appears for each connection made to cuaU. This might > potentially populate dmesg logs over time. > > Error message: > umsm0: this device is not using CDC notify message in intr pipe. > Please send your dmesg to , thanks. > umsm0: intr buffer 0xc1 0x1 0x3 0x0 0x0 0x0 0x0: Please send your dmesg to b...@openbsd.org :-) > Kihaguru. > > www# dmesg > console is /pci@83,4000/isa@7/su@0,3f8 > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2019 OpenBSD. All rights reserved. https://www.OpenBSD.org > > OpenBSD 6.5 (WWW.MP) #0: Thu Jul 4 08:43:43 EAT 2019 > kihag...@www.datastore.ke:/usr/src/sys/arch/sparc64/compile/WWW.MP > real mem = 17179869184 (16384MB) > avail mem = 16862576640 (16081MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root: Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V > cpu0 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz > cpu0: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K > external (64 b/l) > cpu1 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz > cpu1: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K > external (64 b/l) > psycho0 at mainbus0 addr 0xfffb2000: SUNW,psycho, impl 0, version 4, ign c0 > psycho0: bus range 0-0, PCI bus 0 > psycho0: dvma map fe00-, STC0 enabled > pci0 at psycho0 > ebus0 at pci0 dev 1 function 0 "Sun PCIO EBus2" rev 0x01 > "FJSV,scfc" at ebus0 addr 21-210085, 22-220031, 26-260001, > 27-28 ivec 0x23 not configured > "FJSV,flashprom" at ebus0 addr 0-3f not configured > clock1 at ebus0 addr 25-251fff: mk48t59 > "FJSV,panel" at ebus0 addr 210011-210011 ivec 0x25 not configured > ebus1 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 > com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo > com0: console > com1 at ebus1 addr 2e8-2ef ivec 0x2b: ns16550a, 16 byte fifo > hme0 at pci0 dev 1 function 1 "Sun HME" rev 0x01: ivec 0xe1, address > 00:0b:5d:f3:a7:5c > nsphyter0 at hme0 phy 1: DP83843 10/100 PHY, rev. 0 > mpi0 at pci0 dev 2 function 1 "Symbios Logic 53c1030" rev 0x07: ivec 0xe0 > mpi0: 0, firmware 1.0.12.0 > scsibus1 at mpi0: 16 targets, initiator 7 > sym0 at scsibus1 targ 0 lun 0: SCSI2 > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR > sd0 at scsibus0 targ 0 lun 0: SCSI2 > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR > sd0: 70007MB, 512 bytes/sector, 143374738 sectors > sym1 at scsibus1 targ 1 lun 0: SCSI2 > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL > sd1 at scsibus0 targ 1 lun 0: SCSI2 > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL > sd1: 70007MB, 512 bytes/sector, 143374738 sectors > mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 > mpi0: target 1 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 > pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: > DMA, channel 0 configured to native-PCI, channel 1 configured to > native-PCI > pciide0: using ivec 0xe4 for native-PCI interrupt > atapiscsi0 at pciide0 channel 0 drive 0 > scsibus2 at atapiscsi0: 2 targets > cd0 at scsibus2 targ 0 lun 0: ATAPI > 5/cdrom removable > cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 > pciide0: channel 1 disabled (no drives) > ohci0 at pci0 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec > 0xe9, version 1.0, legacy support > usb0 at ohci0: USB revision 1.0 > uhub0 at usb0 configuration 1 interface 0 "Acer Labs OHCI root hub" > rev 1.00/1.00 addr 1 > psycho1 at mainbus0 addr 0xfff9e000: SUNW,psycho, impl 0, version 4, ign c0 > psycho1: bus range 128-128, PCI bus 128 > psycho1: dvma map fe00-, STC0 enabled, STC1 enabled > pci1 at psycho1 > bge0 at pci1 dev 1 function 0 "Fujitsu PRIMEPOWER250/450 LAN" rev > 0x02, BCM5702/5703 A2 (0x1002): ivec 0xc0, address 00:0b:5d:f4:27:5c > brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 > "counter-timer" at mainbus0 addr 0xfff8bc00 not configured > umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > ucom0 at umsm0 > umsm1 at uhub0 port 1 configuration 1 interface 1 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > ucom1 at umsm1 > umsm2 at uhub0 port 1 configuration 1 interface 2 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > ucom2 at umsm2 > umass0 at uhub0 port 1 configuration 1 interface 3 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > umass0: using SCSI over Bulk-Only > scsibus3 at umass0: 2 targets, initiator 0 > cd1 at scsibus3 targ 1 lun 0: SCSI2 > 5/cdrom removable > umass1 at uhub0 port 1 configuration 1 interface 4 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > umass1: using SCSI over Bulk-Only > scsibus4 at umass1: 2 targets, initiator 0 > sd2 at scsibus4 targ 1
Re: umsm: sparc64
On Thu, Jul 04, 2019 at 12:52:15PM +0300, Kihaguru Gathura wrote: > Hereby attached the new multiprocessor kernel with umsm working ok. > > The error message appears for each connection made to cuaU. This might > potentially populate dmesg logs over time. > > Error message: > umsm0: this device is not using CDC notify message in intr pipe. > Please send your dmesg to , thanks. > umsm0: intr buffer 0xc1 0x1 0x3 0x0 0x0 0x0 0x0: Can you try this USB device on a different OpenBSD machine (e.g. an amd64 one). I wonder if this is the device just sending a bad message along the way. The first byte should be 0xa1 (UCDC_NOTIFICATION) and not 0xc1. > Kihaguru. > > www# dmesg > console is /pci@83,4000/isa@7/su@0,3f8 > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2019 OpenBSD. All rights reserved. https://www.OpenBSD.org > > OpenBSD 6.5 (WWW.MP) #0: Thu Jul 4 08:43:43 EAT 2019 > kihag...@www.datastore.ke:/usr/src/sys/arch/sparc64/compile/WWW.MP > real mem = 17179869184 (16384MB) > avail mem = 16862576640 (16081MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root: Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V > cpu0 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz > cpu0: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K > external (64 b/l) > cpu1 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz > cpu1: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K > external (64 b/l) > psycho0 at mainbus0 addr 0xfffb2000: SUNW,psycho, impl 0, version 4, ign c0 > psycho0: bus range 0-0, PCI bus 0 > psycho0: dvma map fe00-, STC0 enabled > pci0 at psycho0 > ebus0 at pci0 dev 1 function 0 "Sun PCIO EBus2" rev 0x01 > "FJSV,scfc" at ebus0 addr 21-210085, 22-220031, 26-260001, > 27-28 ivec 0x23 not configured > "FJSV,flashprom" at ebus0 addr 0-3f not configured > clock1 at ebus0 addr 25-251fff: mk48t59 > "FJSV,panel" at ebus0 addr 210011-210011 ivec 0x25 not configured > ebus1 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 > com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo > com0: console > com1 at ebus1 addr 2e8-2ef ivec 0x2b: ns16550a, 16 byte fifo > hme0 at pci0 dev 1 function 1 "Sun HME" rev 0x01: ivec 0xe1, address > 00:0b:5d:f3:a7:5c > nsphyter0 at hme0 phy 1: DP83843 10/100 PHY, rev. 0 > mpi0 at pci0 dev 2 function 1 "Symbios Logic 53c1030" rev 0x07: ivec 0xe0 > mpi0: 0, firmware 1.0.12.0 > scsibus1 at mpi0: 16 targets, initiator 7 > sym0 at scsibus1 targ 0 lun 0: SCSI2 > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR > sd0 at scsibus0 targ 0 lun 0: SCSI2 > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR > sd0: 70007MB, 512 bytes/sector, 143374738 sectors > sym1 at scsibus1 targ 1 lun 0: SCSI2 > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL > sd1 at scsibus0 targ 1 lun 0: SCSI2 > 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL > sd1: 70007MB, 512 bytes/sector, 143374738 sectors > mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 > mpi0: target 1 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 > pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: > DMA, channel 0 configured to native-PCI, channel 1 configured to > native-PCI > pciide0: using ivec 0xe4 for native-PCI interrupt > atapiscsi0 at pciide0 channel 0 drive 0 > scsibus2 at atapiscsi0: 2 targets > cd0 at scsibus2 targ 0 lun 0: ATAPI > 5/cdrom removable > cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 > pciide0: channel 1 disabled (no drives) > ohci0 at pci0 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec > 0xe9, version 1.0, legacy support > usb0 at ohci0: USB revision 1.0 > uhub0 at usb0 configuration 1 interface 0 "Acer Labs OHCI root hub" > rev 1.00/1.00 addr 1 > psycho1 at mainbus0 addr 0xfff9e000: SUNW,psycho, impl 0, version 4, ign c0 > psycho1: bus range 128-128, PCI bus 128 > psycho1: dvma map fe00-, STC0 enabled, STC1 enabled > pci1 at psycho1 > bge0 at pci1 dev 1 function 0 "Fujitsu PRIMEPOWER250/450 LAN" rev > 0x02, BCM5702/5703 A2 (0x1002): ivec 0xc0, address 00:0b:5d:f4:27:5c > brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 > "counter-timer" at mainbus0 addr 0xfff8bc00 not configured > umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > ucom0 at umsm0 > umsm1 at uhub0 port 1 configuration 1 interface 1 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > ucom1 at umsm1 > umsm2 at uhub0 port 1 configuration 1 interface 2 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > ucom2 at umsm2 > umass0 at uhub0 port 1 configuration 1 interface 3 "HUAWEI HUAWEI > Mobile" rev 2.00/1.02 addr 2 > umass0: using SCSI over Bulk-Only > scsibus3 at umass0: 2 targets, initiator 0 > cd1 at scsibus3 targ 1 lun 0: SCSI2 > 5/cdrom removable > umass1 at
Re: Full Disk Encryption and (U)pgrade via snapshot installer?
In -current you should create sd0 manually. # cd /dev && sh MAKEDEV sd0 And then use bioctl as usual. On Thu, Jul 04, 2019 at 02:02:39AM +, Chris Humphries wrote: > Hello, > > I have full disk encryption active on my machine. I would like to > follow -current, and the FAQ[1] said to grab an install image for a > snapshot and (U)pgrade. > > The problem is, I'm not sure how to manually get my FDE disk live via > shell from the installer. > > I tried doing disklabel on likely candidates, but disklabel claims wd0 > device not configured and sd0 doesn't exist. I didn't see anything > obvious on the -current FAQ. > > Is it possible to do an upgrade from the installer for a FDE disk? > > Thank you! > > 1: https://www.openbsd.org/faq/current.html > > > -- > Chris Humphries > 5223 9548 E1DE DE87 F509 1888 8141 8451 6338 DD29 > -- MS
Re: How to clear the screen correctly in ksh
Joseph Mayer writes: As far as I am aware, since about 6 months ksh clears the screen on ctrl+L by default, no bind is needed anymore? You're right; it's specifically stated in the Changelog for 6.5: https://www.openbsd.org/plus65.html which apparently i didn't read closely enough. :-/ Alexis.
Re: How to clear the screen correctly in ksh
On 2019-07-04, Максим wrote: > Hello > In bash I can press Ctrl-l to clear the screen. > In ksh this key combination does not work. I can clear the screen only > using the command "clear". > > How can I do this using hotkeys in ksh? > And how to do this when in vi mode? > > I tried a workaround by assigning the key combination to Ctrl-l to cwm: > cat .cwmrc > unbind-key C-l > bind-key C-l "/usr/bin/clear" > After reloading cwm there is no effect. > > -- > Maksim Rodin > > Update to 6.5. (Or if, like me, you hate the ^L = clear behaviour, restord the previous behaviour with "bind ^L=redraw").
Re: umsm: sparc64
Hereby attached the new multiprocessor kernel with umsm working ok. The error message appears for each connection made to cuaU. This might potentially populate dmesg logs over time. Error message: umsm0: this device is not using CDC notify message in intr pipe. Please send your dmesg to , thanks. umsm0: intr buffer 0xc1 0x1 0x3 0x0 0x0 0x0 0x0: Kihaguru. www# dmesg console is /pci@83,4000/isa@7/su@0,3f8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2019 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.5 (WWW.MP) #0: Thu Jul 4 08:43:43 EAT 2019 kihag...@www.datastore.ke:/usr/src/sys/arch/sparc64/compile/WWW.MP real mem = 17179869184 (16384MB) avail mem = 16862576640 (16081MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root: Fujitsu Siemens PRIMEPOWER250 2x SPARC64 V cpu0 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz cpu0: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K external (64 b/l) cpu1 at mainbus0: FJSV,SPARC64-V (rev 5.1) @ 1979 MHz cpu1: physical 128K instruction (64 b/l), 128K data (64 b/l), 3072K external (64 b/l) psycho0 at mainbus0 addr 0xfffb2000: SUNW,psycho, impl 0, version 4, ign c0 psycho0: bus range 0-0, PCI bus 0 psycho0: dvma map fe00-, STC0 enabled pci0 at psycho0 ebus0 at pci0 dev 1 function 0 "Sun PCIO EBus2" rev 0x01 "FJSV,scfc" at ebus0 addr 21-210085, 22-220031, 26-260001, 27-28 ivec 0x23 not configured "FJSV,flashprom" at ebus0 addr 0-3f not configured clock1 at ebus0 addr 25-251fff: mk48t59 "FJSV,panel" at ebus0 addr 210011-210011 ivec 0x25 not configured ebus1 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 com0 at ebus1 addr 3f8-3ff ivec 0x2b: ns16550a, 16 byte fifo com0: console com1 at ebus1 addr 2e8-2ef ivec 0x2b: ns16550a, 16 byte fifo hme0 at pci0 dev 1 function 1 "Sun HME" rev 0x01: ivec 0xe1, address 00:0b:5d:f3:a7:5c nsphyter0 at hme0 phy 1: DP83843 10/100 PHY, rev. 0 mpi0 at pci0 dev 2 function 1 "Symbios Logic 53c1030" rev 0x07: ivec 0xe0 mpi0: 0, firmware 1.0.12.0 scsibus1 at mpi0: 16 targets, initiator 7 sym0 at scsibus1 targ 0 lun 0: SCSI2 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR sd0 at scsibus0 targ 0 lun 0: SCSI2 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00RAR_AAN0P5200RAR sd0: 70007MB, 512 bytes/sector, 143374738 sectors sym1 at scsibus1 targ 1 lun 0: SCSI2 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL sd1 at scsibus0 targ 1 lun 0: SCSI2 0/direct fixed serial.FUJITSU_MAT3073N_SUN72G_000506B00SSL_AAN0P5200SSL sd1: 70007MB, 512 bytes/sector, 143374738 sectors mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 mpi0: target 1 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using ivec 0xe4 for native-PCI interrupt atapiscsi0 at pciide0 channel 0 drive 0 scsibus2 at atapiscsi0: 2 targets cd0 at scsibus2 targ 0 lun 0: ATAPI 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 disabled (no drives) ohci0 at pci0 dev 10 function 0 "Acer Labs M5237 USB" rev 0x03: ivec 0xe9, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 configuration 1 interface 0 "Acer Labs OHCI root hub" rev 1.00/1.00 addr 1 psycho1 at mainbus0 addr 0xfff9e000: SUNW,psycho, impl 0, version 4, ign c0 psycho1: bus range 128-128, PCI bus 128 psycho1: dvma map fe00-, STC0 enabled, STC1 enabled pci1 at psycho1 bge0 at pci1 dev 1 function 0 "Fujitsu PRIMEPOWER250/450 LAN" rev 0x02, BCM5702/5703 A2 (0x1002): ivec 0xc0, address 00:0b:5d:f4:27:5c brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 "counter-timer" at mainbus0 addr 0xfff8bc00 not configured umsm0 at uhub0 port 1 configuration 1 interface 0 "HUAWEI HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom0 at umsm0 umsm1 at uhub0 port 1 configuration 1 interface 1 "HUAWEI HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom1 at umsm1 umsm2 at uhub0 port 1 configuration 1 interface 2 "HUAWEI HUAWEI Mobile" rev 2.00/1.02 addr 2 ucom2 at umsm2 umass0 at uhub0 port 1 configuration 1 interface 3 "HUAWEI HUAWEI Mobile" rev 2.00/1.02 addr 2 umass0: using SCSI over Bulk-Only scsibus3 at umass0: 2 targets, initiator 0 cd1 at scsibus3 targ 1 lun 0: SCSI2 5/cdrom removable umass1 at uhub0 port 1 configuration 1 interface 4 "HUAWEI HUAWEI Mobile" rev 2.00/1.02 addr 2 umass1: using SCSI over Bulk-Only scsibus4 at umass1: 2 targets, initiator 0 sd2 at scsibus4 targ 1 lun 0: SCSI2 0/direct removable vscsi0 at root scsibus5 at vscsi0: 256 targets softraid0 at root scsibus6bootpath: /pci@83,4000/FJSV,ulsa@2,1/disk@0,0 root on sd0a (e489192361503865.a) swap on sd0b dump on sd0b umsm0: this device is not using CDC notify message in intr pipe. Please send your dmesg to
Re: How to clear the screen correctly in ksh
‐‐‐ Original Message ‐‐‐ On Thursday, 4 July 2019 16:39, Alexis wrote: > Максим a23s4a2...@yandex.ru writes: > > In bash I can press Ctrl-l to clear the screen. > > In ksh this key combination does not work. I can clear the > > screen only > > using the command "clear". > > How can I do this using hotkeys in ksh? > > i have this in my .kshrc: > > bind -m '^L=^Uclear^J^Y' > > Alexis. As far as I am aware, since about 6 months ksh clears the screen on ctrl+L by default, no bind is needed anymore?
AESGCM supported in IKEv1 phase 2 but not in phase 1
Just tried to configure an IKEv1 VPN connection with AESGCM but isakmpd only supports that in phase 2 but not in phase 1. See https://marc.info/?l=openbsd-cvs=128516335103833=2 for the commit. Is there any special reason why AESGCM has not been implemented for phase 1 as well?
Re: How to clear the screen correctly in ksh
Максим writes: In bash I can press Ctrl-l to clear the screen. In ksh this key combination does not work. I can clear the screen only using the command "clear". How can I do this using hotkeys in ksh? i have this in my .kshrc: bind -m '^L=^Uclear^J^Y' Alexis.
Re: DNS Race Condition on Boot
On Thu, Jul 04, 2019 at 09:14:19AM +0100, Andy Lemin wrote: > Hi guys, > > Is anyone else aware of the Unbound and PF race condition that exists when > FQDNs are used in pf.conf with a local Unbound server? Yes, it's an obvious one isn't it? > > The issue occurs when pf starts before unbound, but where pf fails to start > as it cannot resolve some DNS names.. and so unbound also fails to work when > it is started later in the boot because pf failed to start.. > > The only solution I’ve found so far is to add some commands to /etc/rc.local > (run end of boot) to temporarily disable (the failed) pf, restart unbound, > and restart pf again now unbound is working. > > Just wondering if anyone knows of a cleaner workaround? PS; Using an external > DNS server in resolv.conf is not an option in this scenario. Do not use DNS names in pf.conf. Use a IP addresses or a table filled from a file. Run some script to update the file periodically. If it changed kick pf. -Otto
DNS Race Condition on Boot
Hi guys, Is anyone else aware of the Unbound and PF race condition that exists when FQDNs are used in pf.conf with a local Unbound server? The issue occurs when pf starts before unbound, but where pf fails to start as it cannot resolve some DNS names.. and so unbound also fails to work when it is started later in the boot because pf failed to start.. The only solution I’ve found so far is to add some commands to /etc/rc.local (run end of boot) to temporarily disable (the failed) pf, restart unbound, and restart pf again now unbound is working. Just wondering if anyone knows of a cleaner workaround? PS; Using an external DNS server in resolv.conf is not an option in this scenario. Cheers, Andy. Sent from a teeny tiny keyboard, so please excuse typos
How to clear the screen correctly in ksh
Hello In bash I can press Ctrl-l to clear the screen. In ksh this key combination does not work. I can clear the screen only using the command "clear". How can I do this using hotkeys in ksh? And how to do this when in vi mode? I tried a workaround by assigning the key combination to Ctrl-l to cwm: cat .cwmrc unbind-key C-l bind-key C-l "/usr/bin/clear" After reloading cwm there is no effect. -- Maksim Rodin
Re: Feeding DHCP leases into unbound
On Thu, Jun 22, 2017 at 11:47:03AM +0200, Andreas Kusalananda Kähäri wrote: > Hi, > > I have unbound(8) and dhcpd(8) running on a router (OpenBSD 6.1-stable). > dhcpd currently hands out fixed addresses to my clients, but I'd like > these to be allocated dynamically from the common pool, while at the > same time being resolvable. > > Is there an existing solution for feeding the IP-addresses of the leases > that dhcpd hands out into the unbound configuration and reload it, or > would I have to write a script that parses the lease declarations in > /var/db/dhcpd.leases? I have scripted it the other way around. I have comments in /etc/hosts containing the MAC addresses for the hosts and then generate dhcpd and unbound configurations from that. dhcpd offers IP address based on MAC. > > I know about dnsmasq in ports which I believe serves as both DHCP and > DNS server, but I'd rather use the software in the base system if at all > possible. > > Regards, > Kusalananda -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
