Unsupported (?) Realtek USB WiFi dongles: RTL8188FTV and RTL8812AU

2023-01-11 Thread Pontus Stenetorp
Hello @misc,

While cleaning over the holidays I found and tried a bunch of USB dongles with 
OpenBSD (most worked just fine), hoping that perhaps I could find something to 
add to `sys/dev/usb/usbdevs` after having watched Stefan Sperling's EuroBSDcon 
2017 talk. The ones I found that were not working with OpenBSD were two WiFi 
dongles with chipsets RTL8188FTV and RTL8812AU.

However, after reading the urtwn(4) source with my near non-existent kernel 
development knowledge, I now believe that it is not as simple as just adding 
the device IDs and hooking them into urtwn(4) to get them working. Am I correct 
in this? It would have been fun to author a patch, test the devices, and 
improve the hardware support for everyone.

For reference, please find the dmesg(8) and `usbdevs -vv` outputs below.

RTL8188FTV:

ugen0 at uhub0 port 7 "Realtek 802.11n" rev 2.00/0.00 addr 4

addr 04: 0bda:f179 Realtek, 802.11n
 high speed, power 500 mA, config 1, rev 0.00, iSerial 1CBFCECE0806
 driver: ugen0

RTL8812AU:

ugen0 at uhub0 port 7 "Realtek 802.11n NIC" rev 2.00/0.00 addr 4

addr 04: 0bda:8812 Realtek, 802.11n NIC
 high speed, power 500 mA, config 1, rev 0.00, iSerial 123456
 driver: ugen0

Best regards,
Pontus Stenetorp



Re: Query on openrsync(1)

2023-01-11 Thread Nick Holland

On 1/10/23 03:49, Abhishek Chakravarti wrote:


OpenBSD newbie here. While trying to backup my OpenBSD configs to my
Arch Linux box, I noted a discrepancy between the openrsync(1) manpage
examples and what I encountered. The steps to reproduce are as follows:

```
$ uname -a
OpenBSD oberon.taranjali.org 7.2 GENERIC.MP#758 amd64
$ touch foo bar
$ rsync -av foo bar abhishek@192.168.1.3:/home/abhishek
ksh: rsync: not found
$ openrsync -av foo bar abhishek@192.168.1.3:/home/abhishek
Enter passphrase for key '/home/abhishek/.ssh/id_ed25519':
Transfer starting: 2 files
bar
foo
Transfer complete: 56 B sent, 187 B read, 0 B file size
```

The EXAMPLES section for the openrsync(1) specifically mention rsync and
not openrsync. I did find an earlier thread related to this issue:
https://marc.info/?l=openbsd-misc=162123821229046=2

The suggestion from that thread seems to be to use the rsync package
instead of openrsync. Is this still the case? And if not, shouldn't the
openrsync(1) manpage examples invoke openrsync instead of rsync?

Thank you for your time and consideration.



I'm a big fan of rsync, and was really excited by openrsync being
built into OpenBSD, but so far, it hasn't done the jobs I need it
to do :-/

A few things that cause me trouble are the lack of a -H (preserve
hard links -- I bet that's ugly to code), -W (disable the
delta-transfer "feature".  Yes, I know it was The Reason for rsync,
but in my experience, it takes longer to do the delta transfers
than to just send the whole bloomin' file for the vast majority
of my usage.  And I don't mean 5% longer -- I'm talking 400%
longer sometimes.  And maybe worse...unpredictable), and I'm a
big fan and user of --link-dest.

But ... if it does what you want, absolutely, give it a spin.
If it doesn't...either install the package or grab the source code
to openrsync, add what you need and submit it. :)


I think there was some talk about ultimately naming it rsync, but
unless it is 100% feature compatible (and I'm not sure I'd consider
that a good thing), that will cause confusion in my world.

Nick.



Re: Unbound fails to resolve some domains

2023-01-11 Thread Rodrigo Readi
The only logs I get in /var/log/messages:

