Topics

1

20.7 Legacy Series / WLAN Card replacement for Compex WLE200NX miniPCI (guess Atheros AR9280)

« on: October 06, 2020, 11:24:14 am »

Hi there,

I use a Varia Store APU2C4 Router with a Compex WLE200NX a/b/g/n miniPCI Wifi card (guess Atheros AR9280 Chipset). Since first installation the card produced so many problems, either because of slowness or crashes like

Code: [Select]

ath0: stuck beacon; resetting (bmiss count 8)or

Code: [Select]

ath0: device timeout
There was no way to set it up properly. So I'm considering to replace the card. Are there any recommendations, which alternativ Wifi Card would be easy to install without having to change anything regarding the OPNsense setup?

Best, hirschferkel

2

20.7 Legacy Series / [Solved]Activate / deactivate WAN with timetable / Schedule

« on: September 14, 2020, 05:06:51 pm »

Is there any way to activate a WAN (Wifi) and to switch it of e.g. during weekends to save energie? I was able to create a schedule, but I can only find ways to administrate services with the firewall but no way to ton on / turn of a Wifi?

Best, hirschferkel

3

20.7 Legacy Series / [SOLVED] APU2C4 | kernel: mmc0: Card at relative address 22964 failed to select

« on: August 04, 2020, 06:15:11 pm »

Hi there,

after upgrading to 20.7 I get this error queue. Any idea how to fix it?
CPU-Typ AMD GX-412TC SOC (4 cores)
APU2C4

20.1 is running without any problems.

Best, hirschferkel

Code: [Select]

2020-08-04T18:13:01 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:13:01 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:13:01 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:13:01 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:13:01 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:13:01 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:13:01 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:13:01 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:13:01 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:13:01 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:13:01 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:12:58 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:12:58 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:12:58 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:12:58 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:12:45 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:12:45 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:12:32 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:12:32 kernel: mmc0: CMD7 failed, RESULT: 1
2020-08-04T18:12:32 kernel: mmc0: Card at relative address 22964 failed to select
2020-08-04T18:12:32 kernel: mmc0: CMD7 failed, RESULT: 1

4

19.7 Legacy Series / bootup illegal action?

« on: August 28, 2019, 04:23:33 pm »

That's what I got after half a day of thinking the hardware was broken, 10 unsucessfull starts and some wired fixing:

Code: [Select]

opnsense: /usr/local/etc/rc.bootup: The command '/usr/local/bin/rrdtool update /var/db/rrd/opt2-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: /var/db/rrd/opt2-packets.rrd: illegal attempt to u…

5

Hardware and Performance / OPNsense Varia AMD APU2C4 broke - Replace with APU2D2?

« on: August 28, 2019, 01:26:21 pm »

Hello,

after only three years my 250 € router has completely crashed today: A Varia OPNsense complete system based on a PC Engines AMD APU2C4 board. This is a bit early as I think ...

Now I'm forcibly looking for a quick fix to put my network back into operation, with all the VPN set ups etc. Therefore, I would most likely buy a different router, because I have only made poor experiences with the Varia router and because it broke down so fast. In addition, from the very beginning the built-in Wifi card was miserable and their support bad.

But I have no idea what routers under 200 € are reasonable and which can easily just run with the OPNsense set up I have stored on my smard card. I've been trying to search the internet, but that was not really insightful.

Or does it make sense to buy just another board, maybe the APU2D2 or APU2D4? Maybe I would bring a new Wifi card, too, because I have an Aetheros card that has been producing a lot of timeouts.


Is it as easy as I imagine, that I only will have to

    unscrew the old board
    put on the wifi card
    screw in the boart
    insert the smartcard


and then the stored system would simply run again?
Has a motherboard already a built in bios that's  automatically loaded, so the system of the smart card will start on the first start?

Thanks for your help, hirschferkel

6

German - Deutsch / OPNsense Varia AMD APU2C4 abgeschmiert - Ersatz mit APU2D2?

« on: August 28, 2019, 01:13:00 pm »

Hallo,

nach nur drei Jahren ist heute mein 250€ Router komplett abgeschmiert: Ein Varia OPNsense Komplettsystem basierend auf einem PC Engines AMD APU2C4 Board. Das ist etwas früh wie ich finde...

