OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of waxhead »
  • Show Posts »
  • Topics
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

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.

  • Messages
  • Topics
  • Attachments

Topics - waxhead

Pages: [1] 2
1
21.7 Legacy Series / Minor GUI bug
« on: October 10, 2021, 08:01:47 pm »
Firewall->Settings->Normalization

Hovering over any item under general settings such as disable interface scrub, ip do not fragment or ip random id hides the text by giving it the same color as the background color.

I use the tukan theme , but I bet there is something inconsistent with the GUI itself.

2
21.1 Legacy Series / Automatic firmware update notification?!
« on: May 24, 2021, 01:39:13 pm »
I have to do system->firmware->status->check for updates or via the system info widget in the lobby click the check or updates link.

Is there really anything that problematic with having OPNsense by itself, (perhaps once a day) check an URL to see if it's firmware version match or if there is a update available? I would much rather prefer to see in the system widget when an update is available instead of mindlessly having to click and hope there is something exciting waiting for me.

Would this be possible to add in a future update/release?

3
21.1 Legacy Series / For 21.1.3-amd64 -> Lobby->Dashboard->Traffic widget broken in SeaMonkey 2.53.6
« on: March 11, 2021, 06:53:40 pm »
Reporting->Traffic->Graph works fine, but...
Lobby->Dashboard->Traffic widget does not display graphs on SeaMonkey 2.53.6

This
... was working in 21.1.1
... was broken in 21.1.2 , but I did not report it - hoping for it to be fixed in 21.1.3.

It all works on Chrome 88.0.4324.182 (Debian), but please test your updates for stable versions on older browsers as well. Not everyone needs or wants to run on the latest fancy stuff, and it is not fun when thins break. This is a minor problem of course, but things such as buttons not working (which was fixed with a workaround in 21.1.2) is not always fun.
Don't get me wrong - you guys are doing a great job so keep up the good work!

4
21.1 Legacy Series / Will /var be periodically backed up even if it is set as a memory filesystem?
« on: February 16, 2021, 12:01:29 pm »
I upgraded by opnsense box with SSD's and decided to put /var in RAM.
If I enable all the periodic backups (rrd,dhcp leases,netfow and captive portal) at 1 hour interval it is not clear to me if this would be the same as having /var periodically saved to disk causing a unclean reboot / shutdown to result in max 1 hour of lost logs.

5
21.1 Legacy Series / Bug?: Can't edit aliases
« on: January 30, 2021, 03:10:18 pm »
Apparently I am not able to edit aliases by clicking the pen like button (Firewall->Aliases->existing alias->pen icon)

I tried in two different browsers , SeaMonkey 2.54 (daily driver) and Chromium v83 with the same result. Also ran System->Firmware->Updates->Audit->Health which I assume checks that all files are ok and don't have checksum errors...
I tested this with both the tukan theme (which I use by default) and the OPNsensedefault theme.

Is it just me or do others have this problem as well?

6
21.1 Legacy Series / Upgrade to 21.1 may take *very* long time (>1h)
« on: January 28, 2021, 10:38:46 pm »
Hi,

I just wanted to warn that upgrading to 21.1 on my old box (core 2 duo era) took a very long time (over 1 hour) after all packages was downloaded. If this is indeed expected it might be a good idea to add a warning somewhere so that people don't assume that their box is hanging.

Except from that - everything seems to be running perfectly, so congratulations to the OPNsense team with yet another great release as usual! Thanks a bunch! :)

7
21.1 Legacy Series / Will opnsense 21.1 dashboard traffic graph remember history?
« on: January 13, 2021, 05:58:26 pm »
The traffic graph widget on the dashboard does not remember history. E.g. just showing what happens from you load the dashboard and for as long as it is up. Now that chart.js is being used - will it show history in 21.1 or is this planned for future releases?

8
General Discussion / Nitpick : opnsense version number usually off by one month...
« on: January 11, 2021, 05:58:57 pm »
Hi,

Last time I posted something that I was displeased with the othersense fanatic picked it up and made a mess out of it so I am going to try to thread very carefully here....

From what I can remember many of the recent releases have been done just a couple of days before the end of the month. Assuming that 21.1 will be released by the end of this month , would it not make more sense to call it 21.2 to better reflect when it was released? I feel this would be more consistent with both the releases and peoples expectations.

Yes, I appreciate that opnsense is free, and this is a minor issue so I almost don't feel right complaining about this at at all , but on the other hand I have chosen to donate (and I encourage others to as well) so perhaps I have bought myself the "right" to be a tad unpleasant.