Jan 11 21:14:27 nc10 unbound: [86313:0] notice: init module 0: validator
Jan 11 21:14:27 nc10 unbound: [86313:0] notice: init module 1: iterator

But now it is resolving normally. It seems sometimes fails to resolve,
sometimes do it.


2023-01-11 20:10 GMT, Martin Schröder :
> Am Mi., 11. Jan. 2023 um 21:06 Uhr schrieb Rodrigo Readi
> :
>> It stopped to resolve some domains, for example qwant.com
>
> All fine here.
>
>> Any Idea what is happening?
>
> Not without some logs.
>
> Best
> Martin
>
>



Re: Missing dependencies for git-send-email(1)?

2023-01-11 Thread Steffen Nurpmeso
Hello.

Abhishek Chakravarti wrote in
 <87y1q9w5w1@oberon.taranjali.org>:
 |
 |Running a fresh install of OpenBSD 7.2 GENERIC.MP#758 amd64 in a VM.
 |The git-send-email(1) tool is available when pkg_add git is
 |done. However, when attempting to use it, git-send-email fails reporting
 |an out-of-date IO::Socket::SSL. After installing the following packages
 |with pkg_add I was able to get git-send-email to work:
 |  - p5-IO-Socket-SSL
 |  - p5-MIME-tools
 |  - p5-Authen-SASL
 |
 |Should these packages not be part of the git package? Perhaps I'm wrong;
 |if so I would welcome being corrected.
 |
 |Thank you for your time and consideration.

This is only the git built-in variant, but git-send-email can make
use of external tools, and i, in fact, _never_ (since before 2015)
used a different variant (for real).  The little MUA i maintain
documents something like

 [sendemail]
 smtpserver = /usr/local/bin/s-nail
 smtpserveroption = -t
 #smtpserveroption = -Sexpandaddr
 smtpserveroption = -Athe-account-you-need
 ##
 suppresscc = all
 suppressfrom = false
 assume8bitEncoding = UTF-8
 #to = /tmp/OUT
 confirm = always
 chainreplyto = true
 multiedit = false
 thread = true
 quiet = true
 annotate = true

   Newer git(1) versions (v2.33.0) added the option sendmailCmd.

You could also "simply" send format-patch output with anything you
wanted, including OpenBSD base tools (i presume .. but never tried
it).

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)



Re: Unbound fails to resolve some domains

2023-01-11 Thread Martin Schröder
Am Mi., 11. Jan. 2023 um 21:06 Uhr schrieb Rodrigo Readi :
> It stopped to resolve some domains, for example qwant.com

All fine here.

> Any Idea what is happening?

Not without some logs.

Best
Martin



Unbound fails to resolve some domains

2023-01-11 Thread Rodrigo Readi
I have unbound 1.16.3 on OpenBSD 7.2, all obtained by succesive upadates
(no new installation).

It stopped to resolve some domains, for example qwant.com

Any Idea what is happening?

Thanks
Rodrigo



Missing dependencies for git-send-email(1)?

2023-01-11 Thread Abhishek Chakravarti


Running a fresh install of OpenBSD 7.2 GENERIC.MP#758 amd64 in a VM.
The git-send-email(1) tool is available when pkg_add git is
done. However, when attempting to use it, git-send-email fails reporting
an out-of-date IO::Socket::SSL. After installing the following packages
with pkg_add I was able to get git-send-email to work:
  - p5-IO-Socket-SSL
  - p5-MIME-tools
  - p5-Authen-SASL

Should these packages not be part of the git package? Perhaps I'm wrong;
if so I would welcome being corrected.

Thank you for your time and consideration.

-- 
Abhishek Chakravarti
abhis...@taranjali.org | Kolkata, IN
fifthestate.co.in | refpersys.org | taranjali.org



Re: BiDi sfp in ix

