RE: What's going on with my iptables?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 4, 2010 5:03 pm, Gary Smith wrote:
>> Thanks Gary.
>> I went ahead with your suggestion but I still can't seem to figure out
>> where the problem is.
>> For example, this is me trying to ping google.com from the shell:
>>
>> [220040.098711] FW: IN= OUT=eth1 SRC=MYPUBIP DST=72.14.234.104 LEN=84
>> TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=871 SEQ=14
>>
>> [...]
>>
>> [220040.342816] FW: IN=eth0 OUT=
>> MAC=00:03:47:42:5c:17:00:04:ed:99:2c:fb:08:00 SRC=72.14.234.104
>> DST=MYPUBIP LEN=84 TOS=0x00 PREC=0x00 TTL=53 ID=48058 PROTO=ICMP TYPE=0
>> CODE=0 ID=871 SEQ=14
>>
>>
>> It all seems to be pretty kosher (except for the fact that the packets
>> are
>> being dropped)..
>
>
> You are dropping outgoing packets.  Stop doing that :).  Unless you are
> ultra paranoid about traffic originating from your firewall, there is no
> need to drop OUTPUT.  IMHO, the OUTPUT chain is useful for when you need
> to block specific outgoing traffic in a certain manner, say, port 25, to
> make sure that all mail flows through a specific server on your network
> for compliance, etc.  Or in the case of proxying, where you want to ensure
> that all traffic going to port 80 goes through the proxy and only the
> proxy can go out.
>
> In essence, you are saying, do let my requests go out...
>
> Then, for the input chain, make sure you have a rule to allow established
> and related connections to come in (and to be forwarded) and then return
> packets that originated from your network should be able to return just
> fine.
>
> -A FORWARD -m conntrack --ctstate ESTABLISHED -j ACCEPT
> -A INPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT
>
> Give that a try.
>

Thanks!
That seemed to do the trick.
I guess my original rule:

-A INPUT -i $INTERNET -m state --state ESTABLISHED,RELATED -j ACCEPT

somehow stopped working.

Unfortunately I am having troubles with port forwarding & opening
now..none of them are accessible from the outside :(

-A INPUT -j ACCEPT -p tcp --destination-port 80 -i $INTERNET
-A INPUT -j ACCEPT -p tcp --destination-port 22 -i $INTERNET

-A FORWARD -i $INTERNET -p tcp --dport 9500 -j ACCEPT
-t nat -A PREROUTING -p tcp -i $INTERNET --dport 9500 -j DNAT
--to-destination 10.0.1.11
-A FORWARD -i $INTERNET -p tcp --dport 8112 -j ACCEPT
-t nat -A PREROUTING -p tcp -i $INTERNET --dport 8112 -j DNAT
--to-destination 10.0.1.11

What's wrong now??

-JK

--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux