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

[Anne]

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. 

 

In the server console nothing particular happens, in the client console the
following can be seen:

 

Opening device LAN-verbinding 7

Opened UDP socket

Opened UDP socket

Sending DNS queries for iodine.port0.org to 62.179.104.196

Autodetecting DNS query type (use -T to override).Opened UDP socket

 

Using DNS type NULL queries

Version ok, both using protocol v 0x00000502. You are user #0

Enabling interface 'LAN-verbinding 7'

Setting IP of interface 'LAN-verbinding 7' to 10.0.0.2 (can take a few
seconds)...

 

Server tunnel IP is 10.0.0.1

Skipping raw mode

Using EDNS0 extension

Switching upstream to codec Base128

Server switched upstream to codec Base128

No alternative downstream codec available, using default (Raw)

Switching to lazy mode for low-latency

Server switched to lazy mode

Autoprobing max downstream fragment size... (skip with -m fragsize)

768 ok.. 1152 ok.. ...1344 not ok.. ...1248 not ok.. ...1200 not ok.. .1176
ok.. ...1188 not ok.. wi

ll use 1176-2=1174

Setting downstream fragment size to max 1174...

Connection setup complete, transmitting data.

chroot not available

Got SERVFAIL as reply: server failed or recursion timeout

Hmm, that's 2227172. Your data should still go through...

 

While investigating this issue I've tried a few things, but to no avail. It
seems to me that the routing table is correct, that all traffic for the
10.x.x.x network should be routed over the new network device:
LAN-verbinding 7.

 

IPv4 routetabel

===========================================================================

Actieve routes:

Netwerkadres             Netmasker          Gateway        Interface Metric

          0.0.0.0          0.0.0.0    192.168.154.1  192.168.154.103     25

         10.0.0.0  255.255.255.224         On-link          10.0.0.2    286

         10.0.0.2  255.255.255.255         On-link          10.0.0.2    286

        10.0.0.31  255.255.255.255         On-link          10.0.0.2    286

        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306

        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306

  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306

    192.168.154.0    255.255.255.0         On-link   192.168.154.103    281

  192.168.154.103  255.255.255.255         On-link   192.168.154.103    281

  192.168.154.255  255.255.255.255         On-link   192.168.154.103    281

        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306

        224.0.0.0        240.0.0.0         On-link          10.0.0.2    286

        224.0.0.0        240.0.0.0         On-link   192.168.154.103    281

  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306

  255.255.255.255  255.255.255.255         On-link          10.0.0.2    286

  255.255.255.255  255.255.255.255         On-link   192.168.154.103    281

=========================================================================== 

 

Anybody any ideas what to try or where to look?

 

Kind regards,

 

Anne

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/iodine-users/attachments/20110731/b153813f/attachment-0002.html>