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

[Robin. B]

Hello Anne, hope that everything is good now that you haven't replied to
that last email?

 To all of us, this is a request, has anyone ever setup up a good working
Iodine server on the following OS list, Ubuntu, Fedora, debian etc,
Has anyone ever setup and a good working iodine server with encryption or
interface encryption say like ipsec etc,
anyone ever setup a good working iodine server on a DD-WRT router or any
other gadget of the same kind,
This is my request, why suffer trying to set it up when someone out there
has already take trouble, but kind enough to share every step of what they
did to the member <iodine-users at lists.wpkg.org>, i mean it will make it
easier for everyone to set up the server and appreciate.
Well i hope the admin and my fellow members finds that a big point.
The good thing about that will be, if someone is a newcomer and wants info
its easier to share the same config.
However, i suggest a live config of from a working server, not the author's
config, and whoever is kind enough to share, should make sure that they
don't include there public/global ip but use something else for security
reasons.
Thanks guys.


On Mon, Aug 8, 2011 at 7:54 AM, Robin. B <robin at iteqpro.com> wrote:

> Hi, Anne, you say that when you ping the server on 10.0.0.1 you get a
> reply, and when you connect the client and again try to ping the same ip
> (10.0.0.1)...? now you get me confused when you use the same ip.
> can you change the ip on the iodine server... to something else and see
> what happens
> I mean if you have the linksys with 10.0.0.1 which i consider as the master
> gateway, then i expect you to have another gateway for the iodine server
> which is to either be a dhcp server or just an iodine server.
> try that, how ever it would be wiser if you give us the server's config
> file, but edit the global ip out first before you do that..Otherwise you end
> up a victim of Luzsec or Anonymous.....
>
>
>
> On Sun, Aug 7, 2011 at 12:12 AM, Anne Kootstra <kootstra at hotmail.com>wrote:
>
>> Hi Robin, thanks for replying. In the past couple of days I've done some
>> investigation.
>>
>> As per usual I've started the server part on the DD-WRT router using
>> putty.
>> When ping 10.0.0.1 on the router I get a reply, both in the same session
>> as
>> well as a separate putty session . When I ping 10.0.0.1 on my Windows
>> Vista
>> machine, without the Iodine client running, I get a reply from the ping.
>> When I start the client on the windows machine I'm no longer able to ping
>> 10.0.0.1 anymore.
>>
>> When I start the Iodine client I'm running a command line terminal with
>> administrator privileges, as it will not start otherwise. I see that the
>> network device is initialized and Windows reports it as being in use.
>>
>> While sending a ping I've used smsniff to check if the ping is actually
>> sent
>> across the network device and this application doesn't register it.
>>
>> I'm currently at the end of my own knowledge in the matter. If some
>> specific
>> information is helpful, please let me know and I will share it. So, if you
>> would like to see specific config files, let me know which ones and
>> how/where to obtain them.
>>
>> Kind regards,
>>
>> Anne
>>
>> -----Oorspronkelijk bericht-----
>> Van: Robin. B
>> Verzonden: vrijdag 5 augustus 2011 9:27
>> Aan: Anne Kootstra
>> Onderwerp: Re: [iodine-users] Windows Client: connection succesful, can
>> not
>> ping server.
>>
>> Hi, i could be wrong but i think u need to do some bit of bridging.
>> Maybe if possible first show us the configs and we will see where the
>> problem is.
>>
>> On 8/1/11, Anne Kootstra <kootstra at hotmail.com> wrote:
>> > 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
>> >
>> > _______________________________________________
>> > iodine-users mailing lists
>> > iodine-users at lists.wpkg.org
>> > http://lists.wpkg.org/mailman/listinfo/iodine-users
>> >
>>
>>
>> --
>> **
>> networking . security . linux
>> server support & maintenance
>>
>> +256 712 47 47 14
>> <iteq at iteqguru.com>robin at iteqpro.com
>>
>> _______________________________________________
>> iodine-users mailing lists
>> iodine-users at lists.wpkg.org
>> http://lists.wpkg.org/mailman/listinfo/iodine-users
>>
>
>
>
> --
> **
> networking . security . linux
> server support & maintenance
>
> +256 712 47 47 14
>  <iteq at iteqguru.com>
> robin at iteqpro.com
>
>


-- 
**
networking . security . linux
server support & maintenance

+256 712 47 47 14
<iteq at iteqguru.com>robin at iteqpro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/iodine-users/attachments/20110810/a6cfa811/attachment-0003.html>