Script launcher and a suite of basic scripts for music production?
Is there a script launcher that can be used for basic scripts to facilitate live (or close to live) music performances with OpenBSD? One of the reasons that I am a proponent of using OpenBSD with music, is the fact that much can be done simply, from the command line. Recording audio from a USB sound card, using ffmpeg to add reverb and basic effects, rerouting MIDI, switching instruments in Fluidsynth (still working on that one), potentially replaying audio files as clips, etc. There are a lot of possibilities that could be facilitated by a script launcher (and a suite of basic scripts) for new music creators trying out OpenBSD, would definitely be an asset. The only disadvantage that I can see at this point, is that what I am describing would require a number of open terminals on the desktop, which can be confusing to sort through, particularly during a live performance. Which is part of the reason that a script launcher would be useful. The advantages are many, first and foremost fitting in with the Unix philosophy of combining existing programs for new purposes, providing an open source alternative to commercial DAWs such as Ableton and Bitwig, while at the same time removing the frustration for some users that the only DAW available on OpenBSD is LMMS, as well as the temptation for some to try to compile Zrythm or another DAW to OpenBSD. Ideas or suggestions?
NAT64 across rdomains
Hi misc,
I've been trying to do NAT64 across different rdomains, but haven't had
any success so far. My test setup is as follows:
+---+
|client |
| . . . . . . . . . . . |
| fd00::2/112 |
+---+---+
|
Ethernet |
|
+---+---+
| OpenBSD router|
| . . . . . . . . . . . |
| rdomain 0 |
| re0: fd00::1/112|
| lo0: ::1/128 |
| . . . . . . . . . . . |
| rdomain 1 |
| lo1: 127.0.0.1/8|
+---+
There is a "service" running on the OpenBSD router in rdomain 1,
listening to 127.0.0.1 port 1234:
nc -V 1 -vl 127.0.0.1 1234
The client tries to connect the service via:
nc -zv 64:ff9b::7f00:1 1234
pf.conf only contains the following one line:
pass in log on re0 inet6 proto {tcp, udp} \
from (re0:network) to 64:ff9b::/96 \
rtable 1 af-to inet from 127.0.0.1
packet forwarding is enabled :
net.inet.ip.forwarding=1
net.inet6.ip6.forwarding=1
In my imagination, the client should be able to reach the service and
get a response, with the NAT64ed packet translated to a packet of
127.0.0.1 -> 127.0.0.1. However, although the incoming packet shows up
on pflog0 (so it does match the pf rule), it is not detected on the side
of the listening nc.
Any insights into why this setup does not work, or is "rtable"
incompatible with "af-to"?
Thanks!
Re: Installing with usb
On 2023/01/17 13:08:48 -0300, Gustavo Rios wrote: > Hi folks! > > I am trying to get openbsd installed in my notebook, i am using usb device > (sandisk) to install it. The problem is that when i am given the choice of > source for the install file sets, does not appear usb; only cd0 disk nfs > http and the like. usb counts as 'disk'. It'll then ask you if it's already mounted, reply no, and continue. to find out the name of the usb i think the easiest way is to just unplug and plug it back, the kernel should log the attach on the screen (the writings with the blue background.)
Installing with usb
Hi folks! I am trying to get openbsd installed in my notebook, i am using usb device (sandisk) to install it. The problem is that when i am given the choice of source for the install file sets, does not appear usb; only cd0 disk nfs http and the like. May someone help me ? Thanks a lot -- The lion and the tiger may be more powerful, but the wolves do not perform in the circus
Re: still struggling with dhcpcd and ipv6
On 2023-01-15, Shadrock Uhuru wrote:
> hi everyone
> my isp is zen which uses pppoe
> i have a /64 nd and a /48 pd
> i have configured dhcpcd.conf but can only get an ipv6 address on the
> external pppoe0 interface,
> the internal lan interface only gets a link local from slaac
I doubt it will help, but you shouldn't have "inet6 autoconf" on the
interfaces where you expect to assign from PD.
> i have the following in dhcpcd.conf
> ipv6only
> noipv6rs
> waitip 6
> duid
> persistant
> vendorclassid
> option interface_mtu
> option host_name
> option rapid_commit
> require dhcp_server_identifier
> slaac private
> script ""
> allowinterfaces pppoe0 em0 em1
> interface pppoe0
> ipv6rs
> ia_na 1
> ia_pd 2 em0/1 em1/2
Do you need all of that? Try cutting back to just what's in the example
in dhcpcd's pkg-readme. It worked with Zen last time I tried it (I moved
pppoe off OpenBSD now though).
Also don't discount that Zen might have broken your v6 config, I gave up
using their v6 in the end and shifted it to a tunnel via work instead
because I got fed up asking them to fix it after 2 or 3 times ..
(I should really shift my connection to idnet instead but it will be a
bit of a fiddly move :/)
> SafeIcmpTypes = "{ echorep, echoreq, unreach }"
> pass quick log on em0 all
> pass log inet6 proto icmp6 all icmp6-type $SafeIcmpTypes
> pass out log inet6 proto udp from any port dhcpv6-client to any port
> dhcpv6-server no state
> pass in on egress inet6 proto icmp6 all \
>icmp6-type { routeradv neighbrsol neighbradv }
>
> pass in on egress inet6 proto udp \
> from fe80::/10 port dhcpv6-server \
> to fe80::/10 port dhcpv6-client \
> no state
why the "no state" for these?
--
Please keep replies on the mailing list.
