[iodine-users] Windows Client: connection succesful, can not ping server.

[Anne Kootstra]

This is not a restricted network, the testing is performed while at home
within my own network. 

In order to test whether closing down the regular network would work I've
removed the default routing (route delete 0.0.0.0) and added one routing
specific for the DNS server (route add DNSERVER 255.255.255.255) and one
general routing to the new network connection (route add 0.0.0.0 MASK
0.0.0.0 10.0.0.2). However, this has not yielded the right result either. 
 
Kind regards,
 
Anne

-----Oorspronkelijk bericht-----
Van: root at kryo.se [mailto:root at kryo.se] Namens Erik Ekman
Verzonden: maandag 1 augustus 2011 10:56
Aan: Anne
CC: iodine-users at lists.wpkg.org
Onderwerp: Re: [iodine-users] Windows Client: connection succesful, can not
ping server.

On Sun, Jul 31, 2011 at 22:49, Anne <anne at aiml.info> wrote:
> Presently I'm running Iodine server on my DD-WRT Linux router and
connecting
> to it using the windows client running on Windows Vista. The connection is
> made successfully, as far as I can tell. However, when I try to ping the
> server (standard closing step in all the tutorials I could find) but sadly
> without the expected result.
>

Is this when you connect over unrestricted network or behind a
paywall? If this is behind paywall, does it work on the open net?
Can you provide tcpdump packet captures from both server and client?

/Erik