LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 06-28-2011, 06:55 AM   #1
golden_boy615
Member
 
Registered: Dec 2008
Distribution: Ubuntu Fedora
Posts: 445

Rep: Reputation: 18
tinc vpn problem : No response to MTU probes from & Packet looping back to MYSELF


hello
I Installed tinc vpn on ubuntu server wich is my firewall and proxy server too behind NAT ( my adsl modem has static valid IP address) and windows xp in different city witch has not any related valid static IP address . my configuration is as follows:
on my server[UBUNTU]:
Quote:
cat /etc/tinc/vpn/tinc.conf
Device=/dev/net/tun
Name=vpnserver
PrivateKeyFile=/etc/tinc/vpn/rsa_key.priv

cat /etc/tinc/vpn/hosts/vpnserver
Subnet=10.0.0.0/8
Address=7X.X.X.X
-----BEGIN RSA PUBLIC KEY-----
-----END RSA PUBLIC KEY-----

cat /etc/tinc/vpn/hosts/vpnclient
Subnet=10.0.0.0/8

-----BEGIN RSA PUBLIC KEY-----
-----END RSA PUBLIC KEY-----

cat /etc/tinc/vpn/tinc-up
#!/bin/sh
ifconfig $INTERFACE 10.0.0.1 netmask 255.0.0.0
route add -host 10.0.0.10 dev $INTERFACE
route add -net 10.0.0.0 netmask 255.0.0.0 gw 10.0.0.10

on client[WIN XP] :
Quote:
/etc/tinc/cvpn/tinc.conf
ConnectTo=vpnserver
Interface=cvpn
Name=vpnclient

cat /etc/tinc/cvpn/hosts/vpnserver
Subnet=10.0.0.0/8
Address=7X.X.X.X
-----BEGIN RSA PUBLIC KEY-----
-----END RSA PUBLIC KEY-----

cat /etc/tinc/cvpn/hosts/vpnclient
Subnet=10.0.0.0/8

-----BEGIN RSA PUBLIC KEY-----
-----END RSA PUBLIC KEY-----
I have to say that I added tap device with addtap.bat command in windows and configured it with IP address of 10.0.0.10 and mask 255.0.0.0 .
then I started tinc of both side with level 5 debugging and I got some errors and another strange thing was that tap interface on windows started playing with a ball like those times that an interface tries to get IP address from DHCP.
here is the log of ubuntu server:
Quote:

Purging unreachable nodes
Connection from Y.Y.Y.Y port 1963
Sending ID to <unknown> (Y.Y.Y.Y port 1963): 0 vpnserver 17
Sending 22 bytes of metadata to <unknown> (Y.Y.Y.Y port 1963)
Flushing 22 bytes to <unknown> (Y.Y.Y.Y port 1963)
Got ID from <unknown> (Y.Y.Y.Y port 1963): 0 vpnclient 17
Sending METAKEY to vpnclient (Y.Y.Y.Y port 1963): 1 94 64 0 0 561E39B8F4F7341BD9059FFBA10108CE018A78D61DB5E983CDCCD46DBED7CBD788EF15B963B745A4AEBF80E93C797D2CAC82 143AC77B011F85E8678DF5F59C954AF9C25ECBD4C469FE4C7BC351E028B133CBA7CEA2CF674AA0099CFA1951FAB3A69CC742 47A9F2193689EDB9239D169D76142D169240D6640753975034C3E9A6AFB12598FED7D43C551270411656A88F7434987A6A67 2873D47A038C8A2F7170FDB218C2F9C66CE930A08804D253F6017BC65537B6B7837C0EB4E27E1F6166BC3A673BEC31F73091 688B142174A792447F217838EC23681AF7DCB7753F8881614D324B2A8DF4653B038E7BA7083FA3FF0F8361BB513D4097B27A B69F92AD3F75
Sending 525 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Got METAKEY from vpnclient (Y.Y.Y.Y port 1963): 1 94 64 0 0 62AD225868B7F84AE6DDDC1698C9B78BFA86BCA238398CD9A0BB0213A14AA9BCBF3C9E9AA9006F4B1309FD1D368B98B2CF79 C12FBCCA0A42A3748E29FAEA34E3336FD2B4B00A8C44966F4EC8A177F1AB62DA09E35ECA362446A52CAA4E751C5FAA39E5FC 4C35A6D0F7949566C457C038A8D64818835B6B031818C3174467F5D8D8E978550035F5D13DF5A085A212A19FEF2446C09BD7 F2BAF90DAF7CF42E269A42D1EA8B3DAA3CAD3EF60CF1A016B7C5B18A90B02E75BFD8ACC0788CE31CDA5E19B96BCC02A948DB E56ABB3DA0CCD351E9C26D054E0587D53E056A5E4BB43B0F69FB17D1A7DCB3F4E784E96A4AD3065BC33E71F2D72221F3087F 44B6D3410C40
Sending CHALLENGE to vpnclient (Y.Y.Y.Y port 1963): 2 74842D54F836A8705620A2A0BAC422C2BA723F157200941D0E1D1ACA066D3F765D3391CEDEBD3DFBA72EDE9BBD09D396CF10 5FCCF9389D0B754B86566B397310605CAE3EB74ED01429363C1FABEE0BD9AAE677F0AB7F80EFEE9C668708BF5074D69381B1 9EDB5ACC0AEB066BF2470D0CCC1534420D6B118C43DFEEFCFCA3D95E14EB04B24F0D5FE64C2E7C536789CEA62F590C9A9869 C8F0A025BED4D6529D28C04A7379F77E3D1A516B89B637B32590B8B065F960256245784D1555BB45CC88C0C595F8A44A3706 5B4098ECF2F0AFC0991112B2D3352166CC1E134E268D8569FADD19D204C3C21B032F110D20D2C795C2C89AAC3ACACB64821B C6673CCDDB4B
Sending 515 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 1040 bytes to vpnclient (Y.Y.Y.Y port 1963)
Got CHALLENGE from vpnclient (Y.Y.Y.Y port 1963): 2 933AE1A5C5471F9CAC9CFAC281B673152D60D295805AC2CCE4AC0D66FD7219B820D9D9DC3796147ECD182CB1D188FFA74208 926E2F5FD6A19E5F2BF0A38310720C7896A2DA85D8755429770C0BCCF0E4115ED90B23F81E622A788A1377066E57202D488A 4AE41D6CB34DF0B94575F61D781ABBB400B4B5A613F639C90214A6C7431122D6816D438B5E037C7215BF049FE0803C98AA15 5395CC759064A8D7DCB7EE031CEBC8AA2A005C663156EEC454DE976EA4726F16828BE4DC68463CD713F6B947A458FFA71A94 B8CD33E0F8ADAC9298DC9E6A7AE6F536A589AEFE04E915ECD933985FB84F837FCC4D51B1C6E43BEFAF88FFBF432A2A7D2192 559C77142E1A
Sending CHAL_REPLY to vpnclient (Y.Y.Y.Y port 1963): 3 B53FAA1F32CBBE20002FE8C0CA02309BE0A60001
Sending 43 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Got CHAL_REPLY from vpnclient (Y.Y.Y.Y port 1963): 3 D19EA20DB5E3AB7C4CBC3C46FD26BAB2DCC4026B
Sending ACK to vpnclient (Y.Y.Y.Y port 1963): 4 655 579 4
Sending 12 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 55 bytes to vpnclient (Y.Y.Y.Y port 1963)
Got ACK from vpnclient (Y.Y.Y.Y port 1963): 4 655 1282 c
Connection with vpnclient (Y.Y.Y.Y port 1963) activated
Sending ADD_SUBNET to vpnclient (Y.Y.Y.Y port 1963): 10 59713d73 vpnserver 10.0.0.0/8#10
Sending 43 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Sending ADD_EDGE to everyone (BROADCAST): 12 37875ae3 vpnserver vpnclient Y.Y.Y.Y 655 c 930
Sending 58 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Got ADD_EDGE from vpnclient (Y.Y.Y.Y port 1963): 12 2f21 vpnclient vpnserver 85.15.47.133 655 c 930
Forwarding ADD_EDGE from vpnclient (Y.Y.Y.Y port 1963): 12 2f21 vpnclient vpnserver 85.15.47.133 655 c 930
UDP address of vpnclient set to Y.Y.Y.Y port 655
Node vpnclient (Y.Y.Y.Y port 655) became reachable
Flushing 101 bytes to vpnclient (Y.Y.Y.Y port 1963)
Got ANS_KEY from vpnclient (Y.Y.Y.Y port 1963): 16 vpnclient vpnserver 35E9289FF2C4A22A18F9E0671927E0116453AE2320B26B63 91 64 4 0
Sending MTU probe length 64 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1473 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 588 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 751 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 80 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 574 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1390 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1471 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 78 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 119 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1386 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 382 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1032 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 183 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1162 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 704 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1443 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 64 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 529 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1282 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 703 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 988 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1058 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 179 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1270 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 284 to vpnclient (Y.Y.Y.Y port 655)
Sending MTU probe length 1320 to vpnclient (Y.Y.Y.Y port 655)
No response to MTU probes from vpnclient (Y.Y.Y.Y port 655)
Got PING from vpnclient (Y.Y.Y.Y port 1963): 8
Sending PONG to vpnclient (Y.Y.Y.Y port 1963): 9
Sending 2 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 2 bytes to vpnclient (Y.Y.Y.Y port 1963)
Sending PING to vpnclient (Y.Y.Y.Y port 1963): 8
Sending 2 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 2 bytes to vpnclient (Y.Y.Y.Y port 1963)
Got PONG from vpnclient (Y.Y.Y.Y port 1963): 9
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Got PING from vpnclient (Y.Y.Y.Y port 1963): 8
Sending PONG to vpnclient (Y.Y.Y.Y port 1963): 9
Sending 2 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 2 bytes to vpnclient (Y.Y.Y.Y port 1963)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Sending PING to vpnclient (Y.Y.Y.Y port 1963): 8
Sending 2 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 2 bytes to vpnclient (Y.Y.Y.Y port 1963)
Got PONG from vpnclient (Y.Y.Y.Y port 1963): 9
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Got PING from vpnclient (Y.Y.Y.Y port 1963): 8
Sending PONG to vpnclient (Y.Y.Y.Y port 1963): 9
Sending 2 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 2 bytes to vpnclient (Y.Y.Y.Y port 1963)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Packet looping back to vpnserver (MYSELF)!
Sending PING to vpnclient (Y.Y.Y.Y port 1963): 8
Sending 2 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 2 bytes to vpnclient (Y.Y.Y.Y port 1963)
Got PONG from vpnclient (Y.Y.Y.Y port 1963): 9
Got PING from vpnclient (Y.Y.Y.Y port 1963): 8
Sending PONG to vpnclient (Y.Y.Y.Y port 1963): 9
Sending 2 bytes of metadata to vpnclient (Y.Y.Y.Y port 1963)
Flushing 2 bytes to vpnclient (Y.Y.Y.Y port 1963)
Sending PING to vpnclient (Y.Y.Y.Y port 1963): 8



and this is my client log:
Quote:


2011-06-27 16:11:39 tinc.cvpn[2248]: tincd 1.0.15 (Jun 24 2011 15:06:25) starting, debug level 5
2011-06-27 16:11:39 tinc.cvpn[2248]: {7635C2BF-DD5E-4D72-A378-450EBE0D6395} (cvpn) is a Windows tap device
2011-06-27 16:11:39 tinc.cvpn[2248]: Tap reader running
2011-06-27 16:11:39 tinc.cvpn[2248]: Listening on 0.0.0.0 port 655
2011-06-27 16:11:39 tinc.cvpn[2248]: Ready
2011-06-27 16:11:39 tinc.cvpn[2248]: Trying to connect to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:39 tinc.cvpn[2248]: Connected to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:39 tinc.cvpn[2248]: Sending ID to vpnserver (7X.X.X.X port 655): 0 vpnclient 17
2011-06-27 16:11:39 tinc.cvpn[2248]: Sending 12 bytes of metadata to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:39 tinc.cvpn[2248]: Got ID from vpnserver (7X.X.X.X port 655): 0 vpnserver 17
2011-06-27 16:11:39 tinc.cvpn[2248]: Sending METAKEY to vpnserver (7X.X.X.X port 655): 1 94 64 0 0 669E0DAE2B286D8191593D8845331790B8116A58F56C31B2381345A0A3A4EC855547734D7E3D1C07F9B6026CBD4E85B8AD4D A93B6578F2FF9E409CE0E8E278D404D7B2E69E960D296BB9F773CF2F4C13B8EEFCBD716096CA3A8BDCC11D32D388D8A7654B 36657075B0735CDDB9855B6B3D557D8C6CAE4BDC1C90B88E0D91528895BEA7682AEF07B9B2F4D96054AA67765C2B104E1E83 B3BDC803D2E44FCFCB847A844A80F5DA299D26ACCBBF7356A12DE72F5A8CEA6D2B9E07A37DD9BB7B5975989F9EE6B5C5D917 DD198E2E086FAD5E79449063CB0D57FBAACD8A3276C3DC77F0FB80A9285D2E7B55BBBB830BBA11A0707B54F9D2B304233925 800A32648C49
2011-06-27 16:11:39 tinc.cvpn[2248]: Sending 525 bytes of metadata to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:39 tinc.cvpn[2248]: Flushing 537 bytes to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:39 tinc.cvpn[2248]: Got METAKEY from vpnserver (7X.X.X.X port 655): 1 94 64 0 0 03AA6186BB82DEDD4765E66994BB9BA862FFB7AE184151EBF6DA8E4859DFDD19AB234C928CB30CFCBA5DDD824F2DB505D202 328E38BB583BFDDB53C94901A327A023A8C14A8CCB7FED94244B9549CED452175805F65839E7FFB398A2E5175B621549A53D DFE40A1FDEE18991F12B9F040F9448454AAC0ED504DAD6F4BDEBD883DDD896836DF5BD7E57D30060FA34AB0638DADF51208F ABD13661DD3C48052F005FDC9F390FD29D3157CC9F59C6138FFB3DBCE0E362695AEBCB06B90C9B5DB841E65BE1E2510A14DC BED7B89F25B90BC13806F2DE717C400D594F23B2E2105C4C3A81E55D30C4BB39A78FCB837C9D1F14E9D4490646676FB3B041 E69309A52428
2011-06-27 16:11:39 tinc.cvpn[2248]: Sending CHALLENGE to vpnserver (7X.X.X.X port 655): 2 3BD1CA7C2130103B612E419AD9790084B7E0E98E30AB4D422E4CF060252D5153ED98D9AE29F74EB197A569EE73044655837B BF1A3E1D4D4597DE5EA24A8F39E91CAF91F1E8C37B6C0B67DD013FEB7728C47B3A8B4A4C4453061747BFE52BFDEDD796521A 6E500989716577F59DC6C348FEFD987858600E24481EC5E533B5E17A358046F670D53FD49F86DC01881AFDF67BAF7E836CDC 696965E4DC2618BA42CE77B8FD164C8F87F7F6E15C032134A830A27DE5B90EC9EDCB02E2B3B655364A2ECDAE4451935E0800 83479BAA053E7F5F6C15B23B49CABFAD2C83EF2A0C6D32B5F4136D33729F74DE48776E24EE344E869D589DC208C5A1230D72 4483437CC43D
2011-06-27 16:11:39 tinc.cvpn[2248]: Sending 515 bytes of metadata to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:39 tinc.cvpn[2248]: Got CHALLENGE from vpnserver (7X.X.X.X port 655): 2 3ACE4E4E1E5D9994B683A6A8E4059FBA48176A9D69A843E50A35B034E3CFED2B91AE00DA547E4655552092DDE85E2487BAB7 2EB2D46CF0596A2A36912ADEB0DB80AFE476B4014E255323DD36B4237A8C96D96891931822372427E31C3DB8610D62F8ABE7 D4E8092AA95CC43881239EB7F48DF048F61B9EB5C5B22E94658734729A15FE7606A1F81F89E89A7905A22AFD621C8696E689 A3583D9AE2B3F9A3E2992BF59E2EF69EEFD54E2B5E55F1F9B287786BF3C06A1F6D077DD221E0CF6198EF65DD382EC7ADAF07 A077B1478C9ED9C19F836EEC6CFF44EB385CE4BD5BB36017B55A2924A9403AB18C4C38849C94B62425D2C77739985F19BDEA 0428D9EAFC76
2011-06-27 16:11:39 tinc.cvpn[2248]: Sending CHAL_REPLY to vpnserver (7X.X.X.X port 655): 3 95E7D19001A304C14A0BE3333B9C8B63F5905F45
2011-06-27 16:11:39 tinc.cvpn[2248]: Sending 43 bytes of metadata to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:39 tinc.cvpn[2248]: Flushing 558 bytes to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:40 tinc.cvpn[2248]: Got CHAL_REPLY from vpnserver (7X.X.X.X port 655): 3 FD62F90FFAFF2BB1A0BDEC788AC6B40EE8A50DFE
2011-06-27 16:11:40 tinc.cvpn[2248]: Sending ACK to vpnserver (7X.X.X.X port 655): 4 655 516 c
2011-06-27 16:11:40 tinc.cvpn[2248]: Sending 12 bytes of metadata to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:40 tinc.cvpn[2248]: Got ACK from vpnserver (7X.X.X.X port 655): 4 655 316 4
2011-06-27 16:11:40 tinc.cvpn[2248]: Connection with vpnserver (7X.X.X.X port 655) activated
2011-06-27 16:11:40 tinc.cvpn[2248]: Sending ADD_EDGE to everyone (BROADCAST): 12 4620 vpnclient vpnserver 7X.X.X.X 655 c 416
2011-06-27 16:11:40 tinc.cvpn[2248]: Sending 55 bytes of metadata to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:40 tinc.cvpn[2248]: Flushing 67 bytes to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:40 tinc.cvpn[2248]: Got ADD_SUBNET from vpnserver (7X.X.X.X port 655): 10 7d77f418 vpnserver 10.0.0.0/8#10
2011-06-27 16:11:40 tinc.cvpn[2248]: Forwarding ADD_SUBNET from vpnserver (7X.X.X.X port 655): 10 7d77f418 vpnserver 10.0.0.0/8#10
2011-06-27 16:11:40 tinc.cvpn[2248]: Got ADD_EDGE from vpnserver (7X.X.X.X port 655): 12 49b6ebfa vpnserver vpnclient 85.185.20.3 655 c 416
2011-06-27 16:11:40 tinc.cvpn[2248]: Forwarding ADD_EDGE from vpnserver (7X.X.X.X port 655): 12 49b6ebfa vpnserver vpnclient 85.185.20.3 655 c 416
2011-06-27 16:11:40 tinc.cvpn[2248]: UDP address of vpnserver set to 7X.X.X.X port 655
2011-06-27 16:11:40 tinc.cvpn[2248]: Node vpnserver (7X.X.X.X port 655) became reachable
2011-06-27 16:11:40 tinc.cvpn[2248]: Sending ANS_KEY to vpnserver (7X.X.X.X port 655): 16 vpnclient vpnserver D5C9D57B1E022EB8B63ED57F090213FCDD00DE8CD79F80FE 91 64 4 0
2011-06-27 16:11:40 tinc.cvpn[2248]: Sending 86 bytes of metadata to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:40 tinc.cvpn[2248]: Flushing 86 bytes to vpnserver (7X.X.X.X port 655)
2011-06-27 16:11:40 tinc.cvpn[2248]: Writing packet of 42 bytes to Windows tap device
2011-06-27 16:11:40 tinc.cvpn[2248]: Writing packet of 42 bytes to Windows tap device
I can not ping them.
what is wrong I can not find any thing why my client looking for DHCP even if I gave it static IP address of 10.0.0.10.

Thanks for any help.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Mail is looping back alitrix Linux - Server 18 10-19-2008 04:29 AM
Err:-find_response_record: response packet id 32781 received with no matching record sathyguy Linux - Newbie 2 05-07-2008 01:26 AM
Sending ICMP messages of type 3 when packet size exceeds MTU of the interface nmb1081 Linux - Networking 1 04-13-2008 10:14 PM
LXer: Creating a VPN with tinc LXer Syndicated Linux News 0 04-12-2008 01:50 AM
Cisco VPN and MTU captainkrypto Linux - Networking 24 02-14-2005 12:18 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 04:45 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration