Advertisement
Guest User

Untitled

a guest
May 10th, 2017
244
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.43 KB | None | 0 0
  1. Password:
  2. Opened /dev/tun0
  3. Opened IPv4 UDP socket
  4. Sending DNS queries for t.duman.me to 8.8.8.8
  5. Autodetecting DNS query type (use -T to override).
  6. Using DNS type NULL queries
  7. Version ok, both using protocol v 0x00000502. You are user #0
  8. Setting IP of tun0 to 172.31.27.1
  9. Adding route 172.31.27.0/27 to 172.31.27.1
  10. add net 172.31.27.0: gateway 172.31.27.1
  11. Setting MTU of tun0 to 1130
  12. Server tunnel IP is 172.31.27.0
  13. Testing raw UDP data to the server (skip with -r)
  14. Server is at 172.31.26.18, trying raw login: ....failed
  15. Retrying EDNS0 support test...
  16. Retrying EDNS0 support test...
  17. Retrying EDNS0 support test...
  18. DNS relay does not support EDNS0 extension
  19. Switching upstream to codec Base128
  20. Server switched upstream to codec Base128
  21. No alternative downstream codec available, using default (Raw)
  22. Switching to lazy mode for low-latency
  23. Server switched to lazy mode
  24. Autoprobing max downstream fragment size... (skip with -m fragsize)
  25. ...768 not ok.. ...384 not ok.. 192 ok.. ...288 not ok.. ...240 not ok.. 216 ok.. 228 ok.. ...234 not ok.. ...231 not ok.. 230 ok.. will use 230-2=228
  26. Setting downstream fragment size to max 228...
  27. Connection setup complete, transmitting data.
  28. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  29. iodine: Hmm, that's 1. Your data should still go through...
  30. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  31. iodine: Hmm, that's 2. Your data should still go through...
  32. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  33. iodine: Hmm, that's 3. Your data should still go through...
  34. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  35. iodine: Hmm, that's 4. Your data should still go through...
  36. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  37. iodine: I think 5 is too many. Setting interval to 1 to hopefully reduce SERVFAILs. But just ignore them if data still comes through. (Use -I1 next time on this network.)
  38. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  39. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  40. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  41. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  42. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  43. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  44. iodine: Got SERVFAIL as reply: server failed or recursion timeout
  45. iodine: Got SERVFAIL as reply: server failed or recursion timeout
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement