OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of cirkutbraker »
  • Show Posts »
  • Messages
  • 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

Messages - cirkutbraker

Pages: [1]
1
21.7 Legacy Series / Re: RSS on CL PPPoE
« on: November 04, 2021, 05:14:59 pm »
Quote from: franco on November 04, 2021, 08:30:04 am
Did you use any previous tweaks like net.isr.dispatch=deferred tunable?  Because I think RSS undoes that...

Franco, I did have that tunable set ( net.isr.dispatch=deferred ). Still set, so I'm assuming this means RSS takes precedence and reverts the net.isr.dispatch deferred value.

Given that light load performance looks better, the question is whether heavy load suffers enough to unset RSS on this box. Thoughts? I'll test of course, but welcoming feedback on this. Hard to give up those new peak numbers  :)

2
21.7 Legacy Series / RSS on CL PPPoE
« on: November 04, 2021, 06:53:31 am »
So I somehow skipped the part about the new RSS feature not working with PPPoE and enabled it.

I'm seeing HUGE performance improvement.

Before:

Code: [Select]
Speedtest by Ookla

Server: Green House Data, Inc - Seattle, WA (id = 11329)
ISP: CenturyLink
Latency:     2.01 ms   (0.40 ms jitter)
Download:   550.53 Mbps (data used: 468.2 MB)                               
Upload:   809.91 Mbps (data used: 387.5 MB)                               
Packet Loss:     0.0%

After:

Code: [Select]
Speedtest by Ookla

Server: Whitesky Communications LLC - Seattle, WA (id = 22168)
ISP: CenturyLink
Latency:     2.88 ms   (0.12 ms jitter)
Download:   917.81 Mbps (data used: 471.2 MB)                               
Upload:   906.24 Mbps (data used: 631.9 MB)                               
Packet Loss:     0.0%

This is the same current release 21.7.4 kernel tested before without the tunable and after the tunable "net.inet.rss.enabled" set to value "1".

I'd like to know more about how it's not compatible with PPPoE because I'm inclined to leave it enabled with this improvement (edit: I did review this thread: https://redmine.pfsense.org/issues/4821 but it's all over the place in terms of "it works" vs "it doesn't/can't")

(note that the first test results are very consistent over the course of my use of opnsense on this centurylink fiber connection)

Running on a Protectli Vault 4 Port, 8gb ram, Intel(R) Celeron(R) CPU J3160 @ 1.60GHz (4 cores)

3
Documentation and Translation / Query re: addition to Multiwan how-to
« on: October 05, 2021, 06:51:08 pm »
I recently implemented multiwan successfully on a clean install of Opnsense.

DNS over multiwan failed to function as anticipated based on the existing how-to: https://docs.opnsense.org/manual/how-tos/multiwan.html

Failover was successful in all aspects, but DNS was non functional on the failover gateway. I identified the issue as not having enabled "allow default gateway switching" in System : Settings : General

I believe this constitutes a required step to get multiwan functioning and should be added to the documentation.

I'm happy to submit this as a change to the opnsense docs via a PR but prior to doing so felt it was important to check in here on correct procedure for submitting a doc update for this project. Should I field this in the general forums first? Should I draft an addition to the how-to and PR?

Pages: [1]
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