Messages

1

17.1 Legacy Series / Re: opnsense-update tries to reach FreeBSD:11:i386/16.7 ?

« on: November 28, 2016, 07:46:17 pm »

yes same with -ur

The output is:
Shared object "labsal.so.7" not found, required by "pkg".

I checked with another opnsense installation that I archived and I get already an error when running this command:
pkg add -f https://pkg.opnsense.org/snapshots/i386/pkg-1.9.3_1.txz

the error states that it is for the wrong architecture.

2

17.1 Legacy Series / Re: opnsense-update tries to reach FreeBSD:11:i386/16.7 ?

« on: November 24, 2016, 06:28:06 pm »

Hi,

Thank you now it seems to work again from the webpage. However the "upr" doesn't work as u is not recognised as parameter.

CU AssetBurned

3

17.1 Legacy Series / opnsense-update tries to reach FreeBSD:11:i386/16.7 ?

« on: November 16, 2016, 10:41:04 pm »

Hi,

I tried to figure out how to get to a version past OPNsense 17.1.a_440-i386. And for that I tried to run the firmware update check from the GUI. And get a "Repository Problem" error.

So I checked in the console and saw that opnsense-update tries to reach http://pkg.opnsense.org/FreeBSD:11:i386/16.7/latest/meta.txz

I used this to update to 17.1.a:
# opnsense-update -t opnsense-devel
# opnsense-update -ur 17.1.a
# reboot

and now I tried to run this:
# opnsense-update -sn "17.1\/latest"
# opnsense-update -fp
# reboot

but still stuck with the 440 version and the repository error. Well no wonder that 16.7 folder doesn't exist in the FreeBSD 11 branch.

So what do I miss here?!

CU AssetBurned

4

17.1 Legacy Series / Re: RTL8188 not in AP mode?

« on: November 09, 2016, 03:07:53 pm »

As far as I see it it should be up to date.

Well yes usually Linux is faster, but in this particular case BSD was faster.

5

17.1 Legacy Series / Re: RTL8188 not in AP mode?

« on: November 07, 2016, 11:42:56 pm »

Hi,

Ok that have been too many reinstalls and I confused myself.

So the RTL8188 sticks that I have (different brands) are detected in the console, but when I check the web interface (Wireless -> Device) there is no urtwn interface to select. An RaLink RT5390 stick seems to work fine.

If I however setup the RTL8188 in 16.7 and then perform the upgrade to 17.1.a then the RTL8188 will also allow me to select Access Point mode.

CU AssetBurned

6

17.1 Legacy Series / RTL8188 not in AP mode?

« on: November 07, 2016, 09:53:57 pm »

Hi,

I'm currently trying to figure out why an RealTek RTL8188 USB WiFi stick is not able to be used in Access Point mode in OPNsense 17.1, but fine in FreeBSD 11.0-STABLE amd64.

First I thought it is an limitation of 16.7 but even with the update to the latest alpha it is still not able to choose that mode.
I am able to activate the Access Point mode with an RaLink RT5390 stick.

Could it be that FreeBSD 11 uses already Hosted 2.5 while the 17.1 still uses Hostapd 2.0 ?

The hostapd.conf I used in FreeBSD 11 is pretty short:

Code: [Select]

interface=wlan0
ignore_broadcast_ssid=0
channel=6
logger_syslog=-1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0
debug=3
ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel
hw_mode=g
wmm_enabled=1
ssid=THETESTSSID
macaddr_acl=0
auth_algs=1
ieee8021x=0
wpa=2
wpa_passphrase=abcabcabcabc
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP TKIP
rsn_pairwise=CCMP
And the only lines in the rc.conf related to the stick are:

Code: [Select]

#wireless
wlans_urtwn0="wlan0"
create_args_wlan0="wlanmode hostap"
hostapd_enable="YES"

CU AssetBurned