Re: Reinitializing software from hardware clock?

[Mike Larkin]

On Thu, Jan 11, 2018 at 04:51:47AM +, Maximilian Pichler wrote:
> On Thu, Jan 11, 2018 at 2:23 AM, Mike Larkin  wrote:
> >> Following your hint at vmmci and looking at
> >> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pv/vmmci.c.diff?r1=1.2=1.3=h
> >> it looks like inittodr(9) would reinitialize the software clock.
> >> However it seems to be available inside the kernel only. Is there no
> >> way to do this from userland?
> >
> > not that I know of.
> 
> Not quite what I'd hoped for... now resorting to periodically updating
> the clock:
> 
> while true; do date +%Y%m%d%H%M.%S | ssh virtual_machine 'date; xargs
> doas date'; sleep 60; done

the code is there. you can make a sysctl or other one-off to do what you
want.

Re: 4G modems for OpenBSD?

[lists]

Mon, 8 Jan 2018 15:35:41 -0900 Israel Brewster 
> Could anyone suggest a USB 4G cell modem model that will work well
> with OpenBSD, specifically SMSTools?
> 
> I do need a direct USB connection for the purposes of sending SMS
> messages directly from the system, i.e. I need to be able to send a
> SMS even if the internet is down, so online cloud services or the
> like that can convert e-mail to SMS aren't an option. Thanks.

Hi Israel,

There is an upcoming event that may be related to your cell modem query:

https://fosdem.org/2018/schedule/event/openbsd_alarm_system/

Siemens MC35 modem is listed somewhere inside the talk related blog post

http://vincentdelft.be/post/post_20160710

I am sure this could be easily picked from an online bargain deals site.
Would be interested if you find this useful, and how you made use of it.

Kind regards,
Anton Lazarov

Re: Reinitializing software from hardware clock?

[Maximilian Pichler]

On Thu, Jan 11, 2018 at 2:23 AM, Mike Larkin  wrote:
>> Following your hint at vmmci and looking at
>> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pv/vmmci.c.diff?r1=1.2=1.3=h
>> it looks like inittodr(9) would reinitialize the software clock.
>> However it seems to be available inside the kernel only. Is there no
>> way to do this from userland?
>
> not that I know of.

Not quite what I'd hoped for... now resorting to periodically updating
the clock:

while true; do date +%Y%m%d%H%M.%S | ssh virtual_machine 'date; xargs
doas date'; sleep 60; done

Re: Reinitializing software from hardware clock?

[Mike Larkin]

