Loss connection to some websites

Got a problem with Viscosity or need help? Ask here!

digitalturbulence

Posts: 2
Joined: Sun Jan 10, 2010 5:37 am

Post by digitalturbulence » Sun Jan 10, 2010 5:55 am
Since I upgraded from Viscosity 1.0.4 to 1.0.8 I have serious problems to use it with some sites.
For example http://www.fox.com. I can load a few kilo bytes of the website and then the connection is blocked. If I ping the site I have the same problem.

Example:
Code: Select all
# ping http://www.fox.com
PING a493.na.akamai.net (64.208.186.35): 56 data bytes
64 bytes from 64.208.186.35: icmp_seq=0 ttl=53 time=110.065 ms
64 bytes from 64.208.186.35: icmp_seq=1 ttl=53 time=111.629 ms
64 bytes from 64.208.186.35: icmp_seq=2 ttl=53 time=110.099 ms
64 bytes from 64.208.186.35: icmp_seq=3 ttl=53 time=109.263 ms
64 bytes from 64.208.186.35: icmp_seq=4 ttl=53 time=110.221 ms
64 bytes from 64.208.186.35: icmp_seq=5 ttl=53 time=109.194 ms
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
ping: sendto: No route to host
Request timeout for icmp_seq 10
ping: sendto: Host is down
Request timeout for icmp_seq 11
ping: sendto: Host is down
Request timeout for icmp_seq 12
^C
--- a493.na.akamai.net ping statistics ---
14 packets transmitted, 6 packets received, 57.1% packet loss
round-trip min/avg/max/stddev = 109.194/110.079/111.629/0.803 ms
# dscacheutil -flushcache
# ping http://www.fox.com
PING a493.na.akamai.net (64.208.186.35): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
Request timeout for icmp_seq 0
ping: sendto: Host is down
Request timeout for icmp_seq 1
^C
--- a493.na.akamai.net ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

$ netstat -nr
Routing tables

Internet:
Destination        Gateway            Flags        Refs      Use   Netif Expire
0/1                10.0.0.1           UGSc            1       14    tap0
default            192.168.2.1        UGSc            4        3     en0
default            link#7             UCSI            2        0    tap0
10/24              link#7             UC              3        0    tap0
10.0.0.1           0:ff:7:9e:3a:d4    UHLWI           5        0    tap0   1120
10.0.0.2           22:f8:5b:ec:eb:c8  UHLWI           0        1     lo0
10.0.0.255         ff:ff:ff:ff:ff:ff  UHLWbI          0       12    tap0
64.208.186.35      link#7             UHRLWI          0       11    tap0
69.147.224.162/32  192.168.2.1        UGSc            1        0     en0
127                127.0.0.1          UCS             0        0     lo0
127.0.0.1          127.0.0.1          UH              2    29277     lo0
128.0/1            10.0.0.1           UGSc            2        0    tap0
169.254            link#5             UCS             0        0     en0
169.254.170.186    127.0.0.1          UHS             0        0     lo0
169.254.255.255    ff:ff:ff:ff:ff:ff  UHLWb           3       28    tap0
192.168.2          link#5             UCS             5        0     en0
192.168.2.1        0:16:38:71:2e:e4   UHLWI          12       31     en0   1145
192.168.2.4        127.0.0.1          UHS             1      867     lo0
192.168.2.32       0:1b:63:a8:bb:e2   UHLWI           0       30     en0   1015
192.168.2.255      link#5             UHLWbI          0       25     en0

Internet6:
Destination                             Gateway                         Flags         Netif Expire
::1                                     ::1                             UH              lo0
fe80::%lo0/64                           fe80::1%lo0                     Uc              lo0
fe80::1%lo0                             link#1                          UHL             lo0
fe80::%en0/64                           link#5                          UC              en0
fe80::223:32ff:fe96:f47d%en0            0:23:32:96:f4:7d                UHL             lo0
ff01::/32                               ::1                             Um              lo0
ff02::/32                               ::1                             UmC             lo0
ff02::/32                               link#5                          UmC             en0
The error apears after I see this in the routing table:
64.208.186.35 link#7 UHRLWI 0 11 tap0

I'm not expert with Mac OS X, but what does this mean link#7?
Is this a virtual physical link?

With pinging Google I had the same problem. I saw that there are on server side ARP requests for external networks?!:
19:52:18.866337 arp who-has fx-in-f147.1e100.net tell 169.254.170.186
19:52:19.865728 arp who-has fx-in-f147.1e100.net tell 169.254.170.186
19:52:20.867102 arp who-has fx-in-f147.1e100.net tell 169.254.170.186
19:52:21.866479 arp who-has fx-in-f147.1e100.net tell 169.254.170.186

Why does Linux make ARP requests for external websites outside my local network?
Kernel IP routing table
Code: Select all
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
AAA.BBB.CCC.DDD  0.0.0.0         255.255.255.248 U     0      0        0 eth0
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 tap0
0.0.0.0         AAA.BBB.CCC.XXX  0.0.0.0         UG    100    0        0 eth0
I use Viscosity 1.0.8 and openvpn 2.1.1 on server side. I tested it with two different server with two different ubuntu version (8 and 9).
Could you please help me?
I'm searching for this problem already 2 days.

Best regards,
digitalturbulence

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Jan 11, 2010 5:41 pm
Hi digitalturbulence,

It sounds like you might have DHCP turned on for your TAP connection (when you don't need it). Viscosity 1.0.4 and earlier versions did not support this feature.

Try editing your connection, and un-ticking the "Enable DHCP" checkbox under the General tab. Click Save and try connecting again.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

digitalturbulence

Posts: 2
Joined: Sun Jan 10, 2010 5:37 am

Post by digitalturbulence » Wed Jan 13, 2010 8:29 am
You are right. I disabled DHCP and now it works.
Thanks very much for your help.
3 posts Page 1 of 1