PPP T1 and WAN on 3448 NAT? IP Spoof? Help!

[jgerak]

Ok i have two sites.

                      REMOTE 3448                                                     HQ  3205                                     

I'm having issues connecting for example RDP to computers on the other side of the PPP T1.

Basically just want to bridge the sites together. Both sides have separate WAN connections.

I can ping the 10.10.11.253 Router from the 10.10.10.X

I can not ping the 10.10.10.253 Router from 10.10.11.X

Firewall is off on HQ Netvanta 3205, Sonicwall is firewall.

Firewall is on in the Remote Netvanta 3448.

Sonicwall has route for 10.10.11.0 to use 10.10.10.253 which works.

Getting IP spoofs in my sonicwall at HQ from WAN IP from REMOTE site. <------- Think this is my issue.?.?.?   NAT Issues?

Configs attached

Thanks,

J

[jgerak · Accepted solution]

Forgot to mention I can ping over the PPP T1 both ways when i telnet into the routers

10.10.10.253 can ping 10.10.11.253

10.10.11.253 can ping 10.10.10.253

[Anonymous]

I'll take a stab - 2 things...

Try removing the ip access-policy Private on the 3448's PPP interface

you might take a look at the subnet masks on each ppp interface - see Configuring PPP in AOS Quick Configuration Guide

We do these using a /30 255.255.255.252 subnet mask - remove the peer default ip address statements, and change the ppp interfaces accordingly below...

Not sure if this is the issue

for the 3205 -

nterface ppp 1

  description ppp T1 to Remote

  ip address  192.168.200.201  255.255.255.252

  ip mtu 1500

  media-gateway ip primary

  no shutdown

  cross-connect 1 t1 1/1 1 ppp 1

for the 3448

interface ppp 1

  description ppp T1 to HQ

  ip address  192.168.200.202  255.255.255.252

  ip mtu 1500

  media-gateway ip primary

no shutdown

  cross-connect 1 t1 1/1 1 ppp 1

[jgerak]

I did notice the subnets on the PPP connection and fixed them.

I ended up calling ADTRAN tech support and I must say i'm very pleased with their support. I put a ticket in and about an hour later they called me and helped me figure out the issue.

The issue was i had to put a allow rule in the 10.10.11.X router to the 10.10.10.0/24.

RESOLVED.