AW: AW: [LARTC] Activate ingress policies on suse enterprise serv er 9

Title: AW: AW: [LARTC] Activate ingress policies on suse enterprise server 9   Good Morning, Thanks for your hint, now I can see the dropped packages! But it is only working for port 8080 why not for port 8099?? (If you need some indices please let me know) Thanks Gernot

[LARTC] tc filter - based on iptables - MAC - MARK not working - altough marking on ip src, dst address works

=== tc filter - based on iptables - MAC fw marking not working == DEV="eth1" tc qdisc add dev $DEV root handle 1: htb default 20 tc class add dev $DEV parent 1: classid 1:1 htb rate 600kbps ceil 3276800kbit tc class add dev $DEV parent 1:1 classid 1:15 htb rate 3kbps prio 4 tc class add dev $DEV

Re: [LARTC] Suspicious Attachment

Even if we keep this email in the mailing list i don't see any interest to forward "Suspicious attachment" notifications to everyone. Erwan Le Doeuff Project Manager of rcc project QoS HTB Power tool http://www.rcc-project.net

Re: [LARTC] Suspicious Attachment

removing this person could be a great idea! Erwan Le Doeuff Project Manager of rcc project QoS HTB Power tool http://www.rcc-project.net On 4/18/05, <> wrote: > --

[LARTC] Suspicious Attachment

-- Warning: Message delivery wasn't performed. Reason: Our virus scanner detected very suspicious code in the attachment of a mail addressed to a user of our system. The following message will not be delivered: From: [EMAIL PROT

[LARTC] Suspicious Attachment

-- Warning: Message delivery wasn't performed. Reason: Our virus scanner detected very suspicious code in the attachment of a mail addressed to a user of our system. The following message will not be delivered: From: [EMAIL PROT

[LARTC] SQLiaison E-Mail Virus Alert

SQLiaison Mail Server: GroupShield™ Alert The email server has discovered a problem with the following email. Please note that the sender of the email will not be notified with this message. > More information : Date/Time sent: 18 Apr 2005 16:38:49 Subject line: [LARTC] Re: From: [EMAIL PROT

[LARTC] Suspicious Attachment

-- Warning: Message delivery wasn't performed. Reason: Our virus scanner detected very suspicious code in the attachment of a mail addressed to a user of our system. The following message will not be delivered: From: [EMAIL PROT

Re: AW: [LARTC] Activate ingress policies on suse enterprise server 9

Grames Gernot wrote: Hi, Thanks for the fast response, .)Okay I tried your suggestion for my port 8099 and nothing happened: The tcp ip information goes from a firewall to my port 8099 and this port is than routed to the original 8080, I do that because I don`t want to dirturb my port 8080. But it

AW: [LARTC] Activate ingress policies on suse enterprise server 9

Title: AW: [LARTC] Activate ingress policies on suse enterprise server 9 Hi, Thanks for the fast response, .)Okay I tried your suggestion for my port 8099 and nothing happened: The tcp ip information goes from a firewall to my port 8099 and this port is than routed to the origi

Re: [LARTC] tbf latency problems!

Alaios wrote: thx for your answer... i use the 2.6.10 vanilla kernel.. i have downloaded two weeks ago the latest iproute2. I have installed tbf with the following command $tc qdisc add dev $DEV parent 2:1 tbf rate $EF_RATE burst $EF_BURST mtu $EF_MTU limit $EF_LIMIT and i have got the results usin

Re: [LARTC] QoS for lan users ...

Marcin Sura wrote: Hi I have Linux box (Debian) that acting as a bridge. Eth0 and Eth1 are bridged (br0). Br0 have public IP. Eth0 connects to the internet. Eth1 connect to servers in DMZ (with public IPs). Eth2 connects my Lan (192.168.1.0/24). My connections is 2Mbit/2Mbit. I'

Re: [LARTC] Activate ingress policies on suse enterprise server 9

Grames Gernot wrote: Hi, what is needed to activate ingress policies for enterprise server 9! tc qdisc add dev eth0 ingress tc filter add dev eth0 parent : protocol ip u32 match ip dport 8099 0x police rate 1kbit burst 1kbit mtu 1 drop flowid :1 I get a memory allocation error if I try t

[LARTC] Activate ingress policies on suse enterprise server 9

Hi,   what is needed to activate ingress policies for enterprise server 9!   My current loaded modules: in the attachments   my kernel: Linux linux 2.6.5-7.97-smp #1 SMP Fri Jul 2 14:21:59 UTC 2004 i686 i686 i386 GNU/Linux So you can see the module sch_ingress is loaded and

Re: [LARTC] HTB stalling

> Hi Hi! > > Couple months ago I started to have a strange problem with HTB. > My setup is Fedora Core 2 + Pentium 2 233 + 128 MB of ram and its > serving as a router. > For some time since going to kernel 2.6 my HTB QoS Stalls for couple > seconds, every couple minutes. If the connection load i

[LARTC] Re: HTB stalling

Me too. I've think the problem started after I use kernel 2.6.8.1. IfI good remember I doesn't have this problem with 2.6.7. The new thing in2.6.8.1 was the QoS clock source (or similar). I use here CPU cyclecounter because I have a fast uplink (1 Gbps). I think maybe this can bethe source of th

Re: [LARTC] Test ingress filter

Which tool (can be windows also) can i use to test the ingress filter (tcpip load generator or something else), and set the packet length size and so on! Try taking a look at the Packet Generator in the Linux kernel under "Network Testing" under "Networking Options" (...Networking Options, Network

[LARTC] Test ingress filter

 Hi,I have set a ingress filter to reduce the inbound traffic on one specificport and also i check the packages (buffer).No i want to test the ingress filter if it is working how i a expect.Which tool (can be windows also) can i use to test the ingress filter (tcpipload generator or som

Re: [LARTC] QoS for lan users ...

QoS on eth0 works fine for DMZ, but is there a possibility to doing QoS on eth0 based on private IPs ( 192.168.1.0/24 ) ? Are you wanting to QoS inbound or outbound traffic to and from your private IPs? This should be possible on for inbound on your eth2 interface. You might have to use IMQ