Solved

UDP 5440 not connecting between two Lan-to-Lan VPN's on a Cisco VPN 3000

Posted on 2008-10-15
8
1,726 Views
Last Modified: 2012-05-05
I have a WAN with three locations.  HQ, Dallas, and Boston.  There is a VPN 3005 in HQ the connects the two other locations.  Dallas has a ASA and Boston has a PIX, both connected using IPSec back to HQ.

I also have a VOIP system in all three locations.  HQ can connect to both remote locations, but the VOIP system in Dallas cannot connect to the VOIP system in Boston.  It uses UDP 5440.  The two remote offices can ping eachother and other TCP communication works.

As far as I can tell, I have no filters or access control lists that would be blocking this.  Any ideas?
0
Comment
Question by:davidmccarthy
8 Comments
 
LVL 10

Expert Comment

by:kyleb84
ID: 22726816
If TCP works and UDP does not it has to be a ACL issue...

Have a look at the configs and see if there's something like a::

  access-list permit 101 tcp (...)

but no:

  access-list permit 101 udp (....)

If so, change it to:

  access-list permit 101 ip (...)

That'll allow TCP + UDP.

Maybe post your configs if you still can't figure it out?
Be sure to remove all usernames/passwords first!
0
 

Author Comment

by:davidmccarthy
ID: 22726912
kyleb84: I don't think that's my problem.  Here's more detail:

HQ is 10.0.0.0/16
Dallas is 10.8.0.0/16
Boston is 10.7.0.0/16

In the Boston PIX, the tunnel is setup with:

access-list TunnelToHQ permit ip 10.7.0.0 255.255.0.0 10.0.0.0 255.255.0.0
access-list TunnelToHQ permit ip 10.7.0.0 255.255.0.0 10.8.0.0 255.255.0.0

Likewise the Dallas ASA has:

object-group network HQ
 network-object 10.0.0.0 255.255.0.0
 network-object 10.7.0.0 255.255.0.0
access-list outside_20_cryptomap extended permit ip 10.8.0.0 255.255.0.0 object-group HQ
access-list inside_nat0_outbound extended permit ip 10.8.0.0 255.255.0.0 object-group HQ

I'm leaving out a bunch of stuff here, but it's because I don't think it is relevant.  The UDP traffic I'm having trouble with flows fine between both remote offices and HQ.  

I think the problem must be some combination of the VPN 3005 in HQ and/or the core router in HQ.

There are no access-list at all on the core router (10.0.0.1)  It has the following routing table:
0.0.0.0 0.0.0.0 <internet firewall>
10.0.0.0 255.255.0.0 <connected>
10.8.0.0 255.255.0.0  <vpn 3005>
10.7.0.0 255.255.0.0 <vpn 3005>

It might be impossible to list all of the configuration of the VPN3005 since it is mostly web-based, but neither Lan-to-Lan tunnel has a filter on it.  The tunnel default gateway is 10.0.0.1.

When I traceroute from Dallas to Boston (because ICMP does work), it goes to the Dallas ASA -> Core Router -> VPN 3005 > Boston

As far as I know routing is the same for TCP and UDP, but maybe my routing scheme is affecting the UDP packets?




0
 
LVL 10

Expert Comment

by:kyleb84
ID: 22726956
""As far as I know routing is the same for TCP and UDP, but maybe my routing scheme is affecting the UDP packets?""

I don't see how... routing only happens at layer 3 - IP, not layer 4 - TCP/UDP.

What you've described is exactly how it should be set up, and your ICMP pings proves that the routing is properly configured.

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

You say it's the VoIP system that need to communicate via UDP... I'm guessing your tests were made on a PC?

How is the routing table set up on those VoIP systems?

0
 

Author Comment

by:davidmccarthy
ID: 22733884
I'm using Shoretel VOIP switches.  Here's the routing table from Boston:

destination      gateway
-------------      -----------
0.0.0.0            10.7.0.1
10.7.0.0          10.7.0.5

10.7.0.1 is the PIX in Boston and 10.7.0.5 is the VOIP box.

When I telnet into VOIP box I can run a standard ping to the Dallas VOIP just fine.  When I run what Shoretel calls a "lsp_ping", it fails.  According to their tech support, the lsp_ping is trying to communicate using UDP 5440.  So of course, they are claiming that something must be blocking it along way.

I suppose another approach would be to eliminate the VOIP all together and prove that I can get UDP 5440 from one location to the other.  I know how to test TCP stuff, like telneting to a specific port on a server to see if it connects.  How can I simulate something like that with UDP?

0
What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

 
LVL 10

Accepted Solution

by:
kyleb84 earned 500 total points
ID: 22736304
There's a little app called iperf. It's really for bandwidth testing but does UDP + TCP.


http://dast.nlanr.net/Projects/Iperf/

There's a Microsoft Windows Binary about half way down that page.

install on your laptop and a server at the other site.

Server @ Site1:
iperf -s -u

Your laptop:
iperf -c [IP OF SERVER 1] -u


If it works you'll see something similar to what I've attached.


Server:
 

U:\>iperf -s -u

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

Server listening on UDP port 5001

Receiving 1470 byte datagrams

UDP buffer size: 8.00 KByte (default)

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

[1928] local 192.168.127.156 port 5001 connected with 192.168.127.157 port 1322

[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total Datagrams

[1928]  0.0-10.0 sec  1.25 MBytes  1.05 Mbits/sec  0.000 ms    0/  893 (0%)
 

Laptop:
 

U:\>iperf -c 192.168.127.156 -u

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

Client connecting to 192.168.127.156, UDP port 5001

Sending 1470 byte datagrams

UDP buffer size: 8.00 KByte (default)

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

[1912] local 192.168.127.157 port 1322 connected with 192.168.127.156 port 5001

[ ID] Interval       Transfer     Bandwidth

[1912]  0.0-10.0 sec  1.25 MBytes  1.05 Mbits/sec

[1912] Server Report:

[1912]  0.0-10.0 sec  1.25 MBytes  1.05 Mbits/sec  0.000 ms    0/  893 (0%)

[1912] Sent 893 datagrams
 
 

If it didn't work, you'll only see this on the server:
 

U:\>iperf -s -u

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

Server listening on UDP port 5001

Receiving 1470 byte datagrams

UDP buffer size: 8.00 KByte (default)

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

Open in new window

0
 
LVL 10

Expert Comment

by:kyleb84
ID: 22736315
Well I guess it wouldn't be your laptop, since you'd be at HQ, but anyway, you get the point.
0
 
LVL 1

Expert Comment

by:harrytwotoes
ID: 24828186
Dude.  I'm having this issue and it's driving me mad!

How did you fix it?
0
 

Expert Comment

by:vsmwahae1
ID: 36509669
But, where is teh answer?
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Let’s list some of the technologies that enable smooth teleworking. 
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now