On Sun, Jun 05, 2016 at 11:19:59PM +0200, Felix Eckhofer wrote:
> Hey.
>
> We are currently experimenting with TC_ENABLED=Simple and it seems that
> when we add more than 9 interfaces to tcinterfaces, shorewall fails to
> start.
> It does not matter in which order the interfaces are listed or if they
> are "external" or "internal" (only the first two fields are set), I
> always get (from "shorewall trace start"):
>
> + setup_br166_tc
Is it because tcclasses interface is in hexadecimal?
INTERFACE - interface[[:parent]:class]
Name of interface.
You may specify the interface number rather than the interface name.
If the classify option is given for the interface in
shorewall-tcdevices[1](5), then you must also specify an interface
class (an integer that must be unique within classes associated with
this interface). If the classify option is not given, you may still
specify a class or you may have Shorewall generate a class number from
the MARK value. Interface numbers and class numbers are always
assumed to be specified in hex and class number 1 is reserved as the root
class of the queuing discipline.
http://shorewall.net/traffic_shaping.htm
Warning
Device numbers are expressed in hexidecimal. So the device following 9 is A,
not 10.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
