[Openswan Users] Tunnel up but no communication

[Elias Valea Peri]

Humm, maybe an MTU problem, try reducing mtu at interface level (physical
and/or logical). There's a mtu 'force' parameter in Openswan configuration
but i don't now if only works for KLIPS+2.4 with ipsecx interfaces.
You say 'ping test ok', from end-host to end-host? or host to gw?. Try
using bigger ping sizes, and give us the bigger packet size supported.

Elias

> Hey folks,
>
> Recently I've upgraded an ipsec 2.2.0 to 2.3.1 on an FC2 system. The
> tunnel
> came up just fine, and I could ping both sides. But, for some reason I
> could
> not understand, the communication between the subnets would not occur. I
> use
> an telnet client, and I connect to the server through the ipsec tunnel.
> After the upgrade, the communication stoped working. I could ping the
> other
> side, but when I tried to telnet it, it just hung there... Same thing
> happened when I tried to navigate to it with windows network client.
>
> I could not find an single error in it. No warnings, no failures. With
> tcpdumpt, I could see ESP packages exchange between the two gateways, but
> telnet and network just didn't work. When I downgraded to openswan 2.1.5
> it
> worked just fine. I sucessfully telnet the server and navigated to it with
> windows network client. Same config, same system, just a different version
> of openswan.
>
> Any clues?
>
> Giovani
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.11.1 - Release Date: 02/05/2005
>
> _______________________________________________
> Users mailing list
> Users at openswan.org
> http://lists.openswan.org/mailman/listinfo/users
>