PS! Keep up the good work , opnsense is really a pleasure to use and it is getting better and better for every release it seems ;)

9
20.7 Legacy Series / A couple of feature requests
« on: December 04, 2020, 10:49:19 pm »
Howdy.

I just donated a few bucks to OPNsense so therefore I feel less guilty about posting a couple of feature requests so before I snap out of thinking that I am great - Here goes.

1. Traffic graph (dashboard):
Do not reset state if you switch to another view. How about using the [insight->totals->Last 2 hours, 30 second average] graph instead.

2. Make it possible to hide certain menu elements for less clutter.
For example GUI elements such as [Services->OpenDNS] , or [Services->DHCPv6] could be moved to a "disabled" section on the leftmost menu

3. Optionally turn off GUI animations.
It slows down a lot - especially on my browser (SeaMonkey)

4. Continous realtime interface monitoring. Split the GUI screen - showing real-time traffic on all interfaces on the lowest 20% of the screen (or somewhere else) as an example. Potentially using the same graph as my feature suggestion#1

That's it :)

10
20.7 Legacy Series / Feature request: Topology view
« on: April 21, 2020, 01:52:18 am »
I think it would be nice (and useful) if OPNssense had a topology view somewhere.
For example you could use a description linked to the MAC address / DHCP lease and build a table that describes the topology and what is connected to what.

Would this be interesting? I think it can be very useful for both small and larger networks, it could also be expandable with links to firewall rules, traffic stats, etc....

+------------+------+----------+---------------------------------+
| The ether  | WAN  | OPNsense | Switch48p_VLAN1                 |
|            |      |          +--+------------------------------+
|            |      |          |  | LAN                          |
|            |      |          |  +--+---------------+-----------+
|            |      |          |  |  | server01_file |           |
|            |      |          |  |  +---------------+-----------+
|            |      |          |  |  | server02_www  |           |
|            |      |          |  |  +---------------+-----------+
|            |      |          |  |  | workstation01 |           |
|            |      |          |  |  +---------------+-----------+
|            |      |          |  |  | workstation02 |           |
|            |      |          +--+--+---------------+-----------+
|            |      |          | Switch48p_VLAN2                 |
|            |      |          +--+------------------------------+
|            |      |          |  | OPT1_PUB                     |
|            |      |          |  +--+---------------+-----------+
|            |      |          |  |  | server03_file |           |
|            |      |          |  |  +---------------+-----------+
|            |      |          |  |  | server04_www  |           |
|            |      |          |  |  +---------------+-----------+
|            |      |          |  |  | server05_ftp  |           |
|            |      |          +--+--+---------------+-----------+
|            |      |          | Switch48p_VLAN3                 |
|            |      |          +--+------------------------------+
|            |      |          |  | OPT2_WIFI                    |
|            |      |          |  +--+---------------------------+
|            |      |          |  |  | rpi_ap1                   |
+------------+------+          |  |  +---------------+-----------+
| Cosmos     | WAN2 |          |  |  |               | Cellphone |
+------------+------+          |  |  |               +-----------+
| Multiverse | WAN3 |          |  |  |               | Laptop    |
|            |      |          |  |  +---------------+-----------+
|            |      |          |  |  | rpi_ap2                   |
|            |      |          |  |  +---------------+-----------+
|            |      |          |  |  |               | Guest01   |
+------------+------+----------+--+--+---------------+-----------+


11
General Discussion / Help needed: Replacing 3x switches with 1x partitioned (if possible) switch
« on: August 11, 2019, 11:37:49 am »
Hi,

Currently I have OPNsense set up with 4x deticated links for the following:

  • 1x WAN for Internet access
  • 1x LAN for private stuff
  • 1x OPT1 for public stuff (webservers, etc...)
  • 1x OPT2 for WIFI access , private/guest

LAN + OPT1 and OPT2 go to their own cheap 5 port switches which keeps the networks isolated quite well.

I recently got a bricked Netgear GS724Tv3 switch from the garbage at work and with some help from our nasty uncle Google I was able to de-brick it. This switchs has 24 ports and therefore have more than the 3 (switches) x 5 (ports) = 15 I have today - this should allow for plenty of spare ports for future setup/experiments.

I was hoping that I can replace my 3x switches with this 24 port switch since it fits cleaner in my rack and only require one power plug as well instead of the current mess with 3x power adapters and extra cabling.