2023-01-11 Thread Hrvoje Popovski
On 9.1.2023. 15:21, Hrvoje Popovski wrote:
> On 5.1.2023. 18:43, Hrvoje Popovski wrote:
>> On 4.1.2023. 14:20, Ivo Chutkin wrote:
>>> On 2.1.2023 г. 16:58 ч., Hrvoje Popovski wrote:
 On 28.12.2022. 20:21, Stuart Henderson wrote:
> On 2022-12-28, Hrvoje Popovski  wrote:
>> Hi all,
>>
>> I don't have much experience with BiDi sfp, so I'm asking you guys,
>> should openbsd ix work with 1G BiDi sfp.
> should do, yes.
>
> in case you're not aware, bidi transceivers come in different types,
> e.g.
> your MaxLink ML-S5531-20 transmits at 1550nm and receives at 1310nm, so
> must be paired with a transceiver that transmits at 1310nm and receives
> at 1550nm (e.g. the MaxLink model is ML-S3155-20) - do you have that?
>
> also, they should normally be used with single-mode fibre (due to how
> the bidi optics are coupled into the fibre they *can* also work with
> multimode fibre, though if you do that, insertion loss is high so
> distance is much more limited, plus it's even more sensitive to bending
> than usual in that case).
>
>
 Hi,

 everything is fine regarding transceiver and fiber. I've played with it
 for few days with my ISP and that BiDI sfp works on mikrotik
 RB5009UG+S+IN and cisco 2960 switch. On aruba 2540 (allow unsupported
 transceiver), ibm switch and openbsd ix(4) it won't work.

 I've ordered few BiDi sfp from fs.com and maybe my ISP will lend me
 MaxLink sfp so I could test them in lab.

 Thank you Stuart for information ...

>>> Hi Hrvoje,
>>>
>>> Can you try setting NIC to use speed 1G since it is SFP, not 10G SFP+
>>> module.
>>> My experience is that "media: Ethernet autoselect" not always work.
>>>
>> Hi,
>>
>> yes that's one of the problems. I couldn't set media to 1000baseLX and
>> ifconfig ix0 media only showed me autoselect, even when BiDi was
>> inserted into nic.
>>
>> Maybe that's problem with x552 but i didn't have x520 near me at that time.
>>
>> Good thing is that BiDi sfp's arrived and I will play with them.
>>
> Hi all,
> 
> It seems that ix(4) is having problems with 1G BiDi sfp. I've tested
> FS.COM 1G BiDi and they are working on mikrotik and some switches but on
> OpenBSD I'm getting "status: no carrier" what ever I do.

Hi all,

claudio@ suggested to try same setup with FreeBSD. So I've tried FreeBSD
and Linux and results are same, 1G BiDi from FS.COM coded for Cisco
won't work with Intel 82599 10G card.
If I boot FreeBSD and Linux with that sfp in 82599 or X710 card that
interface will be disabled at boot and won't show up in OS.
On OpenBSD i could see it but mac address is 00:00:00:00:00:00

I've tried all combinations with unsupported_sfp statements for FreeBSD
and Linux but I couldn't see that interface in OS.
If I put that sfp in card after boot status is no carrier whatever I do,
at least on FreeBSD. I'm still playing with Linux..


it seems that I've missed out all football here :)

it seems that I've missed out all football here



Re: sndio and bit perfect playback

2023-01-11 Thread Alexandre Ratchov
On Wed, Jan 11, 2023 at 02:43:25PM +0100, Jan Stary wrote:
> On Jan 11 01:10:11, a...@caoua.org wrote:
> > On Tue, Jan 10, 2023 at 08:22:27PM +, John Rigg wrote:
> > > 
> > > > > # If I recall correctly, I converted to FLAC here because the WAV 
> > > > > headers
> > > > > # generated by aucat and SoX differed, and so SoX would refuse to 
> > > > > play WAV fil
> > > > es
> > > > > # created by aucat.
> > > > 
> > > > That would be a bug in itself.
> > > > How exactly does SoX refuse to play the WAVs created by aucat?
> > > 
> > > sox is strict about headers and will complain if cbSize is inconsistent 
> > > with
> > > fmt size. Workaround is to use the '-t sndfile' option.
> > > 
> > > aucat is not alone here; several other programs write .wav files that
> > > require this option with sox.
> > > 
> > 
> > Here's a diff to switch aucat to extended wav format. According to
> > Microsoft docs, it is needed if bits > 16 or if there are more than 2
> > channels, which aucat supports. It fixes the sox problem.
> 
> Thank you.
> 
> One nit that's perhaps related: $ aucat -n in.wav -o out.wav
> produces a stereo 24bit out.wav, as -c 0:1 -e s24 is the default.
> Would it make more sense with -n to preserve the characteristics
> of in.wav instead?
> 

