[rbak-nsp] Context

[David Freedman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Achmad Himawan wrote:
> Dear all,
> 
> Currently we are using SE-400 as gateway for our PPPoE services using
> Freeradius.
> 
> Its running well now with only one context (local) for various qos
> policy, qos metering, and NAT policing.
> 
> Suppose we want to create another service without NAT, should we
> create another context or just create another pool?

Aim to use different radius attributes and/or subscriber profiles to
achieve this, another context would certainly work but could add
additional complexity in terms of both routing and management.

If you are doing per subscriber NAT this should be straightforward,
simply assign them routable addressing (i.e that does not require the
NAT) and don't deploy the NAT via radius (i.e by omitting your NAT
attributes or referring to a profile which omits them)

If you are doing interface NAT then simply just omit the NAT directives
as above and ensure the interface NAT is configured not to NAT for
routable address space.

Dave.



> 
> Thanks in advance.
> 
> Rgds,
> -Ahmad
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
> 


- --

- ------------------------------------------------
David Freedman
Group Network Engineering
Claranet Limited
http://www.clara.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuRHXEACgkQtFWeqpgEZrJZ7wCgmlPAah2LEAHF3vw/4oIm5UH5
ur0AoLZs+/P48QcOyoa81bFw/PXekl+A
=pE2F
-----END PGP SIGNATURE-----