Nun bin ich zwangsweise auf der Suche nach einer schnellen Lösung wie ich mein Netzwerk wieder in Betrieb nehmen kann, mit allen eingerichteten VPNS etc.. Daher bräuchte ich am liebsten einen anderer Router, da ich mit dem Varia Router nur schlechte Erfahrungen gemacht habe und weil der jetzt so schnell den Geist aufgegeben hat. Außerdem war von Anfang an die verbaute WLAN-Karte miserabel und der Support schlecht.

Aber ich habe überhaupt keine Idee was es da für Router unter 200€ gibt die man einfach mit OPNsense betreiben kann, wenn man ein fertig eingerichtetes System hat. Ich habe schon versucht im Internet zu suchen, aber das war nicht richtig aufschlussreich.

Oder macht es Sinn einfach ein anderes Board zu kaufen, das APU2D2 oder APU2D4? Eventuell brächte ich auch eine neue WLan Karte da hatte ich bisher eine Aetheros Karte die andauernd viele timeouts produziert hat.


Ist es so einfach wie ich mir das vorstelle, dass ich

• das alte Board rausschraube
• die Wlan-Karte aufsetze
• das Boart einschraube
• die Smartcard einstecke

und dann würde das System wieder laufen?
Hat so eine Motherboard dann schon ein Bios automatisch aufgespielt, das das System von der Smartcard lädt?

Danke schon mal für euere Hilfe, hirschferkel

7

19.7 Legacy Series / What doese "kernel: Error(127)" mean on startup?

« on: August 23, 2019, 09:17:35 am »

Hi, I got this kernel Error and wanted to know what it means? Any idea?

Best, hirschferkel

Code: [Select]

Aug 23 09:13:29 kernel: SHA256 ******mRFjkDjwyb7C30JlIQJ2QxxUsC6T4pI****** (RSA)
Aug 23 09:13:27 kernel: Error (127)
Aug 23 09:13:24 kernel: OK
Aug 23 09:13:23 kernel: done.
Aug 23 09:13:23 syslogd: kernel boot file is /boot/kernel/kernel
Aug 23 09:13:23 syslogd: exiting on signal 15
Aug 23 09:13:22 kernel: done.
Aug 23 09:13:21 kernel: done.
Aug 23 09:13:19 kernel: ovpns1: link state changed to UP
Aug 23 09:13:19 kernel:
Aug 23 09:13:17 kernel: pflog0: promiscuous mode enabled
Aug 23 09:13:17 kernel: pflog0: promiscuous mode disabled
Aug 23 09:13:17 kernel:

8

18.7 Legacy Series / kernel: igb1: link state changes to DOWN / UP / DOWN

« on: November 07, 2018, 07:00:30 pm »

Hi there,

I updated my 18.7.6 system today and since then my router goes wired.
I reinstalled the system, settings, changed the Network inputs (assigments of igb1 and igb2) cables, and so on. But it doesn't stop to break Internet connection. I thought maybe igb1 device is broken, but when I switched to igb2 it was the same result.

The whole system ran perfect for 3 month, and I do not know what I can do to get it work again. Any idea? I never saw such messages before.

All the best, hischrschferkel

Code: [Select]

Nov 7 18:51:35 opnsense: /usr/local/etc/rc.linkup: HOTPLUG: Configuring interface opt1
Nov 7 18:51:35 opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet attached event for opt1
Nov 7 18:51:35 kernel: igb1: link state changed to DOWN
Nov 7 18:51:35 kernel: igb1: link state changed to UP
Nov 7 18:51:32 opnsense: /usr/local/etc/rc.linkup: Clearing states to old gateway 192.168.178.1.
Nov 7 18:51:32 opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet detached event for opt1
Nov 7 18:51:31 kernel: igb1: link state changed to DOWN
Nov 7 18:51:31 kernel:

Code: [Select]

