[j-nsp] MX, Nat + BGP

Julien Goodwin jgoodwin at studio442.com.au
Wed May 18 00:45:11 EDT 2011


On 18/05/11 10:34, OBrien, Will wrote:
> I've been working through a nat configuration on my lab MX960 with a MS-DPC blade that I've borrowed.
> To start, I'm trying to create a simple nat'd subnet. However, the NAT guide that I've been provided doesn't really fit my current design.
> 
> The example I'm looking at uses a nat pool that's defined like so:
> 150.150.150.0/24
> 
> with an outside interface that has say, 150.150.150.1/24 on it,
> 
> Ok.
> 
> Well, in my world, I use MX's for BGP announcements. So I'm trying to put the NAT source interface on a lo0 instead of a normal interface.
> 
> Is anyone else doing it this way or is there some other sneaky trick I'm missing? So far applying the service filter only seems to break traffic.

I've not done NAT on MX only SRX, but with an SRX just announce the NAT
pool as a route (static and readvertise, for whatever reason just adding
a pool isn't enough to make it eligible for redist), don't need to
assign it to an interface at all.

-- 
Julien Goodwin
Studio442
"Blue Sky Solutioneering"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20110518/f2a1eec0/attachment.pgp>


More information about the juniper-nsp mailing list