Re: Upgrading to current prep

2018-03-10 Thread Otto Moerbeek 
On Sat, Mar 10, 2018 at 11:42:55PM -0500, Rupert Gallagher wrote:

> Obsd default partitioning and default packaging still fails me.
> /usr/src and /usr/obj contain variable content, and thus should be
> /var/src and /var/obj instead, allowing for /usr to be mounted read
> only as originally intended for unix systems. Further, variable
> content partitions such as /var and /home should be large enough to
> allow for ssd wear levelling, or you will toss away expensive ssds
> like autumn leaves. Finally, all games should be moved from the
> default packages to ports. These changes are done systematically here,
> and it is swearing and smothering each time we do it.  > > Sent from
> ProtonMail Mobile > > > ,> ,> ,>

Get a decent mailer that wraps lines.

The default setup and autoallocation fits development use, for that
/usr shoud be modifiable. 

If the default sizes do not fit you, you can modify them interactively
after auto allocation using the R command or by using an alternate
auto allocation table.

As for wear levelling, it is enough to not just allocate part of the
ssd. It does not not matter if that part is in an fs or not.
Actually, it might be better to make the free space not part of an fs.

As for the games, they have always been part of OpenBSD.

-Otto

Re: Which hexeditor may I use to import binary files via shell?

2018-03-10 Thread Philip Guenther 
On Sat, Mar 10, 2018 at 9:42 PM, Felix Maschek  wrote:
>
> Is there a shell command availabl to import binary files via shell?
> Something like a hex editor?
>

b64encode(1) and the matching b64decode(1)

For files that have only a few bytes that aren't printable ASCII, vis(1)
and unvis(1) may be more friendly.

Philip Guenther

Which hexeditor may I use to import binary files via shell?

2018-03-10 Thread Felix Maschek 

Hi,

I have a running tor node ("scurra") and want to move it to a newer 
server hosted by my ISP.


For this task I have to move (binary) key files from the old server to 
the new oner.


I don't want to open any remote access to the new server (despite the 
tor services, of course). So I've only the management console available.


Is there a shell command availabl to import binary files via shell? 
Something like a hex editor?


Kind regards
Felix

Re: System hangs after detecting radeondrm

2018-03-10 Thread Jonathan Gray 
On Sun, Mar 11, 2018 at 12:15:11AM +, Kaashif Hymabaccus wrote:
> Hello
> 
> I have a sparc64 machine with no real graphics card, only the onboard
> Mach64 framebuffer. I found an ATI Radeon 9200 and decided to see if
> it works, then I could run X, test some graphical ports, etc.
> 
> My problem is that with the GPU connected, the system hangs completely
> and is unresponsive to breaks in the serial line or any form of
> input. I do not have a Sun keyboard, only a USB keyboard connected to
> a PCI USB card (which works with no problem).
> 
> The card itself works fine on an amd64 machine I have, and I did
> preemptively install the radeondrm-firmware package on the
> sparc64. The machine boots up fine if I disable the radeondrm device
> in the kernel.
> 
> This is an unusual setup so I wouldn't be surprised if someone told me
> that it can't work for some reason. The real problem I have is that it
> just hangs and seems a bit hard to debug, so I'd appreciate some
> advice on how to track down the issue myself.

The radeondrm code is designed to take over the console on sparc64.
But the console will only get setup if you have a card with the sun/apple
fcode in the pci option rom.

It may be possible to use a different type of card but it is entirely
possible that path doesn't work at the moment.

radeon cards from sun with fcode

xvr-100 (0x1002:0x5159 pci rv100)
xvr-300 (0x1002:0x5b64 pcie rv380)

