cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2778
Views
0
Helpful
2
Replies

ping PPPoE local virtual-access interface

Hi,

With following config R2 acts as PPPoE server (R2 assign an IP address to a PPPoE client via DHCP)

ip dhcp excluded-address 10.10.1.2 10.10.1.254

!

ip dhcp pool R1

   network 10.10.1.0 255.255.255.0

!

bba-group pppoe global

virtual-template 2

!

!

interface FastEthernet0/0

no ip address

ip virtual-reassembly

duplex auto

speed auto

pppoe enable group global

!

!

interface Virtual-Template2

ip address 10.10.1.2 255.255.255.0

no peer default ip address

!

On R2 when PPP session go up a virtual-access interface is cloned form virtual-template:

R2#sh ip int brie

Interface                  IP-Address      OK? Method Status                Protocol

FastEthernet0/0            unassigned      YES NVRAM  up                    up

FastEthernet0/1            10.10.2.2       YES NVRAM  up                    up

Virtual-Access1            unassigned      YES unset  up                    up

Virtual-Access1.1          10.10.1.2       YES TFTP   up                    up <---------

Virtual-Access2            unassigned      YES unset  down                  down

Virtual-Template2          10.10.1.2       YES NVRAM  down                  down

Now I can ping the remote side (PPPoE client) but not the local interface (10.10.1.2)

R2#deb ip pack det

IP packet debugging is on (detailed)

R2#

R2#

R2#ping 10.10.1.2 re 2

Type escape sequence to abort.

Sending 2, 100-byte ICMP Echos to 10.10.1.2, timeout is 2 seconds:

*Mar  1 00:05:36.531: IP: tableid=0, s=10.10.1.2 (local), d=10.10.1.2 (Virtual-Access1.1), routed via RIB

*Mar  1 00:05:36.535: IP: s=10.10.1.2 (local), d=10.10.1.2 (Virtual-Access1.1), len 100, sending

*Mar  1 00:05:36.539:     ICMP type=8, code=0

*Mar  1 00:05:38.531: IP: tableid=0, s=10.10.1.2 (local), d=10.10.1.2 (Virtual-Access1.1), routed via RIB

*Mar  1 00:05:38.535: IP: s=10.10.1.2 (local), d=10.10.1.2 (Virtual-Access1.1), len 100, sending

*Mar  1 00:05:38.539:     ICMP type=8, code=0

Success rate is 0 percent (0/2)

R2#

from debug it seems R2 originates ICMP echo, route the packet to virtual-access1.1 and then this (sw) interface send it...

I've checked on the remote side....ICMP echoes are not received (as instead when pinging the local IP address configured on a serial interface...)

Why this behaviour ? Thanks.

2 Replies 2

Any idea ? Thanks.

looks like the virtual-template interface is not pingable.

what you can do is to have a loopback interface with the IP you want to assign to virtual-template and then under virtual-template do an unnumbered ip address:

!

interface Loopback1
 ip address 192.168.2.1 255.255.255.0

!

interface Virtual-Template1
 mtu 1492
 ip unnumbered Loopback1
 peer default ip address pool pool-1


!

this way you can ping both local and peer IP:

 

R1#ping 192.168.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/24/32 ms
R1#ping 192.168.2.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.1, timeout is 2 seconds:
!!!!!


--------------------------------------------------------------------------

 

another way would be to use ppp multilink, but I could only make it work if you have virtual-template interfaces on both ends (like you'd use for ppp over frame-relay)