I'd be interested in applications around ownership of IP space or ASNs, but
there's so many ways to skin that cat already that people don't do because
it's 'hard' or 'reduces our flexibility' or sometimes because it involves
hardware upgrades as Christopher Morrow pointed out with RPKI and BGPsec.
Have you configured RNAT yet? Might tidy up your SIP problem. Do you need
the servers to see the client's source port, or is your issue that SIP
response traffic is not on the port the client expects?
Give the guide to setting up RNAT here a try -
http://support.citrix.com/proddocs/topic/netscaler
Matthew Petach wrote:
> On a slightly different note, however--while it's good to
> have an appreciation of the past and how we got here,
> I think it's wise to also recognize we as an industry
> have some challenges bringing new blood in--and
> treating it too much like a sacred priesthood with
If you're staying Cisco, probably the ASR1000 series, or the ASR9K,
depending on needs.
You probably don't need CSR routers if you're not going to 100Gbps.
On Fri, Nov 29, 2013 at 6:37 PM, Jawaid Desktop wrote:
> We're a service provider, and we have a network full of Cat6509's. We are
> findi
Wotcha,
>Number 1 gets you thinking along the IPv6 route (no pun, and imho :) )
>since you have to treat each boxes as if it was public.
I see this kind of statement surprisingly often. Having a public address
doesn't make a device public.
I don't really see a drive to have devices exposed to the
5 matches
Mail list logo
