David Kerr

I cited the `ip` command just as illustration, I wouldn't expect you to use those. I'm guessing (but have not looked in your source to confirm) that you are simply...

Available network namespaces on a host can be found by `ls /var/run/netns`. That directory is not populated by default, but anyone messing around with network namespaces will have created the...

I did a little bit of playing around... I added` -n / --netns` and modified `--iflist`. This is a pure hack (--netns must come before --iflist) but illustrates what is...

Forgive me if I use this issue just to document continuing thoughts on this topic. Hopefully it will be helpful. On further research it looks like we cannot assume that...

> ... vnStat doesn't use threads in its implementation so it would either have to constantly jump between network namespaces or threading be implemented. We don't need to introduce threads,...

I think the biggest design decision is how to store namespace information internally to `vnstat` and in the database. I can think of two options... create a new field, or...

I'll weigh in with my support here. All my IPv6 support is queued up awaiting someone to merge it. I'd also encourage that you create a "development" branch into which...

> @dkerr64, makes sense. I'd be inclined to create a release candidate branch quickly, with a few "quick wins"; your IPv6 code sounds like it should be on a branch...

config parameter `usev6` is not implemented in the current release. It requires merge of PR #291 and then implementing support for it in the various services (that pull request only...

>Then it's just confusing when it's already shown in the example config. That is the bug then !! Odd that this slipped in without corresponding support for it.