similar to: Broken filters?

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

hello, i''m a newbie to this field and a new member to this group.i hv gone through few tc howto and and succesfully controlled the bandwidth of a small network setup. i have a query that is it possible to display the same.i.e. the number of packets uploaded or the number of packets dropped or limited due to BW control,etc. using tc commands.if so then what are those? or is it that i

please, help, i have build vpn server (suse 9 + poptop), i have managed to implement tc htb in ip-up script, but every client has own ppp interface (ppp0, ppp1, ppp2...), and my idea is to share available bandwidth, not to limit connection, how to build root tc rule, when I have more then one interface?... please any one width experiance regards _______________________________________________

Hello I''m doing some qdisc programming and I want to get/read the current ingress rate from a kernel module I was wondering what is the most convenient of achieving this My idea is to load the ingress qdisc and the police filter if necessary. and modify the source to export a structure or function so I can read the ingress rate. How does this sound? Is there a simpler way? With

???? ?????? wrote: > "--best" preset is designed for highest compression, not for faster > compression, isn't it? > IMHO it just means "highest reasonable", not "highest theoretically possible". And please answer to the mailing list, not to me ditectly.

Hi, I'm running the latest version of Samba with a tdbsam backend, configured not to use roaming profiles. Two different XP clients (SP2) are joined to the domain ok but users can only logon by rebooting before entering their logon details. When users logoff and try to logon again (or logon as a different user on the same machine) they get the standard message 'windows cannot connect to

Hi, ==================== Reproducible example: ==================== data(Animals, package="MASS") # interesting dataset # Run model lm1 <- lm(log10(body)~log10(brain), data=Animals) # Setup 2x2 graphics device par(mfrow=c(2,2)) # Plot diagnostics, label the two most "extreme" points based on magnitude of residuals plot(lm1, id.n=2) ==============================