Actually, up until now, I've had NO rules for hme1. hme1 is facing my private LAN 10.0.0.0/24, with IP 10.0.0.1. Since there are no rules, requests were permitted to enter my squid/ipfilter box on that hme1 interface.
My only rules were for the eri0 facing the Internet. I wanted to tighten up the eri0 interface such that nothing could come into eri0 other than return http requests. --- Phil Dibowitz <[EMAIL PROTECTED]> wrote: > Joseph Spenner wrote: > > > I think I know what my problem might be. Could it > be > > that my 'keep state' is never keeping state > because > > the original request isn't recorded due to squid? > > > Hold up here - something's wrong, I think I'm > missing something. You're using > squid. Therefore, I'm assuming you want to allow > internal machines to be able > to access squid. Therefore you need a rule to allow > the packets from the > internal network to squid.. something like > > pass in quick on hme1 from any to any > > I was gonna say keep state there, but with squid > messing with things I don't > think it'll work, so allow things to get to squid, > then use your keep-state > rule below to allow squid to get out... > > Keep in mind I've never put squid and ipf together - > someone should write a > howto on that (not me), i'm just going by my IPF > knowledge here. > > Phil > -- > "They that can give up essential liberty to obtain a > little temporary safety > deserve neither liberty nor safety." > -Benjamin Franklin, 1759 > __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