Yes, this is on my todo list, including preserving the sample rate,
which is the most annoying.



Re: sndio and bit perfect playback

2023-01-11 Thread Jan Stary
On Jan 11 01:10:11, a...@caoua.org wrote:
> On Tue, Jan 10, 2023 at 08:22:27PM +, John Rigg wrote:
> > 
> > > > # If I recall correctly, I converted to FLAC here because the WAV 
> > > > headers
> > > > # generated by aucat and SoX differed, and so SoX would refuse to play 
> > > > WAV fil
> > > es
> > > > # created by aucat.
> > > 
> > > That would be a bug in itself.
> > > How exactly does SoX refuse to play the WAVs created by aucat?
> > 
> > sox is strict about headers and will complain if cbSize is inconsistent with
> > fmt size. Workaround is to use the '-t sndfile' option.
> > 
> > aucat is not alone here; several other programs write .wav files that
> > require this option with sox.
> > 
> 
> Here's a diff to switch aucat to extended wav format. According to
> Microsoft docs, it is needed if bits > 16 or if there are more than 2
> channels, which aucat supports. It fixes the sox problem.

Thank you.

One nit that's perhaps related: $ aucat -n in.wav -o out.wav
produces a stereo 24bit out.wav, as -c 0:1 -e s24 is the default.
Would it make more sense with -n to preserve the characteristics
of in.wav instead?

Jan





> No regressions found with various ports and few windows programs.
> 
> ok?
> 
> Index: afile.c
> ===
> RCS file: /cvs/src/usr.bin/aucat/afile.c,v
> retrieving revision 1.9
> diff -u -p -u -p -r1.9 afile.c
> --- afile.c   24 Oct 2021 21:24:15 -  1.9
> +++ afile.c   10 Jan 2023 23:52:47 -
> @@ -432,12 +432,17 @@ afile_wav_writehdr(struct afile *f)
>   le32_set(, f->endpos - sizeof(hdr.riff));
>   memcpy(hdr.fmt_hdr.id, wav_id_fmt, 4);
>   le32_set(_hdr.size, sizeof(hdr.fmt));
> - le16_set(, 1);
> + le16_set(, WAV_FMT_EXT);
>   le16_set(, f->nch);
>   le32_set(, f->rate);
>   le32_set(, f->rate * f->par.bps * f->nch);
>   le16_set(, f->par.bps * f->nch);
>   le16_set(, f->par.bits);
> + le16_set(,
> + WAV_FMT_EXT_SIZE - WAV_FMT_SIZE - sizeof(hdr.fmt.extsize));
> + le16_set(, f->par.bits);
> + le16_set(, 1);
> + memcpy(, wav_guid, sizeof(hdr.fmt.guid));
>   memcpy(hdr.data_hdr.id, wav_id_data, 4);
>   le32_set(_hdr.size, f->endpos - f->startpos);
>   return afile_writehdr(f, , sizeof(struct wav_hdr));
> 
> 



Re: Httpd shell globbing rules

2023-01-11 Thread a user



it seems to be even though i have syntax error in file, config test gives me 
ok. is it because it parsed single entry?

you are right if i move my default site on top it gives me that output.
are there any reason it's taking first server entry? rather than giving me 40x 
error?




--- Original Message ---
On Wednesday, January 11th, 2023 at 3:55 PM, Crystal Kolipe 
 wrote:


> On Wed, Jan 11, 2023 at 09:42:14AM +, rahul.dshmkh1 wrote:
> 
> > as per httpd.conf file i should be able to match exact one character in 
> > server "a?.sitea.com"
> > but when i test this way i am able to visit sitea, below are the test 
> > results
> > :~> curl a.sitea.com
> > This is site a
> > :~> curl a1.sitea.com
> > This is site a
> > :~> curl ab1.sitea.com -->> this should not be matched? as there are two 
> > characters after a
> 
> 
> The domain 'ab1.sitea.com' does not match any of the server entries in your
> config.
> 
> In this case, the first entry that matches the address and port is used, in
> your case this is 'site a'.
> 
> If you add to /etc/hosts:
> 
> 192.168.25.11 xyz.example
> 
> Then:
> 
> ftp -o - http://xyz.example
> 
> will show 'site a'.
> 
> So maybe you want to move your 'defaultsite' to the top of the config file.
> 
> > 
> > /etc/httpd.conf
> > server "a?.sitea.com" {
> > listen on * port 80
> > root "/a.sitea.com"
> > }
> > 
> > server "b.siteb.com" {
> > listen on * port 80
> > root "b.siteb.com"
> 
> 
> Why is this not have a leading / like your other entires?
> 
> > }
> > 
> > server "defaultsite.com" {
> > listen on * port 80
> > root "/defaultsite.com"}
> > 
> > -



Re: Httpd shell globbing rules

2023-01-11 Thread Crystal Kolipe
On Wed, Jan 11, 2023 at 09:42:14AM +, rahul.dshmkh1 wrote:
> as per httpd.conf file i should be able to match exact one character in 
> server "a?.sitea.com"
> but when i test this way i am able to visit sitea, below are the test results
> :~> curl a.sitea.com
> This is site a
> :~> curl a1.sitea.com
> This is site a
> :~> curl ab1.sitea.com -->> this should not be matched? as there are two 
> characters after a

The domain 'ab1.sitea.com' does not match _any_ of the server entries in your
config.

In this case, the _first_ entry that matches the address and port is used, in
your case this is 'site a'.

If you add to /etc/hosts:

192.168.25.11 xyz.example

Then:

ftp -o - http://xyz.example

will show 'site a'.

So maybe you want to move your 'defaultsite' to the top of the config file.

> 
> /etc/httpd.conf
> server "a?.sitea.com" {
> listen on * port 80
> root "/a.sitea.com"
> }
> 
> server "b.siteb.com" {
> listen on * port 80
> root "b.siteb.com"

Why is this not have a leading / like your other entires?

> }
> 
> server "defaultsite.com" {
> listen on * port 80
> root "/defaultsite.com"}
> 
> -



Httpd shell globbing rules

2023-01-11 Thread rahul.dshmkh1
Hi,
I am learning OpenBSD httpd and as per httpd.conf(5) in servers section i can 
use ? for single character match, but i am unable to test it properly. below is 
my config.

OpenBSD Version(generic)
openbsd# uname -r
7.2

/etc/httpd.conf
server "a?.sitea.com" {
listen on * port 80
root "/a.sitea.com"
}

server "b.siteb.com" {
listen on * port 80
root "b.siteb.com"
}

server "defaultsite.com" {
listen on * port 80
root "/defaultsite.com"}

-
at client side i have below /etc/hosts file
192.168.25.11 a.sitea.com
192.168.25.11 b.siteb.com
192.168.25.11 defaultsite.com
192.168.25.11 a1.sitea.com
192.168.25.11 ab.sitea.com192.168.25.11 ab1.sitea.com

as per httpd.conf file i should be able to match exact one character in server 
"a?.sitea.com"
but when i test this way i am able to visit sitea, below are the test results
:~> curl a.sitea.com
This is site a
:~> curl a1.sitea.com
This is site a
:~> curl ab1.sitea.com -->> this should not be matched? as there are two 
characters after a
This is site a
=
kindly help.