ifb and LXC

ifb and LXC

[Robert LeBlanc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I'm trying to move a KVM guest to LXC and it utilizes ifb in order to
rate limit the ingest rate of data. I'm having problems getting the
ifb0 device up in the contianer but I get "Can't find device 'ifb0'"
when tying to bring it up. The ifb module is loaded on the host.

Host:
Linux my-kvm 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3
(2015-08-04) x86_64 GNU/Linux

LXC:
Debian Jessie
root@betelgeuse:~# lsmod | grep ifb
ifb                    12637  0
root@betelgeuse:~# ip link set dev ifb0 up
Cannot find device "ifb0"

Unlike tun devices, I can't find a device in /dev to know how it
should be "allow" in the container. For tun adapters I add this to the
LXC config file:

lxc.cgroup.devices.allow = c 10:200 rwm

and I create the device inside the container:
mkdir -p /dev/net
mknod -m 0666 /dev/net/tun c 10 200

I suspect that something similar is needed for ifb, but I can't seem
to figure it out. Please let me know if you have any ideas.

- ----------------
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904  C70E E654 3BB2 FA62 B9F1
-----BEGIN PGP SIGNATURE-----
Version: Mailvelope v0.13.2
Comment: https://www.mailvelope.com

wsFcBAEBCAAQBQJVz56LCRDmVDuy+mK58QAA7vAQAI7RcsVU2YjGWNainio9
cP+KMI835vY2g2xJyQRRzIPDzBSDWhanNhSsfWKvSyY8u5Khtlguwq5VtX+h
t++yFiaPbUeeTgXiFIUOXkvNypOmuVHGZCru4Xi9+OxHulo55OOHVAs5Uy6Q
6ibQa6XD7sbu36jhNTsiOU4SbouJXy5D6tbcVZ4D/CQ7nBpCYllhsiNZjYO0
P/Kg0QCjiFuNjhohXq5ap3NPhozAikiirPs5mSTcKpsTL6I/b6k3XSuI+zbF
oTFjc8H5qqfw5cZ1rRvinyOM42c7l28ObdjHWFJruh8RkNiZCGKmjH00/DVR
TzpSQohzNY8TIgk566cH9Fg5MaMJXgAaIK6KS6MT+lUZx3eR5Dhj0/J4IUkF
CIdWMwociijZVKIvZY+B3b0kISEyWJ98Ym+ZIi7xQtJYKFO75/T2rBPbze7L
KUDSz0xcQAPtcWuzE+aG6cChaXF0YAdovn4hgeRmrEZ1g6x3LQHqH+cFyQCS
idXAKxBNHaEuuI9cyze0yHRw8vSyG7dHl7PWDiuDB3sQc2RhiLwGR0OgMNAl
PS32aosbUj7dZdZfgv7fvG9r/HuVxjk7RtoQs1I8kmpH6FB9yKfea3Nsi14J
IgjdkL/2tdz93RNMP5YkoW6VBZsmgwa+exQnaejV5DpRsOroi0rwsYFrOWDj
5lVR
=LGto
-----END PGP SIGNATURE-----

Re: ifb and LXC

[Bob Miller]

> root@betelgeuse:~# lsmod | grep ifb
> ifb                    12637  0
> root@betelgeuse:~# ip link set dev ifb0 up
> Cannot find device "ifb0"
>
>
> I suspect that something similar is needed for ifb, but I can't seem
> to figure it out. Please let me know if you have any ideas.

Since you ask for ideas instead of answers ;)

On my system modprobe ifb has a configuration parameter setting number 
of interfaces, maybe this is playing into the equation on your system?

ip link show should reveal existing ifb interfaces, so maybe you can use 
that to find what is wrong with ifb0?

fwiw, find /dev/ -name *ifb* returns nothing on my system, however I do 
have /proc/sys/net/ipv4/conf/ifb0


