I might be way off here but that packet might be originally requested by the XBox which is why it was able to get to the XBox, (unless you forwarded things to the XBoxes IP.) IPCop should provide NO information to getting to your internal network unless you allow it... of course you IPCop box being compremised is still a possibility. As long as you have the patches for 1.3.0 you should be okay for now. However if you have some time to kill you should probably install 1.4.0 since there have been many improvments done since 1.3.0.
I'm also running 1.3.0 with all the updates in place and things are working great... when I get time I'll be upgrading to 1.4.0 also. On Fri, 08 Oct 2004 15:22:09 -0600, Rob S <[EMAIL PROTECTED]> wrote: > Hello everyone, > > I was looking over the logs for my ipcop box, and noticed that snort > recorded an icmp packet transmission (and its source ip) that was > attempting to get to my room mate's Xp box, probably just a ping. What > i'm wondering about though, is that the ip of the icmp packet wasn't > recorded under the 'firewall hits' log. Does this mean the packet got > through? I'm using v1.3.0, should i just update to the new version and > not worry? > > -Rob. > > _______________________________________________ > clug-talk mailing list > [EMAIL PROTECTED] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