> 
> Here is the full output on the serial line:
> 
> Connected to /dev/cuaU0 (speed 9600)
> 
> Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 270MHz), No Keyboard
> OpenBoot 3.11, 512 MB memory installed, Serial #1653024.
> Ethernet address 8:0:20:19:39:20, Host ID: 80193920.
> 
> 
> 
>   
> ok boot
> Boot device: disk:a  File and args: 
> OpenBSD IEEE 1275 Bootblock 1.4
> ..>> OpenBSD BOOT 1.9
> Trying bsd...
> Booting /pci@1f,0/pci@1,1/ide@3/disk@0,0:a/bsd
> 8491696@0x100+3408@0x18192b0+200624@0x1c0+3993680@0x1c30fb0 
> symbols @ 0xfef18400 165+565992+375599 start=0x100
> [ using 942784 bytes of bsd ELF symbol table ]
> console is /pci@1f,0/pci@1,1/ebus@1/se@14,40:a
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>   The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2018 OpenBSD. All rights reserved.  https://www.OpenBSD.org
> 
> OpenBSD 6.3-beta (GENERIC) #461: Thu Mar  8 23:11:47 MST 2018
> dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC
> real mem = 536870912 (512MB)
> avail mem = 512303104 (488MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root: Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 270MHz)
> cpu0 at mainbus0: SUNW,UltraSPARC-IIi (rev 1.3) @ 269.808 MHz
> cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 256K external (64 
> b/l)
> psycho0 at mainbus0 addr 0xfffc4000: SUNW,sabre, impl 0, version 0, ign 7c0
> psycho0: bus range 0-2, PCI bus 0
> psycho0: dvma map c000-dfff
> pci0 at psycho0
> ppb0 at pci0 dev 1 function 1 "Sun Simba" rev 0x11
> pci1 at ppb0 bus 1
> ebus0 at pci1 dev 1 function 0 "Sun PCIO EBus2" rev 0x01
> auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003, 
> 72c000-72c003, 72f000-72f003
> power0 at ebus0 addr 724000-724003 ivec 0x25
> "SUNW,pll" at ebus0 addr 504000-504002 not configured
> sab0 at ebus0 addr 40-40007f ivec 0x2b: rev 3.2
> sabtty0 at sab0 port 0: console
> sabtty1 at sab0 port 1
> comkbd0 at ebus0 addr 3083f8-3083ff ivec 0x29: no keyboard
> comms0 at ebus0 addr 3062f8-3062ff ivec 0x2a
> wsmouse0 at comms0 mux 0
> lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 70-7f ivec 0x22: 
> polled
> clock1 at ebus0 addr 0-1fff: mk48t59
> "flashprom" at ebus0 addr 0-f not configured
> audioce0 at ebus0 addr 20-2000ff, 702000-70200f, 704000-70400f, 
> 722000-722003 ivec 0x23 ivec 0x24: nvaddrs 0
> audio0 at audioce0
> hme0 at pci1 dev 1 function 1 "Sun HME" rev 0x01: ivec 0x7e1, address 
> 08:00:20:19:39:20
> nsphy0 at hme0 phy 1: DP83840 10/100 PHY, rev. 1
> machfb0 at pci1 dev 2 function 0 "ATI Mach64" rev 0x9a
> machfb0: ATY,GT-B, 1152x900
> wsdisplay0 at machfb0 mux 1
> wsdisplay0: screen 0 added (std, sun emulation)
> pciide0 at pci1 dev 3 function 0 "CMD Technology PCI0646" rev 0x03: DMA, 
> channel 0 configured to native-PCI, channel 1 configured to native-PCI
> pciide0: using ivec 0x7e0 for native-PCI interrupt
> wd0 at pciide0 channel 0 drive 0: 
> wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors
> wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
> 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
> ppb1 at pci0 dev 1 function 0 "Sun Simba" rev 0x11
> pci2 at ppb1 bus 2
> ohci0 at pci2 dev 1 function 0 "NEC USB" rev 0x41: ivec 0x7d0, version 1.0
> ohci1 at pci2 dev 1 function 1 "NEC USB"

System hangs after detecting radeondrm

2018-03-10 Thread Kaashif Hymabaccus 
Hello

I have a sparc64 machine with no real graphics card, only the onboard
Mach64 framebuffer. I found an ATI Radeon 9200 and decided to see if
it works, then I could run X, test some graphical ports, etc.

My problem is that with the GPU connected, the system hangs completely
and is unresponsive to breaks in the serial line or any form of
input. I do not have a Sun keyboard, only a USB keyboard connected to
a PCI USB card (which works with no problem).

The card itself works fine on an amd64 machine I have, and I did
preemptively install the radeondrm-firmware package on the
sparc64. The machine boots up fine if I disable the radeondrm device
in the kernel.

