Temat: dziwne połączenie do hosta
jest to dość dziwna sprawa. po uruchomieniu kompa od razu startuje wifi i jak tylko sie połączy z siecią mam dwa połączenia wychodzące, jedno np 91.214.237.8 na port 8074 czyli to jest połączenie do GG, a dugi to własnie ten host i port 80 :/
fragment z tcpdumpa
77.252.2.40.www > debian.local.39653: Flags [F.], cksum 0x5379 (correct), seq 4182375618, ack 432993781, win 181, options [nop,nop,TS val 1847522574 ecr 1964033], length 0
10:37:43.079353 IP (tos 0x0, ttl 64, id 57227, offset 0, flags [DF], proto UDP (17), length 70)
debian.local.60704 > netia-dns2.inetia.pl.domain: [udp sum ok] 32488+ PTR? 40.2.252.77.in-addr.arpa. (42)
10:37:43.087098 IP (tos 0x0, ttl 251, id 42448, offset 0, flags [none], proto UDP (17), length 133)
netia-dns2.inetia.pl.domain > debian.local.60704: [no cksum] 32488 NXDomain q: PTR? 40.2.252.77.in-addr.arpa. 0/1/0 ns: 2.252.77.in-addr.arpa. SOA chacha.inetia.pl. hostmaster.inetia.pl. 2010110901 28800 7200 1814400 86400 (105)
10:37:43.117172 IP (tos 0x0, ttl 64, id 658, offset 0, flags [DF], proto TCP (6), length 52)
debian.local.39653 > 77.252.2.40.www: Flags [.], cksum 0x6bf1 (correct), seq 1, ack 1, win 168, options [nop,nop,TS val 2023317 ecr 1847522574], length 0
10:37:43.187523 IP6 (hlim 255, next-header UDP (17) payload length: 50) fe80::21e:65ff:fe7b:91cc.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)? 40.2.252.77.in-addr.arpa. (42)
10:37:43.187600 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 70)
debian.local.mdns > 224.0.0.251.mdns: [udp sum ok] 0 PTR (QM)? 40.2.252.77.in-addr.arpa. (42)
10:37:43.796949 IP (tos 0x0, ttl 64, id 12483, offset 0, flags [DF], proto TCP (6), length 60)
debian.local.37080 > google.sfm.pl.xmpp-client: Flags [S], cksum 0x4c32 (correct), seq 4089703827, win 5840, options [mss 1460,sackOK,TS val 2023487 ecr 0,nop,wscale 7], length 0
10:37:44.189169 IP6 (hlim 255, next-header UDP (17) payload length: 50) fe80::21e:65ff:fe7b:91cc.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)? 40.2.252.77.in-addr.arpa. (42)
10:37:44.189247 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 70)
debian.local.mdns > 224.0.0.251.mdns: [udp sum ok] 0 PTR (QM)? 40.2.252.77.in-addr.arpa. (42)
10:37:45.733862 IP (tos 0x0, ttl 64, id 6594, offset 0, flags [DF], proto TCP (6), length 48)
debian.local.45231 > ip-91-214-237-8.gadu-gadu.pl.8074: Flags [P.], cksum 0x34a3 (correct), seq 2255163157:2255163165, ack 3927900782, win 483, length 8
10:37:45.746891 IP (tos 0x0, ttl 56, id 42814, offset 0, flags [DF], proto TCP (6), length 40)
ip-91-214-237-8.gadu-gadu.pl.8074 > debian.local.45231: Flags [.], cksum 0x3c58 (correct), seq 1, ack 8, win 566, length 0
10:37:46.192137 IP6 (hlim 255, next-header UDP (17) payload length: 50) fe80::21e:65ff:fe7b:91cc.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)? 40.2.252.77.in-addr.arpa. (42)
10:37:46.192215 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 70)
debian.local.mdns > 224.0.0.251.mdns: [udp sum ok] 0 PTR (QM)? 40.2.252.77.in-addr.arpa. (42)
jak dla mnie nic konkretnego