Ad Schellevis

not reconsidering (due to the long term maintainability of the json file), but if you wish to disable kea from the gui and use a custom configuration instead just open...

I don’t think we should as we’re not offering a suitable template it will just overwrite the one just created if I’m not mistaken. The standard overwrite always has an...

Before writing my response. I do agree the problem scope is not clear enough. My concerns are that (if I’m not mistaken) we render the templates twice for everybody else...

you can easily inspect the rules in `/usr/local/etc/ipfw.rules` technically for the shaper there's no difference between a vlan or a regular interface.

what is vlan030's parent? if it's the same interface (igb0) that might explain the issue a bit. Our advised best practice is to prevent mixing tagged and untagged traffic, in...

I would test with a clean vlan first (no parents which may overlap), but `ipfw show` on the console would show counters per rule and may indicate overlaps as well.

> you'll have to forgive me I am new to this stuff. What do you mean by "clean vlan"? No problem, I meant an interface without untagged traffic on it....

The vlan part sounds a bit weird here as you're not matching on one at the moment, but I can doublecheck when I'm at the office, easy to test. The...

Just checked at our office, can't reproduce an issue when vlans are being used. The upstream bug tracker doesn't show much either to be honest (https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=ipfw). If you disable "shared...

There is one huge difference there indeed when it comes to ipv4, and that's NAT. I just noticed my test rule was also set to the wifi network, which is...