Re: [arch-general] iptables forward policy

2012-08-28 Thread Juan Diego Tascón
Thanks all for your help

I finally decided to go with a more simple port forwarding solution
using socat a tool to forward tcp conections. This way I can filter
forwarded ports by using the router's INPUT chain.

Cheers

On Sun, Aug 26, 2012 at 1:08 PM, Peter Baldridge
 wrote:
> On Sun, Aug 26, 2012 at 10:11 AM, Juan Diego Tascón 
> wrote:
>
>> Is there any way to debug iptables, Juan,
>
>
> Another good way to debug IPTables (if you can limit the traffic to the box
> to just what you are troubleshooting) use the command :
>
> sudo iptables -Z && sudo watch -n .5 iptables -nvL
>
> ^zeros the counters for iptables
>
> this will serve to show packet counters next to all your rules.  Then you
> can send the traffic you are troubleshooting and see which rule it is
> matching.  From a different window or screen you can add/drop rules and
> watch the counters in real time.  That has always helped me in tough
> IPtables setups since it's a little more realtime/less info than logging.
>
> -pete


Re: [arch-general] iptables forward policy

2012-08-26 Thread Peter Baldridge
On Sun, Aug 26, 2012 at 10:11 AM, Juan Diego Tascón wrote:

> Is there any way to debug iptables, Juan,


Another good way to debug IPTables (if you can limit the traffic to the box
to just what you are troubleshooting) use the command :

sudo iptables -Z && sudo watch -n .5 iptables -nvL

^zeros the counters for iptables

this will serve to show packet counters next to all your rules.  Then you
can send the traffic you are troubleshooting and see which rule it is
matching.  From a different window or screen you can add/drop rules and
watch the counters in real time.  That has always helped me in tough
IPtables setups since it's a little more realtime/less info than logging.

-pete


Re: [arch-general] iptables forward policy

2012-08-26 Thread Bastian Beischer
Dear Juan,

see the section on logging in the wiki:

https://wiki.archlinux.org/index.php/Iptables#Logging

Cheers
Bastian

On Sun, Aug 26, 2012 at 7:11 PM, Juan Diego Tascón  wrote:
> Thanks for both replies. The graphic does it a lot more
> understandable. Is there any way to debug iptables, I mean, like a
> tool where I can visualize the path of a packet and where exactly it
> gets dropped/accepted and also realtime packets headers (src, dst,
> proto, dport, sport, etc)?
>
> On Sat, Aug 25, 2012 at 12:56 PM, Corrado Primier  wrote:
>> 2012/8/25 Juan Diego Tascón :
>>> Good day,
>>
>> Hello :)
>>
>>> I'm thinking of
>>> setting the default FORWARD policy to ACCEPT as my default INPUT
>>> policy is DROP and unless there is a valid FORWARD rule for a given
>>> port the packets wont go anywhere. I'm I right on this?
>>
>> You're wrong. Either a packet goes through the INPUT chain or it goes
>> through the FORWARD chain, depending on its destination. Take a look
>> at this packet flow diagram:
>> http://www.linuxhomenetworking.com/wiki/images/f/f0/Iptables.gif
>>
>> Corrado



-- 
Bastian Beischer
RWTH Aachen University of Technology

@CERN
Office: Bdg 32-4-B12
Phone: +41-22-76-75750
E-mail: bastian.beisc...@cern.ch
Address: CERN, CH-1211 Geneve 23

@RWTH Aachen
Office: 28 C 203
Phone: +49-241-80-27205
E-mail: beisc...@physik.rwth-aachen.de
Address: I. Physikalisches Institut B, Sommerfeldstr. 14, D-52074 Aachen


Re: [arch-general] iptables forward policy

2012-08-26 Thread Juan Diego Tascón
Thanks for both replies. The graphic does it a lot more
understandable. Is there any way to debug iptables, I mean, like a
tool where I can visualize the path of a packet and where exactly it
gets dropped/accepted and also realtime packets headers (src, dst,
proto, dport, sport, etc)?

On Sat, Aug 25, 2012 at 12:56 PM, Corrado Primier  wrote:
> 2012/8/25 Juan Diego Tascón :
>> Good day,
>
> Hello :)
>
>> I'm thinking of
>> setting the default FORWARD policy to ACCEPT as my default INPUT
>> policy is DROP and unless there is a valid FORWARD rule for a given
>> port the packets wont go anywhere. I'm I right on this?
>
> You're wrong. Either a packet goes through the INPUT chain or it goes
> through the FORWARD chain, depending on its destination. Take a look
> at this packet flow diagram:
> http://www.linuxhomenetworking.com/wiki/images/f/f0/Iptables.gif
>
> Corrado


Re: [arch-general] iptables forward policy

2012-08-25 Thread Corrado Primier
2012/8/25 Juan Diego Tascón :
> Good day,

Hello :)

> I'm thinking of
> setting the default FORWARD policy to ACCEPT as my default INPUT
> policy is DROP and unless there is a valid FORWARD rule for a given
> port the packets wont go anywhere. I'm I right on this?

You're wrong. Either a packet goes through the INPUT chain or it goes
through the FORWARD chain, depending on its destination. Take a look
at this packet flow diagram:
http://www.linuxhomenetworking.com/wiki/images/f/f0/Iptables.gif

Corrado


Re: [arch-general] iptables forward policy

2012-08-25 Thread Damjan

On 25.08.2012 18:47, Juan Diego Tascón wrote:

Good day,

I'm currently configuring a router. I'm setting the default policies
to DROP in the INPUT OUTPUT AND FORWARD chains. I'm thinking of
setting the default FORWARD policy to ACCEPT as my default INPUT
policy is DROP and unless there is a valid FORWARD rule for a given
port the packets wont go anywhere. I'm I right on this? or could
someone deliberately setup a packet to be forwarded from my router to
my lan? all I could find on google was one similar question with no
answer :(


FORWARD and INPUT are completely different.
INPUT is for packets that are in the end are destined for the host (i.e. 
routed to the host).


FORWARD is for packets, that are only forwarded by the host, the packets 
will not go through the INPUT chain.



In a normal routed network this depends on the destination IP of the 
packet, but if you DNAT the packets in the PREROUTING chain of the nat 
table the destination IP will change.



--
дамјан


[arch-general] iptables forward policy

2012-08-25 Thread Juan Diego Tascón
Good day,

I'm currently configuring a router. I'm setting the default policies
to DROP in the INPUT OUTPUT AND FORWARD chains. I'm thinking of
setting the default FORWARD policy to ACCEPT as my default INPUT
policy is DROP and unless there is a valid FORWARD rule for a given
port the packets wont go anywhere. I'm I right on this? or could
someone deliberately setup a packet to be forwarded from my router to
my lan? all I could find on google was one similar question with no
answer :(

Thanks