This is an unusual setup so I wouldn't be surprised if someone told me
that it can't work for some reason. The real problem I have is that it
just hangs and seems a bit hard to debug, so I'd appreciate some
advice on how to track down the issue myself.

Here is the full output on the serial line:

Connected to /dev/cuaU0 (speed 9600)

Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 270MHz), No Keyboard
OpenBoot 3.11, 512 MB memory installed, Serial #1653024.
Ethernet address 8:0:20:19:39:20, Host ID: 80193920.



  
ok boot
Boot device: disk:a  File and args: 
OpenBSD IEEE 1275 Bootblock 1.4
..>> OpenBSD BOOT 1.9
Trying bsd...
Booting /pci@1f,0/pci@1,1/ide@3/disk@0,0:a/bsd
8491696@0x100+3408@0x18192b0+200624@0x1c0+3993680@0x1c30fb0 
symbols @ 0xfef18400 165+565992+375599 start=0x100
[ using 942784 bytes of bsd ELF symbol table ]
console is /pci@1f,0/pci@1,1/ebus@1/se@14,40:a
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2018 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 6.3-beta (GENERIC) #461: Thu Mar  8 23:11:47 MST 2018
dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC
real mem = 536870912 (512MB)
avail mem = 512303104 (488MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root: Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 270MHz)
cpu0 at mainbus0: SUNW,UltraSPARC-IIi (rev 1.3) @ 269.808 MHz
cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 256K external (64 
b/l)
psycho0 at mainbus0 addr 0xfffc4000: SUNW,sabre, impl 0, version 0, ign 7c0
psycho0: bus range 0-2, PCI bus 0
psycho0: dvma map c000-dfff
pci0 at psycho0
ppb0 at pci0 dev 1 function 1 "Sun Simba" rev 0x11
pci1 at ppb0 bus 1
ebus0 at pci1 dev 1 function 0 "Sun PCIO EBus2" rev 0x01
auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003, 
72c000-72c003, 72f000-72f003
power0 at ebus0 addr 724000-724003 ivec 0x25
"SUNW,pll" at ebus0 addr 504000-504002 not configured
sab0 at ebus0 addr 40-40007f ivec 0x2b: rev 3.2
sabtty0 at sab0 port 0: console
sabtty1 at sab0 port 1
comkbd0 at ebus0 addr 3083f8-3083ff ivec 0x29: no keyboard
comms0 at ebus0 addr 3062f8-3062ff ivec 0x2a
wsmouse0 at comms0 mux 0
lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 70-7f ivec 0x22: polled
clock1 at ebus0 addr 0-1fff: mk48t59
"flashprom" at ebus0 addr 0-f not configured
audioce0 at ebus0 addr 20-2000ff, 702000-70200f, 704000-70400f, 
722000-722003 ivec 0x23 ivec 0x24: nvaddrs 0
audio0 at audioce0
hme0 at pci1 dev 1 function 1 "Sun HME" rev 0x01: ivec 0x7e1, address 
08:00:20:19:39:20
nsphy0 at hme0 phy 1: DP83840 10/100 PHY, rev. 1
machfb0 at pci1 dev 2 function 0 "ATI Mach64" rev 0x9a
machfb0: ATY,GT-B, 1152x900
wsdisplay0 at machfb0 mux 1
wsdisplay0: screen 0 added (std, sun emulation)
pciide0 at pci1 dev 3 function 0 "CMD Technology PCI0646" rev 0x03: DMA, 
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide0: using ivec 0x7e0 for native-PCI interrupt
wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
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
ppb1 at pci0 dev 1 function 0 "Sun Simba" rev 0x11
pci2 at ppb1 bus 2
ohci0 at pci2 dev 1 function 0 "NEC USB" rev 0x41: ivec 0x7d0, version 1.0
ohci1 at pci2 dev 1 function 1 "NEC USB" rev 0x41: ivec 0x7d1, version 1.0
ehci0 at pci2 dev 1 function 2 "NEC USB" rev 0x02: ivec 0x7d2
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "NEC EHCI root hub" rev 2.00/1.00 
addr 1
radeondrm0 at pci2 dev 3 function 0 "ATI Radeon 9200 PRO" rev 0x01
drm0 at radeondrm0
radeondrm0: ivec 0x7d8

