Freesco, NND, CDN, EOS

Jak mam to zinterpretowac i jesli ktos dzieli jak to zablokowac ttl ??? :
ps 80.54.251.2 to moje ip zewnetrzne serwera do ktorego jest lan podlaczony . a to 195.150.92.12 to nie mam pojecia jak puszczam ping spod windowsa to odpowiada !!!!

NATDet 1.0.5 started 23-00-2006 13:23:36
[+] device: "eth0", signatures: 150.
[*] 23-00-2006 13:24:30: NAT at 80.54.251.2 for 4 system(s) [100%]
Used factors: TSTAMP TTL
[*] 23-00-2006 16:09:14: NAT at 195.150.92.12 for 2 system(s) [100%]
Used factors: OSGENRE TSTAMP TTL

_________________
Czy to juz koniec Lanow ...

Masz sieć na eth0
A te IP to z twojej sieci
To chyba przeanalizowało internet a nie twoja sieć
Chyba, że nie rozumiem działanie programu.

_________________
Symetryk światło, CDN2 3.1.4-4-ARCH i686 AMD E-350 Processor AuthenticAMD & kilku użyszkodników

lokalna mam na eth 1 . a net mam na eth 0 , ale jak dalem wartosc any to mi wywalilo dopiero wtedy mase wartosci z netu .

_________________
Czy to juz koniec Lanow ...

Mam dokładnie taki sam problem, dołączam sie do pytania.
Po interfejscie lokalnym wypisuje mi globalne udostepnianie
[root@router rc.d]# natdet -i eth1
NATDet - NAT Detection tool, version 1.0.5
(c) Marcin Ulikowski <elceef@itsec.pl>
[+] device: "eth1", signatures: 150.
[*] 14-00-2007 12:52:43: NAT at 201.141.215.165 for 1 system(s) [100%]
[*] 14-00-2007 12:53:14: NAT at 24.244.133.211 for 1 system(s) [100%]
[*] 14-00-2007 12:53:27: NAT at 190.16.240.215 for 1 system(s) [100%]
[*] 14-00-2007 12:53:35: NAT at 201.215.105.151 for 1 system(s) [100%]
[*] 14-00-2007 12:53:51: NAT at 69.245.178.157 for 1 system(s) [100%]
[*] 14-00-2007 12:53:54: NAT at 217.165.190.165 for 1 system(s) [100%]
[-] caught SIGINT(2) signal, exiting...
[root@router rc.d]# natdet -i eth1 -v -vv
NATDet - NAT Detection tool, version 1.0.5
(c) Marcin Ulikowski <elceef@itsec.pl>
[+] device: "eth1", signatures: 150.
[*] 14-00-2007 12:56:20: NAT at 24.244.133.211 for 1 system(s) [100%]
Used factors: TTL
[#146]["Windows NT", 109, 0 (9sec)] vs ["Windows NT", 110, 0]
[*] 14-00-2007 12:56:29: NAT at 141.213.194.89 for 1 system(s) [100%]
Used factors: TTL
[#54]["Windows NT", 108, 0 (58sec)] vs ["Windows NT", 109, 0]
[*] 14-00-2007 12:56:33: NAT at 217.165.190.165 for 1 system(s) [100%]
Used factors: TTL
[#170]["Windows NT", 114, 0 (12sec)] vs ["Windows NT", 113, 0]
[*] 14-00-2007 12:56:39: NAT at 24.155.29.228 for 1 system(s) [100%]
Used factors: TTL
[#98]["Windows NT", 107, 0 (44sec)] vs ["Windows NT", 108, 0]
[*] 14-00-2007 12:56:39: NAT at 69.114.50.45 for 1 system(s) [100%]
Used factors: TTL
[#139]["Unknown", 110, 0 (1sec)] vs ["Unknown", 111, 0]
[*] 14-00-2007 12:57:11: NAT at 67.167.208.180 for 1 system(s) [100%]
Used factors: TTL
[#117]["Unknown", 107, 0 (64sec)] vs ["Unknown", 108, 0]

[root@router rc.d]# natdet -i eth0 -v -vv
NATDet - NAT Detection tool, version 1.0.5
(c) Marcin Ulikowski <elceef@itsec.pl>
[+] device: "eth0", signatures: 150.
[*] 14-00-2007 12:59:09: NAT at 72.141.203.20 for 1 system(s) [100%]
Used factors: TTL
[#58]["Windows NT", 109, 0 (3sec)] vs ["Windows NT", 110, 0]
[*] 14-00-2007 12:59:18: NAT at 190.55.4.169 for 1 system(s) [100%]
Used factors: TTL
[#108]["Unknown", 30, 0 (2sec)] vs ["Unknown", 31, 0]
[*] 14-00-2007 12:59:19: NAT at 69.245.178.157 for 1 system(s) [100%]
Used factors: TTL
[#113]["Windows NT/9x", 109, 0 (2sec)] vs ["Windows NT/9x", 110, 0]
[*] 14-00-2007 12:59:33: NAT at 24.131.3.171 for 1 system(s) [100%]
Used factors: TTL
[#155]["Windows NT", 111, 0 (2sec)] vs ["Windows NT", 110, 0]
[*] 14-00-2007 12:59:45: NAT at 201.141.215.165 for 1 system(s) [100%]
Used factors: TTL
[#124]["Windows NT", 108, 0 (18sec)] vs ["Windows NT", 107, 0]
[*] 14-00-2007 12:59:46: NAT at 200.126.83.56 for 1 system(s) [100%]
Used factors: TTL
[#162]["Windows NT", 111, 0 (13sec)] vs ["Windows NT", 112, 0]


Brdzo dziwne zachowanie, niestety powtarza sie na 2 serwerze

No i jest odpowiedz na dreczące mnie pytanie a mianowicie:
"
To się zdarza, gdy użytkownicy korzystają z sieci p2p.
Jest to spowodowane faktem, iż NATDet czyta także pakiety przychodzące
z zewnątrz. Najprostszym rozwiązaniem jest zastosowanie odpowiedniej
regułki BPF, która odfiltruje niepotrzebne adresy:
# natdet -i eth1 'src net 192.168.0.0 mask 255.255.255.0'
Zakładam, że Twój intarface ma taki właśnie adres oraz maskę.
"