David Lamparter [EMAIL PROTECTED] 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
Steve M Bibayoff schrieb:
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
David Lamparter [EMAIL PROTECTED] wrote:
Do you have NAT / mangling / etc. running somewhere? The connection
tracking timeout is 500 s afaik, maybe GRE is NATed on one of your
gateways?
A possible explanation would be that east does SNAT on GRE packets
or
west does DNAT on GRE ... so
I haveing something wierd going on, can't seem to figure why. I have two
private networks (neta netb), being masq'ed behind RH 7.3
machines(east west). I also have iptables running on both machines. I
could ping from west to east anytime with no problem, but when I try to
ping from east to
Hi,
Steve M Bibayoff schrieb:
internal infaces on linux boxes eth0 on x.x.x.1neta=192.168.0.0/24
netb=192.168.1.0/24ip rules on east:
# ip tunnel add netb mode gre remote a.b.c.e local f.g.h.i ttl 255
# ip link set netb up arp on
# ip addr add 192.168.0.254/24 dev netb
