[LARTC] tc/wondershaper and RTNETLINK answers: Invalid argument

2004-03-10 Thread Bernard McAuley
Hi,

I've been trying out the wondershaper script, but on several of the
examples I keep getting the error message:-

RTNETLINK answers: Invalid argument


On the following line:-

tc filter add dev eth0 parent : protocol ip prio 50 u32 match ip src
\
   0.0.0.0/0 police rate 512kbit burst 10k drop flowid :1

Based on other posts to this mail list, I gather it is an issue with
kernel modules. I've tried compiling my own version of tc (using the
path for HTB), but this hasn't helped.  I'm currently running with the
2.4.25 kernel, and I've set the following configs in the kernel build
which I believe are needed. 

#
# Automatically generated by make menuconfig: don't edit
#

# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_PNP=y
# CONFIG_IP_PNP_DHCP is not set
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_INET_ECN=y
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
# CONFIG_IP_NF_MATCH_UNCLEAN is not set
# CONFIG_IP_NF_MATCH_OWNER is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
# CONFIG_IP_NF_TARGET_MIRROR is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_NAT_AMANDA=m
# CONFIG_IP_NF_NAT_LOCAL is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_NET_CLS_RSVP=m
# CONFIG_NET_CLS_RSVP6 is not set
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set

# CONFIG_FEALNX is not set
CONFIG_NATSEMI=m
CONFIG_8139TOO=m

Can any one suggest what modules might be missing, or recommend a
technique to identifying the omitted modules,

Regards,

Bernard McAuley
[EMAIL PROTECTED]



___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


Re: [LARTC] bandwidth limiting incoming data

2003-06-26 Thread Bernard Robbins
Stef,

Can you point me to the location of the docs for the filters + policers?

Stef Coene wrote:
On Monday 23 June 2003 14:31, K S Sreeram wrote:

On Mon, 2003-06-23 at 05:47, Trevor Warren wrote:

Hello Sreram,

AFAIK all Traffic Shaping be it Ingress/Egress can be done at your end.
This will help majorly on the link at your end by prioritising trafic
appropriately.
You can't possibly change traffic priorities at your isps end.
Maybe my mail wasnt clear, but what i wanted to know is how to shape
incoming traffic on my box, and not at the ISP's end, which I cant
control.
Incoming traffic can be controlled with filters + policers.  Or a more 
complicated setup can be done with IMQ + HTB.

Stef

--

Bernard Robbins
Systems Support Specialist
VLM International, Inc.
___
[EMAIL PROTECTED] src]# make me --with-more_time --with-more_money
90% of being smart is knowing what you're dumb at.
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


[LARTC] T-1 bandwith

2003-04-03 Thread Bernard
I hope somebody can point me in the right direction. Ive seen a lot of 
documentation on how to get htb and cbq to work with different types of 
modems, but is there any documentation about t-1's? This is what my 
situation is: I have a 24 channel t-1 fractionalized down to 16 because 
of the 8 voice channels. That leaves me with a total 1024kb for up and 
downloads. I have 5 customers with full t-1's that will be downloading 
from me at the same time I am downloading something. Of course my users 
and I get 90% of the bandwidth and they get the other 10%. I would like 
the situation to be: limit myself and my users to 10% and give the 
customers the other 90% when they are downloading from me, evenly shared 
between whichever customers that are downloading at that time. Any help 
would be most appreciated.

Thanks,
Bernard
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/