>
> - ----------------
> Robert LeBlanc
> PGP Fingerprint 79A2 9CA4 6CC4 45DD A904  C70E E654 3BB2 FA62 B9F1
> -----BEGIN PGP SIGNATURE-----
> Version: Mailvelope v0.13.2
> Comment: https://www.mailvelope.com
>
> wsFcBAEBCAAQBQJVz56LCRDmVDuy+mK58QAA7vAQAI7RcsVU2YjGWNainio9
> cP+KMI835vY2g2xJyQRRzIPDzBSDWhanNhSsfWKvSyY8u5Khtlguwq5VtX+h
> t++yFiaPbUeeTgXiFIUOXkvNypOmuVHGZCru4Xi9+OxHulo55OOHVAs5Uy6Q
> 6ibQa6XD7sbu36jhNTsiOU4SbouJXy5D6tbcVZ4D/CQ7nBpCYllhsiNZjYO0
> P/Kg0QCjiFuNjhohXq5ap3NPhozAikiirPs5mSTcKpsTL6I/b6k3XSuI+zbF
> oTFjc8H5qqfw5cZ1rRvinyOM42c7l28ObdjHWFJruh8RkNiZCGKmjH00/DVR
> TzpSQohzNY8TIgk566cH9Fg5MaMJXgAaIK6KS6MT+lUZx3eR5Dhj0/J4IUkF
> CIdWMwociijZVKIvZY+B3b0kISEyWJ98Ym+ZIi7xQtJYKFO75/T2rBPbze7L
> KUDSz0xcQAPtcWuzE+aG6cChaXF0YAdovn4hgeRmrEZ1g6x3LQHqH+cFyQCS
> idXAKxBNHaEuuI9cyze0yHRw8vSyG7dHl7PWDiuDB3sQc2RhiLwGR0OgMNAl
> PS32aosbUj7dZdZfgv7fvG9r/HuVxjk7RtoQs1I8kmpH6FB9yKfea3Nsi14J
> IgjdkL/2tdz93RNMP5YkoW6VBZsmgwa+exQnaejV5DpRsOroi0rwsYFrOWDj
> 5lVR
> =LGto
> -----END PGP SIGNATURE-----
> --
> To unsubscribe from this list: send the line "unsubscribe lartc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: ifb and LXC

