If I've missed something, I apologize, but it seems the simple fix is to ssh into the intermediary server, and from there to telnet to the target server. Correct me if there's some reason this solution won't work.<br>
<br>ipsec tunnels shouldn't change the source or destination of a TELNET packet at all. The original source and destination are still the original source and destination. If you want to change that, you need a proxy server instead.<br>
<br><div class="gmail_quote">On Sun, Dec 25, 2011 at 11:31 PM, Anupam Malhotra <span dir="ltr"><<a href="mailto:anupam.malhotra@u2opiamobile.com">anupam.malhotra@u2opiamobile.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Thomas<br>
<br>
Thanks for the useful insight. In my ipsec.conf file, "left" is indeed set<br>
to my localIP (xl.xl.xl.xl). However, I tried setting that to my public IP<br>
(xp.xp.xp.xp) (keeping all other configurations same). In that case the<br>
tunnel is not coming up. You are right that my peer is not strongswan. Here<br>
is my Ipsec.conf file:<br>
<br>
config setup<br>
charonstart=yes<br>
#nat_traversal = yes<br>
nat_traversal = no<br>
plutostart=yes<br>
plutodebug=all<br>
plutostderrlog =/var/log/pluto.log<br>
<br>
conn %default<br>
keyexchange=ikev1<br>
type=tunnel<br>
auth=esp<br>
authby=psk<br>
auto=start<br>
ikelifetime=28800<br>
left=xl.xl.xl.xl<br>
leftnexthop=%defaultroute<br>
<br>
<br>
conn umb<br>
leftsourceip=xl.xl.xl.xl<br>
leftsubnet=xp.xp.xp.xp/32<br>
right=<Public IP of peer><br>
rightsubnet=<xr.xr.xr.xr>/32<br>
esp=3des-md5<br>
ike=3des-md5-modp1024<br>
pfs=no<br>
<br>
Please suggest.<br>
<div class="im"><br>
Best Regards<br>
Anupam Malhotra<br>
<br>
<br>
-----Original Message-----<br>
</div><div class="im">From: Thomas Egerer [mailto:<a href="mailto:thomas.egerer@secunet.com">thomas.egerer@secunet.com</a>]<br>
Sent: Friday, December 23, 2011 7:13 PM<br>
To: Anupam Malhotra<br>
</div><div class="im">Cc: 'gowrishankar'; <a href="mailto:users@lists.strongswan.org">users@lists.strongswan.org</a><br>
Subject: Re: [strongSwan] Telnet over a tunnel using Local IP (rather than<br>
Public IP)<br>
<br>
</div><div><div></div><div class="h5">On 12/23/2011 11:17 AM, Anupam Malhotra wrote:<br>
> Hi Thomas<br>
><br>
> The IKE_SA-negotiation is not failing. The tunnel is coming up. Only<br>
> issue is that the local IP is being seen at the remote end (rather<br>
> than the public IP).<br>
Your output 'ip x s s' tells me, that your tunnel-endpoint on the local side<br>
of the box running strongswan is your *local* ip-address.<br>
> src <remote IP: xr.xr.xr.xr> dst <local IP:xl.xl.xl.xl> src <local IP:<br>
> xl.xl.xl.xl> <remote IP: xr.xr.xr.xr><br>
<br>
This is only the case if your config tells strongswan to do so. If your peer<br>
only accepts ESP packets from xp.xp.xp.xp then your tunnel-endpoint (left in<br>
ipsec.conf) is supposed to say so. If that tunnel cannot be created you<br>
should consult the log file. Your peer should have the config modified<br>
appropriately.<br>
Let us look at your ipsec.conf, maybe we can figure it out then.<br>
Your peer is no strongswan, I assume?<br>
<br>
Cheers,<br>
Thomas<br>
<br>
<br>
<br>
<br>
<br>
</div></div><div><div></div><div class="h5">_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.strongswan.org">Users@lists.strongswan.org</a><br>
<a href="https://lists.strongswan.org/mailman/listinfo/users" target="_blank">https://lists.strongswan.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>