| 1 |
Well I'm not on the expert level when it comes to networking
|
1 |
Well I'm not on the expert level when it comes to networking
|
| 2 |
I can do simple tasks like knowing at least the name of an ip address through DNS lookup but I am not on the level of analyzing arp/tcp dumps or anything of the sort
|
2 |
I can do simple tasks like knowing at least the name of an ip address through DNS lookup but I am not on the level of analyzing arp/tcp dumps or anything of the sort
|
| 3 |
\n
|
3 |
\n
|
| 4 |
Well at least, not just yet and it'll probably take some time for that
|
4 |
Well at least, not just yet and it'll probably take some time for that
|
| 5 |
\n
|
5 |
\n
|
| 6 |
Just wondering if there's some easier way, some clue for me to know whether or not the server/ip being connected to is legitimately ZK. But if that ain't possible for stuff utilizing Amazon Web Services then I guess that's yet another reason for me to hate AWS.
|
6 |
Just wondering if there's some easier way, some clue for me to know whether or not the server/ip being connected to is legitimately ZK. But if that ain't possible for stuff utilizing Amazon Web Services then I guess that's yet another reason for me to hate AWS.
|
| 7 |
\n
|
7 |
\n
|
| 8 |
On a side note, thanks for even going to the point of giving consideration of running out of space due to a pile of dumps
|
8 |
On a side note, thanks for even going to the point of giving consideration of running out of space due to a pile of dumps
|
|
|
9 |
\n
|
|
|
10 |
Chobby tries to connect to 34.194.132.103 HTTPS
|
|
|
11 |
\n
|
|
|
12 |
Doing reverse DNS lookup for 34.194.132.103 shows
|
|
|
13 |
ec2-34-194-132-103.compute-1.amazonaws.com
|
|
|
14 |
\n
|
|
|
15 |
How2Judge
|
Can I have all IPs associated with ZK so I could only allow it to access those certain IPs?