Hi Bjoern.
My apologies for the delay in response.
> and no rules specific to ICMP?
The only ICMP-specific rules allow everything through;
[host1] ~# ipfw show | grep icmp
0170035776 3023614 pipe 25 icmp from any to table(1) in via em0
0170135776 3023614 skipto 1999 icmp from a
On Mon, 30 Oct 2006, Khetan Gajjar wrote:
There are no firewall rules that are specific to the IPSec tunnels.
and no rules specific to ICMP?
This, combined with the fact that small data transfer sessions
across the IPSec tunnels work but small ones don't lead me to believe
this could be a PM
Hi George.
Around Today, "[EMAIL PROTECTED]" wrote :
> I'm confused as to why you attribute this to PMTU discovery. Do you
> see ICMP errors indicating that? Have you run traceroutes in both
> directions from each host?
Thanks for your response. I have tried aliased IP's on the machines
whi
On Fri, Oct 27, 2006 at 09:03:35PM +0200, Khetan Gajjar wrote:
> Hi.
Hi.
[]
> racoon does its thing, and the ipsec tunnels come up. I can ping
> both sides, and there are no ipfw rules running. Connectivity via
> ssh and nfs seems to work fine, as do DNS zone transfers (for very
> small zones
Hi Khetan,
I'm confused as to why you attribute this to PMTU discovery. Do you
see ICMP errors indicating that? Have you run traceroutes in both
directions from each host?
Thanks,
George
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.or
Hi.
Summary; searching for this problem revealed another query, but no
solution -
http://lists.freebsd.org/pipermail/freebsd-net/2005-July/007899.html
Explanation;
I'm experiencing a broken path MTU discovery problem between two
hosts connecting with each other via IPSec transport mode, exaspera