On Thu, Jan 11, 2018 at 02:22:00AM +, Maximilian Pichler wrote:
> On Wed, Jan 10, 2018 at 6:50 PM, Mike Larkin  wrote:
> >> > My question is: Can OpenBSD be told initialize the software from the
> >> > hardware clock again after the system is booted?
> 
> > This does occur on occasion; for example, when running an OpenBSD vmm(4)
> > guest, vmd(8) will notify the guest to resynch the clock from the RTC
> > after the host resumes from suspend/hibernate (actually, "any time
> > the host clock varies from more than 5s since it was last read by vmd(8"),
> > but that practically means "only during suspend/hibernate resumes").
> >
> > If the OP was looking for code to do this for whatever reason, it's done
> > via vmmci(4).
> 
> In fact this is precisely the use case I had in mind, except for that
> instead of inside vmm OpenBSD is running in Virtualbox on Mac OS. The
> clock seems to drift randomly and is off significantly after
> suspend/hibernate.
> 
> Following your hint at vmmci and looking at
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pv/vmmci.c.diff?r1=1.2=1.3=h
> it looks like inittodr(9) would reinitialize the software clock.
> However it seems to be available inside the kernel only. Is there no
> way to do this from userland?
> 
> Thanks!
> 

not that I know of.

Re: Reinitializing software from hardware clock?

[Maximilian Pichler]

On Wed, Jan 10, 2018 at 6:50 PM, Mike Larkin  wrote:
>> > My question is: Can OpenBSD be told initialize the software from the
>> > hardware clock again after the system is booted?

> This does occur on occasion; for example, when running an OpenBSD vmm(4)
> guest, vmd(8) will notify the guest to resynch the clock from the RTC
> after the host resumes from suspend/hibernate (actually, "any time
> the host clock varies from more than 5s since it was last read by vmd(8"),
> but that practically means "only during suspend/hibernate resumes").
>
> If the OP was looking for code to do this for whatever reason, it's done
> via vmmci(4).

In fact this is precisely the use case I had in mind, except for that
instead of inside vmm OpenBSD is running in Virtualbox on Mac OS. The
clock seems to drift randomly and is off significantly after
suspend/hibernate.

Following your hint at vmmci and looking at
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pv/vmmci.c.diff?r1=1.2=1.3=h
it looks like inittodr(9) would reinitialize the software clock.
However it seems to be available inside the kernel only. Is there no
way to do this from userland?

Thanks!

Re: Probable mistake in PF tagging example ruleset order

[trondd]

On Wed, January 10, 2018 2:44 pm, Aham Brahmasmi wrote:
> Hi,
>
> I am trying to learn and understand the pf tagging mechanism. I was
> wondering whether my understanding of the order in the example at
> https://www.openbsd.org/faq/pf/tagging.html is correct. If it is, then
> there might be a mistake in the order. The relevant lines are
>

Read the rules tagging follows again.  Tags are sticky.  Also a packet
passing through the firewall, say from a LAN machine to the internet, will
be evaluated twice.  If it gets tagged the first time, it'll have that tag
already when evaluated the second time.  If it matches a rule which tags
it, then matches another rule later, it still has the tag from the first
match.

> ...
> pass out on egress inet tag LAN_INET_NAT tagged LAN_INET nat-to (egress)
> pass in on $int_if from $int_net tag LAN_INET
> ...
> pass out quick on egress tagged LAN_INET_NAT
> ...
>
> My understanding:
> For the first line, an IPv4 packet that is already tagged with LAN_INET
> will now have the tag LAN_INET_NAT, and will be passed out on the
> egress interface after Network Address Translation.
>
> For the second line, a packet that is coming from the internal network
> on the internal interface will be passed and tagged with LAN_INET.
>
> For the third line, a packet that is tagged with LAN_INET_NAT will be
> passed out on the egress interface, and the rule evaluation will stop.
>
> Now, if my understanding is correct, then a packet will never match the
> first line, since the LAN_INET tagging happens only in the second line.
> And if that is the case, the third line will also not match, since the
> LAN_INET_NAT tagging happens in the first line.
>

Don't just read the rules from top to bottom.  Follow the packet.  Where
is the packet coming from?  Where is it going?  If there is a packet
coming from the LAN through this firewall to the internet what rules
match?  Does that rule tag the packet?  Does evaluation continue?

That's pass 1.  Since this packet is not destined for this machine, but
for something on the internet, it has to leave this machine.  So now it's
evaluated as an outgoing packet.  Did it get tagged before?  What rules
match based on direction and tag?  Does it get a new tag?  Does evaluation
continue?  Does it match anything else?


> If my understanding is correct, then we may need to switch the order of
> the first and second lines.
>
> The complete ruleset is
>
> int_if  = "dc0"
> dmz_if  = "dc1"
> int_net = "10.0.0.0/24"
> dmz_net = "192.168.0.0/24"
> www_server  = "192.168.0.5"
> mail_server = "192.168.0.10"
>
> table  persist file "/etc/spammers"
> # classification -- classify packets based on the defined firewall
> # policy.
> block all
> pass out on egress inet tag LAN_INET_NAT tagged LAN_INET nat-to (egress)
> pass in on $int_if from $int_net tag LAN_INET
> pass in on $int_if from $int_net to $dmz_net tag LAN_DMZ
> pass in on egress proto tcp to $www_server port 80 tag INET_DMZ
> pass in on egress proto tcp from  to port smtp tag SPAMD rdr-to \
> 127.0.0.1 port 8025
>
> # policy enforcement -- pass/block based on the defined firewall policy.
> pass in  quick on egress tagged SPAMD
> pass out quick on egress tagged LAN_INET_NAT
> pass out quick on $dmz_if tagged LAN_DMZ
> pass out quick on $dmz_if tagged INET_DMZ
>
> Thanks.
>
> Regards,
> ab
> -|-|-|-|-|-|-|--
>

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

Just used J00 screwdriver to open my USG-PRO 4, worked great.

Unfortunately I found the USG-PRO 4 uses a soldered SanDisk SDIN7DP2-4G
eMMC Flash Drive.  No way to replace internal storage.  ;-)


On Sat, 6 Jan 2018, Diana Eichert wrote:


thanks, I had come to a similar conclusion, though I think they are
JIS screws.

diana

On Sat, 6 Jan 2018, Mihai Popescu wrote:


the PH00 screws don't want to turn with my jeweler's screwdriver.


They may be PZ00. Take care not to mix different types of screws and
bits! PH and PZ look very much alike.

Re: Bitmask for 224.0.0.0 in Martians PF table entry

[Mike Coddington]

On Wed, Jan 10, 2018 at 07:55:53PM +0100, Aham Brahmasmi wrote:
> Hi,
> 
> What is the correct bitmask for the 224.0.0.0 Martian table entry in
> pf.conf?
> 
> There are two bitmasks in two links on this page -
> http://www.team-cymru.org/bogon-reference-http.html. /3 in the The Text
> Bogon List, Aggregated and /4 in IPv4 Fullbogons. /3 is also present in
> https://www.openbsd.org/faq/pf/example1.html.
> 
> I think it should be /3, but I am still learning pf.

224.0.0.0/3 would include the 240.0.0.0/4 block as well. For what it's
worth, I use 224.0.0.0/3 myself.

-- 
Put your Nose to the Grindstone!
-- Amalgamated Plastic Surgeons and Toolmakers, Ltd.

Re: Performance issues as KVM guest?

[Mark Carroll]

On 10 Jan 2018, Mike Larkin wrote:

> On Wed, Jan 10, 2018 at 03:51:19PM +, Mark Carroll wrote:
(snip)
>> I wondered, is anybody else seeing significant performance problems with
>> OpenBSD (or other BSDs) virtual instances since Meltdown patching? Is
>> there anything to tweak at my end or am I reliant on the provider?
>
> There are a ton of threads talking about this issue, and it's not meltdown
> specific. Please search the archives.

Ah, perhaps I was wrong to think they're something else -- I'm not their
only customer who found significant issues starting immediately after
last weekend's patching when things had worked fine before. I'll look
back at those threads more carefully then, perhaps they made some other
relevant change at the same time.

-- Mark

Probable mistake in PF tagging example ruleset order

[Aham Brahmasmi]

Hi,

I am trying to learn and understand the pf tagging mechanism. I was
wondering whether my understanding of the order in the example at
https://www.openbsd.org/faq/pf/tagging.html is correct. If it is, then
there might be a mistake in the order. The relevant lines are
...
pass out on egress inet tag LAN_INET_NAT tagged LAN_INET nat-to (egress)
pass in on $int_if from $int_net tag LAN_INET
...
pass out quick on egress tagged LAN_INET_NAT
...

My understanding:
For the first line, an IPv4 packet that is already tagged with LAN_INET
will now have the tag LAN_INET_NAT, and will be passed out on the
egress interface after Network Address Translation.

For the second line, a packet that is coming from the internal network
on the internal interface will be passed and tagged with LAN_INET.

For the third line, a packet that is tagged with LAN_INET_NAT will be
passed out on the egress interface, and the rule evaluation will stop.

Now, if my understanding is correct, then a packet will never match the
first line, since the LAN_INET tagging happens only in the second line.
And if that is the case, the third line will also not match, since the
LAN_INET_NAT tagging happens in the first line.

If my understanding is correct, then we may need to switch the order of
the first and second lines.

The complete ruleset is

int_if  = "dc0"
dmz_if  = "dc1"
int_net = "10.0.0.0/24"
dmz_net = "192.168.0.0/24"
www_server  = "192.168.0.5"
mail_server = "192.168.0.10"

table  persist file "/etc/spammers"
# classification -- classify packets based on the defined firewall
# policy.
block all
pass out on egress inet tag LAN_INET_NAT tagged LAN_INET nat-to (egress)
pass in on $int_if from $int_net tag LAN_INET
pass in on $int_if from $int_net to $dmz_net tag LAN_DMZ
pass in on egress proto tcp to $www_server port 80 tag INET_DMZ
pass in on egress proto tcp from  to port smtp tag SPAMD rdr-to \
127.0.0.1 port 8025

# policy enforcement -- pass/block based on the defined firewall policy.
pass in  quick on egress tagged SPAMD
pass out quick on egress tagged LAN_INET_NAT
pass out quick on $dmz_if tagged LAN_DMZ
pass out quick on $dmz_if tagged INET_DMZ

Thanks.

Regards,
ab
-|-|-|-|-|-|-|--

Bitmask for 224.0.0.0 in Martians PF table entry

[Aham Brahmasmi]

Hi,

What is the correct bitmask for the 224.0.0.0 Martian table entry in
pf.conf?

There are two bitmasks in two links on this page -
http://www.team-cymru.org/bogon-reference-http.html. /3 in the The Text
Bogon List, Aggregated and /4 in IPv4 Fullbogons. /3 is also present in
https://www.openbsd.org/faq/pf/example1.html.

I think it should be /3, but I am still learning pf.

Thanks.

Regards,
ab

Re: Performance issues as KVM guest?

[Mike Larkin]

On Wed, Jan 10, 2018 at 03:51:19PM +, Mark Carroll wrote:
> Since my hosting provider https://www.bytemark.co.uk/cloud-hosting/
> patched for Meltdown last weekend I'm seeing significant performance
> issues with an OpenBSD virtual instance there. It seems okay after a
> fresh reboot but then progressively returns to being very slow: for
> example "sleep 1" may take four seconds, then five, six, seven, then
> rather more. Curiously it does tend to be an integral multiplier.
> 
> I wondered, is anybody else seeing significant performance problems with
> OpenBSD (or other BSDs) virtual instances since Meltdown patching? Is
> there anything to tweak at my end or am I reliant on the provider?
> 
> -- Mark
> 

There are a ton of threads talking about this issue, and it's not meltdown
specific. Please search the archives.

-ml

> 
> OpenBSD 6.1 (GENERIC) #26: Wed Oct  4 18:41:35 CEST 2017
> 
> rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> real mem = 1055870976 (1006MB)
> avail mem = 1019322368 (972MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf1c10 (10 entries)
> bios0: vendor Bochs version "Bochs" date 01/01/2011
> bios0: Bochs Bochs
> acpi0 at bios0: rev 0
> acpi0: sleep states S3 S4 S5
> acpi0: tables DSDT FACP SSDT APIC HPET
> acpi0: wakeup devices
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: QEMU Virtual CPU version 2.1.3, 2200.42 MHz
> cpu0: 
> FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT,HV,NXE,LONG,LAHF
> cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 
> 64b/line 16-way L2 cache
> cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 1000MHz
> ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
> acpihpet0 at acpi0: 1 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpicpu0 at acpi0: C1(@1 halt!)
> "ACPI0006" at acpi0 not configured
> "PNP0303" at acpi0 not configured
> "PNP0F13" at acpi0 not configured
> "PNP0700" at acpi0 not configured
> "PNP0400" at acpi0 not configured
> "PNP0501" at acpi0 not configured
> "ACPI0007" at acpi0 not configured
> pvbus0 at mainbus0: KVM
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
> pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 
> wired to compatibility, channel 1 wired to compatibility
> pciide0: channel 0 disabled (no drives)
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus1 at atapiscsi0: 2 targets
> cd0 at scsibus1 targ 0 lun 0:  ATAPI 5/cdrom 
> removable
> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
> uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
> piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9
> iic0 at piixpm0
> vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
> vio0 at virtio0: address fe:ff:00:00:4f:1a
> virtio0: msix shared
> virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Memory" rev 0x00
> viomb0 at virtio1
> virtio1: apic 0 int 11
> virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00
> vioblk0 at virtio2
> scsibus2 at vioblk0: 2 targets
> sd0 at scsibus2 targ 0 lun 0:  SCSI3 0/direct fixed
> sd0: 25600MB, 512 bytes/sector, 52428800 sectors
> virtio2: msix shared
> "Intel 6300ESB WDT" rev 0x00 at pci0 dev 6 function 0 not configured
> isa0 at pcib0
> isadma0 at isa0
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 1: density unknown
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 
> addr 1
> uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet" 
> rev 1.00/0.00 addr 2
> uhidev0: iclass 3/0
> ums0 at uhidev0: 3 buttons, Z dir
> wsmouse1 at ums0 mux 0
> vscsi0 at root
> scsibus3 at vscsi0: 256 targets
> softraid0 at root
> scsibus4 at softraid0: 256 targets
> root on sd0a (312946608d4051a2.a) swap on sd0b dump on sd0b
> 

Re: Reinitializing software from hardware clock?

[Mike Larkin]

On Wed, Jan 10, 2018 at 01:23:19PM -, Christian Weisgerber wrote:
> On 2018-01-10, Maximilian Pichler  wrote:
> 
> > * At boot the software clock (the value returned by gettimeofday) is
> > initialized from the hardware clock (the one with the coin-shaped
> > battery).
> 
> ... from the RTC ("real-time clock"), yes.
> 
> > My question is: Can OpenBSD be told initialize the software from the
> > hardware clock again after the system is booted?
> 
> No.
> 

This does occur on occasion; for example, when running an OpenBSD vmm(4)
guest, vmd(8) will notify the guest to resynch the clock from the RTC
after the host resumes from suspend/hibernate (actually, "any time
the host clock varies from more than 5s since it was last read by vmd(8"),
but that practically means "only during suspend/hibernate resumes").

If the OP was looking for code to do this for whatever reason, it's done
via vmmci(4).

-ml

> > (Also, is the hardware clock ever modified aside from explicit
> > invocations of date(1) or similar?)
> 
> Yes,
> * when the system is properly shut down, and
> * periodically every 30 minutes, to prevent the RTC from drifting
>   off during long uptimes.
> 
> -- 
> Christian "naddy" Weisgerber  na...@mips.inka.de
> 

Re: Free OpenBSD Puffy Stickers

[x9p]

On Tue, January 2, 2018 6:09 pm, x9p wrote:
>
...
> 3rd batch sent, missing one (Philipines) which will be sent in the 4rd batch. 
> still lots of
...

4th batch sent. still lots of stickers. if ask please send from email active in 
any list.

cheers.

--
x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 
E7EE

"I don't know where I'm going from here, but I promise it won't be boring." - 
David Bowie

Re: Kernel memory leaking on Intel CPUs?

[Charlie Eddy]

Excuse me, I can support the far-seeing generalities in the message you
linked but am confused about the specifics. It looks like processor hangs,
and deadlock, and poorly documented page table handling by the MMU, are
concrete issues specified.

Respectfully: Are there any direct links to Meltdown or Spectre founded in
the bugs noted in these errata? Or, is this a straw man argument against a
chip manufacturer?

If there are not any direct links, but the argument against Intel itself
still stands, is that because there are other chip manufacturers who have
proven that it is possible to write unexploitable code?

Please let me know.

2018-01-10 3:21 GMT-08:00 Zbyszek Żółkiewski :

> 10 years passed, Theo de Raadt: https://marc.info/?l=openbsd-
> misc=118296441702631
>
> _
> Zbyszek Żółkiewski
>
> >
> > https://spectreattack.com/
> >
>
>

state of Netdata on OpenBSD

[Alceu R. de Freitas Jr.]

Hello folks,
I'm considering installing Netdata on OpenBSD 6.2, but I found this issue on 
Github:
https://github.com/firehol/netdata/issues/1083
Unfortunately, it doesn't tell if Netdata works out of the box on OpenBSD, if 
requires the Collectd (supposedly integrated with it) or if it doesn't work at 
all.
Did you guys have any success in using it?
It did gave a shot to Collected, the problem was to get a decent web app to 
visualize the charts...
Thanks!
Alceu

Performance issues as KVM guest?

[Mark Carroll]

Since my hosting provider https://www.bytemark.co.uk/cloud-hosting/
patched for Meltdown last weekend I'm seeing significant performance
issues with an OpenBSD virtual instance there. It seems okay after a
fresh reboot but then progressively returns to being very slow: for
example "sleep 1" may take four seconds, then five, six, seven, then
rather more. Curiously it does tend to be an integral multiplier.

I wondered, is anybody else seeing significant performance problems with
OpenBSD (or other BSDs) virtual instances since Meltdown patching? Is
there anything to tweak at my end or am I reliant on the provider?

-- Mark


OpenBSD 6.1 (GENERIC) #26: Wed Oct  4 18:41:35 CEST 2017
rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1055870976 (1006MB)
avail mem = 1019322368 (972MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf1c10 (10 entries)
bios0: vendor Bochs version "Bochs" date 01/01/2011
bios0: Bochs Bochs
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: QEMU Virtual CPU version 2.1.3, 2200.42 MHz
cpu0: 
FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT,HV,NXE,LONG,LAHF
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 1000MHz
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
"ACPI0006" at acpi0 not configured
"PNP0303" at acpi0 not configured
"PNP0F13" at acpi0 not configured
"PNP0700" at acpi0 not configured
"PNP0400" at acpi0 not configured
"PNP0501" at acpi0 not configured
"ACPI0007" at acpi0 not configured
pvbus0 at mainbus0: KVM
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 
wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0:  ATAPI 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int 9
iic0 at piixpm0
vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
vio0 at virtio0: address fe:ff:00:00:4f:1a
virtio0: msix shared
virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Memory" rev 0x00
viomb0 at virtio1
virtio1: apic 0 int 11
virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00
vioblk0 at virtio2
scsibus2 at vioblk0: 2 targets
sd0 at scsibus2 targ 0 lun 0:  SCSI3 0/direct fixed
sd0: 25600MB, 512 bytes/sector, 52428800 sectors
virtio2: msix shared
"Intel 6300ESB WDT" rev 0x00 at pci0 dev 6 function 0 not configured
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 1: density unknown
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 
addr 1
uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet" rev 
1.00/0.00 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 3 buttons, Z dir
wsmouse1 at ums0 mux 0
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
root on sd0a (312946608d4051a2.a) swap on sd0b dump on sd0b

Re : Lenovo T60p touchpad not working (6.2-stable/amd64)

[gro...@grompf.net]

Hi,

Quite the same appears here on a no name laptop with stock 6.2 kernel.
Pms0 disappears when booting in uefi mode. And not when booting in mbr
mode.
Strange and funny.

Re: Lenovo T60p touchpad not working (6.2-stable/amd64)

[Jonathan Thornburg]

In a recent message to misc@ I wrote
On Wed, Jan 10, 2018 at 03:14:43PM +0100, Jonathan Thornburg wrote:
> I have a Lenovo T60p laptop (amd64) currently running 6.2-stable (dmesg
> below).  [[...]]
> 
> My problem is that the touchpad does not work: [[...]]
> 
> As a temporary workaround I have plugged in a USB (wired) mouse, and I
> was delighted to see that it 'just worked'.  What's even more peculiar
> is that _when_the_USB_mouse_is_plugged_in_ the touchpad works again!

Amendment: when the USB mouse is plugged, the touchpad *sometimes*
works again.  And sometimes it doesn't (finger movements on the touchpad
are ignored again).

-- 
-- "Jonathan Thornburg [remove -animal to reply]" 

   Dept of Astronomy & IUCSS, Indiana University, Bloomington, Indiana, USA
   currently visiting Max-Plack-Institute fuer Gravitationsphysik
  (Albert-Einstein-Institut), Potsdam-Golm, Germany
   "There was of course no way of knowing whether you were being watched
at any given moment.  How often, or on what system, the Thought Police
plugged in on any individual wire was guesswork.  It was even conceivable
that they watched everybody all the time."  -- George Orwell, "1984"

Lenovo T60p touchpad not working (6.2-stable/amd64)

[Jonathan Thornburg]

I have a Lenovo T60p laptop (amd64) currently running 6.2-stable (dmesg
below).  I last rebuilt from source on 2017-12-15, but a cvs-update of
/usr/src today (2018-01-10) shows no changes, so this machine is fully
up to date for -stable.

My problem is that the touchpad does not work: finger movements on the
touchpad either have no effect on the X cursor, or sometimes result in
small movements of the X cursor which are not proportional to the finger
movement.

For what it's worth, this same computer has in the past had its touchpad
'just work' under OpenBSD 4.9, 5.1, 5.4, 5.6, 5.8, and 6.0 (all initially
-release and then -stable).

As a temporary workaround I have plugged in a USB (wired) mouse, and I
was delighted to see that it 'just worked'.  What's even more peculiar
is that _when_the_USB_mouse_is_plugged_in_ the touchpad works again!

Any suggestions for reviving the touchpad (without plugging in a mouse)?

Here are the dmesg for booting without a mouse plugged in (/var/run/dmesg.boot),
then the dmesg after pluggin in the mouse and unplugging it once or twice:
# cat /var/run/dmesg.boot
OpenBSD 6.2-stable (GENERIC.MP) #0: Fri Dec 15 23:48:42 PST 2017
b...@copper.astro.indiana.edu:/sys/arch/amd64/compile/GENERIC.MP
real mem = 3203203072 (3054MB)
avail mem = 3099160576 (2955MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
bios0: vendor LENOVO version "7IET25WW (1.06 )" date 03/15/2007
bios0: LENOVO 8742W1B
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT 
SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) 
PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.69 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 4MB 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 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.35 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 12 (EXP3)
acpiprt6 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu1 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 100 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"IBM0057" at acpi0 not configured
"IBM0071" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "92P1139" serial  3681 type LION oem "Panasonic"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK not docked (0)
acpivideo0 at acpi0: VID_
acpivout0 at acpivideo0: LCD0
acpivideo1 at acpi0: VID_
acpivout at acpivideo1 not configured
cpu0: Enhanced SpeedStep 1994 MHz: speeds: 2000, 1667, 1333, 1000 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: msi
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Mobility FireGL V5250" rev 0x00
drm0 at radeondrm0
radeondrm0: msi
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog Devices 
AD1981HD
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address 
00:16:41:e7:a7:b1
ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi
pci3 at ppb2 bus 3
wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: msi, MoW1, 
address 00:19:d2:c5:84:c5
ppb3 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: msi
pci4 at ppb3 bus 4
ppb4 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: msi
pci5 at 

Re: no valid ntpd peers

[Stuart Henderson]

On 2018-01-10, Maximilian Pichler  wrote:
> On Wed, Jan 10, 2018 at 6:05 PM, Stuart Henderson  
> wrote:
>> On 2018/01/10 09:43, Maximilian Pichler wrote:
>>> $ doas rdate -nvp pool.ntp.org
>>> rdate: Unable to receive NTP packet from server: No route to host
>>
>> This usually indicates either not having a route, or a firewall rule
>> on the OpenBSD system blocking it.
>
> Indeed, the ISP was to blame here. Mac OS couldn't get the time
> either.

Ouch. It would be nice if they fixed that...

Re: Reinitializing software from hardware clock?

[Christian Weisgerber]

On 2018-01-10, Maximilian Pichler  wrote:

> * At boot the software clock (the value returned by gettimeofday) is
> initialized from the hardware clock (the one with the coin-shaped
> battery).

... from the RTC ("real-time clock"), yes.

> My question is: Can OpenBSD be told initialize the software from the
> hardware clock again after the system is booted?

No.

> (Also, is the hardware clock ever modified aside from explicit
> invocations of date(1) or similar?)

Yes,
* when the system is properly shut down, and
* periodically every 30 minutes, to prevent the RTC from drifting
  off during long uptimes.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

Re: no valid ntpd peers

[Craig Skinner]

Hi Maximilian,

On Wed, 10 Jan 2018 18:10:37 +0700 Maximilian Pichler wrote:
> Indeed, the ISP was to blame here. Mac OS couldn't get the time
> either. Once I switched to my phone's internet connection everything
> was fine.

Perhaps the ISP has an NTP/date/time server for customers to sync from?

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

Re: Reinitializing software from hardware clock?

[Janne Johansson]

2018-01-10 12:30 GMT+01:00 Maximilian Pichler :

> My vague understanding of how OpenBSD keeps track of time is:
>
> * At boot the software clock (the value returned by gettimeofday) is
> initialized from the hardware clock (the one with the coin-shaped
> battery).
>
>
Not available on all platforms, in which case the kernel sometimes just
grabs the latest timestamp of the filesystem and takes it from there.


> * The software clock is then incremented hz(9) times a second by a CPU
> interrupt.
> My question is: Can OpenBSD be told initialize the software from the
> hardware clock again after the system is booted?
>
>
How would one try to know which is more exact?

For some/most platforms, the (multiple) internal timers are crazy exact
down to
counting cycles in the CPU, and others are not so exact and skew based on
CPU
load and other factors. (I think the obsd-on-mac68k used to suffer from
cpu-time-skew)
For emulated and virtual machines, its even worse, since the guest usually
can't tell
when the host decided to switch cpu frequency based on load or other
factors, throwing
off all kinds of "1 us is X loops in this microsleep routine" calibrations
one might have made
early on.


> (Also, is the hardware clock ever modified aside from explicit
> invocations of date(1) or similar?)
>

-- 
May the most significant bit of your life be positive.

Reinitializing software from hardware clock?

[Maximilian Pichler]

My vague understanding of how OpenBSD keeps track of time is:

* At boot the software clock (the value returned by gettimeofday) is
initialized from the hardware clock (the one with the coin-shaped
battery).

* The software clock is then incremented hz(9) times a second by a CPU
interrupt.

My question is: Can OpenBSD be told initialize the software from the
hardware clock again after the system is booted?

(Also, is the hardware clock ever modified aside from explicit
invocations of date(1) or similar?)

Thanks!

Re: Kernel memory leaking on Intel CPUs?

[Zbyszek Żółkiewski]

10 years passed, Theo de Raadt: 
https://marc.info/?l=openbsd-misc=118296441702631

_
Zbyszek Żółkiewski

> 
> https://spectreattack.com/
> 

Re: no valid ntpd peers

[Maximilian Pichler]

On Wed, Jan 10, 2018 at 6:05 PM, Stuart Henderson  wrote:
> On 2018/01/10 09:43, Maximilian Pichler wrote:
>> $ doas rdate -nvp pool.ntp.org
>> rdate: Unable to receive NTP packet from server: No route to host
>
> This usually indicates either not having a route, or a firewall rule
> on the OpenBSD system blocking it.

Indeed, the ISP was to blame here. Mac OS couldn't get the time
either. Once I switched to my phone's internet connection everything
was fine.

Thanks

Re: no valid ntpd peers

[Stuart Henderson]

On 2018/01/10 09:43, Maximilian Pichler wrote:
> $ doas rdate -nvp pool.ntp.org
> rdate: Unable to receive NTP packet from server: No route to host

This usually indicates either not having a route, or a firewall rule
on the OpenBSD system blocking it.

> $ nc -vu pool.ntp.org 123
> Connection to pool.ntp.org 123 port [udp/ntp] succeeded!

It's UDP - this indicates nothing. You haven't sent anything at this point.

>  $ traceroute -c -p 123 pool.ntp.org
> traceroute: Warning: pool.ntp.org has multiple addresses; using 203.159.70.33
> traceroute to pool.ntp.org (203.159.70.33), 64 hops max, 40 byte packets
>  1  10.0.2.2 (10.0.2.2)  0.867 ms  0.349 ms  0.246 ms
>  2  * * *
>  3  192.168.11.1 (192.168.11.1)  2.514 ms  2.137 ms  1.786 ms
>  4  125.213.235.25 (125.213.235.25)  2.848 ms  2.51 ms  2.617 ms
>  5  125.213.235.17 (125.213.235.17)  5.88 ms  3.059 ms  3.211 ms
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * 125.213.235.17 (125.213.235.17)  3.367 ms !X *
> 
> Disabling pf (as well as the firewall on the host MacOS) gives
> identical results.
> 
> Also, it looks like no packets are coming back (suggested by David
> Dahlberg in a private message):
> $ doas tcpdump -envps1500 -i em0 port ntp or icmp
> tcpdump: listening on em0, link-type EN10MB
> 06:16:31.765946 08:00:27:34:76:da 52:54:00:12:35:02 0800 90:
> 10.0.2.15.47084 > 203.158.247.150.123: [bad udp cksum cf8d! -> 5deb]
> v4 client strat 0 poll 0 prec 0 dist 0.00 disp 0.00 ref
> (unspec)@0.0 orig 0.0 rec -0.0 xmt
> -34468692.156416639 [tos 0x10] (ttl 64, id 34769, len 76)
> 06:16:31.766020 08:00:27:34:76:da 52:54:00:12:35:02 0800 90:
> 10.0.2.15.35704 > 203.158.118.2.123: [bad udp cksum 4df9! -> 780a] v4
> client strat 0 poll 0 prec 0 dist 0.00 disp 0.00 ref
> (unspec)@0.0 orig 0.0 rec -0.0 xmt
> -95552486.879830002 [tos 0x10] (ttl 64, id 47214, len 76)
> 06:16:31.766340 08:00:27:34:76:da 52:54:00:12:35:02 0800 90:
> 10.0.2.15.31315 > 103.22.182.121.123: [bad udp cksum 29e8! -> dad3] v4
> client strat 0 poll 0 prec 0 dist 0.00 disp 0.00 ref
> (unspec)@0.0 orig 0.0 rec -0.0 xmt
> +1659942531.907521903 [tos 0x10] (ttl 64, id 53951, len 76)
> 06:16:31.766494 08:00:27:34:76:da 52:54:00:12:35:02 0800 90:
> 10.0.2.15.11278 > 203.159.70.33.123: [bad udp cksum 1e19! -> 6dc7] v4
> client strat 0 poll 0 prec 0 dist 0.00 disp 0.00 ref
> (unspec)@0.0 orig 0.0 rec -0.0 xmt
> +94128219.587299346 [tos 0x10] (ttl 64, id 30931, len 76)
> 06:16:31.768890 52:54:00:12:35:02 08:00:27:34:76:da 0800 90:
> 125.213.235.17 > 10.0.2.15: icmp: host 203.158.247.150 unreachable -
> admin prohibited filter [icmp cksum ok] [tos 0xd0] (ttl 63, id 48216,
> len 76)
> 
> What is "admin prohibited filter"?

Some firewalls return this for blocked packets. In this case, it seems
fairly likely that it's being blocked by 125.213.235.17.

Panic: ffs_blkfree on 6.0 GENERIC.MP

[George Kourvoulis]

Hello,

Today I have found one of my gateways (VM on esxi 6.5) in the state that is
shown here:
https://imgur.com/a/SV687

Unfortunately I didn't have time to gather more info because I had to
reboot the machine in order to resume operations.

Any pointers would be much appreciated.

Thanks,
George

PS. Here is the output of my dmesg:

OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2130640896 (2031MB)
avail mem = 2061656064 (1966MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (239 entries)
bios0: vendor Phoenix Technologies LTD version "6.00" date 04/05/2016
bios0: VMware, Inc. VMware Virtual Platform
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S3F0(S3)
S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) S10F(S3) S11F(S3)
S12F(S3) S13F(S3) [...]
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) Xeon(R) CPU E5-2620 v3 @ 2.40GHz, 2397.56 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,ARAT
cpu0: 256KB 64b/line 8-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 65MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
acpimcfg0 at acpi0 addr 0xf000, bus 0-127
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
"PNP0001" at acpi0 not configured
"PNP0303" at acpi0 not configured
"PNP0F13" at acpi0 not configured
"PNP0A05" at acpi0 not configured
"PNP0400" at acpi0 not configured
"PNP0501" at acpi0 not configured
"PNP0501" at acpi0 not configured
"PNP0700" at acpi0 not configured
acpiac0 at acpi0: AC unit online
pvbus0 at mainbus0: VMware
vmt0 at pvbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel
0 configured to compatibility, channel 1 configured to compatibility
pciide0: channel 0 disabled (no drives)
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0:  ATAPI
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus
disabled
"VMware VMCI" rev 0x10 at pci0 dev 7 function 7 not configured
vga1 at pci0 dev 15 function 0 "VMware SVGA II" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
mpi0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: apic 1 int
17
mpi0: 0, firmware 1.3.41.32
scsibus2 at mpi0: 16 targets, initiator 7
sd0 at scsibus2 targ 0 lun 0:  SCSI2 0/direct
fixed
sd0: 10240MB, 512 bytes/sector, 20971520 sectors
mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
ppb1 at pci0 dev 17 function 0 "VMware PCI" rev 0x02
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel 82545EM" rev 0x01: apic 1 int 18,
address 00:50:56:b8:fd:45
em1 at pci2 dev 2 function 0 "Intel 82545EM" rev 0x01: apic 1 int 16,
address 00:50:56:b8:f4:6a
em2 at pci2 dev 3 function 0 "Intel 82545EM" rev 0x01: apic 1 int 17,
address 00:50:56:b8:9f:11
em3 at pci2 dev 4 function 0 "Intel 82545EM" rev 0x01: apic 1 int 18,
address 00:50:56:b8:d7:85
ppb2 at pci0 dev 21 function 0 "VMware PCIE" rev 0x01
pci3 at ppb2 bus 3
ppb3 at pci0 dev 21 function 1 "VMware PCIE" rev 0x01
pci4 at ppb3 bus 4
ppb4 at pci0 dev 21 function 2 "VMware PCIE" rev 0x01
pci5 at ppb4 bus 5
ppb5 at pci0 dev 21 function 3 "VMware PCIE" rev 0x01
pci6 at ppb5 bus 6
ppb6 at pci0 dev 21 function 4 "VMware PCIE" rev 0x01
pci7 at ppb6 bus 7
ppb7 at pci0 dev 21 function 5 "VMware PCIE" rev 0x01
pci8 at ppb7 bus 8
ppb8 at pci0 dev 21 function 6 "VMware PCIE" rev 0x01
pci9 at ppb8 bus 9
ppb9 at pci0 dev 21 function 7 "VMware PCIE" rev 0x01
pci10 at ppb9 bus 10
ppb10 at pci0 dev 22 function 0 "VMware PCIE" rev 0x01
pci11 at ppb10 bus 11
ppb11 at pci0 dev 22 function 1 "VMware PCIE" rev 0x01
pci12 at ppb11 bus 12
ppb12 at pci0 dev 22 function 2 "VMware PCIE" rev 0x01
pci13 at ppb12 bus 13
ppb13 at pci0 dev 22 function 3 "VMware PCIE" rev 0x01
pci14 at ppb13 bus 14
ppb14 at pci0 dev 22 function 4 "VMware PCIE" rev 0x01
pci15 at ppb14 bus 15
ppb15 at pci0 dev 22 function 5 "VMware PCIE" rev 0x01
pci16 at 

Re: no valid ntpd peers

[x9p]

On Wed, January 10, 2018 7:28 am, Maximilian Pichler wrote:
> On Wed, Jan 10, 2018 at 11:55 AM, x9p  wrote:
>> I had similar problems once under VirtualBox, other OS. try switching from 
>> NAT to BRIDGED
>> mode and give it a try.
>
> Thanks, but no luck on my end. Any insight into why this should have helped?
>

my bet was a buggy NAT from virtualbox. You did put the network in bridged 
mode, renew dhcp,
and got an IP from the LAN right? not 10.0.2.x

cheers.

--
x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 
E7EE

"I don't know where I'm going from here, but I promise it won't be boring." - 
David Bowie

Re: no valid ntpd peers

[Maximilian Pichler]

On Wed, Jan 10, 2018 at 11:55 AM, x9p  wrote:
> I had similar problems once under VirtualBox, other OS. try switching from 
> NAT to BRIDGED
> mode and give it a try.

Thanks, but no luck on my end. Any insight into why this should have helped?

Re: 4G modems for OpenBSD?

[Daniel Gracia]

This scenario is trivial, as far as the Sierra Wireless Airlink supports
UDP client/server links. I.e., a properly configurated gateway (easily done
through their web interface) should be able to accept UDP packets on any
defined port and accept messages in the form
'<<>>',
so just using netcat to send the line

<<<16046556677,ASCII,14,5448495320495320412054455354>>>

(being the message formatted in hex ASCII, in this case 'THIS IS A TEST')
will do the trick. You should receive another UDP packet to a port of your
choice ACKing the message. And that's all.

Regards!


2018-01-09 18:03 GMT+01:00 Israel Brewster :

> On Jan 9, 2018, at 12:07 AM, Daniel Gracia  wrote:
>
>
> Maybe this is not exactly the solution you're looking for, but have you
> considered using a 4G gateway? In the past I've had great success with
> Sierra Wireles AirLink family. It's pretty easy to send SMS commands
> through IP with them, so a local Ethernet connection to the gateway should
> do the trick. Neat devices!
>
>
> Sounds worth checking out. I can always connect it directly via a second
> ethernet port or the like, so being IP should be fine.
>
> The main concern is that the machine in question be able to get a message
> out, even if the switch it is connected to dies. So a little creative
> networking, and a solution like this should be fine, as long as the SMS
> commands can be sent from the command line.
>
> Thanks!
>
> ---
> Israel Brewster
> Systems Analyst II
> Ravn Alaska
> 5245 Airport Industrial Rd
> 
> Fairbanks, AK 99709
> 
> (907
> )
> 450-7293
> ---
>
>
> Regards,
>
>
> 2018-01-09 1:35 GMT+01:00 Israel Brewster :
>
> Could anyone suggest a USB 4G cell modem model that will work well with
> OpenBSD, specifically SMSTools? I've looked over most of the list in "man
> umsm", but those all appear to be 3G. That said, I haven't checked every
> model on the list, so there could be one or more 4G models that I missed.
> I've also seen this thread: http://openbsd-archive.7691.
> n7.nabble.com/4g-LTE-modem-td106310.html  n7.nabble.com/4g-LTE-modem-td106310.html>, but that is over 5 years old.
> There is also this thread: http://openbsd-archive.7691.
> n7.nabble.com/Anyone-experienced-with-4G-LTE-modems-td281872.html <
> http://openbsd-archive.7691.n7.nabble.com/Anyone-experienced-with-4G-LTE-
> modems-td281872.html>, but that doesn't appear to offer any suggestions
> of USB cell modems - just suggestions of using external cellular routers.
>
> I do need a direct USB connection for the purposes of sending SMS messages
> directly from the system, i.e. I need to be able to send a SMS even if the
> internet is down, so online cloud services or the like that can convert
> e-mail to SMS aren't an option. Thanks.
>
> ---
> Israel Brewster
> Systems Analyst II
> Ravn Alaska
> 5245 Airport Industrial Rd
> 
> Fairbanks, AK 99709
> 
> (907
> )
> 450-7293
> ---
>
>
>
>
>
>
>