Messages

We're finalising our internal meta-discussion on the roadmap and we've come to the conclusion that we are going to provide the following:

(1) Reachable goals for 16.1
(2) Vision and wishlist for 16.7+

This allows us to remain flexible by not locking in on 16.7 just yet while staying transparent on the matter of what happens after 16.1.

A few comments about the suggestions follow in the next post.

Immer gerne. :)

Die Nutzer werden in der config.xml gespeichert zu erreichen im alten Code über die globale Variable $config, im MVC Code weiß ich es gerade nicht ohne nachschauen.

Hi romain,

the problem of this thread has been fixed in 15.7.2.

If you are talking about VLAN HW filtering, that is still being tested and thus not finalised (we have a preliminary fix in master but it doesn't work as well as it should).


Cheers,
Franco

Hi Jakob,

thanks for this. 256 looks like a doable amount. We've had trouble with 128 MB installations and OOM kills, but with 77 MB free this looks like a stable setup. Does the sluggishness also affect networking or only GUI responsiveness? It could well be the CPU not being powerful enough to run the PHP code.


Cheers,
Franco

PS: I still fear that fetching updates may fail sooner or later. There is no easy way out of this without RAM or providing a larger NanoBSD image (the current one is 1GB, but maybe it should be 2GB per slice).

Hi there,

I haven't seen SoftEther in the FreeBSD ports collection, but that doesn't mean we can't put it in there. I will do the following: see what it takes to get a port running and if it works provide it as an optional build, maybe even pushing it to FreeBSD ports mid-term.

I can't promise any GUI , but once the daemon is in it would be relatively easy for others to get started on this using our new MVC infrastructure.

See: https://github.com/opnsense/ports/issues/11

How does that sound? :)


Cheers,
Franco

We don't support compressed lists yet as far as I know.

Als nächstes kannst du über "Interfaces: (Assign)" das WLAN "ath0_wlan1" einem echten Firewall-Interface (eher Zone) zuweisen. Danach kannst du über dessen Konfigurationsbildschirm alles einstellen, siehe Screenshot.

Could you please provide output for:

# df -h
# pkg info

The root menu should be there even when you use SSH. What kind of login are you getting instead? Have you set the serial console to 115200?

Again, I need more info. A screenshot of the console, ping statistics, an indication of what happens on reboot. Wether the GUI times out or only certain pages won't work, etc.

Note that the console is not equal to an ssh login, because the latter is a network connection based method and might be affected like the GUI.

Not unless we get extra info, crash reports and the like. If all is stuck, pulling the plug is a last resort to get a running system back. The console being completely stuck is highly unlikely. Also, SSH might still be working, does ping work?

LibreSSL was forked by OpenBSD developers and is trying to retain compatibility with OpenSSL, but removed unsafe APIs and put a lot of work into hardening the code base. The direct CVE count comparison between the two shows that LibreSSL was indeed safer. You can find a lot of details about why LibreSSL exists on the internet.

The only caveat might be speed, operating system support and other optimisation (hardware acceleration). Since it has become super easy we encourage everyone to try and if it works just the same I'd recommend simply sticking with LibreSSL. There is no more "what if", there is only "do".

The wiki is not exactly up to date, but shows you that the "vga" or "serial" usb installer images are what you are looking for, depending on whether you have an embedded device or a VGA port:

https://wiki.opnsense.org/index.php/Installation_and_Initial_Configuration#OpenSSL_images

FWIW, it's gotten a lot better. We've been on our road, introduced unique changes that we do like stick to because we believe they allow us to move forward further and in turn make OPNsense better each step of the way. It's all about choice, even to the core of the whole OpenSSL vs. LibreSSL as well as *sense vs. m0n0wall division. The choice is up to you. The people that like our project matter to us. They help (and have helped) make this a project to be worth to consider. It's their project now as well.

Peace out. ;)

Die Treiber von pfSense und OPNsense kommen von FreeBSD, es ist also sehr wahrscheinlich.

Aus deiner Frage schließe ich, dass deine Druckerfrage für pfSense ist?

Wenn WLAN ein OPT(1) Gerät ist, dann fehlt sicherlich eine Firewall Regel, die den Traffic erlaubt. Es ist jedoch sehr schwer zu sagen, welches Druckerprotokoll du erreichen möchtest. Diese Information ist wichtig für die Freischaltung. Auch, ob der Drucker von der Firewall auf "ping" anspringt, oder vom LAN, ob der Drucker eine IP Addresse bekommt über DHCP, und und und...