I was hoping that I can somehow "partition" the switch to keep certain ports isolated from each other. From what I have learned recently VLANS is apparently the way to go, but there is a clear warning in opnsense that "Not all drivers/NICs support 802.1Q VLAN tagging properly. On cards that do not explicitly support it, VLAN tagging will still work, but the reduced MTU may cause problems. "

What sort of problems are we talking about here? corruption? complete failure? discarded packages?! How do I know if VLAN is supported or now - can I test it without creating a setup?! Do it need to be supported on everything or just one component of the networks such as OPNsense?!

I also discovered that my switch allow me to set up something called PVID which seems to be a "internal VLAN id" for the networks on the switch, but I don't understand if I need support for this on the other end somehow.

VLAN / PVID marked ports also have what I learned is called TAGGED, UNTAGGED and EXCLUDED. As I understand this the tagging/untagging bit only adds or removes a VLAN ID on the incomming/outgoing package.

As you probably have understood by now I am a complete imbecile when it comes to VLAN's and that sort of thing. I have heard about it , but I know nothing about it except from a few articles found around internet which is not very useful.

What I am trying to achieve is to simply have 3x isolated switches in one switch. E.g. set port 1-5 to network A, port 6-10 to network B, 11-15 to network C without possibility of interaction between those A,B,C's on the switch.

I would appreciate if someone can help point me in the right direction for what to read / what do do.

12
General Discussion / forum.opnsense.org website usability request
« on: July 01, 2019, 05:50:37 pm »
Howdy,

On the forums there is a rather huge search button that you have to click to open a searchbox. WHY???! There is more than enough room even on my 4:3 display to keep the search box open all the time.  It would be great if this could be open like a normal sensible searchbox and it would be good it if could use a normal font as well instead of the huge font currently used.

13
19.1 Legacy Series / [FEATURE REQUEST] - Keep the lobby CPU graph persistent and show staurated CPU
« on: March 23, 2019, 05:31:14 pm »
1st of all - thanks for OPNsense - by far better and makes more sense than a certain other sense which does not make sense anymore... anyway ...

In lobby->dashboard the system information widget shows CPU usage. In a dual CPU system it appears to show  the combined CPU usage e.g. if one CPU is at 100% and the other at 0% the widget shows 50%. That's ok , but I wish the CPU widget either showed pr. CPU or at least changed the color of the graph to RED if *ONE* CPU is at 100%.
The reason for this should be obvious - some task that can't be parallelized will hog the CPU and the widget is giving the impression that the firewall is running just fine.

The CPU graph (just like the traffic graphs) are NOT persistent and does not show any history unless you keep the lobby->dasboard up for a while - in my opinion the graphs would have been better if they showed some history.

Please consider changing this for an update / for the 19.7 series

14
19.1 Legacy Series / [FEATURE REQUEST] - Keep the lobby traffic graphs persistent
« on: January 26, 2019, 03:00:20 pm »
The traffic graph in the lobby:dashboard is not persistent. If I change to another view and get back the graphs start from scratch. Please consider adding a history for the last n hours

15
18.7 Legacy Series / Roadmap : false advertising?!
« on: July 31, 2018, 08:27:07 pm »
Hi,

Just for the record I would like to state that I am in love with OPNsense and lots of good thing have happened since it was forked from pfSense. So nothing wrong with that.

What I do have an issue with is the roadmap. How can you change the roadmap right before release as you see fit without even admitting that some things where simply not done.

For example:
https://opnsense.org/about/road-map/
vs
https://web.archive.org/web/20180604160509/https://opnsense.org/about/road-map/

Maybe I am misunderstanding that roadmap, but I view it as  "release goals" and "planned future stuff" which admittedly is also on that webpage.
So don't get me wrong , but would it not be much better (and more honest) to put a red cross over the goals/planned features that where missed? The way it is done now look nice from a marketing perspective. Wow these guys meet their release goals all the time , but we know that is not true and *if' (and that is a big if) my memory serves me correctly this have happened before as well.

I think that adding new things are ok , but please consider marking failed (or delayed) features with either red=cancelled, or yellow=planned for future release.

We all know that software projects often scraps certain features since something better come along. I do realize that my post may sound a bit harsh , but for me the roadmap is quite frankly "false advertising" and I would really appreciate if you can not remove things from the roadmap , but instead mark them a bit more clearly as either cancelled or delayed. After all this is only natural for a software with fixed release dates...

PS! Looking forward to trying out 18.7 - keep up the good work, and thanks for the (free) fish! :)

Pages: [1] 2
OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2