Hi,
Would separate areas solve the problem ?
I mean have public interfaces in area 0 and private interfaces in area 1.
This way, you will have separate neighboring on private and public
interfaces.
If area 1 is a stub area, the routes learned on public interfaces won't
be announced via the private interfaces.


Emmanuel Muncal wrote:
> Good Day to the list!
>
> I am trying to run OSPF over a network with a router with an Alias IP.
> For example: Router 1 has a PUBLIC IP 2.2.2.2/24 <http://2.2.2.2/24>
> and an alias PRIVATE IP 1.1.1.2/24 <http://1.1.1.2/24 >. The other OSPF
> peer has PUB IP 2.2.2.3/24 <http://2.2.2.3/24> and PRIV IP 1.1.1.3/24
> < http://1.1.1.3/24>.
>
> I got no problems in  OSPF advertisements.  Only that I am learning
> the routes via the 2 IP. For example: 2.2.2.3 < http://2.2.2.3>   via
> 2.2.2.3 <http://2.2.2.3>  and via 1.1.1.3 <http://1.1.1.3>. Which is
> right.
>
> What I want to do is that the PUBLIC IP will learn via PUBLIC IP
> Interface. While PRIVATE IP  from PRIVATE IP Interface.
>
> Is there such a way to do this?
>
> Sorry fo the newbie question.
>
>
> Thanks in Advance.
>
>
> Cheers!
>
> Emmanuel
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users-UOy77sIEA+cAd7ICUelF/Q@public.gmane.org
> http://lists.quagga.net/mailman/listinfo/quagga-users
>

Send Quagga-users mailing list submissions to
        quagga-users-UOy77sIEA+cAd7ICUelF/Q@public.gmane.org

To subscribe or unsubscribe via the World Wide Web, visit
         http://lists.quagga.net/mailman/listinfo/quagga-users
or, via email, send a message with subject or body 'help' to
        quagga-users-request-UOy77sIEA+cAd7ICUelF/Q@public.gmane.org

You can reach the person managing the list at
        quagga-users-owner-UOy77sIEA+cAd7ICUelF/Q@public.gmane.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Quagga-users digest..."


Today's Topics:

   1. [quagga-users 8764] Integrating bgpd and iptables
      (Felipe Grazziotin - SouthTech SuperDatacenter)


----------------------------------------------------------------------

Message: 1
Date: Fri, 03 Aug 2007 12:19:44 -0300
From: Felipe Grazziotin - SouthTech SuperDatacenter
        < fgrazziotin-+kFIu4fVGTY4j/f6Vo8NEw@public.gmane.org>
Subject: [quagga-users 8764] Integrating bgpd and iptables
To: quagga-users-UOy77sIEA+cAd7ICUelF/Q@public.gmane.org
Message-ID: < 46B34790.5080506-+kFIu4fVGTY4j/f6Vo8NEw@public.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello list,

has anyone made any kind of integration between quagga's BGP daemon and
iptables?
I need to do something like CISCO ACLs to restrict traffic from some
clients to specific blocks
received from a few ASNs.

For example, say that I receive a full feeds from an uplink, and a
client buys traffic for only certain ASN, say 65530 and 65520.
My BGP configuration will announce only those two ASN to my client, but
how can I make sure that the client isn't going to set his default
gateway to my router and use my access to other ASNs?

My idea was to use something integrated between bgpd and iptables to
only accept traffic from his networks to the blocks from those two ASNs,
and deny any other kind of connection.

Any suggestions? Any idea will be appreciated.

--
Yours,

Felipe Grazziotin



------------------------------

_______________________________________________
Quagga-users mailing list
Quagga-users-UOy77sIEA+cAd7ICUelF/Q@public.gmane.org
http://lists.quagga.net/mailman/listinfo/quagga-users


End of Quagga-users Digest, Vol 49, Issue 4
*******************************************