Re: Qos/TrafficShaping(on Shorewall) Howto available for Web-viewing

From: Homer (hparker_at_homershut.net)
Date: 04/28/04

  • Next message: Alexander Dalloz: "Re: Sendmail and masq" 
    To: For users of Fedora Core releases <fedora-list@redhat.com>
Date: Wed, 28 Apr 2004 12:10:40 -0500

    On Tue, 2004-04-27 at 21:03, Ow Mun Heng wrote:

    >
    > Please have a view and please feedback accordingly. I think It needs a
    > little more work, esp in that QoS only can shape outgoing traffic and not
    > incoming.
    >

            That's the reason I didn't use Wondershaper.. I've got 4 interfaces in
    my firewall and needed to throttle them all differently.. To throttle
    both directions, you have to apply tc rules to both interfaces.. IE: you
    want 192.168.1.1 to have 256k with QOS both ways, you have to mark the
    packets as they come in, and then let tc use the marks to set the packet
    to a rule.. Then you do it for the other interface.. So you end up
    marking the packets coming in both interfaces, and in my case, I mark
    according to origination and destination.. You've just set it for 256k
    both ways.. And yes, I use Shorewall as well.. Works like a champ ;) As
    for you're HowTo, it looked pretty good, just wanted to let you know how
    to handle both directions... For your next HowTo ;) 

    -- 
Homer <hparker@homershut.net>
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Alexander Dalloz: "Re: Sendmail and masq"

    Relevant Pages

    • Re: Traffic NOT moving through the correct network interface?
      ... outbound traffic on port 12345 through eth1 and all traffic on port 54321 through eth2, ... So you'll also need a tool such as iptables to mark outgoing packets. ... However advanced routing may be difficult to set up with interfaces which are configured using DHCP. ... Iptables can also mark whole connections based on the input interface, so replies can be routed through the same interface. ...
      (alt.os.linux)
    • Re: IPMP enabled serious Network Problems
      ... inet 10.xx.xx.49 netmask ffffff00 broadcast xxxxxxx.255 ... Turn off this option to track all network interfaces ... input packets with dribble condition detected ...
      (comp.unix.solaris)
    • Re: [PATCH 4/5] ieee802154: add documentation about our stack
      ... +Currently only IEEE 802.15.4 layer is implemented. ... +Most of IEEE 802.15.4 MLME interfaces are directly mapped on netlink commands. ... +2) 'SoftMAC' or just radio. ... are you sending IP packets over this ARPHRD_IEEE802154 network devices ...
      (Linux-Kernel)
    • Re: ISR CBAC prolem
      ... When I apply CBAC onto inside interface without any ACL's ... Have you determined if packets are arriving out of order? ... I'm running CEF and netflow on both outside and inside interfaces... ... > increase the inspection timouts. ...
      (comp.dcom.sys.cisco)
    • Re: Help Broadcasting a UDP packet on the LAN:URGENT
      ... We use all-ones packets well ... > network interfacethey should be using to do this. ... > interfaces because you have a per-network broadcast address if you want ... That way you get "for free" to control which interfaces should send ...
      (freebsd-net)