Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    'pfctl: jme0_vlan10: driver does not support altq'

    2.1 Snapshot Feedback and Problems - RETIRED
    4
    7
    3410
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z
      zandr last edited by

      I'm trying to set up a traffic shaper. Strange install problems described here mean I'm running 2.1, but I don't think this is 2.1 specific.

      I'm running this on a Shuttle XS35v2 as a one-armed router, with a GS108T doing the vlan swtiching/tagging.

      Just following the wizard (single WAN, single LAN) and lowering the priority for p2p traffic leaves me with:

      The error I get is:

      php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'pfctl: jme0_vlan10: driver does not support altq'

      Is this because the combination of jme and vlan actually isn't supported, or am I doing something wrong?

      Or, is this a 2.1 bug after all? I've posted a couple of other issues in the 2.1 forum and haven't gotten any traction, so I thought I'd try out here.

      1 Reply Last reply Reply Quote 0
      • E
        eri-- last edited by

        That means jme does not support altq.

        1 Reply Last reply Reply Quote 0
        • C
          Cino last edited by

          ermal,

          Does this mean em doesn't supported altq either in 2.1? It is for supported in 2.0.1. http://forum.pfsense.org/index.php/topic,48074.msg253378.html#msg253378

          1 Reply Last reply Reply Quote 0
          • Z
            zandr last edited by

            ermal-
            I don't think that's the case, from the altq(4) man page:

            SUPPORTED DEVICES
                The driver modifications described in altq(9) are required to use a cer-
                tain network card with ALTQ.  They have been applied to the following
                hardware drivers: age(4), alc(4), ale(4), an(4), ath(4), aue(4), bce(4),
                bfe(4), bge(4), cas(4), dc(4), de(4), ed(4), em(4), ep(4), epair(4),
                fxp(4), gem(4), hme(4), ipw(4), iwi(4), jme(4), le(4), msk(4), mxge(4),
                my(4), nfe(4), nge(4), npe(4), nve(4), ral(4), re(4), rl(4), rum(4),
                sf(4), sge(4), sis(4), sk(4), ste(4), stge(4), txp(4), udav(4), ural(4),
                vge(4), vr(4), wi(4), and xl(4).

            So this is clearly something specific to vlans. If as Cino says it's broken for em, then this is must be a regression. I'd believe that not all the tricks are supported on cheap-and-nasty hardware like jme, but em? Really?

            1 Reply Last reply Reply Quote 0
            • E
              eri-- last edited by

              This is 2.1?

              1 Reply Last reply Reply Quote 0
              • Z
                zandr last edited by

                @ermal:

                This is 2.1?

                Yes, as I said in the initial post, this is 2.1.

                1 Reply Last reply Reply Quote 0
                • C
                  cmb last edited by

                  Ermal opened a ticket on this.
                  http://redmine.pfsense.org/issues/2349

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post