* [LARTC] RTNETLINK answers: Invalid argument
@ 2001-06-19 10:38 Michal Kolesar
2001-06-21 7:48 ` Michal Kolesar
` (15 more replies)
0 siblings, 16 replies; 17+ messages in thread
From: Michal Kolesar @ 2001-06-19 10:38 UTC (permalink / raw)
To: lartc
[-- Attachment #1.1: Type: text/plain, Size: 1299 bytes --]
Hi all,
I have installed 2.4.5 kernel, Debian Potato.
my tc script:
#!/bin/bash
tc qdisc add dev eth1 root handle 20: cbq bandwidth 10Mbit avpkt 1000
echo root
tc class add dev eth1 parent 20:0 classid 20:1 cbq bandwidth 10Mbit rate \
10Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000
echo class
tc class add dev eth1 parent 20:1 classid 20:100 cbq bandwidth 10Mbit rate \
5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \
bounded
echo 100
tc class add dev eth1 parent 20:1 classid 20:200 cbq bandwidth 10Mbit rate \
5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \
bounded
echo 200
tc qdisc add dev eth1 parent 20:100 sfq quantum 1514b perturb 15
echo sfq100
tc qdisc add dev eth1 parent 20:200 sfq quantum 1514b perturb 15
echo sfq200
tc filter add dev eth1 parent 20:0 prio 25 u32 match ip src 192.168.0.7 flowid 20:100
echo filter100
tc filter add dev eth1 parent 20:0 prio 50 u32 match ip src 192.168.0.0/24 flowid 20:100
echo filter200
after running my tc script:
0 root@gateway:/root# source /etc/init.d/tc
root
class
100
200
sfq100
sfq200
RTNETLINK answers: Invalid argument
filter100
RTNETLINK answers: Invalid argument
filter200
my kernel .config file is attached.
Thank you for help!
kolisko
[-- Attachment #1.2: Type: text/html, Size: 2101 bytes --]
[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 14201 bytes --]
#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_TOSHIBA is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
# CONFIG_SMP is not set
# CONFIG_X86_UP_IOAPIC is not set
#
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
# CONFIG_PM is not set
# CONFIG_ACPI is not set
# CONFIG_APM is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID5=m
CONFIG_BLK_DEV_LVM=m
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_DEBUG=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK=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_ROUTE_LARGE_TABLES=y
# CONFIG_IP_PNP 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 is not set
CONFIG_SYN_COOKIES=y
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=y
CONFIG_IP_NF_FTP=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_LIMIT=y
CONFIG_IP_NF_MATCH_MAC=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_MULTIPORT=y
CONFIG_IP_NF_MATCH_TOS=y
CONFIG_IP_NF_MATCH_TCPMSS=y
CONFIG_IP_NF_MATCH_STATE=y
# CONFIG_IP_NF_MATCH_UNCLEAN is not set
# CONFIG_IP_NF_MATCH_OWNER is not set
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
# CONFIG_IP_NF_TARGET_MIRROR is not set
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_REDIRECT=y
CONFIG_IP_NF_NAT_FTP=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_MARK=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_TCPMSS=y
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_CSZ=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_DSMARK=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
CONFIG_NET_CLS_POLICE=y
#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set
#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_IDEDMA_PCI is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_IDEDMA_PCI_AUTO is not set
# CONFIG_BLK_DEV_IDEDMA is not set
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD7409 is not set
# CONFIG_AMD7409_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_PIIX_TUNING is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_BLK_DEV_OSB4 is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
#
# SCSI support
#
# CONFIG_SCSI is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set
#
# Network device support
#
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
# CONFIG_3C515 is not set
# CONFIG_ELMC is not set
# CONFIG_ELMC_II is not set
CONFIG_VORTEX=y
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_SK98LIN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
CONFIG_SHAPER=m
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Input core support
#
# CONFIG_INPUT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
# CONFIG_SERIAL_CONSOLE is not set
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# I2C support
#
# CONFIG_I2C is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set
#
# Joysticks
#
# CONFIG_JOYSTICK is not set
# CONFIG_QIC02_TAPE is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_I810=y
CONFIG_AGP_VIA=y
CONFIG_AGP_AMD=y
CONFIG_AGP_SIS=y
CONFIG_AGP_ALI=y
CONFIG_DRM=y
CONFIG_DRM_TDFX=y
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_MGA is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
CONFIG_REISERFS_FS=m
CONFIG_REISERFS_CHECK=y
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=m
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
# CONFIG_RAMFS is not set
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
CONFIG_NTFS_FS=m
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_SYSV_FS_WRITE is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set
#
# Network File Systems
#
# CONFIG_CODA_FS is not set
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
CONFIG_NLS_CODEPAGE_852=m
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
CONFIG_NLS_ISO8859_2=m
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VIDEO_SELECT is not set
# CONFIG_MDA_CONSOLE is not set
#
# Frame-buffer support
#
# CONFIG_FB is not set
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
#
# Kernel hacking
#
# CONFIG_MAGIC_SYSRQ is not set
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar @ 2001-06-21 7:48 ` Michal Kolesar 2001-06-21 13:43 ` Wingtung.Leung ` (14 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Michal Kolesar @ 2001-06-21 7:48 UTC (permalink / raw) To: lartc [-- Attachment #1: Type: text/plain, Size: 1936 bytes --] Hello, is here somebody who can help me? Where is the best place (mailinglist) for tc troubleshoting? Or if You need some another information tell me please. iptables-1.2.2 - from original sources ip utility, iproute2-ss991023 - from debian potato distribution I am newbie I dont have experiences with tc. What is wrong? Thank You! kolisko ----- Original Message ----- From: Michal Kolesar To: lartc@mailman.ds9a.nl Sent: Tuesday, June 19, 2001 12:38 PM Subject: [LARTC] RTNETLINK answers: Invalid argument Hi all, I have installed 2.4.5 kernel, Debian Potato. my tc script: #!/bin/bash tc qdisc add dev eth1 root handle 20: cbq bandwidth 10Mbit avpkt 1000 echo root tc class add dev eth1 parent 20:0 classid 20:1 cbq bandwidth 10Mbit rate \ 10Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000 echo class tc class add dev eth1 parent 20:1 classid 20:100 cbq bandwidth 10Mbit rate \ 5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \ bounded echo 100 tc class add dev eth1 parent 20:1 classid 20:200 cbq bandwidth 10Mbit rate \ 5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \ bounded echo 200 tc qdisc add dev eth1 parent 20:100 sfq quantum 1514b perturb 15 echo sfq100 tc qdisc add dev eth1 parent 20:200 sfq quantum 1514b perturb 15 echo sfq200 tc filter add dev eth1 parent 20:0 prio 25 u32 match ip src 192.168.0.7 flowid 20:100 echo filter100 tc filter add dev eth1 parent 20:0 prio 50 u32 match ip src 192.168.0.0/24 flowid 20:100 echo filter200 after running my tc script: 0 root@gateway:/root# source /etc/init.d/tc root class 100 200 sfq100 sfq200 RTNETLINK answers: Invalid argument filter100 RTNETLINK answers: Invalid argument filter200 my kernel .config file is attached. Thank you for help! kolisko [-- Attachment #2: Type: text/html, Size: 3776 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar 2001-06-21 7:48 ` Michal Kolesar @ 2001-06-21 13:43 ` Wingtung.Leung 2001-06-21 13:44 ` Stef Coene ` (13 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Wingtung.Leung @ 2001-06-21 13:43 UTC (permalink / raw) To: lartc On Tue, 19 Jun 2001, Michal Kolesar wrote: > my kernel .config file is attached. I don't see any problems in your script at first sight. Are you sure you enabled the u32 filter in the kernel? I wasn't able to view it because your mail agent defined the mime type as octetstream/application. Could you please fix that and check the QoS settings. They should like like: # # QoS and/or fair queueing # CONFIG_NET_SCHED=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NET_SCH_CBQ=y CONFIG_NET_SCH_CSZ=y CONFIG_NET_SCH_PRIO=y CONFIG_NET_SCH_RED=y CONFIG_NET_SCH_SFQ=y CONFIG_NET_SCH_TEQL=y CONFIG_NET_SCH_TBF=y CONFIG_NET_SCH_GRED=y CONFIG_NET_SCH_DSMARK=y CONFIG_NET_SCH_INGRESS=y CONFIG_NET_QOS=y CONFIG_NET_ESTIMATOR=y CONFIG_NET_CLS=y CONFIG_NET_CLS_TCINDEX=y CONFIG_NET_CLS_ROUTE4=y CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=y CONFIG_NET_CLS_U32=y CONFIG_NET_CLS_RSVP=y CONFIG_NET_CLS_RSVP6=y CONFIG_NET_CLS_POLICE=y Regards. -- GnuPG public key: http://www.keyserver.net fingerprint = A3C4 DE50 712D 4FA8 C564 4D96 5E06 C9CC ECFA 19C5 _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar 2001-06-21 7:48 ` Michal Kolesar 2001-06-21 13:43 ` Wingtung.Leung @ 2001-06-21 13:44 ` Stef Coene 2001-06-21 13:44 ` Stef Coene ` (12 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Stef Coene @ 2001-06-21 13:44 UTC (permalink / raw) To: lartc > Michal Kolesar wrote: > > Hi all, > > I have installed 2.4.5 kernel, Debian Potato. > > my tc script: > #!/bin/bash > > tc qdisc add dev eth1 root handle 20: cbq bandwidth 10Mbit avpkt 1000 > echo root > tc class add dev eth1 parent 20:0 classid 20:1 cbq bandwidth 10Mbit > rate \ > 10Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000 > echo class > tc class add dev eth1 parent 20:1 classid 20:100 cbq bandwidth 10Mbit > rate \ > 5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \ > bounded > echo 100 > tc class add dev eth1 parent 20:1 classid 20:200 cbq bandwidth 10Mbit > rate \ > 5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \ > bounded > echo 200 > tc qdisc add dev eth1 parent 20:100 sfq quantum 1514b perturb 15 > echo sfq100 > tc qdisc add dev eth1 parent 20:200 sfq quantum 1514b perturb 15 > echo sfq200 > tc filter add dev eth1 parent 20:0 prio 25 u32 match ip src > 192.168.0.7 flowid 20:100 > echo filter100 > tc filter add dev eth1 parent 20:0 prio 50 u32 match ip src > 192.168.0.0/24 flowid 20:100 > echo filter200 > > > after running my tc script: > 0 root@gateway:/root# source /etc/init.d/tc > root > class > 100 > 200 > sfq100 > sfq200 > RTNETLINK answers: Invalid argument > filter100 > RTNETLINK answers: Invalid argument > filter200 Do you use modules? No: make sure you enabled everything, Yes: make sure te modules are loaded. Stef -- stafke@iname.com stef.coene@belgacom.net More QOS info : http://users.belgacom.net/staf/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (2 preceding siblings ...) 2001-06-21 13:44 ` Stef Coene @ 2001-06-21 13:44 ` Stef Coene 2002-03-05 21:38 ` David E. Parks ` (11 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Stef Coene @ 2001-06-21 13:44 UTC (permalink / raw) To: lartc > Michal Kolesar wrote: > > Hi all, > > I have installed 2.4.5 kernel, Debian Potato. > > my tc script: > #!/bin/bash > > tc qdisc add dev eth1 root handle 20: cbq bandwidth 10Mbit avpkt 1000 > echo root > tc class add dev eth1 parent 20:0 classid 20:1 cbq bandwidth 10Mbit > rate \ > 10Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000 > echo class > tc class add dev eth1 parent 20:1 classid 20:100 cbq bandwidth 10Mbit > rate \ > 5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \ > bounded > echo 100 > tc class add dev eth1 parent 20:1 classid 20:200 cbq bandwidth 10Mbit > rate \ > 5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \ > bounded > echo 200 > tc qdisc add dev eth1 parent 20:100 sfq quantum 1514b perturb 15 > echo sfq100 > tc qdisc add dev eth1 parent 20:200 sfq quantum 1514b perturb 15 > echo sfq200 > tc filter add dev eth1 parent 20:0 prio 25 u32 match ip src > 192.168.0.7 flowid 20:100 > echo filter100 > tc filter add dev eth1 parent 20:0 prio 50 u32 match ip src > 192.168.0.0/24 flowid 20:100 > echo filter200 > > > after running my tc script: > 0 root@gateway:/root# source /etc/init.d/tc > root > class > 100 > 200 > sfq100 > sfq200 > RTNETLINK answers: Invalid argument > filter100 > RTNETLINK answers: Invalid argument > filter200 Do you use modules? No: make sure you enabled everything, Yes: make sure te modules are loaded. Stef -- stafke@iname.com stef.coene@belgacom.net More QOS info : http://users.belgacom.net/staf/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (3 preceding siblings ...) 2001-06-21 13:44 ` Stef Coene @ 2002-03-05 21:38 ` David E. Parks 2002-03-05 21:53 ` bert hubert ` (10 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: David E. Parks @ 2002-03-05 21:38 UTC (permalink / raw) To: lartc i'm fairly new to the list and just encountered this problem.. i have 2 machines, one w/ kernel 2.4.2-2 and the other w/ 2.4.12. the kernel config files are the same on both machines w/ all the same stuff compiled in. however, the 2.4.12 machine can't run tc, ip, etc (get RTNETLINK answers: Invalid argument) and the 2.4.2-2 machine has no problems. does anyone know why or how to fix. i really don't want to downgrade my kernel if i don't have to. thanks, david parks -------------------------------------------------------- when good things happen to bad people... -------------------------------------------------------- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (4 preceding siblings ...) 2002-03-05 21:38 ` David E. Parks @ 2002-03-05 21:53 ` bert hubert 2002-03-06 0:52 ` Richardson, Robert ` (9 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: bert hubert @ 2002-03-05 21:53 UTC (permalink / raw) To: lartc On Tue, Mar 05, 2002 at 04:38:32PM -0500, David E. Parks wrote: > i'm fairly new to the list and just encountered this problem.. > > i have 2 machines, one w/ kernel 2.4.2-2 and the other w/ 2.4.12. the > kernel config files are the same on both machines w/ all the same stuff > compiled in. however, the 2.4.12 machine can't run tc, ip, etc (get > RTNETLINK answers: Invalid argument) and the 2.4.2-2 machine has no > problems. Are you really sure they are the same? Did you run 'make oldconfig' on 2.4.12? Do your modules work? Regards, bert -- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk http://lartc.org Linux Advanced Routing & Traffic Control HOWTO _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (5 preceding siblings ...) 2002-03-05 21:53 ` bert hubert @ 2002-03-06 0:52 ` Richardson, Robert 2002-04-22 7:58 ` Alberto.Baragatti ` (8 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Richardson, Robert @ 2002-03-06 0:52 UTC (permalink / raw) To: lartc [-- Attachment #1: Type: text/plain, Size: 2719 bytes --] I get the same error message also, but for a non-related reason, maybe. I am trying to run RX/TX load balancing on a RedHat a 6.2 download server. The version of iproute is iproute-2.2.4-2. When I invoke the command "ip rule list", I get the error message: RTNETLINK answers: Invalid argument Dump terminated My ifconfig output shows that everything is being processed by eth0. I even downloaded iproute2-current.tar.gz and ran a make, it did not seem to upgrade the /sbin/ip file. OR, I did not configure it correctly. My /etc/rc.d/rc.local file reads: ip rule add from xxx.xx.xxx.xxx table 30 ip rule add from xxx.xx.xxx.xxx table 31 ip rule add from xxx.xx.xxx.xxx table 32 ip route add xxx.xx.xxx.x/28 dev eth0 table 30 ip route add xxx.xx.xxx.x/28 dev eth1 table 31 ip route add xxx.xx.xxx.x/28 dev eth2 table 32 ip route add xxx.xx.xxx.x/28 equalize nexthop dev eth0 nexthop dev eth1 nexthop dev eth2 ip route add default via xxx.xx.xxx.x dev eth0 table 30 ip route add default via xxx.xx.xxx.x dev eth1 table 31 ip route add default via xxx.xx.xxx.x dev eth2 table 32 ip route add default equalize nexthop via xxx.xx.xxx.x dev eth0 nexthop via xxx.xx.xxx.x dev eth1 nexthop via xxx.xx.xxx.x dev eth2 My /etc/sysconfig/network file has the following: NETWORKING=yes HOSTNAME=server.domainname.com DOMAINNAME=activision.com GATEWAY=xxx.xx.xxx.xxx GATEWAYDEV=eth0 CONFIG_IP_ROUTE_MULTIPATH=yes CONFIG_IP_MULTIPLE_TABLES=yes CONFIG_IP_ADVANCED_ROUTER=yes Can the load balancing I am attempting work on RedHat Linux 6.2? Thanks, Robert. +++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: bert hubert [mailto:ahu@ds9a.nl] Sent: Tuesday, March 05, 2002 1:53 PM To: David E. Parks Cc: lartc@mailman.ds9a.nl Subject: Re: [LARTC] RTNETLINK answers: Invalid argument On Tue, Mar 05, 2002 at 04:38:32PM -0500, David E. Parks wrote: > i'm fairly new to the list and just encountered this problem.. > > i have 2 machines, one w/ kernel 2.4.2-2 and the other w/ 2.4.12. the > kernel config files are the same on both machines w/ all the same stuff > compiled in. however, the 2.4.12 machine can't run tc, ip, etc (get > RTNETLINK answers: Invalid argument) and the 2.4.2-2 machine has no > problems. Are you really sure they are the same? Did you run 'make oldconfig' on 2.4.12? Do your modules work? Regards, bert -- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk http://lartc.org Linux Advanced Routing & Traffic Control HOWTO _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ [-- Attachment #2: Type: text/html, Size: 5223 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (6 preceding siblings ...) 2002-03-06 0:52 ` Richardson, Robert @ 2002-04-22 7:58 ` Alberto.Baragatti 2002-04-29 4:08 ` hanhbnetfilter ` (7 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Alberto.Baragatti @ 2002-04-22 7:58 UTC (permalink / raw) To: lartc Hi All, concerning the problem when running the "ip ru ls" command. I faced with the same problem, and I solved it by making sure to include the following settings into the kernel configuration (2.4.18): 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_ROUTE_LARGE_TABLES=y The new kernel is then able to perform policy routing in the correct way (iproute2-010824) ciao - Alberto -----Original Message----- From: ext Richardson, Robert [mailto:RRichardson@activision.com] Sent: Mittwoch, 6. März 2002 1:53 To: 'bert hubert'; David E. Parks Cc: lartc@mailman.ds9a.nl Subject: RE: [LARTC] RTNETLINK answers: Invalid argument I get the same error message also, but for a non-related reason, maybe. I am trying to run RX/TX load balancing on a RedHat a 6.2 download server. The version of iproute is iproute-2.2.4-2. When I invoke the command "ip rule list", I get the error message: RTNETLINK answers: Invalid argument Dump terminated My ifconfig output shows that everything is being processed by eth0. I even downloaded iproute2-current.tar.gz and ran a make, it did not seem to upgrade the /sbin/ip file. OR, I did not configure it correctly. My /etc/rc.d/rc.local file reads: ip rule add from xxx.xx.xxx.xxx table 30 ip rule add from xxx.xx.xxx.xxx table 31 ip rule add from xxx.xx.xxx.xxx table 32 ip route add xxx.xx.xxx.x/28 dev eth0 table 30 ip route add xxx.xx.xxx.x/28 dev eth1 table 31 ip route add xxx.xx.xxx.x/28 dev eth2 table 32 ip route add xxx.xx.xxx.x/28 equalize nexthop dev eth0 nexthop dev eth1 nexthop dev eth2 ip route add default via xxx.xx.xxx.x dev eth0 table 30 ip route add default via xxx.xx.xxx.x dev eth1 table 31 ip route add default via xxx.xx.xxx.x dev eth2 table 32 ip route add default equalize nexthop via xxx.xx.xxx.x dev eth0 nexthop via xxx.xx.xxx.x dev eth1 nexthop via xxx.xx.xxx.x dev eth2 My /etc/sysconfig/network file has the following: NETWORKING=yes HOSTNAME=server.domainname.com DOMAINNAME=activision.com GATEWAY=xxx.xx.xxx.xxx GATEWAYDEV=eth0 CONFIG_IP_ROUTE_MULTIPATH=yes CONFIG_IP_MULTIPLE_TABLES=yes CONFIG_IP_ADVANCED_ROUTER=yes Can the load balancing I am attempting work on RedHat Linux 6.2? Thanks, Robert. +++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: bert hubert [ mailto:ahu@ds9a.nl] Sent: Tuesday, March 05, 2002 1:53 PM To: David E. Parks Cc: lartc@mailman.ds9a.nl Subject: Re: [LARTC] RTNETLINK answers: Invalid argument On Tue, Mar 05, 2002 at 04:38:32PM -0500, David E. Parks wrote: > i'm fairly new to the list and just encountered this problem.. > > i have 2 machines, one w/ kernel 2.4.2-2 and the other w/ 2.4.12. the > kernel config files are the same on both machines w/ all the same stuff > compiled in. however, the 2.4.12 machine can't run tc, ip, etc (get > RTNETLINK answers: Invalid argument) and the 2.4.2-2 machine has no > problems. Are you really sure they are the same? Did you run 'make oldconfig' on 2.4.12? Do your modules work? Regards, bert -- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk http://lartc.org Linux Advanced Routing & Traffic Control HOWTO _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (7 preceding siblings ...) 2002-04-22 7:58 ` Alberto.Baragatti @ 2002-04-29 4:08 ` hanhbnetfilter 2002-04-29 8:08 ` Stef Coene ` (6 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: hanhbnetfilter @ 2002-04-29 4:08 UTC (permalink / raw) To: lartc Dear sir(lady) I used iproute2-2.4.7-now-ss011019-donotuse.tar.gz and iputils-ss011202.tar.gz for linux kernel 2.4.18 iptables 1.2.6 CONFIG_NETLINK_DEV=y CONFIG_IP_NF_TARGET_NETLINK=y i can use any command option about "ip" but I can not use "tc" such as tc qdisc add dev eth0 parent 10:100 sfq quantum 1514b perturb 15 the error message is "RTNETLINK answers: Invalid argument" please tell me how can i do? _________________________________________________________ Do You Yahoo!? 摊开你的掌心 让我看看你 http://sweepstakes.yahoo.com/2002cnuser _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (8 preceding siblings ...) 2002-04-29 4:08 ` hanhbnetfilter @ 2002-04-29 8:08 ` Stef Coene 2003-06-20 7:06 ` [LARTC] RTNETLINK answers: invalid argument Trevor Warren ` (5 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Stef Coene @ 2002-04-29 8:08 UTC (permalink / raw) To: lartc On Monday 29 April 2002 06:08, hanhbnetfilter wrote: > Dear sir(lady) > I used iproute2-2.4.7-now-ss011019-donotuse.tar.gz > and iputils-ss011202.tar.gz for linux kernel 2.4.18 > iptables 1.2.6 > > CONFIG_NETLINK_DEV=y > > CONFIG_IP_NF_TARGET_NETLINK=y > i can use any command option about "ip" > but I can not use "tc" such as > tc qdisc add dev eth0 parent 10:100 sfq quantum 1514b > perturb 15 > the error message is "RTNETLINK answers: Invalid > argument" > please tell me how can i do? Do you have a kernel with QOS support enabled ? Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.openprojects.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [LARTC] RTNETLINK answers: invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (9 preceding siblings ...) 2002-04-29 8:08 ` Stef Coene @ 2003-06-20 7:06 ` Trevor Warren 2003-06-20 18:17 ` Ana Carolina Alonso ` (4 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Trevor Warren @ 2003-06-20 7:06 UTC (permalink / raw) To: lartc Hello Ana, There could me multiple reasons for the same. Try shortlisting the same from here for a start. * Is your kernel patched with htb support * Upgraded to 2.4.20> preferably 2.4.21 which has wonderful support for HTB inbuilt. * Does your version of tc support the same. * If not google for htb and get the tc binary from their homepage. Trevor On Fri, 2003-06-20 at 23:47, Ana Carolina Alonso wrote: > Hello, I had configure my router linux which has Suse 7.2, kernel 2.4.21. > I had installed the QoS support into the kernel. When I run the comand tc > to create a CBQ qdisc, this work very well, but when I run tc to create the > HTB qdisc I receive next message: > > RTNETLINK answers: Invalid argument > > when my comand is: > > tc qdisc add dev eth0 root handle 1:htb > > Thanks in advance! > > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ -- ( >- GNU/LINUX, It's all about CHOICE -< ) /~\ __ trevor@clovertechnologies.com __ /~\ | \) / Pre Sales Consultant - Red Hat \ (/ | |_|_ \ 9820349221(M) | 22881326(O) / _|_| \___________________________________/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* [LARTC] RTNETLINK answers: invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (10 preceding siblings ...) 2003-06-20 7:06 ` [LARTC] RTNETLINK answers: invalid argument Trevor Warren @ 2003-06-20 18:17 ` Ana Carolina Alonso 2003-06-20 18:56 ` Stef Coene ` (3 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Ana Carolina Alonso @ 2003-06-20 18:17 UTC (permalink / raw) To: lartc Hello, I had configure my router linux which has Suse 7.2, kernel 2.4.21. I had installed the QoS support into the kernel. When I run the comand tc to create a CBQ qdisc, this work very well, but when I run tc to create the HTB qdisc I receive next message: RTNETLINK answers: Invalid argument when my comand is: tc qdisc add dev eth0 root handle 1:htb Thanks in advance! _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [LARTC] RTNETLINK answers: invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (11 preceding siblings ...) 2003-06-20 18:17 ` Ana Carolina Alonso @ 2003-06-20 18:56 ` Stef Coene 2003-10-28 12:08 ` [LARTC] RTNETLINK answers: Invalid argument usign wondershaper Luciano Lima ` (2 subsequent siblings) 15 siblings, 0 replies; 17+ messages in thread From: Stef Coene @ 2003-06-20 18:56 UTC (permalink / raw) To: lartc On Friday 20 June 2003 20:17, Ana Carolina Alonso wrote: > Hello, I had configure my router linux which has Suse 7.2, kernel 2.4.21. > I had installed the QoS support into the kernel. When I run the comand tc > to create a CBQ qdisc, this work very well, but when I run tc to create the > HTB qdisc I receive next message: > > RTNETLINK answers: Invalid argument > > when my comand is: > > tc qdisc add dev eth0 root handle 1:htb You need a tc binary with support. You can download one from www.docum.org or form the htb homepage. Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* [LARTC] RTNETLINK answers: Invalid argument usign wondershaper 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (12 preceding siblings ...) 2003-06-20 18:56 ` Stef Coene @ 2003-10-28 12:08 ` Luciano Lima 2003-10-28 17:52 ` Stef Coene 2005-04-03 16:54 ` [LARTC] RTNETLINK answers: Invalid argument Nicolas Mailhot 15 siblings, 0 replies; 17+ messages in thread From: Luciano Lima @ 2003-10-28 12:08 UTC (permalink / raw) To: lartc Hi, I compiled the last iproute2 version: iproute2-2.4.7-now-ss020116 and tried to use wondershaper. It seams that I missed something so that I can not use htb. # tc qdisc add dev eth0 root handle 1: htb RTNETLINK answers: Invalid argument The kernel is compiled with all QoS modules and the module sch_htb is loaded. Do I need to load any other modules before running this tc command ? Thanks, Luciano Lima _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [LARTC] RTNETLINK answers: Invalid argument usign wondershaper 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (13 preceding siblings ...) 2003-10-28 12:08 ` [LARTC] RTNETLINK answers: Invalid argument usign wondershaper Luciano Lima @ 2003-10-28 17:52 ` Stef Coene 2005-04-03 16:54 ` [LARTC] RTNETLINK answers: Invalid argument Nicolas Mailhot 15 siblings, 0 replies; 17+ messages in thread From: Stef Coene @ 2003-10-28 17:52 UTC (permalink / raw) To: lartc On Tuesday 28 October 2003 13:08, Luciano Lima wrote: > Hi, > > I compiled the last iproute2 version: iproute2-2.4.7-now-ss020116 and > tried to use wondershaper. > > It seams that I missed something so that I can not use htb. > > # tc qdisc add dev eth0 root handle 1: htb > RTNETLINK answers: Invalid argument > > The kernel is compiled with all QoS modules and the module sch_htb is > loaded. Do I need to load any other modules before running this tc command > ? You need a tc binary with htb support. You can find the patch on the htb website or a precompiled tc binary on the website of htb or on www.docum.org. Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.openprojects.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ ^ permalink raw reply [flat|nested] 17+ messages in thread
* [LARTC] RTNETLINK answers: Invalid argument 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar ` (14 preceding siblings ...) 2003-10-28 17:52 ` Stef Coene @ 2005-04-03 16:54 ` Nicolas Mailhot 15 siblings, 0 replies; 17+ messages in thread From: Nicolas Mailhot @ 2005-04-03 16:54 UTC (permalink / raw) To: lartc [-- Attachment #1.1.1: Type: text/plain, Size: 784 bytes --] Hi, On this Fedora Core Devel (Raw Hide) system, if I boot on a distribution kernel (based on 2.6.12rc1-bk2) the network is fine. If I build a custom 2.6.12-rc1-V0.7.43-06 or 2.6.12-rc1-mm4 kernel the network interface fails to initialise on boot with RTNETLINK answers: Invalid argument. What can possibly cause this ? My kernel config should be mostly fine - I used it extensively at a time and diffing it with Red Hat does not show any obvious suspects (to me)). Thoug I haven't built any custom kernels for a few months, so possibly some Fedora or kernel bits changed. My iproute version should be fairly current : iproute-2.6.11-1 I've attached an strace of the problem command if it can help shed some light on this Regards, -- Nicolas Mailhot [-- Attachment #1.1.2: debug.txt --] [-- Type: text/plain, Size: 3805 bytes --] execve("/sbin/ip", ["/sbin/ip", "route", "replace", "169.254.0.0/16", "dev", "eth0"], [/* 36 vars */]) = 0 uname({sys="Linux", node="rousalka.dyndns.org", ...}) = 0 brk(0) = 0x8067000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=58029, ...}) = 0 old_mmap(NULL, 58029, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f58000 close(3) = 0 open("/lib/libresolv.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320Cm\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=76336, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f57000 old_mmap(0x6d2000, 75880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x6d2000 old_mmap(0x6e1000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe000) = 0x6e1000 old_mmap(0x6e3000, 6248, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x6e3000 close(3) = 0 open("/lib/tls/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\332>\277"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=1465764, ...}) = 0 old_mmap(0xbdf000, 1190876, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xbdf000 old_mmap(0xcfc000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x11d000) = 0xcfc000 old_mmap(0xd00000, 7132, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xd00000 close(3) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f56000 set_thread_area({entry_number:-1 -> 6, base_addr:0xb7f566c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 mprotect(0x6e1000, 4096, PROT_READ) = 0 mprotect(0xcfc000, 8192, PROT_READ) = 0 mprotect(0xbdb000, 4096, PROT_READ) = 0 munmap(0xb7f58000, 58029) = 0 socket(PF_NETLINK, SOCK_RAW, 0) = 3 setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0 setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) = 0 bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0 getsockname(3, {sa_family=AF_NETLINK, pid=5665, groups=00000000}, [12]) = 0 time(NULL) = 1112445811 sendto(3, "\24\0\0\0\22\0\1\3t\223NB\0\0\0\0\0\200\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20 recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\344\0\0\0\20\0\2\0t\223NB!\26\0\0\0Z\4\3\1\0\0\0\10\0"..., 16384}], msg_controllen=0, msg_flags=0}, 0) = 696 brk(0) = 0x8067000 brk(0x8088000) = 0x8088000 recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0t\223NB!\26\0\0\0\0\0\0\1\0\0\0\10\0\0"..., 16384}], msg_controllen=0, msg_flags=0}, 0) = 20 sendmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{",\0\0\0\30\0\5\5u\223NB\0\0\0\0\2\20\0\0\376\3\375\1\0"..., 44}], msg_controllen=0, msg_flags=0}, 0) = 44 recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"$\0\0\0\2\0\0\0u\223NB!\26\0\0\352\377\377\377,\0\0\0\30"..., 16384}], msg_controllen=0, msg_flags=0}, 0) = 36 dup(2) = 4 fcntl64(4, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE) close(4) = 0 write(2, "RTNETLINK answers: Invalid argum"..., 36RTNETLINK answers: Invalid argument ) = 36 exit_group(2) = ? [-- Attachment #1.2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 189 bytes --] [-- Attachment #2: Type: text/plain, Size: 143 bytes --] _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2005-04-03 16:54 UTC | newest] Thread overview: 17+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar 2001-06-21 7:48 ` Michal Kolesar 2001-06-21 13:43 ` Wingtung.Leung 2001-06-21 13:44 ` Stef Coene 2001-06-21 13:44 ` Stef Coene 2002-03-05 21:38 ` David E. Parks 2002-03-05 21:53 ` bert hubert 2002-03-06 0:52 ` Richardson, Robert 2002-04-22 7:58 ` Alberto.Baragatti 2002-04-29 4:08 ` hanhbnetfilter 2002-04-29 8:08 ` Stef Coene 2003-06-20 7:06 ` [LARTC] RTNETLINK answers: invalid argument Trevor Warren 2003-06-20 18:17 ` Ana Carolina Alonso 2003-06-20 18:56 ` Stef Coene 2003-10-28 12:08 ` [LARTC] RTNETLINK answers: Invalid argument usign wondershaper Luciano Lima 2003-10-28 17:52 ` Stef Coene 2005-04-03 16:54 ` [LARTC] RTNETLINK answers: Invalid argument Nicolas Mailhot
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox