Re: Firewall seemingly being bypassed

I'm not real knowledgeable in this stuff. Here is a traceroute, but I can't tell anything from it. The firewall is searching for the -string vtigercrm. I thought that packets coming in with that in it would be rejected. I don't now how routing would affect that.

traceroute to 69.58.178.57 (69.58.178.57), 30 hops max, 60 byte packets
1 me.me.32.254 (me.me.32.254) 0.805 ms me.me.32.253 (me.me.32.253) 0.552 ms me.me.32.254 (me.me.32.254) 0.630 ms
2 me.me.0.241 (me.me.0.241) 0.568 ms me.me.0.233 (me.me.0.233) 0.531 ms me.me.0.229 (me.me.0.229) 0.488 ms
3 verisign.telecity4.nl-ix.net (193.239.117.25) 0.935 ms 0.883 ms 0.830 ms
4 xe-2-3-0.r2.bb-fo.lon3.vrsn.net (199.7.62.61) 6.214 ms xe-3-0-0.r1.bb-fo.lon3.vrsn.net (199.7.62.21) 7.339 ms xe-1-2-0.r2.bb-fo.lon3.vrsn.net (199.16.94.173) 7.396 ms
5 xe-5-1-0.r1.bb-fo.nyc3.vrsn.net (199.7.62.44) 81.286 ms xe-4-2-0.r2.bb-fo.nyc3.vrsn.net (199.7.62.59) 80.234 ms 80.289 ms
6 xe-0-2-0.r1.bb-fo.nyc3.vrsn.net (199.16.94.1) 80.029 ms xe-2-1-0.r2.bb-fo.ilg1.vrsn.net (199.7.62.18) 83.186 ms 199.7.62.64 (199.7.62.64) 81.419 ms
7 199.7.62.66 (199.7.62.66) 81.706 ms xe-1-2-0.r1.bb-fo.ilg1.vrsn.net (199.16.94.10) 81.402 ms po1.2010.r1.shared-fo.ilg1.vrsn.net (199.16.95.10) 103.165 ms
8 po1.2010.r1.shared-fo.ilg1.vrsn.net (199.16.95.10) 103.166 ms te1-2.r2.colo-fo.ilg1.vrsn.net (69.58.176.194) 83.119 ms 86.078 ms
9 te1-2.r1.colo-fo.ilg1.vrsn.net (69.58.176.198) 81.467 ms * *
10 * * *
...