1 |
On 01/22/2012 12:54 PM, Grant wrote: |
2 |
>> |
3 |
>> `watch` isn't going to help too much unless you're looking at it. Append the |
4 |
>> output to some log file instead. I chose netstat because its output looked |
5 |
>> easier to parse with a stupid regexp. |
6 |
>> |
7 |
>> while true; do |
8 |
>> netstat -antp | grep ':993 '>> mystery.log; |
9 |
>> sleep 1; |
10 |
>> done; |
11 |
>> |
12 |
>> You'll want to change the port -- I tested to make sure that was really |
13 |
>> logging my Thunderbird connections. |
14 |
> |
15 |
> I'm still getting the blocked outbound requests to port 3680 on my |
16 |
> firewall and I'm running the above script (changed 993 to 3680) on the |
17 |
> local system indicated by SRC in the firewall log, but mystery.log |
18 |
> remains empty. I tested the script with other ports and it seems to |
19 |
> be working fine. |
20 |
> |
21 |
> Also the MAC indicated in the firewall log is 14 blocks long and the |
22 |
> local system in question has a MAC address 6 blocks long according to |
23 |
> ifconfig, but the 6 blocks from ifconfig do match 6 of the blocks |
24 |
> reported by the firewall. |
25 |
> |
26 |
> Does this make sense to anyone? |
27 |
> |
28 |
|
29 |
Are you running it as root? If not, you could be missing some connections. |
30 |
|
31 |
I also typed the 't' in netstat out of habit -- that limits the output |
32 |
to tcp connections. You can remove it to catch the UDP ones. |