Re: OpenBSD 7.2 on Oracle Cloud

2023-04-06 Thread Antun Matanović
On Thu, 6 Apr 2023 at 12:55, Fabio Martins  wrote:
>
> Try to add an entry in grub like in this article:
>
> https://raby.sh/installing-openbsd-on-ovhs-vps-2016-kvm-machines.html

I have tried that, but it did not resolve the issue. Sorry I forgot to
mention it originally.

On Thu, 6 Apr 2023 at 14:24, Janne Johansson  wrote:
>
> That is very much not the same issue. The arm64 instances on Oracle
> finds the correct kernel and boots it, it just crashes at or after the
> scsi attachment.

This has been my experience as well, except on the amd64 instance,
haven't tried arm64.



Re: Creating a "multicast bridge"?

2023-04-06 Thread Martin Schröder
Am Do., 6. Apr. 2023 um 15:27 Uhr schrieb Why 42? The lists account.
:
> I'd like to create a "bridge" between two IP networks which will pass
> only multicast info. / traffic.

So it should only route FF00::/8?

Best
Martin



Creating a "multicast bridge"?

2023-04-06 Thread Why 42? The lists account.


Hi All,

I'd like to create a "bridge" between two IP networks which will pass
only multicast info. / traffic.

Is that something that I could do using OpenBSD and pf? I don't see
anything specific to multicasting in the pf.conf man page but I suppose
it should be possible to define a set of rules based on the standard
multicast address ranges that would pass (or forward?) traffic between
two interfaces X and Y.

In this case the traffic should be passed "bidirectionally", if that's
actually a word :-)

Or, I see that "bridge(4)" might also be a potential solution for this,
although I've never used that before. Would that be a better basis?

Are there examples of how to define pf rules for a bridge configuration?

It's not entirely clear to me, but from what I've read it may be
necessary to pass additional management / meta traffic, in addition to
the actual multicast data, i.e. so that the switches on either side can
track the multicast groups being created and their members?

The source of the multicast data will be Windows 10 based applications.

Since I'll be creating the system specifically for this purpose, I can
use any version of OpenBSD for this.

When I get it running, I'd like to track the behaviour of the traffic.
Are there any tools that would be recommended for this? I thought of
using wireshark, or more likely tshark, perhaps with its "-z" statistics
option.

Grateful for any advice - thanks in advance!

Cheers,
Robb.



Re: OpenBSD 7.2 on Oracle Cloud

2023-04-06 Thread Janne Johansson
Den tors 6 apr. 2023 kl 12:57 skrev Fabio Martins :
> Try to add an entry in grub like in this article:
>
> https://raby.sh/installing-openbsd-on-ovhs-vps-2016-kvm-machines.html

That is very much not the same issue. The arm64 instances on Oracle
finds the correct kernel and boots it, it just crashes at or after the
scsi attachment.

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



Re: OpenBSD 7.2 on Oracle Cloud

2023-04-06 Thread Fabio Martins
Try to add an entry in grub like in this article:

https://raby.sh/installing-openbsd-on-ovhs-vps-2016-kvm-machines.html

On Wednesday, April 5, 2023, Antun Matanović 
wrote:

> I'm trying to set up OpenBSD on an Always Free VM.Standard.E2.1.Micro
> instance and I keep getting a page fault (log included below).
> I created an instance using the default Oracle Linux 8 image with all
> default settings except for disabling in-transit encryption. From
> there I just dd'd the install72.img to /dev/sda and rebooted into the
> cloud shell.I also used `set tty com0` as suggested here:
> https://www.alextsang.net/articles/20221022-132025/index.html
> I also tried starting the instance using the Ubuntu image, disabling
> all the Oracle Cloud Agent services as well as writing the
> miniroot72.img but nothing worked.
> Here is the output:
> >> OpenBSD/amd64 BOOTX64 3.62
> boot>
> cannot open hd0a:/etc/random.seed: No such file or directory
> booting hd0a:/7.2/amd64/bsd.rd: 3916484+1639424+3884040+0+704512
> [109+438912+292606]=0xa61d70
> entry point at 0x1001000
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2022 OpenBSD. All rights reserved.
> https://www.OpenBSD.org
>
> OpenBSD 7.2 (RAMDISK_CD) #725: Tue Sep 27 12:02:48 MDT 2022
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 1049554944 (1000MB)
> avail mem = 1013784576 (966MB)
> random: good seed from bootblocks
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x3f94 (9 entries)
> bios0:
> bios0: QEMU Standard PC (i440FX + PIIX, 1996)
> acpi0 at bios0: ACPI 1.0
> acpi0: tables DSDT FACP APIC HPET BGRT
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: AMD EPYC 7551 32-Core Processor, 3594.00 MHz, 17-01-02
> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,
> SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,
> AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,
> LONG,LAHF,CMPLEG,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,
> TOPEXT,CPCTR,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,
> RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,VIRTSSBD,XSAVEOPT,
> XSAVEC,XGETBV1,XSAVES
> cpu0: 64KB 64b/line 2-way D-cache, 64KB 64b/line 2-way I-cache, 512KB
> 64b/line 16-way L2 cache, 16MB 64b/line 16-way L3 cache
> cpu0: apic clock running at 1830MHz
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
> acpihpet0 at acpi0: 1 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> "ACPI0006" at acpi0 not configured
> acpipci0 at acpi0 PCI0
> acpicmos0 at acpi0
> com0 at acpi0 COM1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo
> com0: console
> "QEMU0001" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> "PNP0A06" at acpi0 not configured
> "QEMU0002" at acpi0 not configured
> "ACPI0010" at acpi0 not configured
> acpicpu at acpi0 not configured
> pvbus0 at mainbus0: KVM
> pci0 at mainbus0 bus 0
> 0:2:0: rom address conflict 0x/0x1
> pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
> "Intel 82371SB ISA" rev 0x00 at pci0 dev 1 function 0 not configured
> 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 ignored (disabled)
> pciide0: channel 1 ignored (disabled)
> uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
> "Intel 82371AB Power" rev 0x03 at pci0 dev 1 function 3 not configured
> "Bochs VGA" rev 0x02 at pci0 dev 2 function 0 not configured
> virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
> vio0 at virtio0: address 02:00:17:03:5f:26
> virtio0: msix shared
> virtio1 at pci0 dev 4 function 0 "Qumranet Virtio SCSI" rev 0x00
> vioscsi0 at virtio1: qsize 128
> scsibus0 at vioscsi0: 255 targets
> uvm_fault(0x8190a468, 0x8, 0, 1) -> e
> fatal page fault in supervisor mode
> trap type 6 code 0 rip 8123622b cs 8 rflags 10282 cr2 8 cpl e
> rsp 81a06670
> gsbase 0x818f6ff0  kgsbase 0x0
> panic: trap type 6, code=0, pc=8123622b
>
> The operating system has halted.
> Please press any key to reboot.
>
>

-- 
Atenciosamente,

Fabio Martins

(+5521) 97914-8106 (Signal)
https://www.linkedin.com/in/fabio1337br/