Messages

Hi guys I've been using OPNSENSE with an internal m.2 Qualcomm Atheros Wireless NFA222 card (Atheros AR9462) all the way up to OpnSense 20.1 and its been working perfectly fine.  I've recently upgraded from 20.1 up to 20.7.3 and it was still functioning fine for days.

I decided to do a Reset to factory defaults now my system was upgraded and start a fresh, only to find that is not properly detecting my WIFI card properly now, or allowing me to configure it.

Does anyone know if the Devs have removed anything from 20.7.3 that might have been available in 20.1 which might be causing this?

Am I going to need to start looking for Atheros files and including them in 20.7.3?  :)

Same mate...  :o

[if_iwm.koiwm8000cfw.ko]

Hi SOUK,

Can you point me to a thread with patches/code?


Thanks,
Franco

I've just got the card detecting finally

The files below are already showing in the 17.1 dev install \boot\kernel directory which are for the Intel® Dual Band Wireless-AC 8260 (Intel 8260ngw) and Intel® Dual Band Wireless-AC 8265 (Intel 8265NGW) M.2 Wi-Fi cards. 

if_iwm.ko
iwm8000cfw.ko

I've just added the following to /boot/loader.conf.local

if_iwm_load="YES"
iwm8000Cfw_load="YES"

I then added the following to /etc/rc.conf.local
wlans_iwm0="wlan0"
ifconfig_wlan0="WPA DHCP"

Its showing its mac address under the Wi-Fi device now, so im going to try and set it up and see how that pans out.

[we still have WiFi to figure out]

There are some more things that need tweaking before 17.1-BETA can go out:

o GUI has a couple of UI glitches with PHP 7.0 in the MVC framework,
o we still have WiFi to figure out
o an secure the approach for loading kernel modules at bootup,
o release 16.7.10 with the package manager fix required for a smooth transition

Hi Franco, are you going to be adding driver support for the Intel 8000 series cards, like the 8260. I believe some folks have got it working on FreeBSD11.  It would be nice to finally get a decent Wi-Fi card in my machine.

I've moved back to stable from the experimental version at the moment, but once you've updated the Wi-Fi side of things I will jump back on it to test it again.

One big piece to note is that both base (the underlying operating system itself) and ports (the third-party packages, like Suricata) are all compiled as Position-Independent Executables (PIEs). That means that every application has ASLR fully applied to it.

OPNsense 16.7.7 has PIE applied to base only. PIEified ports will launch with 17.1. Really good stuff to see.

I'm hoping to land SEGVGUARD in time for 17.1. SEGVGUARD provides ASLR bruteforce protection.

I followed the update procedure, does this look right?

OPNsense 17.1.a_549-amd64?
FreeBSD 11.0-RELEASE-p2?
OpenSSL 1.0.2j 26 Sep 2016?


Also, why is it i can never install Opnsense via USB with any USB installation method via Rufus it always fails.  I'm only ever able to re-install Opnsense via cdrom which is a right pain cos all my cd's are scratched to **** so my install takes like 20minutes via DVD due to read errors..  ;D LOL

USB install works fine with that other sense router software, is their anything i can do about that?  I've got like 2 rusty old DVD's left and im pretty sure they're unusable now..   ;D

Hey everyone,

I've put up instructions for upgrading into the FreeBSD 11.0 sets above, but please be aware that 17.1 is currently ALPHA status and anything can happen there.


Cheers,
Franco

I will give it a go... try my luck!

Hi SOUK,

These errors are common in FreeBSD 10 for said hardware. Apparently a lot of work went into FreeBSD 11 and it is fixed there, but the fixes never went back to 10.x, so until we migrate to FreeBSD 11, these errors will not go away and the hardware hardly works.

There are some workarounds like only using channel 12 (??), but I don't exactly remember, some people had the same issues before and the old threads can possibly help operate the hardware until the major FreeBSD update is done.


Cheers,
Franco

Hi Franco, any idea when will we start seeing the newer Opensense based one FREEBSD11 being rolled out?

I'd like to see some substantially improved Wi-Fi driver and chipset support for all of the newer vastly improved M.2, PCI-E and USB3 Wi-Fi devices out there. 

The current WI-FI support and development on both Opensense and Pfsense is atrocious really with regards to Wi-Fi.  All you ever hear is buy a stand-alone access point; same old, same old.. :))

It's like we've been living in the stone ages whilst technology has been evolving a million miles an hour.  Mean while even the cheapest routers out there are rocking far superior tech where Wi-Fi performance is concerned, so how about jump in on that action?   ;D

Best place to start Dev is with the M.2 2230 Intel Dual Band Wireless AC 8260 so I can stop moaning. lol

[Can anyone tell me how to get my Wifi working using this card.]

Can anyone tell me how to get my Wifi working using this card.

PRIMARY PROBLEM:

I've tried it in Opnsense v16.7 / v17.1 and both detect the card and allow me to effectively configure it the same way I can configure my existing USB WiFi dongle, but the Atheros M.2 card itself is not producing any WiFi signal for any of my devices to see. I'm also receiving the following errors in my log.

I'm also getting the following error in my logs non stop, which I'm assuming is related to the fault.:

also
Sep 14 14:41:14    kernel: ath0: stuck beacon; resetting (bmiss count 0)
Sep 14 14:41:14    kernel: ath0: stuck beacon; resetting (bmiss count 4)
Sep 14 14:41:14    kernel: ath0: stuck beacon; resetting (bmiss count 0)
Sep 14 14:41:14    kernel: ath0: stuck beacon; resetting (bmiss count 4)
Sep 14 14:41:14    kernel: ath0: stuck beacon; resetting (bmiss count 0)
Sep 14 14:41:14    kernel: ath0: stuck beacon; resetting (bmiss count 4)

Again, the card is:
- Qualcomm Atheros Wireless NFA222 (Atheros AR9462).
- Qualcomm Atheros QCNFA222 | PPD-QCNFA222 | Foxconn | NGFF| 168c0034 | abgn |   Atheros AR9462

[Hi chemlud]

Hi!

I tried several USB sticks, finally and in the end I plugged in a SATA DVD-ROM and everything went... ehm... no not fine, but finally got something running  on that board.

Hi chemlud, I tried the cdrom installation method using this OPNsense-16.7-OpenSSL-cdrom-amd64.iso and I can confirm that the cdrom version has worked and enabled me to now install Opnsense finally.

Looks good so far, although for some reason my M.2 Atheros Wi-Fi card is detected and allows me to configure every part of it but doesn't actually produce a Wi-Fi signal now.  I will raise that in another post though I guess.

I appreciate your help man...  Thank you.

[Hi chemlud,]

Hi!

This board is tricky (aka nightmarish) to install to. I tried several USB sticks, finally and in the end I plugged in a SATA DVD-ROM and everything went... ehm... no not fine, but finally got something running  on that board. The J1900 predecessor of this board was even worse, have a google :-)

PS: Only try with latest firmware installable...

http://www.gigabyte.de/products/product-page.aspx?pid=5631#bios

Hi chemlud,

Yeah im aware of the J1900 issues, but the GA-N3150N-D3V hasn't really been and issue on pfsense to be honest, at least not for me.  Mine shipped on the F3 firmware that worked fine and its currently on the F4 (the latest) and again that worked fine with regards to pfsense,  I'm actually on it right now on 2.4 experimental too and so far so good.

The only software I've had problems running so far on this motherboard is Opnsense, which is a shame because I've been reading their main website and learning all about its improvements and the myths and facts and it sounds appealing.

I appreciate your feedback nontheless, and will hook up one of my bluray drives now and give that a go and see how i get on.  Fingers crossed!

I will post back and let you know how i get on...  thank you.  ;)

[WARNING: attempt to domain_add(bluetooth) after domainfinalize()WARNING: attempt to domain_add(netgraph) after domainfinalize()]

I'm currently running pfsense version 2.3 stable, which has been great.  Today I decided that I would try out pfsense latest version 2.4 alpha (Experimental) and while I'm at it give Opnsense a try for the first time.

I tried the following installation images of Opnsense in case one had a feature preventing my installation from completing:

- OPNsense-16.7-OpenSSL-vga-amd64.img
- OPNsense-16.7-OpenSSL-vga-i386.img

- OPNsense-16.7-OpenSSL-serial-amd64.img
- OPNsense-16.7-OpenSSL-serial-i386.img

And during my USB installation using each of those images the installation halts and the last thing it says on the screen is this:

WARNING: attempt to domain_add(bluetooth) after domainfinalize()
WARNING: attempt to domain_add(netgraph) after domainfinalize()

My system meets all of the requirements of the recommended hardware specification to run this platform, but I seem to be getting this error over and over again before I can even get to a point that i can install Opnsense; its not looking good so far.

Any ideas why this keeps happening, I've never seen this before ...