Messages

Great guide... perhaps it should be pulled into the OPNsense documentation.... I also went from a consistent F to an B using this guide.

Because I saw some 'spikiness' on the upload I made a couple of adjustments to put things in better alignment with the Using Dummynet AQM paper and from the SQM bufferbloat recomendations on the LEDE project. Beautifully it bumped me up to an A:

UpPipe
Enable CoDel: Checked
CoDel target: 10
FQ-CoDel quantum: 1514
FQ-CoDel limit: 1024
FQ-CoDel flows: 1024

DownPipe
CoDel target: 10
FQ-CoDel quantum: 1514
FQ-CoDel limit: 1024
FQ-CoDel flows: 1024

Sorry it took me so long to reply.  I thought I already had until I looked today.  So, everything worked perfectly.  Running like a dream... till this week. 

Freak storm took us offline and my new breadboarded router fried on the desk.  At the end of the day, the motherboard and it's tiny cluster of hardware was perfectly fine.  Of all the nutty things: It was the HDD that got nuked. Literally burned a hole in it.

Soooooo... take 2. Every expectation it'll be fine... although this time I'll get the google drive backups working!

PhilD

Franco: I'll certainly take you up on pinning down a custom kernel... once I get to that point. ;) One step at a time!

Lattera: No worries.  I appreciate even having a heads up. I know from experience how much of a migraine not having a robot zombie army of clones gets in the way of checking off todo items. All in due time.

Thanks gents.

PhilD

Awesome.  That should help tremendously.

I'll tiptoe though and see if I can get away with making only a few changes needed to get my system working. I'd rather not loose traffic shaping if I can get away with it.  It's surprising how much traffic a single teenager can absorb if left unchecked.

That said, I won't say no to an already patched branch. Given time, I normally can figure out most puzzles... perhaps I'll be pleasantly surprised and things will work smoothly.

PhilD

Thanks for taking a look.  I know you've got to have a couple of items on your plate  ;)

The thread I linked to suggests that it's in 10.3... but it's not that clear if that's because of some custom work or if it's already built in.

That said, I see no reason to be able to suck it up for a month or two.  Especially if I can get some of my older hardware to cooperate.  I figured I'd end up with a few bruises before I had this little monster working right regardless.

I have a software development background (but with windows and .NET)... so I certainly understand where your coming from from the project perspective.

Would you mind answering a couple of questions? At first blush, the changes I'd need to make appear trivial, but I don't know nix well enough to tell if it only appears that way because I'm clueless. 

Thanks again,
PhilD

Is this something that would be reasonable for a novice to tackle following the online resources (and re-do when new updates are applied)? Or is it something so complex that I'd be effectively on a digital snipe hunt?

Out of curiosity, where did this end up?

I am running into this trying to get my new system ready... unfortunately if I apply any stress I encounter the stuck beacon and bf_next not NULL! errors and normally get kicked off wifi.

At the moment I've got my OPNsense cobbled together with bubblegum and bailing wire while I sort out my next steps.

At the moment in seems that I need to custom compile a kernel with the updates I need to get my hardware working anyway (https://forum.opnsense.org/index.php?action=post;topic=2345.0)...

Don't misunderstand me, I know I'm not asking about something that's trivial in any way.  Just trying to make sure I'm not chasing my tail when fixes already exist.

Thanks!
PhilD

Looks like the Intel 8260 isn't loading either... but I haven't sorted the drivers/path needed to solve that.  So, if anyone has an idea how to resolve that, I'd appreciate it too.

PhilD

Any chance we can get support for the Intel I219V added to the kernel?

Link to the PFsense discussion on the same topic: https://forum.pfsense.org/index.php?topic=101689.0

Looks like we have the em & lem drivers compiled in the kernel too... or at least I'm getting similar errors.

Thanks,
PhilD