Quantcast
Channel: All EdgeRouter posts
Viewing all articles
Browse latest Browse all 60861

Re: L2TP IPSEC routing woes...

$
0
0

Thanks for the response!  ...I really appreciate it.  Correct, Once the tunnel is establishedd, I can successfully ping the interface of the downstream router (192.168.101.3) thats on the same broadcast domain as the client.  Pings time out once I try to hit the gateway interfaces on that same cisco router (10.10.2.1, 10.10.3.1, etc...)  Per your request, here is the requested commands on the ubiquiti edge router.

 

chief@ubnt:~$ show ip route
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
> - selected route, * - FIB route, p - stale info
IP Route Table for VRF "default"
S *> 0.0.0.0/0 [210/0] via 73.225.222.1, eth1
S *> 10.10.2.0/24 [5/0] via 192.168.101.3, eth0
S *> 10.10.4.0/24 [5/0] via 192.168.101.3, eth0
S *> 10.10.5.0/24 [5/0] via 192.168.101.3, eth0
S *> 10.10.6.0/24 [5/0] via 192.168.101.3, eth0
S *> 10.10.7.0/24 [5/0] via 192.168.101.3, eth0
S *> 10.10.8.0/24 [5/0] via 192.168.101.3, eth0
S *> 10.10.9.0/24 [5/0] via 192.168.101.3, eth0
S *> 10.10.11.0/24 [1/0] via 192.168.101.3, eth0
C *> 73.225.222.0/23 is directly connected, eth1
C *> 127.0.0.0/8 is directly connected, lo
C *> 192.168.101.0/24 is directly connected, eth0
C *> 192.168.102.0/24 is directly connected, switch0

chief@ubnt:~$ show ip route forward
default via 73.225.222.1 dev eth1 proto zebra
10.10.2.0/24 via 192.168.101.3 dev eth0 proto zebra
10.10.4.0/24 via 192.168.101.3 dev eth0 proto zebra
10.10.5.0/24 via 192.168.101.3 dev eth0 proto zebra
10.10.6.0/24 via 192.168.101.3 dev eth0 proto zebra
10.10.7.0/24 via 192.168.101.3 dev eth0 proto zebra
10.10.8.0/24 via 192.168.101.3 dev eth0 proto zebra
10.10.9.0/24 via 192.168.101.3 dev eth0 proto zebra
10.10.11.0/24 via 192.168.101.3 dev eth0 proto zebra
73.225.222.0/23 dev eth1 proto kernel scope link src 73.225.223.206
192.168.101.0/24 dev eth0 proto kernel scope link src 192.168.101.1
192.168.102.0/24 dev switch0 proto kernel scope link src 192.168.102.1

 

And just as a reference point, here is a 'show route' on the cisco router showing it's corresponding abilities to get back.

 

switch276bf6#show ip route
Maximum Parallel Paths: 1 (1 after reset)
IP Forwarding: enabled
Codes: > - best, C - connected, S - static

S 0.0.0.0/0 [1/1] via 192.168.101.1, 4149:21:02, vlan 1
C 10.10.2.0/24 is directly connected, vlan 2
C 10.10.4.0/24 is directly connected, vlan 4
C 10.10.5.0/24 is directly connected, vlan 5
C 10.10.8.0/24 is directly connected, vlan 8
C 10.10.9.0/24 is directly connected, vlan 9
C 10.10.10.0/24 is directly connected, vlan 10
C 10.10.11.0/24 is directly connected, vlan 11
C 192.168.101.0/24 is directly connected, vlan 1
S 192.168.102.0/24 [1/1] via 192.168.101.1, 4149:21:02, vlan 1
S 192.168.108.0/24 [1/1] via 192.168.101.1, 17:40:34, vlan 1

 

Will be more than happy to do a tcpdump, but it might take me a day or so (travelinng).


Viewing all articles
Browse latest Browse all 60861

Trending Articles