Re: wifi gui manager
On 2018-08-20, Edgar Pettijohn III wrote: > I've written a simple gui wifi manager. It can be found at: > > https://sourceforge.net/projects/openbsd-wifi-manager/ I'd strongly recommend using source control rather than just posting a zip file. By breaking up development into chunks and describing what you've done you can help yourself and others figure things out if a change goes wrong, and review it later which can be useful as a learning experience. > It is very much in an alpha testing phase. I need to clean it up and > make it a little more appealing to the eye. In my limited testing it > works well. If you experience issues please let me know. > > It requires: > > OpenBSD (tested on 6.3) Comments from reading the code, - Not sure if it was changed before or after 6.3, but certainly in -current "ifconfig scan" no longer requires root. - Some drivers report dB values (and iirc some are + some are -), others report %, so the signal strength mechanism won't work in some cases - Doesn't handle open networks - (Might want some rethink to cater for "ifconfig join" in -current) - Doesn't really need to fire off dhclient if it's already running on the interface? On 2018-08-20, Consus wrote: > Oh my god, why sourceforge? Why not? At least it's not gitlab or github!
Re: wifi gui manager
On 10:46 Tue 21 Aug, Stuart Henderson wrote: > On 2018-08-20, Consus wrote: > > Oh my god, why sourceforge? > > Why not? At least it's not gitlab or github! It's been known for embedding spam in zip archives. Also what's wrong with gitlab/github?
Re: routing traffic to transparent squid cluster
On 2018-08-16, Joerg Streckfuss wrote:
> Am 15.08.2018 um 18:26 schrieb Stuart Henderson:
>> On 2018-08-15, George wrote:
>>> I believe you may be looking for a redirect not a relay. It all really
>>> depends on your network topology and what you are trying to do but in
>>> general something like this is what you are looking at:
>>
>> For directing traffic from a PF box to a separate Squid box setup
>> as an interception ("transparent") proxy, you want "route-to" rather
>> than "rdr-to" (see squid pkg-readme).
>>
>> I haven't tried this with relayd but it looks like redirection with
>> "route to" is what's needed here.
>>
>> An associated "divert-to" is also needed on the box running Squid
>> (again see the pkg-readme).
>>
>>
>
> I tried to get the relayd part with redirects and the route-to option
> running. The Problem here in my opinion is the listen option of redirects.
> You could say something like: listen on ip X port 80 route-to y. So the
> redirect will listen for the _destination_ ip X with port 80 and will route
> this packets to Y.
> But how could you say: listen for _all_ packets coming from this special ip
> to any port 80 route to Y?
Ah yes of course, in that case relayd doesn't seem suitable for this
job as-is.
> My first thought was to divert the relevant packets with pf to localhost and
> then a redirect should do the job. The pf part is not the problem. But I
> didn't
> find a running redirect configuration. I think grabing diverted packets from
> localhost are the job of relays not redirects, right?
You definitely don't want a redirect for this, squid itself wants to get the
packets with divert-to so it can lookup the original destination address.
Redirecting would remove that address. So in that case it would require
changes to relayd.
Re: x260 hang at halt/reboot
On 2018-08-16, Frank Groeneveld wrote: > On Wed, Aug 15, 2018, at 15:02, Stuart Henderson wrote: >> Thanks for the suggestion, currently OpenBSD and UEFI only. >> I'll give it a try with MBR when I can afford a better SSD and rebuild it >> on that. >> > > I need CSM mode enabled on my X260 to get it working correctly. Is it > disabled for you? It is enabled. While looking for that I thought to try various other boot options and did manage to have it reboot successfully the first time after changing to UEFI only, but not the second time.
Re: Conundrum with pf
On Mon, Aug 20, 2018 at 09:21:54PM +, Walt wrote: > I don't really remember for sure from the last time I did a fresh install, > but I think that /etc/sysctl.conf isn't there by default -- if you need it, > you have to create it yourself. > > Walt > Having done multiple fresh installs over the last few months as I got my home network in shape, I can confirm that /etc/sysct.conf is not present by default and needs to be created manually if needed. -- Jon Tabor tab...@obsolete.site http://obsolete.site 'There is a saying: There is no such thing as overkill. There is only “Open fire!” and “Reloading!”' ― John Ringo, The Hot Gate
Re: wifi gui manager
On 2018-08-21, Consus wrote: > On 10:46 Tue 21 Aug, Stuart Henderson wrote: >> On 2018-08-20, Consus wrote: >> > Oh my god, why sourceforge? >> >> Why not? At least it's not gitlab or github! > > It's been known for embedding spam in zip archives. That was some years ago under previous ownership. > Also what's wrong with gitlab/github? They encourage devs to be lazy and not produce proper stable release assets. Lots of mess in the ports tree from people who just tag something on github, don't produce a stable tarball, don't generate autoconf scripts etc.
Re: wifi gui manager
On Aug 21, 2018 5:46 AM, Stuart Henderson wrote: > > On 2018-08-20, Edgar Pettijohn III wrote: > > I've written a simple gui wifi manager. It can be found at: > > > > https://sourceforge.net/projects/openbsd-wifi-manager/ > > I'd strongly recommend using source control rather than just posting a > zip file. By breaking up development into chunks and describing what > you've done you can help yourself and others figure things out if a > change goes wrong, and review it later which can be useful as a learning > experience. Agreed. Just wanted an initial look, so I can plan my next steps better. > > > It is very much in an alpha testing phase. I need to clean it up and > > make it a little more appealing to the eye. In my limited testing it > > works well. If you experience issues please let me know. > > > > It requires: > > > > OpenBSD (tested on 6.3) > > Comments from reading the code, > > - Not sure if it was changed before or after 6.3, but certainly in > -current "ifconfig scan" no longer requires root. Good to know. > > - Some drivers report dB values (and iirc some are + some are -), > others report %, so the signal strength mechanism won't work in some > cases Where can I find more about that? Is it in the individual manuals or will I have to dig through the driver code? > > - Doesn't handle open networks > Aware, but I haven't seen an open network in quite some time. Not sure if it's necessary. I guess it wouldn't hurt though. > - (Might want some rethink to cater for "ifconfig join" in -current) > I saw this. I'm waiting for 6.4 so I can play around with it. > - Doesn't really need to fire off dhclient if it's already running > on the interface? Will dhclient automatically see it's a new network? > > > On 2018-08-20, Consus wrote: > > Oh my god, why sourceforge? > > Why not? At least it's not gitlab or github! > > I like sourceforge.
Re: wifi gui manager
On 15:05 Tue 21 Aug, Stuart Henderson wrote: > > Also what's wrong with gitlab/github? > > They encourage devs to be lazy and not produce proper stable release assets. > Lots of mess in the ports tree from people who just tag something on github, > don't produce a stable tarball, don't generate autoconf scripts etc. What do you mean by "stable tarball"? If a tag contains stable version of code you just download the tarball that is generated for the tag. Also autolulz are slow and ugly, please use plain Makefile for C projects.
Re: wifi gui manager
On 2018-08-21, Consus wrote: > On 15:05 Tue 21 Aug, Stuart Henderson wrote: >> > Also what's wrong with gitlab/github? >> >> They encourage devs to be lazy and not produce proper stable release assets. >> Lots of mess in the ports tree from people who just tag something on github, >> don't produce a stable tarball, don't generate autoconf scripts etc. > > What do you mean by "stable tarball"? If a tag contains stable version > of code you just download the tarball that is generated for the tag. So you are part of the problem! I mean a tarball that is generated once and not change, rather than something which changes depending on what software is installed on the cluster node. See ports@ messages ad nauseum. > Also autolulz are slow and ugly, please use plain Makefile for C > projects. They're even slower and uglier if you have to run the m4 stuff to *generate* them before you can even run them, and may not work as intended if they're run through a version of autoconf which they weren't designed for.
support update
0 C Kenya P Nairobi T Nairobi Z P.O. Box 30164-00100 O Weenode I A Bishops Road M e...@weenode.com U B +254 706970697 X N Ultra-secure Enterprise Internet of Things (EIoT). Speciality in web applications development with OpenBSD-httpd web server, PostgreSQL DBMS, FastCGI protocol and C programming language on OpenBSD/ARM platforms.
Let's Encrypt Error with cgit, httpd, acme-client
I am running cgit to host my git repositories on OpenBSD 6.3 and am
trying enable https using Let's Encrypt. The URL of the cgit
repositories is a subdomain of my main domain (e.g. git.domain.com). I
get the following error below whenever I try to provision a certificate
using acme-client. I have specified my hosting provider's nameservers
to my domain registrar and have created an A record pointing the "git"
subdomain to my VM's IP address. Relevant .conf files and
file/directory permissions are below as well.
Any help would be greatly appreciated. Thanks in advance!
Samir
# acme-client -vAD git.domain.com
acme-client: /etc/ssl/private/git.domain.com.key: domain key exists (not
creating)
acme-client: /etc/acme/letsencrypt-privkey.pem: account key exists (not
creating)
acme-client: https://acme-v01.api.letsencrypt.org/directory: directories
acme-client: acme-v01.api.letsencrypt.org: DNS: 23.203.116.227
acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz:
req-auth: git.domain.com
acme-client: /var/www/acme/nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ:
created
acme-client:
https://acme-v01.api.letsencrypt.org/acme/challenge/-kVwLPlPys451fI4-3TgDBcJRBQmvjO7yzUcifUW0AY/6175217714:
challenge
acme-client:
https://acme-v01.api.letsencrypt.org/acme/challenge/-kVwLPlPys451fI4-3TgDBcJRBQmvjO7yzUcifUW0AY/6175217714:
status
acme-client:
https://acme-v01.api.letsencrypt.org/acme/challenge/-kVwLPlPys451fI4-3TgDBcJRBQmvjO7yzUcifUW0AY/6175217714:
bad response
acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid",
"error": { "type": "urn:acme:error:unauthorized", "detail": "Invalid
response from
http://git.domain.com/.well-known/acme-challenge/nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ:
\"\u003c!DOCTYPE
html\u003e\n\u003chtml\u003e\n\u003chead\u003e\n\u003cmeta
http-equiv=\"Content-Type\" content=\"text/html;
charset=utf-8\"/\u003e\n\u003ctitle\u003e500 Internal Server Er\"",
"status": 403 }, "uri":
"https://acme-v01.api.letsencrypt.org/acme/challenge/-kVwLPlPys451fI4-3TgDBcJRBQmvjO7yzUcifUW0AY/6175217714";,
"token": "nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ",
"keyAuthorization":
"nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ.cbdgaka6s7Kv6R_a_Rhq_6VMDSKE2D4VdJyddLn65QI",
"validationRecord": [ { "url":
"http://git.domain.com/.well-known/acme-challenge/nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ";,
"hostname": "git.domain.com", "port": "80", "addressesResolved": [
"ip.address" ], "addressUsed": "ip.address" } ] }] (1039 bytes)
acme-client: bad exit: netproc(21893): 1
/etc/httpd.conf:
ext_ip="0.0.0.0"
server "localhost" {
listen on $ext_ip port 80
# serve the cgit static files directly
location "/cgit.*" {
root "/cgit"
no fastcgi
}
# cgit CGI
root "/cgi-bin/cgit.cgi"
fastcgi socket "/run/slowcgi.sock"
location "/.well-known/acme-challenge/*" {
root { "/acme", strip 2 }
}
}
/etc/acme-client.conf:
authority letsencrypt {
api url "https://acme-v01.api.letsencrypt.org/directory";
account key "/etc/acme/letsencrypt-privkey.pem"
}
authority letsencrypt-staging {
api url "https://acme-staging.api.letsencrypt.org/directory";
account key "/etc/acme/letsencrypt-staging-privkey.pem"
}
domain git.domain.com {
domain key "/etc/ssl/private/git.domain.com.key"
domain certificate "/etc/ssl/git.domain.com.crt"
domain full chain certificate
"/etc/ssl/git.domain.com.fullchain.pem"
sign with letsencrypt
}
/var/www/conf/cgitrc
footer=/conf/cgit.footer
# Enable caching of up to 1000 output entries
cache-size=1000
cache-root=/cgit/cache
# Specify some default clone urls using macro expansion
clone-url=git://git.domain.com/$CGIT_REPO_URL
# Specify the css url
css=/cgit.css
# Show owner on index page
enable-index-owner=0
# Allow http transport git clone
enable-http-clone=0
# Show extra links for each repository on the index page
enable-index-links=0
# Enable ASCII art commit history graph on the log pages
enable-commit-graph=1
# Show number of affected files per commit on the log pages
enable-log-filecount=1
# Show number of added/removed lines per commit on the log pages
enable-log-linecount=1
# Sort branches by date
branch-sort=age
# Add a cgit favicon
favicon=/favicon.ico
# Enable statistics per week, month and quarter
max-stats=quarter
# Set the title and heading of the repository index page
root-title=HotBSD Code Repositories
# Set a subheading for the repository index page
root-desc=
# Allow download of tar.gz, tar.bz2 and zip-files
snapshots=tar.gz
## List of common mimetypes
mimetype.gif=image/gif
mimetype.html=text/html
mimetype.jpg=image/jpeg
mimetype.jpeg=image/jpeg
mimetype.pdf=application/pdf
mimetype.png=image/png
mimetype.svg=image/svg+xml
## Search for these files in the root of the default branch of repositories
## for coming up with the about page:
readme=:README
virtual-root=/
#scan-path=/htdocs/src
scan-path=/repos
# Di
Qualcomm Atheros AR9485 Wireless Network Adapter
Has anyone found a way to get this working on OpenBSD?
Re: Let's Encrypt Error with cgit, httpd, acme-client
Try removing all keys in the ssl directory aswell as
/etc/acme/letsencrypt-privkey.pem
On August 21, 2018 7:46:24 PM UTC, "Parikh, Samir"
wrote:
>I am running cgit to host my git repositories on OpenBSD 6.3 and am
>trying enable https using Let's Encrypt. The URL of the cgit
>repositories is a subdomain of my main domain (e.g. git.domain.com). I
>get the following error below whenever I try to provision a certificate
>using acme-client. I have specified my hosting provider's nameservers
>to my domain registrar and have created an A record pointing the "git"
>subdomain to my VM's IP address. Relevant .conf files and
>file/directory permissions are below as well.
>
>Any help would be greatly appreciated. Thanks in advance!
>Samir
>
># acme-client -vAD git.domain.com
>acme-client: /etc/ssl/private/git.domain.com.key: domain key exists
>(not
>creating)
>acme-client: /etc/acme/letsencrypt-privkey.pem: account key exists (not
>creating)
>acme-client: https://acme-v01.api.letsencrypt.org/directory:
>directories
>acme-client: acme-v01.api.letsencrypt.org: DNS: 23.203.116.227
>acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz:
>req-auth: git.domain.com
>acme-client: /var/www/acme/nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ:
>created
>acme-client:
>https://acme-v01.api.letsencrypt.org/acme/challenge/-kVwLPlPys451fI4-3TgDBcJRBQmvjO7yzUcifUW0AY/6175217714:
>challenge
>acme-client:
>https://acme-v01.api.letsencrypt.org/acme/challenge/-kVwLPlPys451fI4-3TgDBcJRBQmvjO7yzUcifUW0AY/6175217714:
>status
>acme-client:
>https://acme-v01.api.letsencrypt.org/acme/challenge/-kVwLPlPys451fI4-3TgDBcJRBQmvjO7yzUcifUW0AY/6175217714:
>bad response
>acme-client: transfer buffer: [{ "type": "http-01", "status":
>"invalid",
>"error": { "type": "urn:acme:error:unauthorized", "detail": "Invalid
>response from
>http://git.domain.com/.well-known/acme-challenge/nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ:
>\"\u003c!DOCTYPE
>html\u003e\n\u003chtml\u003e\n\u003chead\u003e\n\u003cmeta
>http-equiv=\"Content-Type\" content=\"text/html;
>charset=utf-8\"/\u003e\n\u003ctitle\u003e500 Internal Server Er\"",
>"status": 403 }, "uri":
>"https://acme-v01.api.letsencrypt.org/acme/challenge/-kVwLPlPys451fI4-3TgDBcJRBQmvjO7yzUcifUW0AY/6175217714";,
>"token": "nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ",
>"keyAuthorization":
>"nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ.cbdgaka6s7Kv6R_a_Rhq_6VMDSKE2D4VdJyddLn65QI",
>"validationRecord": [ { "url":
>"http://git.domain.com/.well-known/acme-challenge/nWmGUBfLtIJuzuoNGfegToiMezdT6GaFes83Id2yctQ";,
>"hostname": "git.domain.com", "port": "80", "addressesResolved": [
>"ip.address" ], "addressUsed": "ip.address" } ] }] (1039 bytes)
>acme-client: bad exit: netproc(21893): 1
>
>
>/etc/httpd.conf:
>
>ext_ip="0.0.0.0"
>server "localhost" {
> listen on $ext_ip port 80
>
> # serve the cgit static files directly
> location "/cgit.*" {
> root "/cgit"
> no fastcgi
> }
> # cgit CGI
> root "/cgi-bin/cgit.cgi"
> fastcgi socket "/run/slowcgi.sock"
> location "/.well-known/acme-challenge/*" {
> root { "/acme", strip 2 }
> }
>}
>
>
>/etc/acme-client.conf:
>
>authority letsencrypt {
> api url "https://acme-v01.api.letsencrypt.org/directory";
> account key "/etc/acme/letsencrypt-privkey.pem"
>}
>
>authority letsencrypt-staging {
> api url "https://acme-staging.api.letsencrypt.org/directory";
> account key "/etc/acme/letsencrypt-staging-privkey.pem"
>}
>
>domain git.domain.com {
> domain key "/etc/ssl/private/git.domain.com.key"
> domain certificate "/etc/ssl/git.domain.com.crt"
> domain full chain certificate
>"/etc/ssl/git.domain.com.fullchain.pem"
> sign with letsencrypt
>}
>
>
>/var/www/conf/cgitrc
>footer=/conf/cgit.footer
>
># Enable caching of up to 1000 output entries
>cache-size=1000
>
>cache-root=/cgit/cache
>
># Specify some default clone urls using macro expansion
>clone-url=git://git.domain.com/$CGIT_REPO_URL
>
># Specify the css url
>css=/cgit.css
>
># Show owner on index page
>enable-index-owner=0
>
># Allow http transport git clone
>enable-http-clone=0
>
># Show extra links for each repository on the index page
>enable-index-links=0
>
># Enable ASCII art commit history graph on the log pages
>enable-commit-graph=1
>
># Show number of affected files per commit on the log pages
>enable-log-filecount=1
>
># Show number of added/removed lines per commit on the log pages
>enable-log-linecount=1
>
># Sort branches by date
>branch-sort=age
>
># Add a cgit favicon
>favicon=/favicon.ico
>
># Enable statistics per week, month and quarter
>max-stats=quarter
>
># Set the title and heading of the repository index page
>root-title=HotBSD Code Repositories
>
># Set a subheading for the repository index page
>root-desc=
>
># Allow download of tar.gz, tar.bz2 and zip-files
>snapshots=tar.gz
>
>## List of common mimetypes
>mimetype.gif=image/gif
>mimetype.html=text/html
>mimetype.jpg=image/jp
Re: Let's Encrypt Error with cgit, httpd, acme-client
On 21/08/2018 20:46, Parikh, Samir wrote:> # cgit CGI
root "/cgi-bin/cgit.cgi"
fastcgi socket "/run/slowcgi.sock"
location "/.well-known/acme-challenge/*" {
root { "/acme", strip 2 }
}
}
Do you have /var/www/cgi-bin/cgit.cgi/.well-known/acme-challenge/ directory?
Because this is where the httpd server will look for it.
I usually set a separate virtual host for ACME and serve
it from default path /var/www/acme.
Re: Let's Encrypt Error with cgit, httpd, acme-client
Hi Samir, Parikh, Samir writes: > I am running cgit to host my git repositories on OpenBSD 6.3 and am > trying enable https using Let's Encrypt. I run cgit as well (with the same httpd.conf, acme-client.conf, file permissions, etc), and have no trouble creating and renewing certs. Do you see anything in /var/www/logs/access.log? Here's what I see: example.com 66.133.109.36 - - [21/Aug/2018:23:03:35 -0600] "GET /.well-known/acme-challenge/YXRuZWJ1c2FvdGV1Ym5hc290ZGFvZXNudGh1YW9lc25 HTTP/1.1" 200 87
Re: Let's Encrypt Error with cgit, httpd, acme-client
he...@ezaquarii.com writes:
> On 21/08/2018 20:46, Parikh, Samir wrote:> # cgit CGI
> > root "/cgi-bin/cgit.cgi"
> > fastcgi socket "/run/slowcgi.sock"
> > location "/.well-known/acme-challenge/*" {
> > root { "/acme", strip 2 }
> > }
> > }
>
> Do you have /var/www/cgi-bin/cgit.cgi/.well-known/acme-challenge/ directory?
>
> Because this is where the httpd server will look for it.
Not when you have a location block specifying the correct root...
Re: wifi gui manager
On 18:07 Tue 21 Aug, Stuart Henderson wrote: > On 2018-08-21, Consus wrote: > > On 15:05 Tue 21 Aug, Stuart Henderson wrote: > >> > Also what's wrong with gitlab/github? > >> > >> They encourage devs to be lazy and not produce proper stable release > >> assets. > >> Lots of mess in the ports tree from people who just tag something on > >> github, > >> don't produce a stable tarball, don't generate autoconf scripts etc. > > > > What do you mean by "stable tarball"? If a tag contains stable version > > of code you just download the tarball that is generated for the tag. > > So you are part of the problem! > > I mean a tarball that is generated once and not change, rather than something > which changes depending on what software is installed on the cluster node. If you create a release (https://help.github.com/articles/creating-releases/) then all associated generated tarballs are immutable, as far as I know. > > Also autolulz are slow and ugly, please use plain Makefile for C > > projects. > > They're even slower and uglier if you have to run the m4 stuff to *generate* > them before you can even run them, and may not work as intended if they're > run through a version of autoconf which they weren't designed for. That's why we should nuke autloluz in favor of something else. Just plain Makefiles for example. Or meson, I heard it's okay.
Re: protected domain for tap for vmm vms
On Fri, Aug 17, 2018 at 06:39:22PM +0200, jirib wrote: > Hello, > > I was checking bridge's protected domains and I'm curious > how to add VMM VM's tap into a VMM switch/bridge protected domain. > > It seems it's not implemented yet. > > I wanted to achieve this: > > - multiple VMM VMs in same switch/bridge > - VMs cannot talk to each other inside the bridge > hence protected domain > - VMs can access uplink via bridge's vether > > Jiri > I am not a networking person but is this something VLANs can solve?
Re: wifi gui manager
Consus writes: > On 18:07 Tue 21 Aug, Stuart Henderson wrote: > > On 2018-08-21, Consus wrote: > > > On 15:05 Tue 21 Aug, Stuart Henderson wrote: > > >> > Also what's wrong with gitlab/github? > > >> > > >> They encourage devs to be lazy and not produce proper stable release ass > ets. > > >> Lots of mess in the ports tree from people who just tag something on git > hub, > > >> don't produce a stable tarball, don't generate autoconf scripts etc. > > > > > > What do you mean by "stable tarball"? If a tag contains stable version > > > of code you just download the tarball that is generated for the tag. > > > > So you are part of the problem! > > > > I mean a tarball that is generated once and not change, rather than somethi > ng > > which changes depending on what software is installed on the cluster node. > > If you create a release > (https://help.github.com/articles/creating-releases/) then all > associated generated tarballs are immutable, as far as I know. They're not immutable.
OpenBSD does not recognize my wireless card on 2018 laptop.
Hello y'all. A totally newbie and non english speaker here. My case is simple. Today I receive my new computer, a DELL Inspiron 7000 2-in-1, with AMD Ryzen 7, etc. It came with Windows 10, and there everything worked fine. But I want to start the *nix experience, so I installed openBSD 6.3 -that was easy-, and when I tried to configure de wireless device, I just can't. I read the ifconfig man pages, internet forums, I even did research in that subject in the previous weeks, 'cause I know that the wireless connection was difficult to set in some models. Right now, I tried everything I can think about. -I can't connect with a RJ45, because that doesn't come with my machine. -I put all the firmware from the openBSD repository in an USB stick and plugged it into the laptop -I mounted /dev/sd1i /mnt -I executed dmesg, and read that my wireless card was an Atheros... -I ran " fw_update -p /mnt ". Just like that or specifing the name of the Atheros firmware. -Since that doesn't work, I extracted and copied manually the content of the .tgz to /etc/firmware. -And no matter how many times I did it, and how many times I reboot, when I run "if config", I don't seem to see the proper device recognized by the system. Any idea, 'cause I don't know what else can I do. +++ ++This is the content of /etc/firmware:++ 3c990 3c990-license athn-ar7010 athn-ar7010-11 athn-ar9271 athn-open-ar7010 athn-open-ar9271 atu-at76c503-i3863-ext atu-at76c503-i3863-int atu-at76c503-rfmd-acc-ext atu-at76c503-rfmd-acc-int atu-at76c505-rfmd-ext atu-at76c505-rfmd-int atu-intersil-ext atu-intersil-int atu-license atu-rfmd-ext atu-rfmd-int atu-rfmd2958-ext atu-rfmd2958-int atu-rfmd2958smc-ext atu-rfmd2958smc-int bnx-b06 bnx-b09 bnx-license bnx-rv2p bnx-xi-rv2p bnx-xi90-rv2p cs4280 cs4280-license fxp-d101a fxp-d101b0 fxp-d101ma fxp-d101s fxp-d102 fxp-d102c fxp-d102e fxp-license kue kue-license myx-eth_z8e myx-ethp_z8e myx-license ral-license ral-rt2561 ral-rt2561s ral-rt2661 ral-rt2860 rum-license rum-rt2573 run-license run-rt2870 run-rt3071 symbol-eprim symbol-esec symbol-license tht tht-license tigon-license tigon1 tigon2 tusb3410 tusb3410-license udl_huffman uvideo_info uvideo_isight_05ac-8300 uvideo_r5u87x_05ca-1803 uvideo_r5u87x_05ca-1810 uvideo_r5u87x_05ca-1812 uvideo_r5u87x_05ca-1835 uvideo_r5u87x_05ca-1836 uvideo_r5u87x_05ca-1837 uvideo_r5u87x_05ca-1839 uvideo_r5u87x_05ca-183a uvideo_r5u87x_05ca-183b uvideo_r5u87x_05ca-183e uvideo_r5u87x_05ca-1841 vmm-bios vmm-bios-license yds yds-license zd1211 zd1211-license zd1211b ++This is the output of ifconfig lo0: flags=8049 mtu 32768 index 2 priority 0 llprio 3 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 enc0: flags=0<> index 1 priority 0 llprio 3 groups: enc status: active pflog0: flags=141 mtu 33136 index 3 priority 0 llprio 3 groups: pflog ++This is the output of dmesg+ OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 12487225344 (11908MB) avail mem = 12101697536 (11541MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.1 @ 0xbc4b1000 (82 entries) bios0: vendor Dell Inc. version "1.0.3" date 01/12/2018 bios0: Dell Inc. Inspiron 7375 acpi0 at bios0: rev 2Undefined scope: \\_SB_.PCI0.LPC0.EC0_ acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP UEFI SSDT SLIC MSDM SSDT CRAT CDIT UEFI ASF! BOOT HPET APIC MCFG SLIC WDAT WDRT WSMT VFCT SSDT TPM2 IVRS SSDT SSDT SSDT SSDT FPDT SSDT BGRT acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S0) XHC1(S0) GP18(S4) LID_(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx, 2196.19 MHz 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,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB cpu0: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative acpihpet0: recalibrated TSC
