Messages

1

21.1 Legacy Series / Re: Are your Shaper queue lengths set correctly?

« on: July 21, 2021, 06:14:43 pm »

I even tried editing/running it manually on the CLI:

Code: [Select]

ipfw pipe 10000 config bw 100Mbit/s queue 100 type fq_codel ecn quantum 3000 limit 3000

Still shows:

Code: [Select]

q75536  50 sl.

...but yet if I create a new pipe, with varying configuration, it takes the none-50 value... well, I'm lost.

2

21.1 Legacy Series / Re: Are your Shaper queue lengths set correctly?

« on: July 21, 2021, 05:58:10 pm »

Aye, I did just try that - but no change.

I'm wondering if perhaps the issue is with modifying pipes, rather than on creation - I'm pretty sure I looked to 'up' it after creating the Pipe originally.

I do note that even though I've delete the Pipe through the UI, it remains in the ipfw pipe show command:

10002:  10.000 Mbit/s    0 ms burst 0
q141074 100 sl. 0 flows (1 buckets) sched 75538 weight 0 lmax 0 pri 0 droptail
 sched 75538 type FIFO flags 0x0 0 buckets 0 active

.. also tried the 'Reset' option as well, no change.

3

21.1 Legacy Series / Re: Are your Shaper queue lengths set correctly?

« on: July 21, 2021, 05:51:53 pm »

Created a new pipe, seem to take the value correctly, shows in ipfw pipe show:

Code: [Select]

q141074 100 sl. 0 flows (1 buckets) sched 75538 weight 0 lmax 0 pri 0 droptail
Guess I'll try deleting and re-creating my pipes

4

21.1 Legacy Series / Re: Are your Shaper queue lengths set correctly?

« on: July 21, 2021, 05:30:20 pm »

Ah ha -

Code: [Select]

ipfw sched show

 sched 10001 type FQ_CODEL flags 0x0 0 buckets 0 active
Assuming 50 sl. represents the 50 Queue slots, I do think this still does not take the value from the UI - when set to something other than 50.

EDIT: Found the ipfw rules:

Code: [Select]

/usr/local/etc/ipfw.rules
Does seem to show a correct queue size there:

Code: [Select]

queue 100
Perhaps I'm misinterpreting the ipfw pipe show command :-/

5

21.1 Legacy Series / Re: Are your Shaper queue lengths set correctly?

« on: July 21, 2021, 05:13:46 pm »

I think, that even though I have:

Code: [Select]

Scheduler type: FlowQueue-Codel

ipfw pipe show it also shows as FIFO?

Code: [Select]

sched 75537 type FIFO flags 0x0 0 buckets 0 active

6

21.1 Legacy Series / Are your Shaper queue lengths set correctly?

« on: July 21, 2021, 05:01:08 pm »

Anyone reading this, if you're running the Shaper, on 21.1.8, could you test something for me?

- Edit the Pipe
- Enable Advanced
- Set Queue slots, to a value other than 50 (the default)
- Apply

On the CLI, if you run:

Code: [Select]

ipfw pipe show
Do you still only see the default queue lot size, of 50?

Code: [Select]

q75536  50 sl. 0 flows (1 buckets) sched 10000 weight 0 lmax 0 pri 0 droptail
I had a look in the /tmp directory, to see if I can see the ruleset, but it didn't seem to be there.

I'm pretty sure in 21.1.7 the queues were set correctly based on the value entered in the UI.

7

20.7 Legacy Series / Re: Tunables changed for igb driver

« on: June 29, 2021, 11:23:38 am »

Good catch - I think there is also some suggestions to set the queues equal to the number of cores:

Code: [Select]

dev.x.x.iflib.override_qs_enable="1"
dev.x.x.iflib.override_nrxqs="8"
dev.x.x.iflib.override_ntxqs="8"
So for 8 cores, something similar to the above. As always, YMMV.

8

General Discussion / Re: An old chestnut - mDNS/Bonjour across VLANs

« on: December 06, 2020, 09:36:23 am »

4.3.20 was supposed to fix....

[UAP] Fix intermittent multicast packet loss on static VLANs.

Seems likely that it didn't - airplay problems have not reoccurred since downgrading to 4.0.80

4.0.80 still seems to be solid for me, even though the 'experience' scores for various devices are 'wonky' on this version, the actual wireless connection seems to be sound on all devices.  I was on this before going to the 4.3.x branch... which seems to have been a bit of a disaster generally.

4.3.20 still seems to be ok for me on switches, however, no outstanding issues/problems there for me.

9

General Discussion / Re: An old chestnut - mDNS/Bonjour across VLANs

« on: December 04, 2020, 10:34:18 am »

Started getting a weird, perhaps similar problem to you, on 4.3.20...

Out of the 3 APs, after a few days, one would randomly stop passing multicast traffic - devices wouldn't see the Airplay announcements - port mirroring I could see it leaving the switch, but devices connected to an impacted AP did not see it.  Restarting the AP recovered things, for a few days.... then another AP would be impacted.

So far, downgrading APs to 4.0.80 again it hasn't happened again... yet anyway

10

General Discussion / Re: An old chestnut - mDNS/Bonjour across VLANs

« on: November 29, 2020, 12:00:09 pm »

Something else, whilst I remember, Fast Roaming on the wifi network settings, broke it as well when enabled.

... network Auto Optimise probably will as well, as I believe that restricts Multicast in some way.

11

General Discussion / Re: An old chestnut - mDNS/Bonjour across VLANs

« on: November 28, 2020, 01:35:06 pm »

Not so much the cabling - Sparks can turn a ceiling into swiss-cheese to thread cables pretty quickly (in my experience)... it's more the plastering etc that follows!

Thankfully, we did it before we moved in.  Ummmed and ahhhed at the time, over whether to destroy the place or not.  But now, completely worth it

12

General Discussion / Re: An old chestnut - mDNS/Bonjour across VLANs

« on: November 28, 2020, 11:15:28 am »

No, only iPhones / computers on WiFi - everything else cabled.

13

General Discussion / Re: An old chestnut - mDNS/Bonjour across VLANs

« on: November 28, 2020, 09:51:37 am »

Just set this up myself, there are a few Unifi-isms, I'm running:

3 x Unifi AC AP Pros
1 x Unifi Pro 48 Port Gen2 switch
1 x Unifi Pro 24 Port POE Gen2 switch
A number of Flex and Flex Mini switches

- Firstly, firmware 4.3.20 is key for me.  On APs and switches.  .21 and .22 caused all sorts of havoc.  I shall be staying on this firmware version

- Firewalls rules as you have above, destination 224.0.0.251, UDP, port 5353, inbound all VLANs you want to repeat

- Enable 'Multicast Enhancement' on each wifi network that you have mDNS repeater setup for on the Unifi controller (Settings -> Wifi - > Edit -> Advanced

- Enable IGMP Snooping on the Unifi for each VLAN/profile setup with mDNS (Settings -> Advanced Features ->Network Isolation -> Edit)

- I had to allow all traffic BACK from my AppleTVs, to the streaming devices (iphones, computers).  I think the port range is huge, so I decided to create 2 groups and allow all traffic between them. Airport express seemed to work ok without this, but I believe AppleTV needs to be able to initiate connections back to the iPhone, computer, etc.

.. think that's it

14

20.1 Legacy Series / Re: Replace installation%u2019s SSD

« on: June 11, 2020, 08:46:12 am »

Why not just

1) Full backup of config
2) Fresh install on new ssd
3) Restore config?

Not just me then? :p

Although I guess if you have any /boot/loader.conf.local customisations, these might not (wont?) make it...

15

20.1 Legacy Series / Re: Help with HA setup

« on: June 10, 2020, 04:00:29 pm »

I do not know the current status, but perhaps it provides further research for you, I seem to recall sometime ago reading about problems with CARP on a LAGG.  But perhaps that was just on older versions and was fixed, I'm afraid I cannot recall.

I can say, however, that I run a CARP cluster in the DC, without LAGG, and do not see any problems - so I don't believe it is broken.