netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pieter Smit <mlist2010@vigor.co.za>
To: Jeetu Golani <jeetu.golani@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: VLAN et iptables
Date: Mon, 5 Apr 2010 08:02:40 +0200	[thread overview]
Message-ID: <t2o23731b2b1004042302ie27e3da9hfadcc4413303f5c1@mail.gmail.com> (raw)
In-Reply-To: <201004031328.16411.jeetu.golani@gmail.com>

Hi Jeetu,

My suggestion, simplify your rules a little.

1. Start with a single rule to allow established connections.
2. You seem to have a extra [-m] in the subnet rules. (Could add -m
state --state NEW)
3. Adding a log rule to the end of the Forward table and looking at
non matched packets could help you see what the problem might be.


# for all subnets
 iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
 iptables -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

# for Matunga subnet 192.168.0.0/24
 iptables -A FORWARD -i $INTIF1 -o $EXTIF -s 192.168.0.0/24 -j ACCEPT

 # for Silvassa subnet 172.16.0.0/16
 iptables -A FORWARD -i $INTIF2 -o $EXTIF -s 172.16.0.0/16  -j ACCEPT

# for Colaba subnet 192.168.1.0/24
 iptables -A FORWARD -i $INTIF2 -o $EXTIF -s 192.168.1.0/24 -j ACCEPT

Regards,
Pieter

On Sat, Apr 3, 2010 at 9:58 AM, Jeetu Golani <jeetu.golani@gmail.com> wrote:
> Hi Elko / Marek,
>
> Thank you so much for replying back.
>
> I've pasted down below the ifconfig output and the routing table at the router
> in the head office.
>
> The routers can ping each other, they can also ping their respective PE's. The
> router at the head office, where we have the iptables script, can ping both
> the VPN PE and the gateway for the public IP.
>
> Furthermore if all we have are the following rules, the HO LAN 192.168.0.0
> can reach the public gateway and surf the internet, the remote locations
> can't:
>
> iptables -A FORWARD -i $EXTIF -o $INTIF1 -m state --state
> ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -i $INTIF1 -o $EXTIF -j ACCEPT
> iptables -A FORWARD -i $EXTIF -o $INTIF2 -m state --state
> ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -i $INTIF2 -o $EXTIF -j ACCEPT
>
> iptables -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE
>
> With the script I had posted earlier none of the locations can reach the
> public gateway.
>
> Truly appreciate all the help.
>
> Regards,
> Jeetu
> http://www.ebrain.in
> - An open (GPL) platform to discover and run software off someone in the
> meshed network pool and use it on your own device.
>
> twitter:  @0topcat0 and @ebrainpool
>
>
>
> --------------------------------
> ifconfig output:
>
> eth0      Link encap:Ethernet  HWaddr 00:27:0e:16:e1:a5
>          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>          inet6 addr: fe80::227:eff:fe16:e1a5/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:482754 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:743399 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:38759551 (36.9 MiB)  TX bytes:1024701055 (977.2 MiB)
>          Interrupt:27 Base address:0xe000
>
> eth1      Link encap:Ethernet  HWaddr 00:e0:1c:3b:a0:c1
>          inet6 addr: fe80::2e0:1cff:fe3b:a0c1/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:1750085 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:623003 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:1103786909 (1.0 GiB)  TX bytes:48633230 (46.3 MiB)
>          Interrupt:21 Base address:0x6000
>
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:157 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:17134 (16.7 KiB)  TX bytes:17134 (16.7 KiB)
>
> vlan105   Link encap:Ethernet  HWaddr 00:e0:1c:3b:a0:c1
>          inet addr:10.235.122.158  Bcast:10.235.122.159
> Mask:255.255.255.252
>          inet6 addr: fe80::2e0:1cff:fe3b:a0c1/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:68906 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:68917 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:3445300 (3.2 MiB)  TX bytes:3170595 (3.0 MiB)
>
> #public IP
> vlan689   Link encap:Ethernet  HWaddr 00:e0:1c:3b:a0:c1
>          inet addr: a.b.c.d  Bcast:a.b.c.(d+1)  Mask:255.255.255.252
>          inet6 addr: fe80::2e0:1cff:fe3b:a0c1/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:826133 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:554080 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:1022440202 (975.0 MiB)  TX bytes:42842359 (40.8 MiB)
> ------------------------------------------------------------------
>
> Kernel IP routing table:
>
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 10.235.122.186  0.0.0.0         255.255.255.255 UH    0      0        0
> vlan105
> 10.235.122.94   0.0.0.0         255.255.255.255 UH    0      0        0
> vlan105
> a.b.c.16  0.0.0.0         255.255.255.252 U     0      0        0 vlan689
> 10.235.122.156  0.0.0.0         255.255.255.252 U     0      0        0
> vlan105
> 192.168.1.0     10.235.122.94   255.255.255.0   UG    0      0        0
> vlan105
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 172.16.0.0      10.235.122.186  255.255.0.0     UG    0      0        0
> vlan105
> 0.0.0.0         a.b.c.17  0.0.0.0         UG    0      0        0 vlan689
>
>
>
> On Saturday 03 April 2010, Marek Kierdelewicz wrote:
>> > Hi,
>>
>> Hi Jeetu,
>>
>> >I have a Debian system that I am trying to configure as a router for a
>> >Network Description:
>> >At the head office, the ISP facing router has two physical NICs (eth0
>> >and eth1).
>>
>> Your script looks good. It's probably on purpose but in current setup
>> you won't be able to reach one private subnet from another.
>>
>> Just to be sure - if you want the box to act as a router for subnets
>> 192.168.1.0/24 and 172.16.0.0/16 then you need ip addresses from these
>> subnets on vlan105 interface.
>>
>> Regards,
>> Marek
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2010-04-05  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03  3:57 VLAN et iptables Jeetu Golani
2010-04-03  5:46 ` elko
     [not found] ` <20100403080147.04d1add3@catlap>
2010-04-03  7:58   ` Jeetu Golani
2010-04-05  6:02     ` Pieter Smit [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=t2o23731b2b1004042302ie27e3da9hfadcc4413303f5c1@mail.gmail.com \
    --to=mlist2010@vigor.co.za \
    --cc=jeetu.golani@gmail.com \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).