[This is where it hangs forever]

Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument

2018-03-10 Thread Alexander Hall 


On March 9, 2018 12:55:31 AM GMT+01:00, Stefan Wollny  
wrote:
>Am 09.03.2018 um 00:09 schrieb Stefan Wollny:
>> Am 08.03.2018 um 23:25 schrieb Stefan Wollny:
>>> Am 08.03.2018 um 22:11 schrieb Stefan Wollny:
>>>
 Am 08.03.2018 um 17:44 schrieb Stefan Wollny:
> Gesendet von meinem BlackBerry 10-Smartphone.
>   Originalnachricht  
> Von: Kevin Chadwick
> Gesendet: Donnerstag, 8. März 2018 17:28
> An: misc@openbsd.org
> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
>
> On Thu, 8 Mar 2018 14:47:43 +0100
>
>
>> Has anyone a clue what might have happend and how to solve the
>issue?
>> I searched the net but didn't find any substantial infos on this.
>As
>> the error happends with all three USB-keys I have this is
>unlikely to
>> be cause of the trouble.
> The bootloader normally lists the disks that the bios sees
>beforehand
> e.g.
>
> disk: hd0+ hd1+ sr0*
>>> OpenBSD/amd64 BOOT 3.34
> Perhaps they have been moved around?
>
>
> I tried
>
> boot hd1a:/bsd
>
> but got the same message.
>
> I can enter # fsck -fy hd0a but ‎this just gets me a prompt
>without any action. BTW: This is a SSD.
>
 OK - back at home I downloaded install63.iso and burned a CD which
>does
 start. Choosing "(U)pgrade" I am presented with "Available disks
>are:
 sd0 sd1" - but both are "not a valid root disk". Back to the shell
>I
 tried fdisk but I get "fdisk: sd0: No such file or directory"

 Could this be an issue with the bootloader or is it the encryption
>of
 softraid0 that hinders the upgrade?

>> tb@ provided another valuable hint:
>> I can start the boot-process with 'boot sr0a:/bsd' but this ends with
>a
>> panic:
>>
>> ...
>> softraid0 at root
>> scsibus4 at softraid0:256 targets
>> panic: root device (...) not found
>> Stopped at db_enter+0x5:    popq    %rbp
>>     TID    PID    UID    PRFLAGS    PFLAGS    CPU COMMAND
>> *    0        0        0    0X1        0X200    OK    swapper
>> ...
>>
>OK . final remarks for tonight:
>
>I can start 'boot sr0a:/bsd.rd' but trying to upgrade is the same
>dead-end road - "sd0 is not a valid root device".
>
>'fdisk sd0' shows the expected '*' before the partition number.

It might help to see the actual output. 

>
>'disklabel sd0' shows the expected fstype "RAID" 'for sd0a.

It would certainly help to see the output here. Does it span the *entire* disk, 
from 0 to the end? 

>
>Doing 'bioctl -c C -l /dev/sd0a' says "KDF hint has invalid size".
>
>'installboot -nv sd0a' misses '/usr/mdec/biosboot' - there is only
>'/usr/mdec/mbr'.
>
>While the 'upgrade' started from 'boot sr0a:/bsd.rd' does not see 'sd0'
>the 'install' process started from the CD actually does.

"sd0 is not a valid root device" does not say it does not *see* the device. It 
says "sd0 is not a valid root device", which is totally correct, as it only 
holds some raid metadata and the corresponding encrypted data.

If sd0(a) is a single RAID partition, and sd1 holds the key, your root disk 
should appear as sd2 (or whatever the next unused sdN is).

So, if "sd0 is not a valid root device" and "sd1 is not a valid root device", 
what gives for sd2?

Please provide as much output as possible from the process. Your interpretation 
of it is far less helpful in understanding the problem at hand. 

Sincerely, 
Alexander 

>
>Sigh - I need some sleep...

signify [file ... ]

2018-03-10 Thread Andrew 

Hi Ted !!!

