[SOLVED]ping and incoming connections not working

gymka · 2011-08-27 12:02:41

Problem: eg.

$ ping google.com
PING google.com (209.85.148.99) 56(84) bytes of data.

no answer so i press ctrl+c, i get:
^C

--- google.com ping statistics ---
56 packets transmitted, 0 received, 100% packet loss, time 54999ms

i can't use any torrent client because it accepts connections only then i start client(tested with deluge and transmission). eg. i start deluge->torrent start upload->later it won't start upload, but it sends to server info, server get that info(i tested in situation there i'm the only seeder and there is only one leecher which is under my control)

thoughts about that: i searched for solution for a long time, i very doubt that is a software issue, i think it's hardware problem(and about hardware i know nothing). why i think so:
possible cause of problem:
1. kernel upgrade to 3.0=with ubuntu live cd same problems, so it can't be it
2. i deleted windows xp, windows writes something to network card or bios?
3. hardware problem
before problems started i not did something big, so problem could cause only these 3 items.

i don't have firewall, there was one but for testing purposes i deleted it.
network card Realtek RTL-8169 Gigabit Ethernet, driver is latest(but tested and older version)
i tested with 2 different ISP's. one connected over lan and another just my phone connected as modem over usb cable. in both cases ping not work and all other network services works ok, i can browse, ftp works, i can download torrent(if torrent download starts with program start, not later), skype works, internet radio works, etc.
question: what to do, to make torrents work as they worked earlier? i have this problem about few weaks, in past 3 years i don't have such problems.

Last edited by gymka (2011-08-29 14:04:29)

fukawi2 · 2011-08-27 12:34:26

See where the packets are going missing:

mtr -i5 google.com

You'll probably have to install mtr with pacman

gymka · 2011-08-27 12:40:42

$ mtr -i5 google.com
Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.15.1                      0.0%     2    0.6   0.7   0.6   0.8   0.2
 2. 84.55.40.129.ip.greitas.lt        0.0%     2    4.3   3.4   2.5   4.3   1.3
 3. 10.10.20.20                       0.0%     2    5.6   7.1   5.6   8.6   2.2
 4. ???

if i simply ping that 10.10.20.20 i get answer...

Last edited by gymka (2011-08-27 12:42:04)

R00KIE · 2011-08-27 14:06:23

You cold also try tcptraceroute as icmp packets are sometimes completely discarded/blocked.

Edit:
Forgot to say, you will probably have to install tcptraceroute and then do as root

tcptraceroute www.google.com 80

Last edited by R00KIE (2011-08-27 14:07:20)

gymka · 2011-08-27 14:33:26

same results:

# tcptraceroute google.com 80
Selected device eth0, address 192.168.15.10, port 48972 for outgoing packets
Tracing the path to google.com (74.125.39.106) on TCP port 80 (http), 30 hops max
 1  192.168.15.1  3.185 ms  0.611 ms  0.551 ms
 2  84.55.40.129.ip.greitas.lt (84.55.40.129)  2.520 ms  2.295 ms  2.099 ms
 3  10.10.20.20  7.932 ms  5.480 ms  6.743 ms
 4  * * *
 5  * * *
 6  * * *
 7  *^C

TontonBizar · 2011-08-27 20:05:21

I suggest to check /etc/resolv.conf. This file contains the nameserver adress if you use dhcp. If not fill it manually.

R00KIE · 2011-08-27 22:34:47

TontonBizar wrote:

I suggest to check /etc/resolv.conf. This file contains the nameserver adress if you use dhcp. If not fill it manually.

Doesn't apply here, dns is working just fine as google.com can be resolved.

Try to ping a site in your country instead of an international site and see if it works.

Also is it just me or someone somewhere (not you gymka) screwed up as 10.10.20.20 or any 10.0.0.0/8 is supposed _not_ to show up on the internet?

It might be interesting to see the output of mtr or tcptraceroute to the arch forum (since you seem to be able to reach it) when you can't reach google. I suspect this might be a temporary problem and it should solve itself (I think I have experienced something similar) but let fukawi2 chime in on this, from what I've seen he knows a whole lot more about network stuff than I do and should be able to at least give you some troubleshooting advice.

On the incoming connection problem, if you have a friend on the same ISP see if you can test it with him first, it might be that your ISP started blocking connections to "uncommon" ports in an attempt to curb p2p usage or maybe for some other reason that only your ISP knows.

gymka · 2011-08-28 05:55:26

I(i mean browser) can reach everything and everythere, but "ping" can't reach sites. Tried ping sites in my country, same result. i get answer from ping only then i ping these sites:
127.0.0.1
and
84.55.46.19(my ISP site for clients)
i can't even ping 192.168.0.1(it's router, so how can i browse if i can't reach router?)
and i can't ping 84.55.46.27(it's my ISP site for public)

