1 |
>>> `watch` isn't going to help too much unless you're looking at it. Append |
2 |
>>> the |
3 |
>>> output to some log file instead. I chose netstat because its output |
4 |
>>> 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 |
>> |
16 |
>> I'm still getting the blocked outbound requests to port 3680 on my |
17 |
>> firewall and I'm running the above script (changed 993 to 3680) on the |
18 |
>> local system indicated by SRC in the firewall log, but mystery.log |
19 |
>> remains empty. I tested the script with other ports and it seems to |
20 |
>> be working fine. |
21 |
>> |
22 |
>> Also the MAC indicated in the firewall log is 14 blocks long and the |
23 |
>> local system in question has a MAC address 6 blocks long according to |
24 |
>> ifconfig, but the 6 blocks from ifconfig do match 6 of the blocks |
25 |
>> reported by the firewall. |
26 |
>> |
27 |
>> Does this make sense to anyone? |
28 |
>> |
29 |
> |
30 |
> Are you running it as root? If not, you could be missing some connections. |
31 |
|
32 |
I'm running it as root. |
33 |
|
34 |
> I also typed the 't' in netstat out of habit -- that limits the output to |
35 |
> tcp connections. You can remove it to catch the UDP ones. |
36 |
|
37 |
According to the firewall log, the 3680 requests are TCP connections, |
38 |
but I just switched to 'lsof -i' anyway. |
39 |
|
40 |
- Grant |