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

Topics - hirschferkel

#1
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

ath0: stuck beacon; resetting (bmiss count 8)
or 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
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
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

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?
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:

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
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
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
Hi, I got this kernel Error and wanted to know what it means? Any idea?

Best, hirschferkel

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
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

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:


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


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
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
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
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
This is still an issue in 18.1.3
Are there any ideas, how to solve this kernel stuck beacon issue?

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
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:

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:

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:

"WARNING: Your certificate has expired!".


All the best, hirschferkel
#14
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
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.)
#16
Hallo,

ich wende mich an euch, da unser Router (Varia-Store OPNSense Router) über Nacht seinen Dienst quittiert hat, obwohl wir Hard- und Softwareseitig nichts geändert haben. Bis dato lief bezüglich Internet alles einwandfrei, nur seit heute morgen will der Router partout keine Internet mehr routen.

Zum Netzwerk: Der OPNSense Router hängt an einem VodeafoneKabel-Modem. Die Rechner, die an den Router angeschlossen sind, haben feste IP Adressen.

Der Router empfängt selbst Internet Konnektivität und kann nach außen ohne Paketverlust pingen. Auch die Rechner können nach aussen pingen, aber alle anderen Anwendungen werden nicht geroutet. Über Broser gibt es also kein Internet, Mailandwendungen dunktionieren nicht etc. d.h. die angeschlossenen Geräte erhalten in keiner Anwendung Internet. Dies haben wir auch mit einem zweiten Anbieter als Anschluss an den OPNSense Router getestet (Versatel DSL). Beide Netze haben bis gestern an dem Router einwandfrei funktioniert. Auch über Versatel gibt es kein Routing mehr über den OPNSense Router.

Mit beiden Netzen kommen wir aber über eine angeschlossene Fritzbox problemlos ins Internet.

Meine Frage: Wie kann ich feststellen ob es sich eindeutig um einen Hardwarefehler handelt, was im Moment nahe liegt. Oder wie kann ich zumindest Softwareseitig den Fehler besser eingrenzen? Hat jemand eine hilfreiche Idee?

Schönen Gruß, Hirschferkel
#17
I copied the Nano installation on a Flash drive and booted the router. Everything worked fine, i logged in with the basic account root/opnsense and restored the old backup. This worked fine for one flash card.
The router works fine with it...

So, now, I wanted to store a backup on another flashcard without having to switch of our router. To do so I started the same routine again, BUT: With two different Flash cards it does not work this way anymore.

I log into the basic installation - which actually gets booted - choose the backup and click restore and after this ... the router will not boot anymore from this flash drives.

What am i doing wrong? It worked once but now i fail and i do not know why...and I do not know how to find the error. I'm working in OS X...

Best, hirschferkel
#18
Hi there,

after I unlocked the 17.7 r2 release (I was forced to do so, as OPNsense software announced the lifetime end of this software [17.7r1] would have been reached) the update process started and on reboot everything was gone. When i tried to read the content of the flash drive in terminal (OS X) it only stated the volume size but no partitions anymore.

That's wired.

I have an old backup system on another drive. I'm trying to copy it to this broken flash card, now. First attempt was no success as i tried to copy the working volume to a .dmg on the desktop first and than tried to override the second flash card with this .dmg content. But somehow the VARIA router did not read this flash card...?

So my second attempt, now, is this:
disk1 is Flash drive with broken system
disk2 is working system

Macintosh HDD:~ admin$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            250.1 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *8.1 GB     disk1
   1:                    FreeBSD                         2.0 GB     disk1s1
   2:                    FreeBSD                         2.0 GB     disk1s2
   3:                    FreeBSD                         52.6 MB    disk1s3
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *7.9 GB     disk2
   1:                    FreeBSD                         2.0 GB     disk2s1
   2:                    FreeBSD                         2.0 GB     disk2s2
   3:                    FreeBSD                         52.6 MB    disk2s3
Macintosh HDD:~ admin$ sudo dd if=/dev/disk2 of=/dev/disk1 


Is this going to work or did I miss something completely to get my Varia Store router with OPNsense software back again?

Best, hirschferkel
#19
Hi there,

i get a lot of errors in the reports of my WAN, does anybody know why and what to to? This is just after rebooting, the error rate grows by time...

Rate 5M
RSSI 14.0
In/out packets 493 / 279 (52 KB / 100 KB )
In/out packets (pass) 493 / 279 (52 KB / 100 KB )
In/out packets (block) 112 / 0 (24 KB / 0 bytes )
In/out errors 20172/169
Collisions 0
#20
Seit dem Update auf 17.1.7 erscheinen andauernd folgende Logs, weiß jemand was das zu bedeuten hat?
Der Fehler tritt jedesmal auf, wenn ich mich bei OPNsense im GUI anmelde, oder das Dashboard neu lade / nur lade; diese Logs waren vor dem Update aber definitiv nicht da.

Gateway in OPNsense unter System > Gateways (dynamic, online) zeigt an:
KABEL_DHCP (default)    KABEL    XX.YY.144.254    XX.YY.144.254    Interface KABEL_DHCP Gateway   

Gateway adress i look up
Your IP Address is XX.YY.144.140.

Gateway under Services > Dynamic DNS:
KABEL    No-IP (free)    nickname.ddns.net   XX.YY.144.140    NO-IP name

May 29 13:53:19 opnsense: /index.php: Default gateway down setting as default!
May 29 13:53:19 opnsense: /index.php: Default gateway down setting as default!
May 29 12:53:14 opnsense: /index.php: Default gateway down setting as default!
May 29 12:53:14 opnsense: /index.php: Default gateway down setting as default!