Re: axen - need working USB NIC using axen to test driver change

[Carl Trachte]

On Sun, May 3, 2020 at 4:12 PM gwes  wrote:

> Currently axen.c has its PHY address hardwired to 3.
> I have a StarTech which has the PHY at 0.
> The driver currently searches for all PHYs connected to the MII
> and then ignores the result.
> I want to test my fix on devices which work now.
>
> Can anyone point me to a USB NIC which works with axen?
> thanks
> Geoff Steckel
>

I’m using the StarTech usb 3.0 one on the ThinkPad X1 Carbon. I don’t have
the machine booted up at the moment but I’m running OpenBSD 6.6 and it
works with the axen driver.

I also purchased a usb 2.0 one - this is recognized as an axen device but
it did not work on the ThinkPad X1.  I have not yet tried it on another
older laptop.

>
>

Re: How to enable TLS 1.3?

[Chad Hoolie]

‐‐‐ Original Message ‐‐‐
On Thursday 30. April 2020 kl. 16:38, Kevin Chadwick  
wrote:

> On 2020-04-30 13:55, Chad Hoolie wrote:
>
> > Any idea about relayd though? I don't see any mentioning of 1.3 in man 
> > relayd.conf:
>
> I'm not a dev but tls1.3 dropped RSA and I think requires ecdsa key support 
> that
> relayd currently lacks.
>
> Although httpd was originally based on relayd. I assume the code is different
> here because of relayds more complex tls interception and acceleration 
> abilities.
>
> Pound and nginx may be alternatives, but they likely won't protect the key so
> well, if an exploit is found.


Hello,

Is there any chance we can have TLS 1.3 support in relayd in the upcoming 6.7 
release?

There seems to be clear indication that Google and other search engines do 
favor TLS 1.3 sites over 1.2: The Era of TLS 1.3: Measuring Deployment and 
Usewith Active and Passive Methods: https://arxiv.org/pdf/1907.12762.pdf

--Cheers, Chad

Sent with ProtonMail Secure Email.

Re: rc.d: Webserver is removing daemonization - now what?

[Chad Hoolie]

Thank you Marcus, and the rest of you :)

--Chad


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday 3. May 2020 kl. 16:53, Marcus MERIGHI  wrote:

> chad.hoo...@protonmail.com (Chad Hoolie), 2020.05.03 (Sun) 15:43 (CEST):
>
> > So the folks over at my webserver is removing its daemonization
> > feature, telling its users to use systemd/upstart/a process supervisor
> > instead.
>
> Ugly move by upstream!
>
> > But what does this mean to my webserver's startup script in /etc/rc.d,
> > isn't it dependent on the webserver's ability to daemonize?
>
> You could have shown the content of that rc.d(8) script...?
>
> > Pretty sure I can't manually daemonize it by adding a "&" to the end
> > of my rcexecs so...
>
> Read rc.subr(8), look for "rc_bg".
>
> Marcus

axen - need working USB NIC using axen to test driver change

[gwes]

Currently axen.c has its PHY address hardwired to 3.
I have a StarTech which has the PHY at 0.
The driver currently searches for all PHYs connected to the MII
and then ignores the result.
I want to test my fix on devices which work now.

Can anyone point me to a USB NIC which works with axen?
thanks
Geoff Steckel

Re: rc.d: Webserver is removing daemonization - now what?

[Edgar Pettijohn]

On Sun, May 03, 2020 at 04:53:42PM +0200, Marcus MERIGHI wrote:
> chad.hoo...@protonmail.com (Chad Hoolie), 2020.05.03 (Sun) 15:43 (CEST):
> > So the folks over at my webserver is removing its daemonization
> > feature, telling its users to use systemd/upstart/a process supervisor
> > instead.
> 
> Ugly move by upstream!
> 
> > But what does this mean to my webserver's startup script in /etc/rc.d,
> > isn't it dependent on the webserver's ability to daemonize?
> 

what webserver are you using?

> You could have shown the content of that rc.d(8) script...?
> 
> > Pretty sure I can't manually daemonize it by adding a "&" to the end
> > of my rcexecs so...
>

#rc.local
/path/to/server &

> Read rc.subr(8), look for "rc_bg".
> 
> Marcus

rc.d: Why is it reindenting my startup scripts?

[Chad Hoolie]

Hello,

Noticed my startup scripts are being reindented from 2 spaces to 4 whenever I 
run rcctl, just wondering what the point of that was?

Thanks!

--Chad

Sent with ProtonMail Secure Email.

pkg_add can't resolve package - bad major

[katzeilla]

Hi everyone,

I am using OpenBSD 6.6 and I noticed that pkg_add can't install any new
package:

$ doas pkg_add emacs-26.3-no_x11

quirks-3.185 signed on 2020-04-30T09:14:52Z
Can't install libxml-2.9.9 because of libraries
|library iconv.7.0 not found
| /usr/local/lib/libiconv.so.6.0 (libiconv-1.14p3): bad major
Direct dependencies for libxml-2.9.9 resolve to xz-5.2.4 libiconv-1.14p3
Full dependency tree is libiconv-1.14p3 xz-5.2.4
Can't install emacs-26.3-no_x11: can't resolve libxml-2.9.9
Couldn't install emacs-26.3-no_x11 libxml-2.9.9

AFAIK, I am now in a dependency hell, so I tried pkg_check, but it told
me everything is fine.

$ doas pkg_check -vv
Packing-list sanity: ok
Direct dependencies: ok
Reverse dependencies: ok
Files from packages: ok

Sometimes, pkg_add will try to "merge" older version of package to its
newer version, but this doesn't work:

gettext-0.19.8.1p3->gettext-runtime-0.20.1p0 forward dependencies:
| Dependencies of git-2.21.0 on gettext-* don't match
| Dependencies of glib2-2.58.3p8 on gettext-* don't match
| Dependencies of rspamd-1.9.0 on gettext-* don't match
| Dependencies of libksba-1.3.5p1 on gettext-* don't match
| Dependencies of libgpg-error-1.36 on gettext-* don't match
| Dependencies of python-2.7.16 on gettext-* don't match
| Dependencies of vim-8.1.1048-no_x11 on gettext-* don't match
| Dependencies of p11-kit-0.23.15p0 on gettext-* don't match
| Dependencies of gnupg-2.2.12 on gettext-* don't match
| Dependencies of python-3.6.8p0 on gettext-* don't match
Merging git-2.21.0->2.24.2 (ok)
Merging glib2-2.58.3p8->2.60.7p0 (ok)
Merging rspamd-1.9.0->1.9.4 (ok)
Merging libksba-1.3.5p1->1.3.5p2 (ok)
Merging libgpg-error-1.36->1.36p0 (ok)
Merging python-2.7.16->2.7.16p1 (ok)
Merging vim-8.1.1048-no_x11->8.1.2061-no_x11 (ok)
Merging p11-kit-0.23.15p0->0.23.18.1 (ok)
Merging gnupg-2.2.12->2.2.12p0 (ok)
Merging python-3.6.8p0->3.6.9 (ok)
Detected loop, merging sets ok
|
gettext-0.19.8.1p3+git-2.21.0+glib2-2.58.3p8+gnupg-2.2.12+libgpg-error-1.36+libksba-1.3.5p1+p11-kit-0.23.15p0+python-2.7.16+python-3.6.8p0+rspamd-1.9.0+vim-8.1.1048-no_x11->gettext-runtime-0.20.1p0+git-2.24.2+glib2-2.60.7p0+gnupg-2.2.12p0+libgpg-error-1.36p0+libksba-1.3.5p2+p11-kit-0.23.18.1+python-2.7.16p1+python-3.6.9+rspamd-1.9.4+vim-8.1.2061-no_x11
Detected loop, merging sets ok
|
gettext-0.19.8.1p3+git-2.21.0+glib2-2.58.3p8+gnupg-2.2.12+libgpg-error-1.36+libksba-1.3.5p1+p11-kit-0.23.15p0+python-2.7.16+python-3.6.8p0+rspamd-1.9.0+vim-8.1.1048-no_x11->gettext-runtime-0.20.1p0+git-2.24.2+glib2-2.60.7p0+gnupg-2.2.12p0+libgpg-error-1.36p0+libksba-1.3.5p2+p11-kit-0.23.18.1+python-2.7.16p1+python-3.6.9+rspamd-1.9.4+vim-8.1.2061-no_x11
| python-3.7.4
Can't install p11-kit-0.23.18.1 because of libraries
|library iconv.7.0 not found
| /usr/local/lib/libiconv.so.6.0 (libiconv-1.14p3): bad major
|library tasn1.4.1 not found
| /usr/local/lib/libtasn1.so.4.0 (libtasn1-4.13p0): minor is too small
|library sqlite3.37.7 not found
| /usr/local/lib/libsqlite3.so.37.5 (sqlite3-3.27.2p0): minor is too small
|library curl.26.0 not found
| /usr/local/lib/libcurl.so.25.21 (curl-7.64.1): bad major
|library nghttp2.0.15 not found
| /usr/local/lib/libnghttp2.so.0.14 (nghttp2-1.37.0): minor is too small
|library icudata.15.0 not found
| /usr/local/lib/libicudata.so.14.0 (icu4c-63.1): bad major
|library icui18n.15.0 not found
| /usr/local/lib/libicui18n.so.14.0 (icu4c-63.1): bad major
|library icuuc.15.0 not found
| /usr/local/lib/libicuuc.so.14.0 (icu4c-63.1): bad major
|library lapack.7.1 not found
| /usr/local/lib/liblapack.so.6.0 (lapack-3.7.1p0): bad major
|library gnutls.46.3 not found
| /usr/local/lib/libgnutls.so.46.0 (gnutls-3.6.7): minor is too small
Direct dependencies for
gettext-0.19.8.1p3+git-2.21.0+glib2-2.58.3p8+gnupg-2.2.12+libgpg-error-1.36+libksba-1.3.5p1+p11-kit-0.23.15p0+python-2.7.16+python-3.6.8p0+rspamd-1.9.0+vim-8.1.1048-no_x11->gettext-runtime-0.20.1p0+git-2.24.2+glib2-2.60.7p0+gnupg-2.2.12p0+libgpg-error-1.36p0+libksba-1.3.5p2+p11-kit-0.23.18.1+python-2.7.16p1+python-3.6.9+python-3.7.4+rspamd-1.9.4+vim-8.1.2061-no_x11
resolve to libtasn1-4.13p0 libmagic-5.35 pcre-8.41p2 libiconv-1.14p3
icu4c-63.1 bzip2-1.0.6p9 luajit-2.0.5p1 lapack-3.7.1p0 cvsps-2.1p2
libffi-3.2.1p5 libgpg-error-1.36p0 libgcrypt-1.8.4p0 libusb1-1.0.21p1
p5-Error-0.17025 glib2-2.60.7p0 libksba-1.3.5p2 npth-1.6 gnutls-3.6.7
curl-7.64.1 pinentry-1.1.0p0 gettext-runtime-0.20.1p0 libassuan-2.5.1p0
python-3.7.4 xz-5.2.4 sqlite3-3.27.2p0
Full dependency tree is libnettle-3.4.1p0 python-3.7.4 libassuan-2.5.1p0
p11-kit-0.23.18.1 nghttp2-1.37.0 sqlite3-3.27.2p0 xz-5.2.4 npth-1.6
libidn2-2.0.0p0 gmp-6.1.2p3 curl-7.64.1 pinentry-1.1.0p0
libunbound-1.9.1 gnutls-3.6.7 blas-3.7.1p0 gettext-runtime-0.20.1p0
libsecret-0.18.8p0 libgcrypt-1.8.4p0 libgpg-error-1.36p0
libusb1-1.0.21p1 lua-5.1.5p6 p5-Error-0.17025 glib2-2.60.7p0
libksba-1.3.5p2 gcc-libs-4.9.4p18 libiconv-1.14p3 pcre-8.41p2
libmagic-5.35 libtasn1-4.13p0 bzip2-1.0.6p9 icu4c-63.1 lapack-3.7.1p0

rc.d: Webserver is removing daemonization - now what?

[Chad Hoolie]

Hi,

So the folks over at my webserver is removing its daemonization feature, 
telling its users to use systemd/upstart/a process supervisor instead.

But what does this mean to my webserver's startup script in /etc/rc.d, isn't it 
dependent on the webserver's ability to daemonize?

Pretty sure I can't manually daemonize it by adding a "&" to the end of my 
rcexecs so...

--Chad

Sent with ProtonMail Secure Email.

Re: ieee80211 panic on athn reconfig

[Stefan Sperling]

