On 05/13/2011 07:31 AM, Mr Dash Four wrote: > That is exactly what I have! > > So, do I have this then: (outbound) eth0 -> 212.58.254.251, but passing > through eth1 and (inbound) 212.58.254.251 -> ifb0, but passing through > ifb1? If so, which classes should I use for the purpose of defining my > traffic shaping?
No -- eth1 and ifb1 are the *only* interfaces involved when 10.1.1.12 communicates with 212.58.254.251. eth0 and ifb0 are *not* involved. > > The other "unknown" for me is, assuming I need to use eth0 class for > outbound traffic, that presumably needs to be accounted for from the > eth0 quota and that would be wrong, I think, as that traffic *never* > actually passes through eth0 at all as it is SNATed and actually goes > via eth1, isn't it? In tcrules for eth0, the source IP is 10.1.1.12 and the dest IP is 212.58.254.251. For tcfilters for ifb0, the source IP is 212.58.254.251 and the dest IP is 10.1.2.7. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
