David Lamparter <david.lamparter@t-online.de> wrote:

> I don't know where this ping effect comes from,
>
> east:
> # ip tunnel add netb mode gre remote a.b.c.e local f.g.h.i ttl 255
> # ip link set netb up
> # ip addr add 192.168.0.254/32 peer 192.168.1.0/24 dev netb
>
> west:
> # ip tunnel add neta mode gre remote f.g.h.i local a.b.c.e ttl 255
> # ip link set neta up
> # ip addr add 192.168.1.254/32 peer 192.168.0.0/24 dev neta
>
> - *Or* another possibility:
> east:
> # ip tunnel add netb mode gre remote a.b.c.e local f.g.h.i ttl 255
> # ip link set netb up
> # ip addr add 192.168.2.1/30 dev netb
> # ip route add 192.168.1.0/24 via 192.168.2.2 dev netb
>
> west:
> # ip tunnel add neta mode gre remote f.g.h.i local a.b.c.e ttl 255
> # ip link set neta up
> # ip addr add 192.168.2.2/30 dev neta
> # ip route add 192.168.0.0/24 via 192.168.2.1 dev neta

Tried both of these, am still seeing this weird ping affect. If no
traffic travels over the tunnel for a while (>5 minutes) I can't get
from .0/24 neta(east) to .1/24 netb(west) till after I send some traffic
from west to east first. Once I do that, everything else works fine.

Is there soemthing, that someone could think of, that I should check?

TIA

Steve