Traffic Control Issues Inside Ubuntu Guest

Discussions about using Linux guests in VirtualBox.
Post Reply
ElPete
Posts: 2
Joined: 23. May 2014, 15:39

Traffic Control Issues Inside Ubuntu Guest

Post by ElPete »

I've installed a 64 bit Ubuntu Server. I am trying to set some traffic control inside the device but I am getting an error message. I am not sure if this is an issue with my CPU, my kernel or something else.

If I enter a command for a device that does not exist, I get an error message. If I try a command for a device that DOES exist, I get an error message or blank output. For example:

Existing Device:

tc class show dev eth0 ( No output )
sh tc class change dev eth0 parent 1:0 classid 1:1 htb rate 100Mbps burst 10k ( RTNETLINK answers: No such file or directory )

Device that does not exist:
tc class show dev eth100 ( Cannot find device eth100 )
sh tc class change dev eth100 parent 1:0 classid 1:1 htb rate 100Mbps burst 10k ( Cannot find device eth100 )

Any suggestions would be appreciated.

My CPU Information:
Intel Virtualization Technology: Yes
Inter Hyper Threading Technology: No
Intey 64 Architecture: Yes
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Traffic Control Issues Inside Ubuntu Guest

Post by socratis »

I don't believe that this is a VirtualBox issue, as searching for "RTNETLINK answers: No such file or directory" returns a lot of answers for people trying to do exactly what you're doing (traffic control). Maybe somewhere in there lies the answer?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
ElPete
Posts: 2
Joined: 23. May 2014, 15:39

Re: Traffic Control Issues Inside Ubuntu Guest

Post by ElPete »

You were right. It wasn't a VirtualBox error. I spend a lot of time on Google. The issue was the configuration of the interfaces. The qdisc was fifo and not htb so obviously setting the the htb rates wouldn't work.
Post Reply