/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
Julian Eduardo de Anquin <[EMAIL PROTECTED]> wrote: > > But on my firewall configuration y have > EXTIF="eth1" > INTIF="eth0" I understand that, and your firewall is doing what you've told it. If a packet comes in eth0, and leaves through eth1, then it is properly forwarded according to the rules. However, your rules do not specify what to do with traffic that comes in eth1 and leaves via eth1. So the firewall drops the packets. The real question is, why is internal traffic seen on eth1? Is this impossible in your setup? I mean, due to the cabling, there is absolutely, positively, no way for an internal host's packet to be seen on eth1? For instance, if you have all the computers, and the firewall, and the external ethernet connection, all connected together to the same hub, it might be somehow possible for one of the computers to send a packet to the wrong interface on the firewall. This will confuse it. I can't think of a way that a packet from an internal network can arrive on an external interface, unless you have some funny cabling, or something. It seems quite impossible. Perhaps you could share some information about how your systems are cabled together. -- [EMAIL PROTECTED] (Fuzzy Fox) || "Good judgment comes from experience. sometimes known as David DeSimone || Experience comes from bad judgment." _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
