question

First, you should probably know that table mapping is the best technology for this type of response.  You have shown how you might use block mapping or pattern mapping instead, but table mapping will generally be a lot easier when you have a nice normal table like this.  In fact, if you allow iTest to auto-generate a map for you, it will produce a table map with all of the correct columns, etc.  (I just tried it.)

If you are going to do this via block mapping, you are going to run into problems because of all of the wildcard and optional tokens that you have created.  iTest is going to find lots of different ways that it could potentially match these various rows.  In this particular case, the structure of the table just has too much ambiguity to make block mapping very successful.

Pattern mapping allows you to take block mapping to the next level, because you can be very specific about the patterns you are expecting.  In this case, though, you must deal with that same ambiguity described above by getting into the regex definitions for each of the fields involved -- to remove that ambiguity.  

So I recommend that you just create a table map, and you'll see that it will map it correctly for you.  There is also a feature of table mapping that you might not be aware of, but you can even ask iTest to parse the content within one column so that you can query each sub-part of the column.  So if you set the checkbox, "Parse cell contents", on the definition of the column properties for your" destination" column, you'll be able to query each part of that cell contents -- letting you pull out just the IP address, for example, or check to get other parts of it.