Today I downloaded a fresh SHA256.sig and bsd.rd and successfully
verified them both with signify(1). 


--

signify -C [-q] -p pubkey -x sigfile [file ...]

Just wondering if signify(1) is intended to exit 0 ONLY if the [file
...] is within the shell's pwd ?? By chance, I noticed that 
/path/to/file will fail on the same bsd.rd controlling for the working 
directory. 


You can see the same results by (for example):

a) mkdir /home/bench/snaps
b) cd /home/bench/snaps
c) /home/bench/snaps $> (download SHA256.sig and bsd.rd)
d) /home/bench/snaps $> signify -Cp /etc/signify/openbsd-63-base.pub 
			-x SHA256.sig bsd.rd

Signature Verified
bsd.rd: OK

e) /home/bench/snaps $> mv SHA256.sig ..

f) /home/bench/snaps $> signify -Cp /etc/signify/openbsd-63-base.pub 
			-x ../SHA256.sig bsd.rd

Signature Verified
bsd.rd: OK

g) cd ..

h) /home/bench $> signify -Cp /etc/signify/openbsd-63-base.pub 
			-x SHA256.sig snaps/bsd.rd

Signature Verified
snaps/bsd.rd: FAIL

---

I just wanted to bring this to your attention. 


Big thanks to you and to Marc for such a great utilty !!! Thanks also to
Ingo for a man page full of really useful examples, especially the one
about "verifing a gzip pipeline." That example really shows off your
great work within the context of what makes un*x so amazing.

Have a great weekend !!!

-A

Re: OSPF over gif on top of IPsec transport -current

2018-03-10 Thread Atanas Vladimirov 

On 2018-03-10 00:01, Remi Locherer wrote:

On Fri, Mar 09, 2018 at 06:13:10PM +0100, Remi Locherer wrote:

On Sun, Mar 04, 2018 at 01:08:21PM +0200, Atanas Vladimirov wrote:
> Hi,
>
> I can't make OSPF to work on gif over IPsec.
> With tcpdump on gif I see the OSPFv2-hello only from localhost:
>
> # R1
> [ns]~$ tcpdump -nei gif0
> tcpdump: listening on gif0, link-type LOOP
> 23:19:29.181685 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid
> 192.168.1.1 area 0.0.0.1 [tos 0xc0] [ttl 1]
> 23:19:39.192025 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid
> 192.168.1.1 area 0.0.0.1 [tos 0xc0] [ttl 1]
> 23:19:49.202372 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid
> 192.168.1.1 area 0.0.0.1 [tos 0xc0] [ttl 1]
> 23:19:59.212730 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid
> 192.168.1.1 area 0.0.0.1 [tos 0xc0] [ttl 1]
> 23:20:09.223064 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid
> 192.168.1.1 area 0.0.0.1 [tos 0xc0] [ttl 1]
> 23:20:19.233393 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid
> 192.168.1.1 area 0.0.0.1 [tos 0xc0] [ttl 1]
>
> # R2
> [hodor]~$ tcpdump -nei gif0
> tcpdump: listening on gif0, link-type LOOP
> 12:51:59.316704 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone [tos 0xc0] [ttl 1]
> 12:52:09.327002 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone [tos 0xc0] [ttl 1]
> 12:52:19.337314 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone [tos 0xc0] [ttl 1]
>
> While on enc0 both hello's appears (not sure if `bad ip cksum` is the reason
> for my issues):
>
> # R1
> [ns]~$ tcpdump -nvi enc0
> tcpdump: listening on enc0, link-type ENC
> 12:24:37.625873 (authentic,confidential): SPI 0x11af4dae: 93.123.39.67 >
> 95.87.227.232: 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone E mask 255.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1]
> (id 25841, len 64) (ttl 60, id 37752, len 84)
> 12:24:41.882173 (authentic,confidential): SPI 0x1a3fbc6d: 95.87.227.232 >
> 93.123.39.67: 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid 192.168.1.1
> backbone E mask 255.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1]
> (id 27818, len 64) (ttl 64, id 60563, len 84, bad ip cksum 32d7! -> c614)
> 12:24:47.636188 (authentic,confidential): SPI 0x11af4dae: 93.123.39.67 >
> 95.87.227.232: 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone E mask 255.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1]
> (id 36067, len 64) (ttl 60, id 65348, len 84)
> 12:24:51.892467 (authentic,confidential): SPI 0x1a3fbc6d: 95.87.227.232 >
> 93.123.39.67: 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid 192.168.1.1
> backbone E mask 255.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1]
> (id 5127, len 64) (ttl 64, id 12476, len 84, bad ip cksum 201! -> 81ec)
> 12:24:57.646535 (authentic,confidential): SPI 0x11af4dae: 93.123.39.67 >
> 95.87.227.232: 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone E mask 255.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1]
> (id 39220, len 64) (ttl 60, id 1938, len 84)
>
> # R2
> [hodor]~$ tcpdump -nvi enc0 | grep OSPF
> tcpdump: listening on enc0, link-type ENC
> 12:28:57.894007 (authentic,confidential): SPI 0x11af4dae: 93.123.39.67 >
> 95.87.227.232: 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone E mask 255.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1]
> (id 3667, len 64) (ttl 64, id 14037, len 84, bad ip cksum 2b6d! -> 7bd3)
> 12:29:02.151763 (authentic,confidential): SPI 0x1a3fbc6d: 95.87.227.232 >
> 93.123.39.67: 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid 192.168.1.1
> backbone E mask 25
> 5.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1] (id 16974, len
> 64) (ttl 60, id 21648, len 84)
> 12:29:07.904315 (authentic,confidential): SPI 0x11af4dae: 93.123.39.67 >
> 95.87.227.232: 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone E mask 255
> .255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1] (id 45590, len 64)
> (ttl 64, id 35262, len 84, bad ip cksum 2743! -> 28ea)
> 12:29:12.162049 (authentic,confidential): SPI 0x1a3fbc6d: 95.87.227.232 >
> 93.123.39.67: 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid 192.168.1.1
> backbone E mask 25
> 5.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1] (id 19966, len
> 64) (ttl 60, id 3134, len 84)
> 12:29:17.914621 (authentic,confidential): SPI 0x11af4dae: 93.123.39.67 >
> 95.87.227.232: 10.255.255.1 > 224.0.0.5: OSPFv2-hello  44: rtrid 172.16.1.1
> backbone E mask 255
> .255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1] (id 36161, len 64)
> (ttl 64, id 53105, len 84, bad ip cksum fcb8! -> e336)
> 12:29:22.172468 (authentic,confidential): SPI 0x1a3fbc6d: 95.87.227.232 >
> 93.123.39.67: 10.255.255.2 > 224.0.0.5: OSPFv2-hello  44: rtrid 192.168.1.1
> backbone E mask 25
> 5.255.255.255 int 10 pri 1 dead 40 nbrs [tos 0xc0] [ttl 1] (id 36221, len
> 64) (ttl 60, id 29514, len 84)
>
> If I set a

Re: Upgrading to current prep

2018-03-10 Thread Patrick Marchand 
On Sat, Mar 10, 2018 at 07:22:43PM +, Otto Moerbeek wrote:
> On Sat, Mar 10, 2018 at 02:15:02PM -0500, math...@posteo.net wrote:
> 
> > > You would not be the first
> > > one to have written to a file in /dev instead of a device.
> > 
> > Thats exactly what happened, my /dev/sd1 is 943056 bytes large
> > I was trying to dd dragonflybsd to a usb stick earlier this week and messed 
> > up.
> > 
> > What exactly do I have to do to fix this?
> 
> just rm the file. /dev/sd1 is not a device name anyway,
> 
>   -Otto

cool, thanks!

Re: Upgrading to current prep

2018-03-10 Thread Otto Moerbeek 
On Sat, Mar 10, 2018 at 01:43:04PM -0500, math...@posteo.net wrote:

