Aidan Anderson wrote:
Each of the routers are running Gentoo Linux, Kernel 2.6.18, and Shorewall 3.2.8
In Shorewall terms, version 3.2.8 is really stone-age. That is two major releases behind the current version 4.0.13.
Unfortunately when I tested it, it didn't work. The problem seems to be that the tracking isn't working for traffic arriving on eth2 in DC-B. When I run tcpdumps again, the traffic is getting as far as eth2 on DC-B but no further,
What does that mean? Does in mean that running tcpdump on eth2 shows the responses?
Any pointers in the right direction would be greatly appreciated. Apologies for not being as brief as promised.
These problems are virtually impossible to analyze without a Shorewall dump (see http://www.shorewall.net/support.htm#Guidelines). Unfortunately, the dump output from Shorewall 3.2.8 is not complete enough to understand all problems.
-Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