On Fri, Apr 17, 2020 at 12:08:39PM +0200, Jan Stary wrote:
> This is current/i386 on an ALIX (dmesg below) with
> 
>   athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9
>   athn0: AR9280 rev 2 (2T2R), ROM rev 22, address 04:f0:21:01:d6:86
> 
> # cat hostname.athn0
> inet 192.168.33.1 255.255.255.0 NONE
> media autoselect mode 11g mediaopt hostap chan 2
> nwid stare.cz wpakey hovnoPrdel123
> 
> After changing the password, or the channel, or the mode, and doing
> 
> # sh /etc/netstart athn0
> 
> the machine reproducibly panics (cereal script below).
> 
> I have no idea why it panics in ieee80211_encrypt().
> It happens both with clients associated and not.
> 
> Is this known with athn(4)?
> How can I help debug this?
> 
>   Jan
> 
> 
> ddb> show panic
> ieee80211_encrypt: key unset for sw crypto: 0
> 
> ddb> trace
> db_enter() at db_enter+0x4
> panic(d0b83788) at panic+0xcc
> ieee80211_encrypt(d194e030,d195bc00,d194eb00) at ieee80211_encrypt+0x70
> ar5008_tx(d194e000,d195bc00,d19a,2) at ar5008_tx+0x9a
> ar5008_swba_intr(d194e000) at ar5008_swba_intr+0x238
> ar5008_intr(d194e000) at ar5008_intr+0x12f
> intr_handler(f3b1d67c,d1945480) at intr_handler+0x18
> Xintr_legacy9_untramp() at Xintr_legacy9_untramp+0xf7
> end of kernel

Are you using clients which use powersave mode, such as phones?

This trace goes through ar5008_swba_intr(). The only way to get into
ar5008_tx() from there is when group-addressed frames are queued on the
powersave queue of the AP (ic_bss->ni_savedq).

I cannot see this queue being purged anywhere when the interface goes down.
So it seems what happened is that a stale frame was sitting on this queue
and a fatal transmit attempt occurred when the interface came back up after
being re-configured.

Can you please try this diff?

The same panic and trace has also been reported to me by Ted Patterson.

diff ffca677e9e7ca9efd316fa2f2b6572b193c50cf8 /usr/src
blob - f6349c70279687b18ce89f670b732a62f3696271
file + sys/net80211/ieee80211_node.c
--- sys/net80211/ieee80211_node.c
+++ sys/net80211/ieee80211_node.c
@@ -1595,6 +1595,10 @@ ieee80211_node_cleanup(struct ieee80211com *ic, struct
free(ni->ni_unref_arg, M_DEVBUF, ni->ni_unref_arg_size);
ni->ni_unref_arg = NULL;
ni->ni_unref_arg_size = 0;
+
+#ifndef IEEE80211_STA_ONLY
+   mq_purge(>ni_savedq);
+#endif
 }
 
 void
@@ -2047,7 +2051,7 @@ ieee80211_free_allnodes(struct ieee80211com *ic, int c
splx(s);
 
if (clear_ic_bss && ic->ic_bss != NULL)
-   ieee80211_node_cleanup(ic, ic->ic_bss); /* for station mode */
+   ieee80211_node_cleanup(ic, ic->ic_bss);
 }
 
 void

Re: pkg_add can't resolve package - bad major

[Chris Bennett]

On Sun, May 03, 2020 at 01:07:40PM +, katzeilla wrote:
> Hi everyone,
> 
> I am using OpenBSD 6.6 and I noticed that pkg_add can't install any new
> package:
> 
> $ doas pkg_add emacs-26.3-no_x11
> 
> quirks-3.185 signed on 2020-04-30T09:14:52Z
> Can't install libxml-2.9.9 because of libraries
> |library iconv.7.0 not found
> | /usr/local/lib/libiconv.so.6.0 (libiconv-1.14p3): bad major
> Direct dependencies for libxml-2.9.9 resolve to xz-5.2.4 libiconv-1.14p3
> Full dependency tree is libiconv-1.14p3 xz-5.2.4
> Can't install emacs-26.3-no_x11: can't resolve libxml-2.9.9
> Couldn't install emacs-26.3-no_x11 libxml-2.9.9
> 
> AFAIK, I am now in a dependency hell, so I tried pkg_check, but it told
> me everything is fine.
> 
> $ doas pkg_check -vv
> Packing-list sanity: ok
> Direct dependencies: ok
> Reverse dependencies: ok
> Files from packages: ok
> 
> Sometimes, pkg_add will try to "merge" older version of package to its
> newer version, but this doesn't work:
> 
> gettext-0.19.8.1p3->gettext-runtime-0.20.1p0 forward dependencies:
> | Dependencies of git-2.21.0 on gettext-* don't match
> | Dependencies of glib2-2.58.3p8 on gettext-* don't match
> | Dependencies of rspamd-1.9.0 on gettext-* don't match
> | Dependencies of libksba-1.3.5p1 on gettext-* don't match
> | Dependencies of libgpg-error-1.36 on gettext-* don't match
> | Dependencies of python-2.7.16 on gettext-* don't match
> | Dependencies of vim-8.1.1048-no_x11 on gettext-* don't match
> | Dependencies of p11-kit-0.23.15p0 on gettext-* don't match
> | Dependencies of gnupg-2.2.12 on gettext-* don't match
> | Dependencies of python-3.6.8p0 on gettext-* don't match
> Merging git-2.21.0->2.24.2 (ok)
> Merging glib2-2.58.3p8->2.60.7p0 (ok)
> Merging rspamd-1.9.0->1.9.4 (ok)
> Merging libksba-1.3.5p1->1.3.5p2 (ok)
> Merging libgpg-error-1.36->1.36p0 (ok)
> Merging python-2.7.16->2.7.16p1 (ok)
> Merging vim-8.1.1048-no_x11->8.1.2061-no_x11 (ok)
> Merging p11-kit-0.23.15p0->0.23.18.1 (ok)
> Merging gnupg-2.2.12->2.2.12p0 (ok)
> Merging python-3.6.8p0->3.6.9 (ok)
> Detected loop, merging sets ok
> |
> gettext-0.19.8.1p3+git-2.21.0+glib2-2.58.3p8+gnupg-2.2.12+libgpg-error-1.36+libksba-1.3.5p1+p11-kit-0.23.15p0+python-2.7.16+python-3.6.8p0+rspamd-1.9.0+vim-8.1.1048-no_x11->gettext-runtime-0.20.1p0+git-2.24.2+glib2-2.60.7p0+gnupg-2.2.12p0+libgpg-error-1.36p0+libksba-1.3.5p2+p11-kit-0.23.18.1+python-2.7.16p1+python-3.6.9+rspamd-1.9.4+vim-8.1.2061-no_x11
> Detected loop, merging sets ok
> |
> gettext-0.19.8.1p3+git-2.21.0+glib2-2.58.3p8+gnupg-2.2.12+libgpg-error-1.36+libksba-1.3.5p1+p11-kit-0.23.15p0+python-2.7.16+python-3.6.8p0+rspamd-1.9.0+vim-8.1.1048-no_x11->gettext-runtime-0.20.1p0+git-2.24.2+glib2-2.60.7p0+gnupg-2.2.12p0+libgpg-error-1.36p0+libksba-1.3.5p2+p11-kit-0.23.18.1+python-2.7.16p1+python-3.6.9+rspamd-1.9.4+vim-8.1.2061-no_x11
> | python-3.7.4
> Can't install p11-kit-0.23.18.1 because of libraries
> |library iconv.7.0 not found
> | /usr/local/lib/libiconv.so.6.0 (libiconv-1.14p3): bad major
> |library tasn1.4.1 not found
> | /usr/local/lib/libtasn1.so.4.0 (libtasn1-4.13p0): minor is too small
> |library sqlite3.37.7 not found
> | /usr/local/lib/libsqlite3.so.37.5 (sqlite3-3.27.2p0): minor is too small
> |library curl.26.0 not found
> | /usr/local/lib/libcurl.so.25.21 (curl-7.64.1): bad major
> |library nghttp2.0.15 not found
> | /usr/local/lib/libnghttp2.so.0.14 (nghttp2-1.37.0): minor is too small
> |library icudata.15.0 not found
> | /usr/local/lib/libicudata.so.14.0 (icu4c-63.1): bad major
> |library icui18n.15.0 not found
> | /usr/local/lib/libicui18n.so.14.0 (icu4c-63.1): bad major
> |library icuuc.15.0 not found
> | /usr/local/lib/libicuuc.so.14.0 (icu4c-63.1): bad major
> |library lapack.7.1 not found
> | /usr/local/lib/liblapack.so.6.0 (lapack-3.7.1p0): bad major
> |library gnutls.46.3 not found
> | /usr/local/lib/libgnutls.so.46.0 (gnutls-3.6.7): minor is too small
> Direct dependencies for
> gettext-0.19.8.1p3+git-2.21.0+glib2-2.58.3p8+gnupg-2.2.12+libgpg-error-1.36+libksba-1.3.5p1+p11-kit-0.23.15p0+python-2.7.16+python-3.6.8p0+rspamd-1.9.0+vim-8.1.1048-no_x11->gettext-runtime-0.20.1p0+git-2.24.2+glib2-2.60.7p0+gnupg-2.2.12p0+libgpg-error-1.36p0+libksba-1.3.5p2+p11-kit-0.23.18.1+python-2.7.16p1+python-3.6.9+python-3.7.4+rspamd-1.9.4+vim-8.1.2061-no_x11
> resolve to libtasn1-4.13p0 libmagic-5.35 pcre-8.41p2 libiconv-1.14p3
> icu4c-63.1 bzip2-1.0.6p9 luajit-2.0.5p1 lapack-3.7.1p0 cvsps-2.1p2
> libffi-3.2.1p5 libgpg-error-1.36p0 libgcrypt-1.8.4p0 libusb1-1.0.21p1
> p5-Error-0.17025 glib2-2.60.7p0 libksba-1.3.5p2 npth-1.6 gnutls-3.6.7
> curl-7.64.1 pinentry-1.1.0p0 gettext-runtime-0.20.1p0 libassuan-2.5.1p0
> python-3.7.4 xz-5.2.4 sqlite3-3.27.2p0
> Full dependency tree is libnettle-3.4.1p0 python-3.7.4 libassuan-2.5.1p0
> p11-kit-0.23.18.1 nghttp2-1.37.0 sqlite3-3.27.2p0 xz-5.2.4 npth-1.6
> libidn2-2.0.0p0 gmp-6.1.2p3 curl-7.64.1 pinentry-1.1.0p0
> libunbound-1.9.1 gnutls-3.6.7 blas-3.7.1p0 gettext-runtime-0.20.1p0
> 

ASRock N3150-NUC (Beebox) - xenodm problems

[Fox Steward]

Hi,

when I try "rcctl start xenodm" I get a empty black screen. 
Trying to switch back to another VT fails (e.g. ctrl-alt-F1).

When I start it manually with "/usr/X11R6/bin/xenodm -debug 1" it seems
to work fine.

However, I still get the following dmesg messages though:

-
drm:pid98104:i915_reset_engine *NOTICE* Resetting bcs0 for hang on bcs0
drm:pid98104:i915_reset *NOTICE* Resetting chip for hang on bcs0
drm:pid98104:i915_reset *ERROR* Failed to reset chip
[drm] *ERROR* timeout setting power well state  (fcfff3ff)
[drm] *ERROR* Display PHY 0 is not power up
DPIO read pipe A reg 0x8170 == 0x
DPIO read pipe A reg 0x8098 == 0x
WARN_ON(ctrl != state)WARN_ON(ctrl != state)[drm] *ERROR* timeout
setting power well state  (fcfff3ff)
[drm] *ERROR* Display PHY 0 is not power up
DPIO read pipe A reg 0x8170 == 0x
DPIO read pipe A reg 0x8098 == 0x
WARN_ON(ctrl != state)WARN_ON(ctrl != state)[drm] *ERROR* timeout
setting power well state  (fcfff3ff)
...
-

Any ideas what is the problem? 

And how to debug this?

Note: while xenodm runs manually started I can ssh into the machine and debug.

Below you can find more verbose information about the machine in question:

Thank you kindly,

Fox

