Re: RISCV - port to Mango Pi MQ-Pro (D1)

[Peter J. Philipp]

On Sat, Sep 23, 2023 at 09:15:30AM +0200, Peter J. Philipp wrote:
> On Mon, Sep 18, 2023 at 02:37:50PM +0200, Peter J. Philipp wrote:
> > Hi,
> > 
> > I've been working a little bit on making OpenBSD run on Mango Pi, I haven't
> > succeeded yet, but I think we're close.  My patches are here:
> > 
> > https://github.com/pbug44/openbsd-src/tree/MANGOPI
> 
> Just a status report, I got it to boot to the exec'ing init.  I had to
> disable plic0 and com0, and am running on the boot loaders console.  That is
> probably why I see no installer message (no /dev/console).

Well I'm out of time, given another month I might have made it work.  Here is
my final commit:

https://github.com/pbug44/openbsd-src/commit/e25ff39b81043bbfb71c588fec7eb6c3c0025d91

Another failure, but I learned a lot so it was a success in my eyes.  I'm going
back to programming on my delphinusdnsd for the rest of this year.  That's my
priority.

I'm passing the torch to Miguel, Moritz and Mark who I've been having steady
contact with throughout this.  They have this hardware and are able to
make it work given time.  If nothing happens by december, I may be able to
pick up on this (if I want).

Best Regards,
-peter

-- 
Over thirty years experience on Unix-like Operating Systems starting with QNX.

Re: Bridging em and vlan

[Zé Loff]

On Sat, Sep 30, 2023 at 11:39:36AM -0400, David Higgs wrote:
> All of my devices until now have been behind my OpenBSD NAT router, but I
> recently acquired a Internet of Trash device that I would like to be
> accessible to the internet (yes, I know).
> 
> My home configuration uses a Unifi AP to translate my various SSIDs into
> VLANs which plug into one of my APU em(4) ports.  The IoT thing already has
> its own dedicated SSID/VLAN, but doesn't enjoy living behind my NAT.

Define "doesn't enjoy".  It absolutely requires a public IP?  It needs
some ports to be forwarded?  Has some sort of network connection
detection that fails because some ports are blocked for outgoing
traffic?

> Is there a way for me to bridge just one of the vlan(4) logical interfaces
> with my other em(4) uplink, so that my IoT item can speak DHCP directly
> with my internet provider?

Assuming your WAN connection also gets its IP address by DHCP, will your
ISP assign you multiple IP addresses, one for your uplink, one for the
IoT device?
 
> Can this be done with veb/vport or bridge, or will I need to use something
> more exotic to strip the 802.1q tags before they are sent to my ISP?

If you absolutely need the IoT device to have unfiltered connection to
the internet, you can just create a DMZ of sorts for that VLAN, let all
traffic pass out, forward the necessary ports for incoming traffic, and,
assuming you don't trust the device at all, block all traffic from that
VLAN to the rest of the network (or be very selective about it), and
maybe also from other VLANs to that VLAN.  Putting it in a different
rdomain altogether might also be a good idea.
 
> Thanks in advance,
> 
> --david

-- 
 

OT: Inspired by you.. and by Zuckerberg

[Daniele B.]

Hello,

Inspired by you, and sorry if I forgot someone, 
I reinvented 

https://sim.pli.city

Spare time any feedback could be very welcome.


-- Daniele Bonini