PAT with puplic ip over ADSL

[Dieter Prinesdoma]

Hi,

I have a problem with my 877 Router. A ping to the internet with source Atm 0.1 works. And from the internet to the 80.123.85.105 ip it is also ok.

But from the lan it does´t work.

I think the problem is the PAT config or a route probleme.

Hope you could help me.

thx in advanced

interface ATM0
no ip address
no atm ilmi-keepalive
!
interface ATM0.1 point-to-point
ip address 80.123.85.105 255.255.255.248
ip nat outside
ip virtual-reassembly
pvc 8/64
  encapsulation aal5mux ppp dialer
  dialer pool-member 1
!
!
interface Vlan1
ip address 192.168.2.254 255.255.255.0
ip nat inside
ip virtual-reassembly
!
interface Dialer0
ip address negotiated
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer-group 1
ppp authentication chap callin
ppp chap hostname xxx
ppp chap password xxx
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer0
ip http server
no ip http secure-server
!
ip nat inside source list 1 interface ATM0.1 overload
!
access-list 1 permit 192.168.2.0 0.0.0.255
dialer-list 1 protocol ip permit

[shivlu jain]

Just change the given and then post the results:-

ip nat inside source list 1 interface dialer 0 overload

Add global route with dialer 0 as outgoing interface

ip route 0.0.0.0 0.0.0.0 dialer0

regards

Shivlu Jain

http://www.mplsvpn.info

[Dieter Prinesdoma]

Thx for the answer.

But it was not the solution.

I have the same problem.

Connenction from the router with the source ip from the atm 0.1 is ok.

But not from the lan interface

This is the example from the current config.

version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname Router
!
boot-start-marker
boot-end-marker
!
logging message-counter syslog
enable secret xxx
!
no aaa new-model
!
!
dot11 syslog
ip source-route
!
!        
ip cef
!
!
!
!
username xxx password xxx
!
!
!
archive
log config
  hidekeys
!
!
!
!
!
interface ATM0
no ip address
no atm ilmi-keepalive
!
interface ATM0.1 point-to-point
ip address 80.123.85.105 255.255.255.248
ip nat outside
ip virtual-reassembly
pvc 8/64
  encapsulation aal5mux ppp dialer
  dialer pool-member 1
!
!
interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface Vlan1
ip address 192.168.2.254 255.255.255.0
ip nat inside
ip virtual-reassembly
!
interface Dialer0
ip address negotiated
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer-group 1
ppp authentication chap callin
ppp chap hostname xxx
ppp chap password xxx
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer0
ip http server
no ip http secure-server
!
ip nat inside source list 1 interface Dialer0 overload
!
access-list 1 permit 192.168.2.0 0.0.0.255
dialer-list 1 protocol ip permit
!
!
!
!
control-plane
!
!        
line con 0
no modem enable
line aux 0
line vty 0 4
login
!
scheduler max-task-time 5000
end

[Kelvin Willacey]

If you do a ping from the router using the LAN address as the source interface, are you still unable to ping?

ping 4.2.2.2 source interface Vlan1

Also if you are able to browse, then it is not a NAT problem.

[Dieter Prinesdoma]

A ping from the source vlan 1 doesn´t work. Only from the ATM 0.1.

I think it is a Nat problem but i dont´t know the solution.

[shaun.cooney]

Try issuing show ip nat translations. Are there any translations active? I suspect not.

If not try debug ip nat 1 and post some results.