--- Phil Dibowitz <[EMAIL PROTECTED]> wrote: > > > following lines should allow the return traffic > from > > web requests: > > > > block in log quick on eri0 all > > pass out quick on eri0 proto tcp from any to any > keep > > state > > > > Shouldn't the above be an extremely simple > > proxy/ipfilter box configuration? > > > No. How will the traffic from your internal hosts > get to you to be proxied??? > Also you may want the port = 80 deal here as well. >
I'm not sure I follow. If I have the following config: eri0: 212.X.Y.Z to the Internet hme1: 10.0.0.1 to my private Intranet block in log quick on eri0 all pass out quick on eri0 proto tcp from any to any keep state Then I visit ups.com. The 2nd line in my config allows the packet out, with keep state. When ups.com sends me something back, it should be allowed to return since the keep state. As I mentioned earlier, the following line will permit everything to work: pass in quick on eri0 proto tcp from any to 192.101.77.232/32 So I know that my system is able to route correctly. SO, doesn't the line: pass out quick on eri0 proto tcp from any to any keep state translate to: "Let tcp packets out to any destination on eri0, and remember where the destination is. When I see packets trying to come back from that destination, let them in." ?? > > > I still see the following type of entries in my > logs: > > > > May 14 22:49:45 proxyboxy ipmon[2192]: [ID 702911 > > local0.warning] 22:49:45.339559 eri0 @0:6 b > > 153.2.224.55,80 -> 212.X.Y.Z,9561 PR tcp len 20 40 > -A > > IN > > > Not sure. I think that should work. > Funny side note, given your above snippet: at one of > my old jobs, our NAT box > was called 'proxbox'. > > > 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