# tcptraceroute archlinux.org
Selected device eth0, address 192.168.15.10, port 42318 for outgoing packets
Tracing the path to archlinux.org (66.211.214.131) on TCP port 80 (http), 30 hops max
 1  192.168.15.1  0.940 ms  0.596 ms  0.553 ms
 2  84.55.40.129.ip.greitas.lt (84.55.40.129)  3.047 ms  2.047 ms  2.649 ms
 3  10.10.20.20  5.741 ms  5.935 ms  5.010 ms
 4  * * *
^C

Same problems with different ISP so it's not my ISP problem.

Another thing:

# netstat -lnp|grep deluge
unix  2      [ ACC ]     STREAM     LISTENING     344527 1560/python2        /home/gymka/.config/deluge/ipc/deluge-gtk

as i understand 344527 is port on which app listens, but in application shows that it listens on 51128, then i configured to use only 51128 and restarted deluge

# netstat -lnp|grep deluge
unix  2      [ ACC ]     STREAM     LISTENING     522255 1641/python2        /home/gymka/.config/deluge/ipc/deluge-gtk[/deluge]

transmission atleast shows that port 57781(don't know if it listen it)

# netstat -lnp|grep transmission
tcp        0      0 0.0.0.0:57781           0.0.0.0:*               LISTEN      1833/transmission-g 
tcp        0      0 :::57781                :::*                    LISTEN      1833/transmission-g 
udp        0      0 239.192.152.143:6771    0.0.0.0:*                           1833/transmission-g 
udp        0      0 0.0.0.0:57781           0.0.0.0:*                           1833/transmission-g 
unix  2      [ ACC ]     STREAM     LISTENING     709406 1833/transmission-g /tmp/at-spi2/socket-1833-1804289383

Last edited by gymka (2011-08-28 06:20:12)

fukawi2 · 2011-08-28 08:20:15

TontonBizar wrote:

I suggest to check /etc/resolv.conf. This file contains the nameserver adress if you use dhcp. If not fill it manually.

Totally irrelevent. DNS is working fine.

gymka wrote:

$ mtr -i5 google.com
Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.15.1                      0.0%     2    0.6   0.7   0.6   0.8   0.2
 2. 84.55.40.129.ip.greitas.lt        0.0%     2    4.3   3.4   2.5   4.3   1.3
 3. 10.10.20.20                       0.0%     2    5.6   7.1   5.6   8.6   2.2
 4. ???

if i simply ping that 10.10.20.20 i get answer...

That's weird, I'm not sure of your exact architecture, but I'm guessing...
a) 192.168.15.1 is your modem/router
b) 84.55.40.129.ip.greitas.it is your ISP
c) 10.10.20.20 is something internal at your ISP (some are known to use private address space internally).

Either 10.10.20.20 is sending the packets to the wrong next hop, or the next hop is being a little bitch. Either way, it seems that your ISP is at fault, everything under your control (pc, modem/router) is handling it fine and passing it on.

Last edited by fukawi2 (2011-08-28 08:20:54)

gymka · 2011-08-28 08:51:53

I connect to internet through VPN.
a) 192.168.15.1 is your modem/router //yes it's router but it's not mine, but ISP's. in my house i have antenna so my pc sends everything to router which is in ISP 'house' so it's not mine:)

thisoldman · 2011-08-28 09:23:36

The 10.10.20.20 is a VPN address.

The 10.0.0.0 to 10.255.255.255 (10.0.0.0/8) addresses are not assigned to the public internet. They were set up to be used on private networks. For example, my employer assigns them to machines on our WAN.

TontonBizar · 2011-08-28 09:26:57

Another suggestion just to try to help in seeing things more clearly : could you post the results of ifconfig, the results of route -n.
For the moment i don't see the relation beetween the router 192.168.0.1 or the router 192.168.15.1 you were talking earlier.

Don't feel obliged to do it if you think it's irrelevent, I just try to understand and help.

