heya, i tried this setup with IPV4 addresses on the same subnet (10.0.3.1 and 10.0.3.2) and it worked fine, i.e. i "tcpdump -i enc0" and see encapsulated packets. this leaves me wondering what it is about my prior setup that made it not work.
i saw no appreciable difference in the outputs from each case (working and not working) aside from the absence of messages like: 164326.277770 Cryp 10 crypto_decrypt: before decryption: 164326.279023 Cryp 10 548cc6fb a5c81656 67dd3c90 72907baf cca756ff 2e182d03 f3d68549 84eb0feb 164326.279774 Cryp 10 27c3abc6 b6db491e b9dbb4c6 2cc566c7 833f8826 309e1fbd 479254b7 ac05df31 164326.286832 Cryp 10 crypto_encrypt: before encryption: 164326.287746 Cryp 10 0800000c 01000000 0a000301 0b000018 50c521ac 5d8677fa daf211c7 b41ac606 164326.288767 Cryp 10 a0436258 0000001c 00000001 01106002 12fda71d b73f6e3c 1e79a24f bdb98bed and 164326.068356 Exch 10 nat_t_exchange_check_nat_d: NAT detected, we're behind it ... 164326.289836 Mesg 10 virtual_send_message: enabling NAT-T encapsulation for this exchange in the not working case. any ideas on why this works in the case i have delineated (from 10.0.3.1 to 10.0.3.2) and doesn't work when i have my endpoints at 10.0.0.2 and 10.0.3.2? does this have something to do with NAT detection? >i'm trying to establish a tunnel between two hosts (both are >pentium IIs running a snapshot from 10/28) the with IPs >10.0.0.2 and 10.0.3.2 and living on my home network with >topology as shown: > >############# ############################ ># 10.0.0.2 #--------# 10.0.0.1 pub IP = Z # >############# # 10.0.3.1 # > ############################ > | > | > ############### > # 10.0.3.2 # > ###############
