Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - strahlenopfer

#1
PC Engine boards and Compex WiFi cards are quite popular for OPNsense installations.
With OPNsense 16.7, the configuration of two SSIDs failed on Compex WLE200NX card (Atheros AR9280 chipset). Even with a single SSID, the WiFi performance was quite poor. 

Thanks to OPNsense 17.1 & Freebsd 11, I successfully configured two SSIDs in AP-mode (WPA2 AES, private use and guests).
The performance is just great.  :)

My platform: PC Engines APU.2C4, Compex WLE200NX, 32GB mSATA.

The upgrade from 16.7 to 17.1 was no problem at all, I also confirm that OpenVPN, Intrusion Detection, transparent HTTP + HTTPS proxy with remote ACLs work as expected.

Cheers,

Strahlenopfer

#2
 :)


----------------------------------------------
|      Hello, this is OPNsense 17.1          |         @@@@@@@@@@@@@@@
|                                            |        @@@@         @@@@
| Website: https://opnsense.org/        |         @@@\\\   ///@@@
| Handbook: https://docs.opnsense.org/   |       ))))))))   ((((((((
| Forums: https://forums.opnsense.org/ |         @@@///   \\\@@@
| Lists: https://lists.opnsense.org/  |        @@@@         @@@@
| Code: https://github.com/opnsense  |         @@@@@@@@@@@@@@@
----------------------------------------------


The upgrade was successful! OpenVPN, transparent HTTP and HTTPS proxy with remote acls, Intrusion Detection... everything works as it should.

Platform is PC Engines APU.2C4 with 32GB mSATA.

You and your team did a great job, thanks again for your superb support! :)
#3
Hi franco,
thanks for your reply.

# fetch https://pkg.opnsense.org/sets/packages-17.1-OpenSSL-amd64.tar.sig
# fetch https://pkg.opnsense.org/sets/packages-17.1-OpenSSL-amd64.tar
# opnsense-verify packages-17.1-OpenSSL-amd64.tar
worked like a charm:


# opnsense-verify packages-17.1-OpenSSL-amd64.tar
Verifying signature with trusted certificate pkg.opnsense.org.20161210... done


I found out that /var/cache/opnsense-update/ contained ~50 folders, ~20 of them including incomplete packages-17.1-OpenSSL-amd64.tar files. I checked the SSD, no errors so far, strange...

How do I trigger the upgrade with the successfully downloaded packages-17.1-OpenSSL-amd64.tar file?

PS: Thanks for your excellent support, my donation to OPNsense has been a good investment.  :)
#4
I tried to upgrade from 16.7 (latest updates are installed) to 17.1,  but the upgrade process fails after the package is downloaded:


----------------------------------------------
|      Hello, this is OPNsense 16.7          |         @@@@@@@@@@@@@@@
|                                            |        @@@@         @@@@
| Website: https://opnsense.org/        |         @@@\\\   ///@@@
| Handbook: https://docs.opnsense.org/   |       ))))))))   ((((((((
| Forums: https://forums.opnsense.org/ |         @@@///   \\\@@@
| Lists: https://lists.opnsense.org/  |        @@@@         @@@@
| Code: https://github.com/opnsense  |         @@@@@@@@@@@@@@@
----------------------------------------------

  0) Logout                              7) Ping host
  1) Assign Interfaces                   8) Shell
  2) Set interface(s) IP address         9) pfTop
  3) Reset the root password            10) Filter Logs
  4) Reset to factory defaults          11) Restart web interface
  5) Power off system                   12) Upgrade from console
  6) Reboot system                      13) Restore a configuration

Enter an option: 12

This will automatically fetch all available updates, apply them,
and reboot if necessary.

A major firmware upgrade is available for this installation: 17.1

Make sure you have read the release notes and migration guide before
attempting this upgrade.  Around 300MB will need to be downloaded and
require 600MB of free space.  Continue with this major upgrade by
typing the major upgrade version number displayed above.

Minor updates may be available, answer 'y' to run them instead.

Proceed with this action? [17.1/y/N]: 17.1

Fetching packages-17.1-OpenSSL-amd64.tar: ...opnsense-verify: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature
Signature is not valid
failed



I tried to upgrade serveral times (yesterday and today), I tried several mirrors (OPNsense / LeaseWeb / c0urier.net), but the signature verification constantly fails:
opnsense-verify: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature
Signature is not valid

The internet connection is fine (200 Mbps down, 50 Mbps up), no packet loss or malformed packets.

Any hint on this?
#5
16.1 Legacy Series / Re: Wireless Howto
May 13, 2016, 01:52:24 PM
Hi Kilrathy,

I was able to add two WiFi devices (ath0_wlan1 and ath0_wlan2, both Access Point mode), and I assigned the interfaces to two WiFis. Both SSIDs are seen by the clients, but the clients fail to connect to the second WiFi (ath0_wlan2).

Did you finally manage to get two WiFis working?
#6
Hi

I'm running OPNsense 16.1.13-amd64 on an APU.2C4 board with WiFi card wle200nx.

I added two WiFi devices, ath0_wlan1 (Acces Point mode) and ath0_wlan2 (Acces Point mode), and I was able to assign the interfaces to two WiFis, ath0_wlan1 "internal" and ath0_wlan2 "guest".

Both SSIDs are broadcasted and seen by the clients, but the clients fail to connect to the second WiFi (ath0_wlan2). I deleted and added the WiFi confguration several times, but the clients are only able to connect to the WiFi that was configured first (ath0_wlan1).  I tried different settings (encryption, authentication etc.), but the problem persists.

Has anybody successfully configured two WiFIs with Compex wle200nx?

Cheers