On Wed, Jan 22, 2014 at 01:37:18PM -0700, Matt Larsen - Lists wrote:
> This does not fix the problem.
>
> The router with the public IP address sees the private IP as an IP that
> is on its external interface. I believe this is due to the src-nat
> that does nat for our 10.0.0.0/8 subnets - ne
Are you saying you have a public and private IP on an interface facing the
OSPF network? The issue is that OSPF is spitting out the private IP and
the other side of the OSPF network is hearing the wrong IP (because it only
has the public)?
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1
This does not fix the problem.
The router with the public IP address sees the private IP as an IP that
is on its external interface. I believe this is due to the src-nat
that does nat for our 10.0.0.0/8 subnets - neighboring router has an IP
of 10.16.0.2/24.
I have not been having much luc
If the problem is just that the public address occasionally sneaks through, you
could establish an ospf-in filter to filter out that public network. If the
problem is that the private address never shows up in OSPF, then that would
just be masking the symptom and not solving the problem.
On Ja
I have come across an issue in a couple of places where a router that is
running src-nat and ospf barfs on OSPF because the source IP address for
the OSPF requests going across the private interface keeps coming up as
a public IP address.
I end up getting the message "Received packet from an u
5 matches
Mail list logo
