search for: ufomechanic

Currently using physdev on a bridge to try and isolate certain paths across and to the bridge. It all works except when trying to stop the flow in one direction on the FORWARD chain?? Can someone please help?? Below is the testing done so far. eth1 <---> BRIDGE <---> eth0 # Block (eth0 ---> eth1) - blocks both directions and not just one?? iptables -A FORWARD -m physdev

Hi, I am trying to relate the lended and borrowed statistics to the others and, in particular, compare them with the assigned rates for each class. My understanding is that the lended and borrowed stats are expressed as a number of packets but over what time period do the numbers refer? In addition, for a particular class why do the lended and borrowed figures add up to the sent value? That

Hello I have some rules inserted in the NAT table dual SNAT and DNAT for a connection They use at some moment the same port of the outside network. The problem i have is that the connection tracking in the kernel checks first the oldest rule and then the newest one. I use a system based on ARM XScale processor. Is that the default behaviour and how can i change this behaviour? Marius

I''ve set up Traffic Shaping on a Linux Router. Using HTB with SFQ, i''m trying to slow down heavy downloading for 20 subscribers over a 2048 kbit downlink. I''m classifying internet related traffic using iptables marking. bri0 is my local lan bridge, receiving egress traffic destined for subscribers. tc qdisc add dev bri0 root handle 1: htb default 2 tc class add dev

Hi, I would like setting the mark to be a terminating rule in Iptables. Is there a patch or an argument/parameter that enables this behavior? Or exactly which line do I need to modify in the source code? I would massively prefer not to follow each mark rule with a second rule with the same matching criterion that simply terminates - that''s too untidy for what I''m trying to

It seems like tos should be considered when sorting routes on insertion. Consider this out-of-order route creation: # ip route add 1.1.0.0/24 table 3 nexthop via 192.168.0.23 # ip route add 1.1.0.1/32 table 3 nexthop via 192.168.0.24 # ip route show table 3 1.1.0.1 via 192.168.0.24 dev eth3 1.1.0.0/24 via 192.168.0.23 dev eth3 ok... it''s re-ordered the routes - it makes sense, the