Nov 7 18:42:45 opnsense: /usr/local/etc/rc.newwanip: Interface '' is disabled or empty, nothing to do.
Nov 7 18:42:45 opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'ovpns1'
Nov 7 18:42:44 kernel: ovpns1: link state changed to UP
Nov 7 18:42:41 kernel: ovpns1: link state changed to DOWN
Nov 7 18:42:40 opnsense: /usr/local/etc/rc.openvpn: OpenVPN: Resync server1 VPN-ADMIN
Nov 7 18:42:40 opnsense: /usr/local/etc/rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use KABEL_DHCP.
Nov 7 18:42:39 opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS (XXX.YYY.ZZZ): (Success) DNS hostname update successful.
Nov 7 18:42:39 opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS: updating cache file /var/cache/dyndns_opt1_ixtract.ddns.net_0.cache: 91.XXX.128.YYY
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.newwanip: ROUTING: skipping IPv6 default route
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway '192.168.178.1'
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 192.168.178.1
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.newwanip: ROUTING: no IPv6 default gateway set, assuming wan
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to opt1
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt1'
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.newwanip: On (IP address: 192.XXX.178.YYY) (interface: KABEL[opt1]) (real interface: igb1).
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'igb1'
Nov 7 18:42:38 opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS (XXX.YYY.ZZZ): Processing dummy update on No-IP free account. IP temporarily set to 192.168.1.1
Nov 7 18:42:37 kernel: igb1: link state changed to UP
Nov 7 18:42:34 kernel: igb1: link state changed to DOWN
Nov 7 18:42:32 opnsense: /usr/local/etc/rc.linkup: ROUTING: skipping IPv6 default route

Code: [Select]

Nov 7 19:05:45 apinger: Starting Alarm Pinger, apinger(25841)
Nov 7 19:05:45 apinger: Exiting on signal 15.
Nov 7 19:04:59 apinger: Starting Alarm Pinger, apinger(32367)
Nov 7 19:04:59 apinger: Exiting on signal 15.
Nov 7 19:04:17 apinger: Starting Alarm Pinger, apinger(2188)
Nov 7 19:04:17 apinger: Exiting on signal 15.
Nov 7 19:03:27 apinger: alarm canceled: KABEL_DHCP(192.168.178.1) *** down ***
Nov 7 19:03:27 apinger: ALARM: KABEL_DHCP(192.168.178.1) *** down ***
Nov 7 19:02:30 apinger: Starting Alarm Pinger, apinger(22673)
Nov 7 19:02:29 apinger: Exiting on signal 15.
Nov 7 19:02:27 apinger: Starting Alarm Pinger, apinger(9813)
Nov 7 19:02:26 apinger: Exiting on signal 15.
Nov 7 19:02:14 apinger: Error while feeding rrdtool: Broken pipe
Nov 7 19:01:14 apinger: Starting Alarm Pinger, apinger(23449)
Nov 7 19:01:14 apinger: Exiting on signal 15.
Nov 7 19:00:20 apinger: Error while feeding rrdtool: Broken pipe
Nov 7 18:56:20 apinger: rrdtool respawning too fast, waiting 300s.
Nov 7 18:55:20 apinger: Error while feeding rrdtool: Broken pipe
Nov 7 18:54:20 apinger: Starting Alarm Pinger, apinger(15224)
Nov 7 18:54:20 apinger: Exiting on signal 15.

9

18.7 Legacy Series / Upgrade from 18.1 to 18.7 failed

« on: August 02, 2018, 10:29:42 pm »

Trying to update from 18.1 to 18.7 with console did not work again (as with 17.7 already) with Varia Store Router. Hat to install the nano.img with terminal instead and now it's working. But it's somehow really annoying that the upgrad will never proceed...

Best

10

18.1 Legacy Series / Dynamic DNS (NO-IP) does not update

« on: April 25, 2018, 10:08:31 am »

Hi there,

the IP-Adress of No-IP does not update in OPNsense. I know there is some package which can be installed, but i do not know how to proceed. I' somehow stuck with updating it manually each time I recognize the connection to our server was not updated and ist down, now. I would appreciate an automatic update of OPNsense. Any help?

Best, hirschferkel

11

18.1 Legacy Series / Channel assignment of WIFI ignored

« on: March 22, 2018, 09:02:13 am »

As I have a lot of kernel "stuck bacon" messages in the log files of my WIFI, I tried to switch the channel of the WIFI as some users suggested in the forum, which were suffering the same problems.

But after I changed the transmission channel in OPNsense (as you can see in the screenshot > SDviswits > from channel 11 to channel 2) the Router just ignores these settings and keeps on transmitting on channel 11.

Channel 11 seems somehow fixed. Any idea how I can change that?


Best, hirschferkel

12

18.1 Legacy Series / ath0_wlan - kernel: ath0: stuck beacon; resetting

« on: March 19, 2018, 04:34:38 pm »

This is still an issue in 18.1.3
Are there any ideas, how to solve this kernel stuck beacon issue?

Code: [Select]

kernel       ath0: stuck beacon; resetting (bmiss count 4)
kernel       ath0: stuck beacon; resetting (bmiss count 4)
kernel       ath0: stuck beacon; resetting (bmiss count 4)
kernel       ath0: stuck beacon; resetting (bmiss count 4)
kernel       ath0: stuck beacon; resetting (bmiss count 4)
kernel       ath0: bb hang detected (0x4)
https://forum.opnsense.org/index.php?topic=4059.msg15229#msg15229

13

18.1 Legacy Series / VPN does not work with e.g. "Tunnelblick" anymore > ns-cert-type?

« on: March 02, 2018, 11:11:24 am »

Hi there,

I do not exactly know how to fix the following problem and appreciate any help. I can't connect to my VPN anymore. I used the app "Tunnelblick" to connect to the OPNsense VPN but since today I get the following errors:

Code: [Select]

2018-03-02 11:04:28 VERIFY ERROR: depth=1, error=certificate has expired: C=DE, ST=****, L=****, O=***, emailAddress=s.***@***.de, CN=internal-ca
2018-03-02 11:04:28 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed
2018-03-02 11:04:28 TLS_ERROR: BIO read tls_read_plaintext error
2018-03-02 11:04:28 TLS Error: TLS object -> incoming plaintext read error
2018-03-02 11:04:28 TLS Error: TLS handshake failed
And as I installed the current Beta Version of tunneblick, I got this message:

Code: [Select]

Achtung: Dieses VPN kann möglicherweise in der Zukunft nicht verbunden werden.

Die OpenVPN Konfigurationsdatei für "kerberos-udp-1194-***" enthält die folgenden OpenVPN Optionen:

[b]"ns-cert-type" gilt seit OpenVPN 2.4 als unerwünscht und wurde in OpenVPN 2.5 entfernt[/b]

Sie sollten die Konfiguration aktualisieren, damit sie mit modernen Versionen von OpenVPN genutzt werden kann.

Tunnelblick wird OpenVPN 2.4.4 - OpenSSL v1.0.2n nutzen, um diese Konfiguration zu verbinden.

Dennoch können Sie dieses VPN mit zukünftigen Versionen von Tunnelblick, die nicht eine Version von OpenVPN beinhalten, die diese Optionen akzeptiert, nicht verbinden.
und eben:

Code: [Select]

"WARNING: Your certificate has expired!".
All the best, hirschferkel

14

18.1 Legacy Series / Alias Bug in 18.1: No FTP access from ftp-server after update to 18.1

« on: January 31, 2018, 09:57:38 am »

Since my upgrade to 18.1 our FTP-server can not be accessed from external connections anymore. Users get a wired screen, but the FTP-server is working perfect locally. So the only thing we have changed was the upgrade from 17.7 to 18.1.
Has anyone an idea, what could cause this problems, now? Firewall rules an port forward seem are o.k., as the welcomemessage of the FTP-server is "Welcome ...."?

When you try to connect to the server from local network, you get the required website via port 80 which will not show up from externally. So instead of all ports are being set correctly, it somehow looks like a port-forwarding issue, isn't it?

I really do not have any idea, why the sever will require user login and password, now...

Best

15

18.1 Legacy Series / Updating from 17.7.17 to 18.1 from Webinterface > complete failure

« on: January 30, 2018, 03:38:57 pm »

Using the Webinterface to upgrade from 17.7 to 18.1 caused a dead Router which started and after half an hour of wainting was set back to 17.7.
This was not the expected result...
All Updates from 17.1 ran smoothly and created no single abort or failure.

How can I Update to 18.1? (I use a Varia AMD APU2C4 Router.)