Project

General

Profile

Actions
Copy link

Bug #4345

open

Traffic Shaping doesn't work with Xen netfront driver

Added by Helio Candido almost 10 years ago. Updated almost 3 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Operating System
Target version:
-
Start date:
01/29/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.x
Affected Architecture:

Description

On the version 2.1.5 I got the traffic shaping work without problem but after upgraded to 2.2 it's just doesn't working anymore. I'm getting this message all the time: ...driver does not support altq...

Anything changed to make it right? It was fine on 2.1.5 but on 2.2 dont.

Actions
Copy link
 #1

Updated by Chris Buechler almost 10 years ago

which driver is it saying doesn't support altq?

Actions
Copy link
 #2

Updated by Helio Candido almost 10 years ago

I'm using 2 NIC's Realtek RTL8111/8168 PCI Express Gigabit Ethernet. Both are working on PFSense 2.1.5 with traffic shapping but on 2.2 doesn't.

PFSense in both scenaries is running under XenServer 6.2 SP1 (updated). I just start the configuration using traffic shapping wizard but on the final when I'll click to finish I got that message on 2.2.

Actions
Copy link
 #3

Updated by Chris Buechler almost 10 years ago

  • Status changed from New to Feedback

that should be something that changed to xn NICs after upgrade so they're no longer Realtek, is that the case?

Actions
Copy link
 #4

Updated by Helio Candido almost 10 years ago

Yes, that NIC's changed to xm but still working on 2.1.5 and not on 2.2.

Actions
Copy link
 #5

Updated by Chris Buechler over 9 years ago

  • Subject changed from Traffic Shaping doesn't working to Traffic Shaping doesn't work with Xen netfront driver
  • Category set to Operating System
  • Status changed from Feedback to Confirmed
  • Target version set to 2.2.2
  • Affected Version set to 2.2

updated subject to specific issue at hand here.

Actions
Copy link
 #6

Updated by Chris Buechler over 9 years ago

  • Target version changed from 2.2.2 to 2.2.3
Actions
Copy link
 #7

Updated by Grischa Zengel over 9 years ago

Please, can somebody build an unofficial release (2.2.1+) without netfront. I don't have time to create a build environment (sign LA, create SSH-key, ...).
If somebody has already a build environment it should be easy to build without netfront.

Actions
Copy link
 #8

Updated by Grischa Zengel over 9 years ago

Is there something to test or something else to do?
I'm still on 2.1.5 and want to update.

Actions
Copy link
 #9

Updated by Chris Buechler over 9 years ago

  • Target version changed from 2.2.3 to 2.3
Actions
Copy link
 #10

Updated by Grischa Zengel over 9 years ago

Will be there a real solution in next time or should I add an extra nic to these servers?

Actions
Copy link
 #11

Updated by Chris Buechler over 9 years ago

  • Affected Version changed from 2.2 to 2.2.x

Grischa Zengel wrote:

Will be there a real solution in next time or should I add an extra nic to these servers?

Unknown when it will be fixed. Not a priority to this point.

Actions
Copy link
 #12

Updated by Grischa Zengel over 9 years ago

I'm installing the next server and need 8+ networks. Because xen can't handle so much NICs I have to use tagging.

If you can't fix it, so please remove xn:
  1. build an extra image without xn.
  2. show me an loader option to disable xn.

I can't work with this. With an extra NIC I loose bandwidth.

There are a lot of posts about pfsense 2.2 and buggy xn implementation.

Actions
Copy link
 #13

Updated by Giancarlos Cataldo over 9 years ago

I think same as Grischa Zengel said!
We need an option to disable xn implementation

Actions
Copy link
 #14

Updated by Grischa Zengel over 9 years ago

2.2.4-RELEASE Now Available

When can we use this?
There are security fixes, which we must have.

Actions
Copy link
 #15

Updated by Andreas Pflug about 9 years ago

Just to step in, until VLAN and ALTQ is supported there really needs to be a way to disable xn.

Actions
Copy link
 #16

Updated by Grischa Zengel about 9 years ago

It's time for changes after 8 month:
https://redmine.pfsense.org/issues/4401#note-10

Actions
Copy link
 #18

Updated by Grischa Zengel about 9 years ago

If I read #3670 I will this twice. I'm still on 2.1.5 and ipv6 didn't work with my ISP.

Actions
Copy link
 #19

Updated by Chris Buechler almost 9 years ago

  • Target version deleted (2.3)

the ability to disable PV is there in 2.3 now (#5452) for those who want to retain the previous shaping ability.

Actions
Copy link
 #20

Updated by Kris Phillips almost 3 years ago

This should be retested. There is a lot of kernel changes and Xen improvements in the FreeBSD kernel in the last 6 years.

Actions
Copy link

Also available in: Atom PDF