gymka · 2011-08-28 10:05:46

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:13:D3:17:B9:54  
          inet addr:192.168.15.10  Bcast:192.168.15.255  Mask:255.255.255.0
          inet6 addr: fe80::213:d3ff:fe17:b954/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:773940 errors:0 dropped:0 overruns:0 frame:0
          TX packets:759585 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:462872799 (441.4 Mb)  TX bytes:235223908 (224.3 Mb)
          Interrupt:21 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20632 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20632 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1355389 (1.2 Mb)  TX bytes:1355389 (1.2 Mb)

$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.15.1    0.0.0.0         UG    0      0        0 eth0
192.168.15.0    0.0.0.0         255.255.255.0   U     1      0        0 eth0

Last edited by gymka (2011-08-28 10:06:01)

TontonBizar · 2011-08-28 11:16:53

Thanks for the answer.

Still questions : have you modified files in etc (for example /etc/systcl.conf), and do you experience same problems using another computer (if you have one or if a friend comes with his laptop). If problems occurs with another one, then the problem should be related to the router settings or to your iSP.

For the moment I cannot suggest more...

gymka · 2011-08-28 14:11:34

TontonBizar wrote:

Thanks for the answer.
Still questions : have you modified files in etc (for example /etc/systcl.conf), and do you experience same problems using another computer (if you have one or if a friend comes with his laptop). If problems occurs with another one, then the problem should be related to the router settings or to your iSP.
For the moment I cannot suggest more...

in first post i wrote "with ubuntu live cd same problems" so there is no difference in my settings of archlinux because they don't affect hardware.
thanks to all who tried to help, but questions and possible answers remain same like before creating this topic so i'll try to solve problems by my own:)

Last edited by gymka (2011-08-28 14:13:23)

TontonBizar · 2011-08-28 14:25:49

OK, if you can solve your problem, please let us know. It's good to share knowledge and learn from others.

brebs · 2011-08-28 16:53:16

gymka wrote:

$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.15.1 0.0.0.0 UG 0 0 0 eth0
192.168.15.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0

That is incomplete. You should run:

route add -net 127.0.0.0 netmask 255.0.0.0 dev lo

For route to show:

127.0.0.0 * 255.0.0.0 U 0 0 0 lo

fukawi2 · 2011-08-28 23:50:38

thisoldman wrote:

The 10.10.20.20 is a VPN address.
The 10.0.0.0 to 10.255.255.255 (10.0.0.0/8) addresses are not assigned to the public internet. They were set up to be used on private networks. For example, my employer assigns them to machines on our WAN.

10.x.x.x is part of RFC1918 private address space that are designed for use on private networks, but there is nothing to stop an ISP using it on their internal (but still "public") networks. I have seen plenty who do and it causes all kinds of issues, possibly like this one.

gymka · 2011-08-29 14:04:07

it was ISP fault:)

Arch Linux

#1 2011-08-27 12:02:41

[SOLVED]ping and incoming connections not working

#2 2011-08-27 12:34:26

Re: [SOLVED]ping and incoming connections not working

#3 2011-08-27 12:40:42

Re: [SOLVED]ping and incoming connections not working

#4 2011-08-27 14:06:23

Re: [SOLVED]ping and incoming connections not working

#5 2011-08-27 14:33:26

Re: [SOLVED]ping and incoming connections not working

#6 2011-08-27 20:05:21

Re: [SOLVED]ping and incoming connections not working

#7 2011-08-27 22:34:47

Re: [SOLVED]ping and incoming connections not working

#8 2011-08-28 05:55:26

Re: [SOLVED]ping and incoming connections not working

#9 2011-08-28 08:20:15

Re: [SOLVED]ping and incoming connections not working

#10 2011-08-28 08:51:53

Re: [SOLVED]ping and incoming connections not working

#11 2011-08-28 09:23:36

Re: [SOLVED]ping and incoming connections not working

#12 2011-08-28 09:26:57

Re: [SOLVED]ping and incoming connections not working

#13 2011-08-28 10:05:46

Re: [SOLVED]ping and incoming connections not working

#14 2011-08-28 11:16:53

Re: [SOLVED]ping and incoming connections not working

#15 2011-08-28 14:11:34

Re: [SOLVED]ping and incoming connections not working

#16 2011-08-28 14:25:49

Re: [SOLVED]ping and incoming connections not working

#17 2011-08-28 16:53:16

Re: [SOLVED]ping and incoming connections not working

#18 2011-08-28 23:50:38

Re: [SOLVED]ping and incoming connections not working

#19 2011-08-29 14:04:07

Re: [SOLVED]ping and incoming connections not working

Board footer