[Robert LeBlanc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Bob, thanks for the ideas, they were good ones.

ip link show in the container does not show any ifb devices, but the
host shows two. I'm not using the ones on the host, I only loaded the
module so that the container could have access to it.

/proc/sys/net/ipv4/conf/ifb0 is also missing in the container.

Looks like the container just isn't getting the memo about ifb being
available. Hopefully there are some more ideas out there.

Robert
-----BEGIN PGP SIGNATURE-----
Version: Mailvelope v0.13.2
Comment: https://www.mailvelope.com

wsFcBAEBCAAQBQJV0J/fCRDmVDuy+mK58QAAzpsP/05lf/M/TFYV0vkcJIid
q1Nbxt6tLF/YcXtvAR2LikDxTJ0GksdMDlFvpHMlgjVlCk+x4bG01Cmyvf2e
a7Hn+8kbd7/eKhJMQGJ/USO1OKRpFVJPIwE1ZRr2VPVaGZprUIrlpC+/5Clt
wgnlUkRnwZkWDljY7kSglRLXJ5PcY6I6foOge1fY43tNNU+qILGKcLT7mSYA
3xrhkxCwPJRt+NcLROjsShszorI1LM+0sFRBZyErHsZS1RTncLHqmSU2nFOw
M+bfxaBYziFi/FyV4HVLrll9bR7gLX+sVtlthr6smSY/cRSBhvHAJwxSLgbQ
o8F9OJUWkRJMAbS7vyv5NIyiWVflZY290rhyj/qnwH01kZORy+7MUnLTOL8u
LeCGcqvcVZdTZVmoWcB+qzPqA1QOWxMDvIUfo+f7fQOKZC6vvwOawEhHrlw9
LrV8FtyNMA0gekRX9qSyJOq1AdmfoilPcvqJ4B0CelCzDM3qi/X6QqbMIuaB
HnS45z+f0RQmUH83zHWxxiA/ypJAmo84GHLlY+I81YnOcuXlp4cP+0yaV1S2
yO4VUIutcZfUHpy/zhxVjg33dFQlbjdxy5cKzGGDBHW5ZtcYhPEk229jp778
D62khg32Rd0f9W1J6O0oVcTr4qQKxxvDPreTqoY5IWb2DTu8m5a67/Bfgr/c
dIf3
=cHK4
-----END PGP SIGNATURE-----

On Sat, Aug 15, 2015 at 5:44 PM, Bob Miller <bob@computerisms.ca> wrote:
>> root@betelgeuse:~# lsmod | grep ifb
>> ifb                    12637  0
>> root@betelgeuse:~# ip link set dev ifb0 up
>> Cannot find device "ifb0"
>>
>>
>> I suspect that something similar is needed for ifb, but I can't seem
>> to figure it out. Please let me know if you have any ideas.
>
>
> Since you ask for ideas instead of answers ;)
>
> On my system modprobe ifb has a configuration parameter setting number of
> interfaces, maybe this is playing into the equation on your system?
>
> ip link show should reveal existing ifb interfaces, so maybe you can use
> that to find what is wrong with ifb0?
>
> fwiw, find /dev/ -name *ifb* returns nothing on my system, however I do have
> /proc/sys/net/ipv4/conf/ifb0
>
>
>>
>> - ----------------
>> Robert LeBlanc
>> PGP Fingerprint 79A2 9CA4 6CC4 45DD A904  C70E E654 3BB2 FA62 B9F1
>> -----BEGIN PGP SIGNATURE-----
>> Version: Mailvelope v0.13.2
>> Comment: https://www.mailvelope.com
>>
>> wsFcBAEBCAAQBQJVz56LCRDmVDuy+mK58QAA7vAQAI7RcsVU2YjGWNainio9
>> cP+KMI835vY2g2xJyQRRzIPDzBSDWhanNhSsfWKvSyY8u5Khtlguwq5VtX+h
>> t++yFiaPbUeeTgXiFIUOXkvNypOmuVHGZCru4Xi9+OxHulo55OOHVAs5Uy6Q
>> 6ibQa6XD7sbu36jhNTsiOU4SbouJXy5D6tbcVZ4D/CQ7nBpCYllhsiNZjYO0
>> P/Kg0QCjiFuNjhohXq5ap3NPhozAikiirPs5mSTcKpsTL6I/b6k3XSuI+zbF
>> oTFjc8H5qqfw5cZ1rRvinyOM42c7l28ObdjHWFJruh8RkNiZCGKmjH00/DVR
>> TzpSQohzNY8TIgk566cH9Fg5MaMJXgAaIK6KS6MT+lUZx3eR5Dhj0/J4IUkF
>> CIdWMwociijZVKIvZY+B3b0kISEyWJ98Ym+ZIi7xQtJYKFO75/T2rBPbze7L
>> KUDSz0xcQAPtcWuzE+aG6cChaXF0YAdovn4hgeRmrEZ1g6x3LQHqH+cFyQCS
>> idXAKxBNHaEuuI9cyze0yHRw8vSyG7dHl7PWDiuDB3sQc2RhiLwGR0OgMNAl
>> PS32aosbUj7dZdZfgv7fvG9r/HuVxjk7RtoQs1I8kmpH6FB9yKfea3Nsi14J
>> IgjdkL/2tdz93RNMP5YkoW6VBZsmgwa+exQnaejV5DpRsOroi0rwsYFrOWDj
>> 5lVR
>> =LGto
>> -----END PGP SIGNATURE-----
>> --
>> To unsubscribe from this list: send the line "unsubscribe lartc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe lartc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html