> Hi folks,
> I'm upgrading to -current today, but before I did that I've been
> backuping stuff and making sure I understand the current state of my
> system. My system runs 6.2-release with all syspatches.
> 
> When I installed the system I used the basic installation settings and
> did not modify much, for instance I let openbsd partition the drive.
> 
> The main weird thing I noticed this morning was after running df.
> 
> Filesystem SizeUsed   Avail Capacity  Mounted on
> /dev/sd0a 1005M995M  -40.8M   104%/
> /dev/sd0k  184G   14.6G160G 8%/home
> /dev/sd0d  3.9G3.4M3.7G 0%/tmp
> /dev/sd0f  2.0G1.1G810M58%/usr
> /dev/sd0g 1005M178M777M19%/usr/X11R6
> /dev/sd0h  9.8G4.8G4.5G52%/usr/local
> /dev/sd0j  5.9G2.0K5.6G 0%/usr/obj
> /dev/sd0i  2.0G2.0K1.9G 0%/usr/src
> /dev/sd0e 19.0G   90.9M   18.0G 0%/var
> 
> I'm not sure what happened here, but it may be that the default space
> allocation for / space is too small for desktop usage? It's more
> probable that I've just messed up somehow. Worse case scenario I'm not
> against rebooting into a snapshot bsd.rd and repartioning myself, I just
> backed up everything of import anyways.

1005M of / is large enoug for almost all cases.  It is more likely you
wrote something into /. Try finding it with cd / ; du -kx | sort -n
and then zooming into the large dir. You would not be the first
one to have written to a file in /dev instead of a device.

-Otto


