From: Steve M Bibayoff <smb23@csufresno.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] GRE tunnel wierdness
Date: Tue, 24 Sep 2002 22:22:47 +0000 [thread overview]
Message-ID: <marc-lartc-103290623509366@msgid-missing> (raw)
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 west, it doesn't go through unless I first ping from
west to east (hoepfully this is understandable the way I'm descibing
it). Here is my setup:
------ ------------ ------------ ------
neta---|east|---|dsl router|--internet---|dsl router|--|west|--netb
------ ------------ ------------ ------
internal infaces on linux boxes eth0 on x.x.x.1neta\x192.168.0.0/24
netb\x192.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
# ip route add 192.168.1.0/24 dev netb
ip rules on west:
# ip tunnel add neta mode gre remote f.g.h.i local a.b.c.e ttl 255
# ip link set neta up arp on
# ip addr add 192.168.1.254/24 dev neta
# ip route add 192.168.0.0/24 dev neta
[east]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
a.b.c.w 0.0.0.0 255.255.255.248 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 netb
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 netb
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 a.b.c.x 0.0.0.0 UG 0 0 0 eth0
[west]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
f.g.h.y 0.0.0.0 255.255.255.248 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 neta
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 neta
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 f.g.h.z 0.0.0.0 UG 0 0 0 eth0
Iptables are the same on both boxes except on east I open allow ports 25
80 443 and specifically block port 1003.
If I'm listening on west at neta when I first try to ping anyone on
netb, nothing is coming though unless I have just pinged from netb to
neta first.
Hopefully this isn't too confusing or long winded.
TIA
Steve
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-09-24 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 22:22 Steve M Bibayoff [this message]
2002-09-24 22:42 ` [LARTC] GRE tunnel wierdness David Lamparter
2002-09-25 16:32 ` Steve M Bibayoff
2002-09-25 16:59 ` David Lamparter
2002-09-25 18:01 ` Steve M Bibayoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103290623509366@msgid-missing \
--to=smb23@csufresno.edu \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.