Re: [LARTC] U32 Port Range

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 oops it's rather "sport 0 0xfc00" than "sport 0 0xfbff" if it worked the way I think it would. - -- Thilo Schulz My public PGP key is available at http://home.bawue.de/~arny/public_key.asc -BEGIN PGP SIGNATURE- V

Re: [LARTC] U32 Port Range

024, using "sport 0 0xfbff" *might* work, though I am not sure about that. Some core QoS developers on the kernel may give you more insight than I am able to do. But you can still try it, better than nothing :). - -- Thilo Schulz My public PGP key is available at http://home.b

Re: [LARTC] Trafic monitor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 17 June 2004 16:10, Thilo Schulz wrote: > Anyways, I'll be working on doing a small release package, for those who > are interested in this thing. Don't expect too much from it, I hardly sat a > week at this system. It

Re: [LARTC] Trafic monitor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 17 June 2004 13:51, Thilo Schulz wrote: > At the moment, I have my traffic accounter daemon, say: the one logging the > traffic, linked against electricfence, which should have very negative > effects on performance. I will run a

Re: [LARTC] Trafic monitor

ake this work using sudo. - -- Thilo Schulz My public PGP key is available at http://home.bawue.de/~arny/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA0YXEZx4hBtWQhl4RAnGJAJ4v+lc2XxZTwRDbAynGHXSzqYKTLQCgjiKM 34ytH/wFsTRQUXz5nGf4Qdg= =1l

Re: [LARTC] Trafic monitor

e version tomorrow, but I cannot guarantee for its bugfreeness. Though, most of the parts are done and they also seem to work the way I want them to. Plus, it won't destroy any already-present firewall setups. - -- Thilo Schulz My public PGP key is available at http://home.bawue.de/~arny/public_key

Re: [LARTC] beta-release of H-FSC port for Linux 2.6

ectly. This is > very important for streaming, VoIP, .. (and gamers of course). Exactly. I was able to shape the ping latency down from 2000 ms on large uploads to 60-150 ms using HTB, this is good for ssh - but not good enough for quake3. - -- - Thilo Schulz My public GnuPG key is

Re: [LARTC] Classifying IPv6 tunnel traffic

; What you can't do (to the > best of my knowledge) if going deeper into the packets, and see if IPv6 > pakects inside the IPv4 ones are of some kind or another. 2. I wasn't planning on doing that ;) - -- - Thilo Schulz My public GnuPG key is available at http://home.bawue.de/~a

[LARTC] Classifying IPv6 tunnel traffic

do any ipv6 shaping), So I wondered, whether someone here can give me the filter directive to match these tunnel packets. - -- - Thilo Schulz My public GnuPG key is available at http://home.bawue.de/~arny/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/U4D

Re: [LARTC] Low latency on large uploads - almost done but not quite.

gt; 2.4.21. I have a 133 Mhz AMD 486 - whether setting the resolution timer up would be very good for performance I don't know. - Thilo Schulz -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+8FviZx4hBtWQhl4RA

Re: [LARTC] CBQ-wondershaper superior over HTB-wondershaper?

ng the cbq version. I haven't run any large-scaled tests, but this is the experience I had in practice. - Thilo Schulz -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7ec7Zx4hBtWQhl4RAohkAJ4sKA6j0u8g5RdOh/IDtLeDWAoC+gCfdlIw lvirBt6tswiWrggv/vzxZHA= =SPWK

Re: [LARTC] Low latency on large uploads - almost done but not quite.

limit 0 > > tc qdisc add dev $DEV parent 1:11 handle 30: pfifo limit 0 > > Are you sure limit 0 is possible Yes, at least the status command showed me, that the limit was set to 0. - Thilo Schulz -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+

[LARTC] Low latency on large uploads - almost done but not quite.

fff flowid 1:12 # that's it for now ... - Thilo Schulz -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+60VLZx4hBtWQhl4RAgpkAKCZA9jGYSQoWojsKBbM6iX+FBMcPwCfb2ht mNdHOs2WynRmRsizhoCKoBY= =A4NF -END PGP SIGNATURE- ___ LAR

[LARTC] FYI: Article in C'T computer magazine

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

Re: [LARTC] owner based policy routing

h the very same problem. Owner based policy routing seems not to be possible. - Thilo Schulz ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Collect iproute2 traffic stat

program, just ask me for it. - Thilo Schulz ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] iproute and iptables

o set various things, such as ip addresses, routing entries or the traffic shaper. The iptables tool is responsible for the firewall and the rules in there - as well as some packet mangling and network address translation. You can combine both tools with the -j MARK directive .. rtfm

Re: [LARTC] Fwmark problem - policy routing does not work.

does not. The ip rule does that. Routing does not mangle packets, unless > the packet is locally generated and incomplete. it is generated locally in my case. - Thilo Schulz ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mail

Re: [LARTC] Fwmark problem - policy routing does not work.

ource and destination address do not match. I was going to try it though, and have already compiled a fully NAT able kernel (it was not able to previously, because i thought NAT is not necessary) Also i'm going to contact one of the Policy Routing developers. Thanks for your help. - Thilo S

Re: [LARTC] Fwmark problem - policy routing does not work.

> I can only help you with the marking stuff :( Well, any address i can contact to get further information about this? I'm pretty much at the end with my latin ... ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc

Re: [LARTC] Fwmark problem - policy routing does not work.

given user, as all other user it does work. If i give the via option in the "ip route add table thilo src ." command, the packets are reaching their destination again - yet even though i have given the source ip that should have been used, it is sti

[LARTC] Fwmark problem - policy routing does not work.

have enabled MARK based routing in the kernel (policy routing, everything switched on ..) So I only can ask you on this mailing list - anyone got an idea of what is/what i did wrong? - Thilo Schulz ___ LARTC mailing list / [EMAIL PROTECTED] http://mailm