dmesg
-
OpenBSD 6.7-beta (GENERIC.MP) #170: Sat May  2 13:14:42 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 7954853888 (7586MB)
avail mem = 7701139456 (7344MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed9d0 (17 entries)
bios0: vendor American Megatrends Inc. version "P1.70" date 02/27/2018
bios0: ASRock N3150-NUC
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT AAFT MCFG SSDT SSDT SSDT UEFI LPIT CSRT
acpi0: wakeup devices XHC1(S4) HDEF(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) 
RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PWRB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz, 1600.34 MHz, 06-4c-03
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 79MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz, 1599.99 MHz, 06-4c-03
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz, 1600.01 MHz, 06-4c-03
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz, 1600.00 MHz, 06-4c-03
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus -1 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpicpu2 at acpi0: C1(@1 halt!)
acpicpu3 at acpi0: C1(@1 halt!)
acpipwrres0 at acpi0: CLK0, resource for CAMD
acpipwrres1 at acpi0: CLK0, resource for CAM1
acpipwrres2 at acpi0: CLK1, resource for CAM2, CAM3
acpipwrres3 at acpi0: USBC, resource for XHC1
acpicmos0 at acpi0
acpipci0 at 

Re: Dell VEP 1445 OpenBSD 6.6 Booting Failed

[Stuart Henderson]

On 2020-05-03, Vertigo Altair  wrote:
> Hi,
> I have a Dell VEP 1445 Whitebox, I want to install OpenBSD 6.6. on it. But
> When I try to boot, the boot process is stucking. There is no output after
> " erase ^?, werase"

This is a classic symptom of incorrect interrupt used for the serial port.
Early boot uses polled io up to the "root on xx" line, then it switches
to using the interrupt, if this isn't working you get a fifo-buffer full
(16 bytes for many common UART; count the chars in your output - it
matches) then it stalls.

Can you change irq for com ports in the bios config? If so, set com0 to
port 0x3f8, irq 4. If not try to figure out what it really uses (try
booting another OS that uses ACPI to configure the serial port;
OpenBSD has static config for these) and you can use boot -c and
tell the irq in the kernel, when it's booted use config(8) to modify
the kernel on disk or build your own.

If you get it working please send a full dmesg, I'm interested to see
how it looks!

> BIOS Boot Selector for VEP1400-X
> Version 3.48.0.9-4
>
>
> POST Configuration
>   CPU Signature 506F1
>   CPU FamilyID=6, Model=5F, SteppingId=1, Processor=0
>   Microcode Revision 2E
>   Platform ID: 0x0
>   PMG_CST_CFG_CTL: 0x37
>   Misc EN: 0x840089
>   Gen PM ConA: 0xA0A00200
>   Therm Status: 0x800
>   POST Control=0xEA000F03, Status=0xE600DF00
>
> BIOS initializations...
>
> CPGC Memtest Channel 0 .. PASS
>
> POST:
>   RTC Battery OK at last cold boot
>   RTC date 5/3/2020 9:24:11
>
> POST SPD test ... PASS
>
> POST Lower DRAM Memory test .
> POST ECC Test ... PASS
>
>   Perf cnt (curr,fixed): 0x32AFD1520,0x8B637FB20
>
> POST Lower DRAM Memory test . PASS
> POST Lower DRAM ECC check ... PASS
>
> Current BOOT from Primary BIOS
> DxE POST
>
> POST Upper DRAM Memory test
>   Short memory cell test
>
> POST Upper DRAM Memory test . PASS
> HDD Access .. PASS
> USB device detected
> Temperature test  PASS
> FAN controller test . PASS
> EEPROM test . PASS
> POST PCI test ... PASS
> POST BMC Interface test . PASS
> POST NVRAM check  PASS
> POST overall test results ... PASS
>
> NVRAM: 00 DF 00 E6   03 0F 00 EA   01 55 3E __   00 0F 00 F7
> Version 2.19.1266. Copyright (C) 2019 American Megatrends, Inc.
> BIOS Date: 06/26/2019 22:19:26 Ver: 0ACHI040
> Press  or  to enter setup.
> probing: pc0 com1 com2 com3 mem[640K 1894M 117M 972K 4M 14336M]
> disk: hd0 hd1* hd2*
>>> OpenBSD/amd64 BOOTX64 3.46
> boot> stty com0 115200
> boot> set tty com0
> switching console to com0
>>> OpenBSD/amd64 BOOTX64 3.46
> boot>
> cannot open hd0a:/etc/random.seed: No such file or directory
> booting hd0a:/6.6/amd64/bsd.rd: 3732171+1537024+3885432+0+598016
> [376562+128+455544+303577]=0xa648d0
> entry point at 0x1001000
> 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.6 (RAMDISK_CD) #349: Sat Oct 12 11:03:52 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 17131601920 (16337MB)
> avail mem = 16608419840 (15839MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f1ef000 (55 entries)
> bios0: vendor American Megatrends Inc. version "3.48.0.9-4" date 06/26/2019
> bios0: Dell EMC VEP1445-V220
> acpi0 at bios0: ACPI 6.1
> acpi0: tables DSDT FACP FPDT FIDT MCFG APIC BDAT HPET UEFI SSDT DMAR SPCR
> TPM2 HEST BERT ERST EINJ WSMT
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Atom(TM) CPU C3758 @ 2.20GHz, 2200.40 MHz, 06-5f-01
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu0: 2MB 64b/line 16-way L2 cache
> cpu0: apic clock running at 25MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (PEX0)
> acpiprt2 at acpi0: bus -1 (PEX1)
> acpiprt3 at 

Re: pkg_add can't resolve package - bad major

[Stuart Henderson]

On 2020-05-03, katzeilla  wrote:
> I am using OpenBSD 6.6 and I noticed that pkg_add can't install any new
> package:

You have pre-6.6 packages around and need to get them updated.

Have you run pkg_add -u to update all packages?

Re: rc.d: Webserver is removing daemonization - now what?

[Marcus MERIGHI]

chad.hoo...@protonmail.com (Chad Hoolie), 2020.05.03 (Sun) 15:43 (CEST):
> So the folks over at my webserver is removing its daemonization
> feature, telling its users to use systemd/upstart/a process supervisor
> instead.

Ugly move by upstream!

> But what does this mean to my webserver's startup script in /etc/rc.d,
> isn't it dependent on the webserver's ability to daemonize?
 
You could have shown the content of that rc.d(8) script...?

> Pretty sure I can't manually daemonize it by adding a "&" to the end
> of my rcexecs so...

Read rc.subr(8), look for "rc_bg".

Marcus

Re: Dell VEP 1445 OpenBSD 6.6 Booting Failed

[Vertigo Altair]

Hello Again,
I have already disabled ACPI at the boot prompt, but the result didn't
change.Thanks for suggestion..

Andrea Fleckenstein , 3 May 2020 Paz, 16:41 tarihinde
şunu yazdı:

> Vertigo Altair  writes:
>
> Hello,
>
> I had a Dell XPS 8100 with a similar problem and I was able to get
> around it by disabling ACPI at the boot prompt. Of course, we have very
> different machines, but it's worth a shot. Unfortunately the boot was
> extremely slow, on the order of 10min with acpi reenabled, and several
> minutes
> without it. Hopefully someone more knowledgeable than me will give a
> more reasoned answer. Good luck.
>
> Best,
> Andrea
>
> > Hi,
> > I have a Dell VEP 1445 Whitebox, I want to install OpenBSD 6.6. on it.
> But
> > When I try to boot, the boot process is stucking. There is no output
> after
> > " erase ^?, werase"
> >
> > BIOS Boot Selector for VEP1400-X
> > Version 3.48.0.9-4
> >
> >
> > POST Configuration
> >   CPU Signature 506F1
> >   CPU FamilyID=6, Model=5F, SteppingId=1, Processor=0
> >   Microcode Revision 2E
> >   Platform ID: 0x0
> >   PMG_CST_CFG_CTL: 0x37
> >   Misc EN: 0x840089
> >   Gen PM ConA: 0xA0A00200
> >   Therm Status: 0x800
> >   POST Control=0xEA000F03, Status=0xE600DF00
> >
> > BIOS initializations...
> >
> > CPGC Memtest Channel 0 .. PASS
> >
> > POST:
> >   RTC Battery OK at last cold boot
> >   RTC date 5/3/2020 9:24:11
> >
> > POST SPD test ... PASS
> >
> > POST Lower DRAM Memory test .
> > POST ECC Test ... PASS
> >
> >   Perf cnt (curr,fixed): 0x32AFD1520,0x8B637FB20
> >
> > POST Lower DRAM Memory test . PASS
> > POST Lower DRAM ECC check ... PASS
> >
> > Current BOOT from Primary BIOS
> > DxE POST
> >
> > POST Upper DRAM Memory test
> >   Short memory cell test
> >
> > POST Upper DRAM Memory test . PASS
> > HDD Access .. PASS
> > USB device detected
> > Temperature test  PASS
> > FAN controller test . PASS
> > EEPROM test . PASS
> > POST PCI test ... PASS
> > POST BMC Interface test . PASS
> > POST NVRAM check  PASS
> > POST overall test results ... PASS
> >
> > NVRAM: 00 DF 00 E6   03 0F 00 EA   01 55 3E __   00 0F 00 F7
> > Version 2.19.1266. Copyright (C) 2019 American Megatrends, Inc.
> > BIOS Date: 06/26/2019 22:19:26 Ver: 0ACHI040
> > Press  or  to enter setup.
> > probing: pc0 com1 com2 com3 mem[640K 1894M 117M 972K 4M 14336M]
> > disk: hd0 hd1* hd2*
> >>> OpenBSD/amd64 BOOTX64 3.46
> > boot> stty com0 115200
> > boot> set tty com0
> > switching console to com0
> >>> OpenBSD/amd64 BOOTX64 3.46
> > boot>
> > cannot open hd0a:/etc/random.seed: No such file or directory
> > booting hd0a:/6.6/amd64/bsd.rd: 3732171+1537024+3885432+0+598016
> > [376562+128+455544+303577]=0xa648d0
> > entry point at 0x1001000
> > 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.6 (RAMDISK_CD) #349: Sat Oct 12 11:03:52 MDT 2019
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> > real mem = 17131601920 (16337MB)
> > avail mem = 16608419840 (15839MB)
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f1ef000 (55 entries)
> > bios0: vendor American Megatrends Inc. version "3.48.0.9-4" date
> 06/26/2019
> > bios0: Dell EMC VEP1445-V220
> > acpi0 at bios0: ACPI 6.1
> > acpi0: tables DSDT FACP FPDT FIDT MCFG APIC BDAT HPET UEFI SSDT DMAR SPCR
> > TPM2 HEST BERT ERST EINJ WSMT
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Intel(R) Atom(TM) CPU C3758 @ 2.20GHz, 2200.40 MHz, 06-5f-01
> > cpu0:
> >
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> > cpu0: 2MB 64b/line 16-way L2 cache
> > cpu0: apic clock running at 25MHz
> > cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
> > cpu at mainbus0: not configured
> > cpu at mainbus0: not configured
> > cpu at mainbus0: not configured
> > cpu at mainbus0: not configured
> > cpu at mainbus0: not configured
> > cpu at mainbus0: not configured
> > cpu at mainbus0: not configured
> > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpiprt1 at acpi0: bus -1 (PEX0)

Re: Dell VEP 1445 OpenBSD 6.6 Booting Failed

[Andrea Fleckenstein]

Vertigo Altair  writes:

Hello,

I had a Dell XPS 8100 with a similar problem and I was able to get
around it by disabling ACPI at the boot prompt. Of course, we have very
different machines, but it's worth a shot. Unfortunately the boot was
extremely slow, on the order of 10min with acpi reenabled, and several minutes
without it. Hopefully someone more knowledgeable than me will give a
more reasoned answer. Good luck.

Best,
Andrea

> Hi,
> I have a Dell VEP 1445 Whitebox, I want to install OpenBSD 6.6. on it. But
> When I try to boot, the boot process is stucking. There is no output after
> " erase ^?, werase"
>
> BIOS Boot Selector for VEP1400-X
> Version 3.48.0.9-4
>
>
> POST Configuration
>   CPU Signature 506F1
>   CPU FamilyID=6, Model=5F, SteppingId=1, Processor=0
>   Microcode Revision 2E
>   Platform ID: 0x0
>   PMG_CST_CFG_CTL: 0x37
>   Misc EN: 0x840089
>   Gen PM ConA: 0xA0A00200
>   Therm Status: 0x800
>   POST Control=0xEA000F03, Status=0xE600DF00
>
> BIOS initializations...
>
> CPGC Memtest Channel 0 .. PASS
>
> POST:
>   RTC Battery OK at last cold boot
>   RTC date 5/3/2020 9:24:11
>
> POST SPD test ... PASS
>
> POST Lower DRAM Memory test .
> POST ECC Test ... PASS
>
>   Perf cnt (curr,fixed): 0x32AFD1520,0x8B637FB20
>
> POST Lower DRAM Memory test . PASS
> POST Lower DRAM ECC check ... PASS
>
> Current BOOT from Primary BIOS
> DxE POST
>
> POST Upper DRAM Memory test
>   Short memory cell test
>
> POST Upper DRAM Memory test . PASS
> HDD Access .. PASS
> USB device detected
> Temperature test  PASS
> FAN controller test . PASS
> EEPROM test . PASS
> POST PCI test ... PASS
> POST BMC Interface test . PASS
> POST NVRAM check  PASS
> POST overall test results ... PASS
>
> NVRAM: 00 DF 00 E6   03 0F 00 EA   01 55 3E __   00 0F 00 F7
> Version 2.19.1266. Copyright (C) 2019 American Megatrends, Inc.
> BIOS Date: 06/26/2019 22:19:26 Ver: 0ACHI040
> Press  or  to enter setup.
> probing: pc0 com1 com2 com3 mem[640K 1894M 117M 972K 4M 14336M]
> disk: hd0 hd1* hd2*
>>> OpenBSD/amd64 BOOTX64 3.46
> boot> stty com0 115200
> boot> set tty com0
> switching console to com0
>>> OpenBSD/amd64 BOOTX64 3.46
> boot>
> cannot open hd0a:/etc/random.seed: No such file or directory
> booting hd0a:/6.6/amd64/bsd.rd: 3732171+1537024+3885432+0+598016
> [376562+128+455544+303577]=0xa648d0
> entry point at 0x1001000
> 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.6 (RAMDISK_CD) #349: Sat Oct 12 11:03:52 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 17131601920 (16337MB)
> avail mem = 16608419840 (15839MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f1ef000 (55 entries)
> bios0: vendor American Megatrends Inc. version "3.48.0.9-4" date 06/26/2019
> bios0: Dell EMC VEP1445-V220
> acpi0 at bios0: ACPI 6.1
> acpi0: tables DSDT FACP FPDT FIDT MCFG APIC BDAT HPET UEFI SSDT DMAR SPCR
> TPM2 HEST BERT ERST EINJ WSMT
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Atom(TM) CPU C3758 @ 2.20GHz, 2200.40 MHz, 06-5f-01
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu0: 2MB 64b/line 16-way L2 cache
> cpu0: apic clock running at 25MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (PEX0)
> acpiprt2 at acpi0: bus -1 (PEX1)
> acpiprt3 at acpi0: bus 2 (PEX2)
> acpiprt4 at acpi0: bus -1 (PEX3)
> acpiprt5 at acpi0: bus -1 (PEX4)
> acpiprt6 at acpi0: bus 4 (PEX5)
> acpiprt7 at acpi0: bus -1 (PEX6)
> acpiprt8 at acpi0: bus -1 (PEX7)
> acpiprt9 at acpi0: bus 1 (VRP2)
> acpiprt10 at acpi0: bus 5 (VRP0)
> acpiprt11 at acpi0: bus 7 (VRP1)
> acpicpu at acpi0 not configured
> acpitz at acpi0 not configured
> "PNP0A08" at 

Re: IKE Multi site-to-site fails

[Tobias Heider]

On Sun, May 03, 2020 at 01:07:56PM +0200, Florian Weber wrote:
> Good morning,
> 
> I am trying to connect to remote locations to our main responder. The issue
> I am facing is that I can connect each site individually without any issue,
> however, I cannot connect both sides at the same time. The sides are connect
> to the Internet via dial-up connections with dynamic IPs from the same
> provider. Hence, creating a specific peer rule for each site doesn't work.
> Is there a way to have both sites connect to the responder? With the confs
> as below, only site B can connect, while site A fails since it uses the
> "main_to_siteB" conf on the responder. If I add quick to the "main_to_siteA"
> conf on the responder, site A works but B fails as it uses the site A
> config. Responder and both initiators run on 6.6 stable.
> 
> Any help or suggestions are greatly appreciated.
> 
> Best,
> 
> Florian

Hi Florian,

the responder needs some way to know if an incoming handshake is meant for
policy 'main_to_siteA' or 'main_to_siteB'.  The peer's IP is not helpful in
this case as it is the same for both policies.
This is why IKEv2 uses IDs (as in srcid and dstid) to uniquely identify peers.

On the initiator side everything looks correct, A and B have unique srcids.
What seems to be missing is the dstid on the responder side which could be
understood as: For initiators sending the ID $dstid, match this policy.

Setting dstid to the matching initiators srcid should help:

ikev2 'main_to_siteA' passive ipcomp esp \
    from 0.0.0.0/0 to 10.8.2.1/32 \
    from 0.0.0.0/0 to 192.168.30.0/24 \
    from 0.0.0.0/0 to 192.168.37.0/24 \
    from 0.0.0.0/0 to 10.253.0.0/24 \
    local A.B.C.D peer $provider \
    srcid A.B.C.D dstid E.F.G.H \
    psk "siteApass" \
    tag "$name-$id"
 
ikev2 'main_to_siteB' passive ipcomp esp \
    from 0.0.0.0/0 to 10.8.1.1/32 \
    from 0.0.0.0/0 to 192.168.41.0/24 \
    from 0.0.0.0/0 to 192.168.47.0/24 \
    local A.B.C.D peer $provider \
    srcid A.B.C.D dstid I.J.K.L \
    psk "siteBpass" \
    tag "$name-$id"

IKE Multi site-to-site fails

[Florian Weber]

Good morning,

I am trying to connect to remote locations to our main responder. The 
issue I am facing is that I can connect each site individually without 
any issue, however, I cannot connect both sides at the same time. The 
sides are connect to the Internet via dial-up connections with dynamic 
IPs from the same provider. Hence, creating a specific peer rule for 
each site doesn't work. Is there a way to have both sites connect to the 
responder? With the confs as below, only site B can connect, while site 
A fails since it uses the "main_to_siteB" conf on the responder. If I 
add quick to the "main_to_siteA" conf on the responder, site A works but 
B fails as it uses the site A config. Responder and both initiators run 
on 6.6 stable.


Any help or suggestions are greatly appreciated.

Best,

Florian


The iked.conf for responder looks like this:
ikev2 'main_to_siteA' passive ipcomp esp \
    from 0.0.0.0/0 to 10.8.2.1/32 \
    from 0.0.0.0/0 to 192.168.30.0/24 \
    from 0.0.0.0/0 to 192.168.37.0/24 \
    from 0.0.0.0/0 to 10.253.0.0/24 \
    local A.B.C.D peer $provider \
    srcid A.B.C.D \
    psk "siteApass" \
    tag "$name-$id"

ikev2 'main_to_siteB' passive ipcomp esp \
    from 0.0.0.0/0 to 10.8.1.1/32 \
    from 0.0.0.0/0 to 192.168.41.0/24 \
    from 0.0.0.0/0 to 192.168.47.0/24 \
    local A.B.C.D peer $provider \
    srcid A.B.C.D \
    psk "siteBpass" \
    tag "$name-$id"

For side A:

ikev2 'site_a_to_main' active esp \
    from 10.8.2.1/32 to 0.0.0.0/0 \
    from 192.168.30.0/24 to 0.0.0.0/0 \
    from 192.168.37.0/24 to 0.0.0.0/0 \
    from 10.253.0.0/24 to 0.0.0.0/0 \
    peer A.B.C.D \
    srcid E.F.G.H \
    dstid A.B.C.D \
    psk "siteApass" \

For side B:

ikev2 'site_b_to_main' active esp \
    from 10.8.1.1/32 to 0.0.0.0/0 \
    from 192.168.41.0/24 to 0.0.0.0/0 \
    from 192.168.47.0/24 to 0.0.0.0/0 \
    peer A.B.C.D \
    srcid I.J.K.L \
    dstid A.B.C.D \
    psk "siteBpass" \

Dell VEP 1445 OpenBSD 6.6 Booting Failed

[Vertigo Altair]

Hi,
I have a Dell VEP 1445 Whitebox, I want to install OpenBSD 6.6. on it. But
When I try to boot, the boot process is stucking. There is no output after
" erase ^?, werase"

BIOS Boot Selector for VEP1400-X
Version 3.48.0.9-4


POST Configuration
  CPU Signature 506F1
  CPU FamilyID=6, Model=5F, SteppingId=1, Processor=0
  Microcode Revision 2E
  Platform ID: 0x0
  PMG_CST_CFG_CTL: 0x37
  Misc EN: 0x840089
  Gen PM ConA: 0xA0A00200
  Therm Status: 0x800
  POST Control=0xEA000F03, Status=0xE600DF00

BIOS initializations...

CPGC Memtest Channel 0 .. PASS

POST:
  RTC Battery OK at last cold boot
  RTC date 5/3/2020 9:24:11

POST SPD test ... PASS

POST Lower DRAM Memory test .
POST ECC Test ... PASS

  Perf cnt (curr,fixed): 0x32AFD1520,0x8B637FB20

POST Lower DRAM Memory test . PASS
POST Lower DRAM ECC check ... PASS

Current BOOT from Primary BIOS
DxE POST

POST Upper DRAM Memory test
  Short memory cell test

POST Upper DRAM Memory test . PASS
HDD Access .. PASS
USB device detected
Temperature test  PASS
FAN controller test . PASS
EEPROM test . PASS
POST PCI test ... PASS
POST BMC Interface test . PASS
POST NVRAM check  PASS
POST overall test results ... PASS

NVRAM: 00 DF 00 E6   03 0F 00 EA   01 55 3E __   00 0F 00 F7
Version 2.19.1266. Copyright (C) 2019 American Megatrends, Inc.
BIOS Date: 06/26/2019 22:19:26 Ver: 0ACHI040
Press  or  to enter setup.
probing: pc0 com1 com2 com3 mem[640K 1894M 117M 972K 4M 14336M]
disk: hd0 hd1* hd2*
>> OpenBSD/amd64 BOOTX64 3.46
boot> stty com0 115200
boot> set tty com0
switching console to com0
>> OpenBSD/amd64 BOOTX64 3.46
boot>
cannot open hd0a:/etc/random.seed: No such file or directory
booting hd0a:/6.6/amd64/bsd.rd: 3732171+1537024+3885432+0+598016
[376562+128+455544+303577]=0xa648d0
entry point at 0x1001000
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.6 (RAMDISK_CD) #349: Sat Oct 12 11:03:52 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 17131601920 (16337MB)
avail mem = 16608419840 (15839MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f1ef000 (55 entries)
bios0: vendor American Megatrends Inc. version "3.48.0.9-4" date 06/26/2019
bios0: Dell EMC VEP1445-V220
acpi0 at bios0: ACPI 6.1
acpi0: tables DSDT FACP FPDT FIDT MCFG APIC BDAT HPET UEFI SSDT DMAR SPCR
TPM2 HEST BERT ERST EINJ WSMT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU C3758 @ 2.20GHz, 2200.40 MHz, 06-5f-01
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 2MB 64b/line 16-way L2 cache
cpu0: apic clock running at 25MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEX0)
acpiprt2 at acpi0: bus -1 (PEX1)
acpiprt3 at acpi0: bus 2 (PEX2)
acpiprt4 at acpi0: bus -1 (PEX3)
acpiprt5 at acpi0: bus -1 (PEX4)
acpiprt6 at acpi0: bus 4 (PEX5)
acpiprt7 at acpi0: bus -1 (PEX6)
acpiprt8 at acpi0: bus -1 (PEX7)
acpiprt9 at acpi0: bus 1 (VRP2)
acpiprt10 at acpi0: bus 5 (VRP0)
acpiprt11 at acpi0: bus 7 (VRP1)
acpicpu at acpi0 not configured
acpitz at acpi0 not configured
"PNP0A08" at acpi0 not configured
"PNP0003" at acpi0 not configured
acpicmos0 at acpi0
"MVS6190" at acpi0 not configured
"PICB000" at acpi0 not configured
"INTC3000" at acpi0 not configured
"PNP0C33" at acpi0 not configured
"MSFT0101" at acpi0 not configured
pci0 at mainbus0 bus 0
0:31:5: mem address conflict 0xfe01/0x1000
pchb0 at pci0 dev 0 function 0 "Intel C3000 Host" rev 0x11
pchb1 at pci0 dev 4 function 0 "Intel C3000 GLREG" rev 0x11
"Intel C3000 RCEC" rev 0x11 at pci0 dev 5 function 0 not configured
ppb0 at pci0 dev 6 function 0 "Intel C3000 PCIE" rev 0x11
pci1 at ppb0 bus 1
"Intel C3000 QAT" rev 0x11 at pci1 dev 0 function 0 not configured
ppb1 at