> 
> Dmesg just for good measure:
> OpenBSD 6.2 (GENERIC.MP) #6: Wed Feb 28 21:13:02 CET 2018
> 
> r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 8261529600 (7878MB)
> avail mem = 8004075520 (7633MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
> bios0: vendor LENOVO version "N14ET42W (1.20 )" date 09/13/2017
> bios0: LENOVO 20BTS0Y500
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT 
> SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR
> acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpiec0 at acpi0
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.51 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: TSC frequency 2594513870 Hz
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT,MELTDOWN
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 1, core 0, package 0
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 MHz
> 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT,MELTDOWN
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 0, core 1, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 MHz
> cpu3: 
>

Upgrading to current prep

2018-03-10 Thread mathuin 
Hi folks,
I'm upgrading to -current today, but before I did that I've been
backuping stuff and making sure I understand the current state of my
system. My system runs 6.2-release with all syspatches.

When I installed the system I used the basic installation settings and
did not modify much, for instance I let openbsd partition the drive.

The main weird thing I noticed this morning was after running df.

Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/sd0a 1005M995M  -40.8M   104%/
/dev/sd0k  184G   14.6G160G 8%/home
/dev/sd0d  3.9G3.4M3.7G 0%/tmp
/dev/sd0f  2.0G1.1G810M58%/usr
/dev/sd0g 1005M178M777M19%/usr/X11R6
/dev/sd0h  9.8G4.8G4.5G52%/usr/local
/dev/sd0j  5.9G2.0K5.6G 0%/usr/obj
/dev/sd0i  2.0G2.0K1.9G 0%/usr/src
/dev/sd0e 19.0G   90.9M   18.0G 0%/var

I'm not sure what happened here, but it may be that the default space
allocation for / space is too small for desktop usage? It's more
probable that I've just messed up somehow. Worse case scenario I'm not
against rebooting into a snapshot bsd.rd and repartioning myself, I just
backed up everything of import anyways.

Dmesg just for good measure:
OpenBSD 6.2 (GENERIC.MP) #6: Wed Feb 28 21:13:02 CET 2018

r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8261529600 (7878MB)
avail mem = 8004075520 (7633MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
bios0: vendor LENOVO version "N14ET42W (1.20 )" date 09/13/2017
bios0: LENOVO 20BTS0Y500
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.51 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2594513870 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 MHz
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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 MHz
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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 3 (EXP1)
acpiprt3 at acpi0: bus 4 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpiprt5 at acpi0: bus 10 (EXP6)
acpicpu0

Re: Xorg hangs on startup (skylake)

2018-03-10 Thread abi 

On 10.03.2018 18:19, Noth wrote:

On 10/03/18 12:29, Stefan Sperling wrote:

On Sat, Mar 10, 2018 at 02:18:16PM +0300, abi wrote:

Hello,

I'm new to OpenBSD, but I'm old FreeBSD user. I've installed

OpenBSD 6.2 to XPS 13 /Skylake/ laptop (it runs FreeBSD with 
unsignificant

issues).

However, the system hangs (blackscreen, hard shutdown required) 
after startx

command.

Please try a -current snapshot.

Latest snapshot still has this bug. It's ongoing since 6.2 was 
introduced unfortunately

I see. Are there any PRs around I can check ?

Re: Xorg hangs on startup (skylake)

2018-03-10 Thread Noth 



On 10/03/18 12:29, Stefan Sperling wrote:

On Sat, Mar 10, 2018 at 02:18:16PM +0300, abi wrote:

Hello,

I'm new to OpenBSD, but I'm old FreeBSD user. I've installed

OpenBSD 6.2 to XPS 13 /Skylake/ laptop (it runs FreeBSD with unsignificant
issues).

However, the system hangs (blackscreen, hard shutdown required) after startx
command.

Please try a -current snapshot.

Latest snapshot still has this bug. It's ongoing since 6.2 was 
introduced unfortunately.

Re: Xorg hangs on startup (skylake)

2018-03-10 Thread abi 

On 10.03.2018 14:29, Stefan Sperling wrote:

On Sat, Mar 10, 2018 at 02:18:16PM +0300, abi wrote:

Hello,

I'm new to OpenBSD, but I'm old FreeBSD user. I've installed

OpenBSD 6.2 to XPS 13 /Skylake/ laptop (it runs FreeBSD with unsignificant
issues).

However, the system hangs (blackscreen, hard shutdown required) after startx
command.

Please try a -current snapshot.

The same behaviour, system hangs after glamor initialization.
Logs: https://pastebin.com/0Hub2icY

Re: Xorg hangs on startup (skylake)

2018-03-10 Thread Stefan Sperling 
On Sat, Mar 10, 2018 at 02:18:16PM +0300, abi wrote:
> Hello,
> 
> I'm new to OpenBSD, but I'm old FreeBSD user. I've installed
> 
> OpenBSD 6.2 to XPS 13 /Skylake/ laptop (it runs FreeBSD with unsignificant
> issues).
> 
> However, the system hangs (blackscreen, hard shutdown required) after startx
> command.

Please try a -current snapshot.

> 
> No alterations to the system was made after install, setup excluded games,
> laptop uses UEFI,
> 
> OpenBSD installed to usb stick.
> 
> I've done the following homework:
> 
> 1. Tried vesa driver -> No screens found. (I have the same with FreeBSD)
> 
> 2. Tried wsfb driver -> No screens found (If this is analog of FreeBSD's
> scfb, it worked there)
> 
> 3. Tried intel -> system hangs as with modesetting.
> 
> I expected difficulties, bot not too early :) I set machdep.allowaperture=1
> as X suggests.
> 
> Logs - https://pastebin.com/RkZz2b1y
> 
> The only errors are
> error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to load
> firmware i915/skl_dmc_ver1.bin (-22)
> error: [drm:pid0:i915_gem_init_hw] *ERROR* Failed to initialize GuC, error
> -8 (ignored)
> 
> but they should be harmless
> 
> 
>

Xorg hangs on startup (skylake)

2018-03-10 Thread abi 

Hello,

I'm new to OpenBSD, but I'm old FreeBSD user. I've installed

OpenBSD 6.2 to XPS 13 /Skylake/ laptop (it runs FreeBSD with 
unsignificant issues).


However, the system hangs (blackscreen, hard shutdown required) after 
startx command.


No alterations to the system was made after install, setup excluded 
games, laptop uses UEFI,


OpenBSD installed to usb stick.

I've done the following homework:

1. Tried vesa driver -> No screens found. (I have the same with FreeBSD)

2. Tried wsfb driver -> No screens found (If this is analog of FreeBSD's 
scfb, it worked there)


3. Tried intel -> system hangs as with modesetting.

I expected difficulties, bot not too early :) I set 
machdep.allowaperture=1 as X suggests.


Logs - https://pastebin.com/RkZz2b1y

The only errors are
error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to load 
firmware i915/skl_dmc_ver1.bin (-22)
error: [drm:pid0:i915_gem_init_hw] *ERROR* Failed to initialize GuC, 
error -8 (ignored)


but they should be harmless